On Thu, Apr 11, 2002 at 01:06:58PM -0400, Mike Black wrote:
| On further examination it looks like spamc is the culprit.
No it isn't. Read the bug report again.
| Doing and strace shows spamc is blocked on a write...
Of course it is. If milter would do a read() then spamc's write()
wouldn't be blocked. The only thing you could have spamc do about it
is read() lots and lots of data into memory (before it write()s) and
hope that malloc() doesn't fail somewhere along the way. Apart from
fixing milter, you can try and have sendmail itself not even bother
trying to scan large messages. I know that is easy to do with exim,
but I know nothing of configuring sendmail.
HTH,
-D
--
Religion that God our Father accepts as pure and faultless is this: to
look after orphans and widows in their distress and to keep oneself from
being polluted by the world.
James 1:27
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
