Problems with double dots at the beginning of lines about swiftmailer

I forgot to mention: This bug seems to be different from bug #81. This time the above cache suppression code will work even it is put after the message instance code, immediately before initiating the batchSend.

Original creation date: 2009-11-08T23:53:47Z
Original reporter: michael-e

Please delete my second comment if possible, since it is wrong. I tested once again and found that the code must be placed before the message instance (like it has been the case with the old bug).

I am sorry.

Original creation date: 2009-11-08T23:58:10Z
Original reporter: michael-e

I made some more tests. This time, the "double-dot phenomenon" is only in the text part of the emails.

Could it be that the bugfix cared for the html part, but not for the text part?

Original creation date: 2009-11-10T11:17:54Z
Original reporter: michael-e

Bug #113 which is somehow related does occur in text/plain and text/html mails.

Original creation date: 2010-05-17T10:56:06Z
Original reporter: softjury

Please see latest command on #113.

Original creation date: 2010-05-20T23:47:15Z
Original reporter: Chris Corbyn

We need confirmation of the transport Used,

if it's sendmail without the -i flag this can explain the problem.

Original creation date: 2011-03-23T10:18:39Z
Original reporter: xdecock

No, I have been using the SMTP transport.

Original creation date: 2011-03-23T11:37:52Z
Original reporter: michael-e

Can you give the information about the server you're using?

Is it a problem on every mailboxes or just some specific client mailboxes?

Original creation date: 2011-03-23T11:39:46Z
Original reporter: xdecock

I tested it with my own mailboxes (which normally don't show this behaviour). The fact that it does not happen for the first recipient (but for all following) indicates that the problem is not in the mailbox. Obviously Email #1 is different from the others, so it must be SwiftMailer's fault.

Unfortunately I don't have a test setup at the moment.

Original creation date: 2011-03-23T11:46:20Z
Original reporter: michael-e

Ok, definitively a cache problem, i'll check how this can be the problem.

It seems that the dotStuffed version is cached but re-DotStuffed none the
less.

Original creation date: 2011-03-23T11:48:18Z
Original reporter: xdecock

[brettjashford]

i am still experiencing this issue in v5.0.1

Swift_Preferences::getInstance()->setCacheType('null');
seems to have fixed it

[fabpot]

fixed in #401