[lkml]   [2000]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectWild thangs, was: sendmail fails to deliver mail with attachments in /var/spool/mqueue
Some wild blatherings about sendmail...

- Uses lots of memory to send a big file.
Incorrect. I just verified it with a 10 meg file which became a 14 meg attachment.
Sendmail consumed an additional 5 megs combined while handling the input and output v.s.
an idle daemon. Idle is 1.8M, recv was 4.0M, send was 2.3M, no measure on the remote
side. I sent it via pine to a remote address.

- Requires high load average allowance
Incorrect. Same machine barely spiked a tenth of a point for this load and dropped
back to .05. Only time I adjusted the configured load average allowance was back in my
naive days and we got hit with 80,000 in the queue at one time from multiple spammers.
Part of this test's load came from numerous things running and the mail sending required
spinup of the drive which blocked.

- Can't send large files
Incorrect. I've used sendmail for the last seven years and sometimes sent emails
with attachments totally near 100 megs. I very frequently handle mails through this
queue that are larger than 1M.

- Qmail's time has come v.s. sendmail
I strongly disagree, I'm not the richest person or company so I frequently run most
things on one box. Sendmail handles perfectly fine. If your setup is hitting the sky
with load average or failing to send mails, you have a site setup problem.

- New sendmails have problems talking to old sendmails.
Not since I discovered the problem was ECN and not sendmail.

I noticed in the original email that the system was stuck in D state on the
/sbin/modprobe for 11 nwfs attempts. Did nobody notice this? (load average goes up due
to IO bound procs; D state) I have a lot of options enabled w/ all of my sendmail
setups, and most of them include patches to use SQL for the tables which requires even
more daemons to be active.

In short, sendmail does just fine on linux. If it's not doing just fine, there's static
in the headset. There isn't any TCP/IP issue or we would have heard a whole lot more



"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was

title:Blue Labs Developer
fn:David Ford
 \ /
  Last update: 2005-03-22 12:45    [W:0.026 / U:0.760 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site