Closed (duplicate)
Project:
Mime Mail
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Apr 2009 at 09:25 UTC
Updated:
30 Apr 2010 at 14:13 UTC
Jump to comment: Most recent
Comments
Comment #1
Breakerandi commentedsubscribe, I got the same problem.. I don't know, perhaps its an Mime Mail issue?
Comment #2
rstauss commentedSame problem here but not (only) with Simplenews. I guess its Mime Mail, too, because it happens also with Notify.
Comment #3
sutharsan commentedIf it is a problem with included CSS, it is not Simplenews. Another possibility is too long URL's, please check.
Always test with the latest dev release of simplenews and mime mail.
Moving to Mime Mail as it seems to be CSS related.
Comment #4
miro_dietikerThis might be a problem with one of your involved files like CSS.
But it might also be due to the CSS pseudo-compression in term of being removed.
#448670: Spaces and Line Breaks are removed from CSS definitions
Marking it duplicate since correcting the CSS fixed exactly that for me.
Comment #5
sutharsan commentedNote that '500 Line too long' can also occur when the email contains a very long URL. One solution is to encode the email content using base64_encode() (the flip side is that the email size increases 33%).
Comment #6
Anonymous (not verified) commentedI encountered the same problem with the "Nemesis ESMTP" server used and developed by Schlund & Partner (1&1).
I'm not sure if this is a problem with Mime Mail, with Drupal itself or with PHP but I just wasted two days trying to find out what's wrong. Here are my findings.
When sending long E-Mails in HTML format such as newsletters produced by the Simplenews module, the 1&1 mail servers refuse to accept the mail.
I narrowed it down to a problem with the linebreak format. The problem is that the message body is sent with Linux style linebreaks (LF) and Nemesis ESMTP doesn't seem to support that. It ignores the linebreaks and throws a "500 line limit exceeded" error as the message body obviously contains too many characters per line.
I implemented an alternative mail engine in one of my modules that replaces LF with CRLF before sending the message and that fixed the problem.
The Drupal website that is affected by this problem is running on Windows, using hMail as the MTA of choice. This problem did not occur on a similar Drupal website on a Linux system. It seems the Linux MTA used there automatically replaces LF with CRLF before forwarding the message to the remote server.
I verified this by sending newsletters from both websites to different mail addresses. The mails produced by the Windows system use LF, the mails produced by the Linux system use CRLF. The mails using CRLF pass without problems. The mails using only LF are rejected.
Comment #7
sgabe commented@Chi-Yu: I think what you described here is more like a Drupal core issue, since drupal_wrap_mail() deliberately converts CRLF into LF and IMHO this issue is still a duplicate of #448670: Spaces and Line Breaks are removed from CSS definitions what caused such problems like this one.
Comment #8
Anonymous (not verified) commentedThe issues might be related but they are not the same.
#448670: Spaces and Line Breaks are removed from CSS definitions describes a problem with CSS definitions and content which is in fact longer than the allowed maximum line length.
What I'm describing here is a case where the content is inside this limit but the mail server will still issue the "500 line limit exceeded" error.
You can have a linebreak after every single word. If the message body is long enough, the mail server will still reject the message as it simply doesn't understand LF and treats the message body as a single line.
Please explain how this is a duplicate?
Comment #9
sgabe commented@Chi-Yu: I think you have misunderstood my post: This issue here with number 436474 is a duplicate. What you experience is another one and not related to this one, because this problem was fixed with #448670: Spaces and Line Breaks are removed from CSS definitions. As I mentioned above I think what you described is not even a Mime Mail issue irrespectively of the error message. See my previous post about
drupal_wrap_mail().