8 messages in net.sourceforge.lists.courier-users[courier-users] Re: Header size excee...
FromSent OnAttachments
uchuMay 29, 2005 4:25 pm 
Sam VarshavchikMay 29, 2005 5:27 pm 
uchuMay 30, 2005 6:51 am 
Alessandro VeselyMay 31, 2005 3:57 am 
Bowie BaileyMay 31, 2005 6:42 am 
uchuMay 31, 2005 11:46 am 
Bowie BaileyMay 31, 2005 12:08 pm 
uchuMay 31, 2005 12:44 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: Header size exceeds policy limit, LOGIC?Actions...
From:uchu (onl@gaiahost.coop)
Date:May 29, 2005 4:25:30 pm
List:net.sourceforge.lists.courier-users

we recently started using Courier in production mode and have had a few users already get the "534 Message header size, or recipient list, exceeds policy limit." error when try to send out even small group emails. The reason I have been able to diagnose so far is that the users are using their address book, which adds some extraneous info into the TO: field other than just the email addresses, with allows it to pass the "bofh : maxrcpts" setting that we use of 99...but causes it to fail on the header size limit.

i've read through the list archive for the responses and saw the one patch available at:

http://sourceforge.net/mailarchive/message.php?msg_id=7102590

That patch references that it relates that the 5000 byte limit relates to the TO: field. Where newer posts like the one below relate that this limit is for any single line within the body that is more than 5000 bytes.

http://sourceforge.net/mailarchive/message.php?msg_id=10839189

So, my questions:

1) What is the logic behind the header size limit of 5000 bytes, since it seems it is not only to protect against too many recipients? Is it some memory reading issue?

2) One posting referred to a 500 byte limit that also generates this error, does anyone know if that was a typo?

http://sourceforge.net/mailarchive/message.php?msg_id=1910957

3) For anyone that has applied the above patch, does it seem to cause any problems with the reliable operation of Courier?

4) I searched through the changelog and couldn't find reference to this being changed, so does anyone if more recent versions of Courier either implement the patch above or allow this setting to be modified via a simple system setting instead of code change.

thanks for any help or tips someone can offer...i'm learning to be confident in reading through the code myself, so maybe i'll be able to diagnose this myself in time...but right now would appreciate it if anyone has easily accessible ideas.

thanks,