On 02.03.13 01:48, Gordon Messmer wrote:
>I'm not sure if this is intentional or not, but the error given is
>definitely not descriptive. In submit.C, the getrcpts function loops
>through each header. If any header line is greater than 5000 bytes, or
>if any multi-line header is greater than 100,000 bytes, the function
>will bail out with the error "534 Message header size exceeds policy limit."
>
>However, after processing headers, the message body is read with the
>same read_next_line function, and the 5000 byte limit is applied there
>as well. I've been getting cron output from my rss2email job because
>it's sending a simple message whose body is a block of HTML greater than
>5000 bytes with no newlines. For HTML, that seems pretty normal. I
>don't think this should be treated as an error condition.
>
>I can think of a few different ways to fix this, some more hack-ish than
>others. Is this a limitation by design?
the RFC 5322 clearly says:
Each line of characters MUST be no more than
998 characters, and SHOULD be no more than 78 characters, excluding
the CRLF.
the same applies for former standard RFC2822. so, any line crossing this
limit violates the RFC.
Which courier version do you use. IIRC, Sam did some changes to this message
to be more verbose in the past.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Enter any 12-digit prime number to continue.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
