Just recently setup a new mail server at my ISP and we've run into a
problem and I'm not sure what is causing it.
The system is BSDI 3.1 with sendmail 8.9.3 and procmail-3.11pre7 setup
as the local mailer. We're using the hashed spool (2 levels/tiers) and
everything seemed to work fine in our initial limited testing before
bringing it on line. Once online everything works fine except for a
problem with some mail/attachments. Using 'mailq' we see things like this:
...
SAA17225 4211880 Sun Mar 7 18:58 <diana(_at_)cuppark(_dot_)com>
(Operating system error)
<jcbordi(_at_)rockisland(_dot_)com>
MAA04686 9933545 Mon Mar 8 12:17 <dreamscape(_at_)rockisland(_dot_)com>
(Operating system error)
<victor(_at_)rockisland(_dot_)com>
<deeorcas(_at_)rockisland(_dot_)com>
...
And from the system logs (maillog) we see this:
...
Mar 9 14:01:41 cronus sendmail[734]: SAA17225:
to=<jcbordi(_at_)rockisland(_dot_)com>, delay=1+19:02:43, xdelay=00:01:09,
mailer=local, stat=Operating system error
Mar 9 14:05:14 cronus sendmail[734]: MAA04686:
to=<victor(_at_)rockisland(_dot_)com>,
ctladdr=<dreamscape(_at_)rockisland(_dot_)com> (2793/118), delay=1+01:47:16,
xdelay=00:01:09, mailer=local, stat=Operating system error
Mar 9 14:06:22 cronus sendmail[734]: MAA04686:
to=<deeorcas(_at_)rockisland(_dot_)com>,
ctladdr=<dreamscape(_at_)rockisland(_dot_)com> (2793/118), delay=1+01:48:24,
xdelay=00:01:08, mailer=local, stat=Operating system error
...
Mar 9 14:00:32 cronus procmail[1741]: Out of memory as I tried to allocate
4198448 bytes
Mar 9 14:06:22 cronus procmail[2179]: Out of memory as I tried to allocate
4198457 bytes
...
Here's the entry from 'sendmail.cf' if this helps any:
Mlocal, P=/usr/local/bin/procmail, F=lsDFMAw5:/|@qSPfhn9, S=10/30, R=20/
40,
T=DNS/RFC822/X-Unix,
A=procmail -Y -a $h -d $u
Obviously something is amiss. I setup an '/etc/procmailrc' with a logfile
and 'verbose=on' but nothing showed up in the log to help track this down,
apparently its erroring out before it has a chance to log anything.
Wondering if anybody else has seen or run into this problem before and if
you could provide any information to help me track this down and solve it.
I'm not the greatest BSDI wiz as I just get to play with it once in awhile,
but it almost seems like its running into a resource limit, especially since
it only happens with large messages, either that or its a sendmail/procmail
problem. Appreciate any help and hopefully I can learn something from this,
thanks.
--
If guns cause crime, pencils cause misspelled words !
Mike Hall <mhall(_at_)riverside(_dot_)org>, (MH993) -
http://www.riverside.org
System Administrator (*nix, Perl, CGI hacker, certified OS/2 Specialist)