Relationship Graph View Issue Dependency Graph
related to child of duplicate of

View Issue Details

IDProjectCategoryView StatusLast Update
0018485phpList 3 applicationEmailpublic28-01-17 14:24
Reportersuela 
PrioritynormalSeveritymajorReproducibilityalways
Status assignedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0018485: Equal signs "=" included in content and footer of campaign messages sent to OUTLOOK
DescriptionEqual signs "=" included in both content and footer of campaign messages sent to OUTLOOK
-Equal signs included also in the link of "powered by phpList" logo so the redirect does not work
-The link of "powered by phpList" logo is revealed when email opened in browser, not revealed on Thunderbird or mobileApp (screenshots included)
TagsNo tags attached.

Activities

suela

14-01-17 01:33

administrator  

suela

14-01-17 01:36

administrator  

suela

14-01-17 01:37

administrator  

duncanc

14-01-17 12:40

updater   ~0058621

This problem can usually be remedied by using a different encoding to quoted-printable, such as 8 bit. There are a number of topics in the support forum about this problem.

The underlying problem might be caused by using long lines (> about 1000 characters) in the html. If the line length can be kept shorter than that then using quoted-printable may well work. See https://github.com/PHPMailer/PHPMailer/issues/606

michiel

15-01-17 12:05

manager   ~0058629


In order to fix this, I'd need

1. access to the (an) outlook mailbox
2. access to the system where you sent it from (or steps to replicate)

samtuke

16-01-17 12:00

administrator   ~0058631

Michiel: outlook and phpList server login details sent to you.

suela

17-01-17 00:16

administrator   ~0058638

The extra "=" signs appears in the subscribtion confirmation links too makeing the links nonfunctional.

michiel

18-01-17 22:52

manager   ~0058648

yes, the = signs indicate quoted-printable.

It must be something else though. I tried to replicate it but haven't managed yet. Will continue to investigate.

michiel

19-01-17 23:35

manager   ~0058652


I've been sending mails from my test system without htis issue. Can you upload the config file for the affected installation?

then i'll copy the settings, and see if it still happens.

samtuke

20-01-17 11:10

administrator  

tf-config.php (4,404 bytes)

samtuke

20-01-17 11:12

administrator   ~0058655

Config file attached. I believe the version is 3.3-RC2. Could the issue be related to the fact that the code is from GitHub (not Sourceforge)?

samtuke

20-01-17 11:13

administrator   ~0058656

FYI: we tested with and without click tracking enabled and the results were the same.

samtuke

20-01-17 15:23

administrator   ~0058657

I have found a report apparently relating to this issue from November 19th last year, from a phpList Hosted user:

> comment=I have found a bug in your newest release.
>
> When requesting a password reset, the link in the email is incorrect. It has an = symbol in the name of the website, plus another = symbol in the numbers at the end of the link, making the link invalid.
>
> Removing the extra = signs opens the correct password reset page.

michiel

22-01-17 23:30

manager   ~0058659


I can't find it. It may be related to the MTA. I don't think phpList is doing this. Can you try sending via a different relay, eg Gmail? All my test mails come out fine, even when using a similar config to yours.

samtuke

23-01-17 12:43

administrator  

tmp.md (28,137 bytes)

samtuke

23-01-17 12:43

administrator   ~0058662

Attached email source of an affected email

duncanc

23-01-17 17:53

updater   ~0058663

Last edited: 23-01-17 17:56

View 2 revisions

What seems to be happening is the soft linebreaks added by the quoted-printable encoding are themselves being encoded. That process splits each line after I think 75 characters. Those additional new lines are preceeded by =, so that they can be removed when decoding.

Sending an email to my own Outlook address then comparing a small part of the result. This is my result that displays properly

      

To forward this message, please do not use the forward button of y=
our email application, because this message was made specifically for you o=
nly. Instead use the <a href=3D"https://www.dcameron.me.uk/lists/lt.php?id=
=3Df0sJDAkZC1tURQoP">forward page</a> in our newsletter system.


whereas Sam's attached email has this

      

To forward this message, please do not use the forward button of y=
=3D=0A=
our email application, because this message was made specifically for you o=
=3D=0A=
nly. Instead use the <a href=3D"http://thinkingfree.org/lists/?p=3Dforward&=
amp;=3D=0A=
amp;uid=3D1980916659a8062f13364388c897b5f7&mid=3D23">forward page</a> i=
=3D=0A=
n our newsletter system.
=0D

The significant difference to me is that Sam's email has lots of =0D sequences, suggesting that the source has mixed line endings, such as some lines ending in CR, others in LF. Can you confirm whether that is the case Sam?

I forgot that Mantis manges html, so I have added a screenshot

duncanc

23-01-17 17:57

updater  

samtuke

24-01-17 12:44

administrator   ~0058668

Hi Duncan,

> The significant difference to me is that Sam's email has lots of =0D sequences, suggesting that the source has mixed line endings, such as some lines ending in CR, others in LF. Can you confirm whether that is the case Sam?

The source of the message looks standard (using CKEditor, no unusual characters when viewing message source, just HTML tags). There is one error in the campaign content (as opposed to footer etc.) in this message, which is the addition of '=' between the words "some" and "campaign".

Retrieving the campaign content from the database directly, I see no errors, just the text:

Testing some campaign content



And some text that goes



over multiple lines



I'm unsure of the line endings without further investigation using dos2unix or similar.

samtuke

24-01-17 12:47

administrator   ~0058669

Changing HTML email encoding in phpList's config file (https://resources.phplist.com/system/config/htmlemail_encoding) as Duncan suggested appears to have remedied the issue.

However this raises the question of why this issue could not be replicated when HTML email encoding was not explicitly set on other test machines. The line length explanation could explain it.

Could it be the database encoding configuration that is causing the issue?

duncanc

25-01-17 09:18

updater   ~0058671

Last edited: 25-01-17 09:42

View 3 revisions

Can you revert to the original quoted-printable encoding and send a test email with smtp debug enabled. That should show whether the =0D sequences are coming from phplist/phpmailer.
Add or change this line in the config file

define('PHPMAILER_SMTP_DEBUG', 2);

Also the email in the tmp.md file has two meta tags, the second of which appears to have been corrupted. Can you remove the second one just to exclude that as a possible cause?

Update - just noticed from the config file you attached that it is sending through php not using smtp, so that debug setting doesn't apply.

samtuke

27-01-17 16:13

administrator   ~0058682

On the test server used no SMTP server is configured as far as I'm aware.

How should the meta tag be removed?

duncanc

27-01-17 17:54

updater   ~0058684

I guess that you are using a template for that message, so that should contain the html elements. If you don't use a template then I think phplist has some boilerplate html that wraps the message content but I don't think that has two meta tags.