On Dec 21, 2007 5:13 PM, Theo Van Dinter <[EMAIL PROTECTED]> wrote: > On Fri, Dec 21, 2007 at 04:58:44PM +0100, Michael Grant wrote: > > I'm running 3.2.3. I'm noticing that spamc/spamd fails when it's > > presented large messages containing rather large mime attachments > > It doesn't fail in as much as it doesn't send it to spamd, as per its design. > > > Anyone else seen this? Anyone have a fix? > > man spamd > > It's suggested to not send messages to spamd that are > 250K in size.
Actually, it doesn't say this in the spamd man page at all. However, spamc does have a limit and it states the maximum message size is 256M, not 256K and defaults to 500K. I see one needs to set the -s option to an appropriately larger size to get spamc to work with larger messages. But in any case, milter-spamc does not use spamc to submit to spamd, it talks directly to spamd, thus this limitation in spamc this should not be an issue. These messages are well below 256M. milter-spamc only sends down the first 64K of the message in fact. Furthermore, if spamd is rejecting the message because of message size, it would be really good if it returned an error like "message greater than 256K" or something like that. What it's doing is closing the connection (i.e. no status message at all, just an EOF). Older versions of spamd do not do this, I have 3.1.9 running on another box which does not have this behavior. Both are using the same version of perl: 5.8.8. Michael Grant
