Thread: [maildropl] preline + Maildrop (1.5, and earlier) + qmail dies with huge mail messages
Brought to you by:
mrsam
From: Chris G. <cg...@ya...> - 2002-11-15 16:16:26
|
I've got a problem. I'm trying to filter GIANT email messages to an imap folder. Up until about 200MB everything worked splendidly. Now my setup (was 1.3.5, now is 1.5) will choke on the mail message, and it'll leave the unfinished mail message in the Maildir/tmp directory. This fills up my drive rather quickly. :) I expect its the "Watchdog Timer" that is causing the problem. I only expect it to get worse as the mail messages get larger. Alternately, it could be preline that doesn't like the large messages. Can I compile Maildrop such that I don't have to use preline anymore? The best thing to do would to have ripmime process the message and avoid the maildir altogether. Would I do something like if (/From:.*whoever@somewhere\.com/) { to "| ripmime -i - -d somedir" } I still think the watchdog timer would have a problem. Any suggestions? __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com |
From: Mike L. <tu...@mi...> - 2002-11-15 17:53:05
|
Chris Gamache (cg...@ya...) wrote this on 11 15, 02 at 11:19:=20 > I've got a problem. I'm trying to filter GIANT email messages to an imap > folder. Up until about 200MB everything worked splendidly. Now my setup (= was > 1.3.5, now is 1.5) will choke on the mail message, and it'll leave the > unfinished mail message in the Maildir/tmp directory. This fills up my dr= ive > rather quickly. :) >=20 > I expect its the "Watchdog Timer" that is causing the problem. I only exp= ect it > to get worse as the mail messages get larger.=20 Even larger than 200M? And on a regular basis? Wow.=20 =20 > Alternately, it could be preline that doesn't like the large messages. Ca= n I > compile Maildrop such that I don't have to use preline anymore? >=20 > The best thing to do would to have ripmime process the message and avoid = the > maildir altogether. Would I do something like I would think the best thing to do would be to not send 200M+ sized emails. :-) Seriously. I know it sounds flippant, but once you get into that size, that's what FTP is for. Even if maildrop could/would handle it, how well does your MUA handle such huge attachments? --=20 PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF Member, LEAF Project <http://leaf.sourceforge.net> AIM: MikeLeone Public Key - <http://www.mike-leone.com/~turgon/turgon-public-key.asc> Registered Linux user# 201348 |
From: Chris G. <cg...@ya...> - 2002-11-15 18:52:04
|
--- Mike Leone <tu...@mi...> wrote: > I would think the best thing to do would be to not send 200M+ sized emails. > :-) Seriously. I know it sounds flippant, but once you get into that size, > that's what FTP is for. I figured as much. FTP requires the intelligence be on the sending end. Right now the intelligence is on the receiving end... The imap folder is readable only by the user to which the file is sent. The files are pgp encrypted before they are emailed. Maildrop runs as the receiving user. Qmail + Maildrop is a great unattended file processing solution. :) > Even if maildrop could/would handle it, how well does your MUA handle such > huge attachments? It doesn't. I snag them from the imap folder and remove the attachments before the MUA can get to it. Now, I have an even bigger problem. As a result of my experimentation I've managed to completly mangle my maildrop config. Maildrop is eating all my rule-less email. I upgraded from 1.3.5 to 1.5.0 and I used --enable-syslog=1 and --enable-keep-fromline=1 at compile time. root@mail:/usr/local/src/maildrop-1.5.0# cat ~user/.qmail #./Maildir/ | /var/qmail/bin/preline /usr/local/bin/maildrop -f root@mail:/usr/local/src/maildrop-1.5.0# Do I _have_ to export a system variable for the default maildir (which would be ~/Maildir) in /etc/maildroprc or ~home/.mailfilter ?? CG __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com |
From: Sam V. <mr...@co...> - 2002-11-15 22:42:08
|
Chris Gamache writes: > --- Mike Leone <tu...@mi...> wrote: > >> I would think the best thing to do would be to not send 200M+ sized emails. >> :-) Seriously. I know it sounds flippant, but once you get into that size, >> that's what FTP is for. > > I figured as much. FTP requires the intelligence be on the sending end. Right > now the intelligence is on the receiving end... The imap folder is readable > only by the user to which the file is sent. The files are pgp encrypted before > they are emailed. Maildrop runs as the receiving user. Qmail + Maildrop is a > great unattended file processing solution. :) You can adjust your maildrop script to check the $SIZE variable, and only feed ripmime mail that's below a comfortable limit. -- Sam |
From: Chris G. <cg...@ya...> - 2002-11-18 14:20:28
|
Saw the $SIZE option in the "Tips and Tricks" ... :) Good suggestion. I tried using ripmime over the weekend: if (/From:.*whatever@somewhere\.com/) { to "| ripmime -i - -d $HOME/tmp" } My harddrive didn't fill up with temp files, but the files that it ripped were incomplete. I guess the watchdog timer stopped the process before it completed. n/p ... we can do a --enable-global-timeout=900 at compile time. Is there a way to selectively disable (or lengthen) the watchdog timer? I know ahead of time which processes should take longer than 5 minutes. That'd be a better way to skin this cat, IMO. Not much of a C programmer, but I did dig a bit. I saw in xconfig.h a GLOBAL_TIMEOUT option... I'm not sure what it would take to override the deafult timeout with an environment variable. I think that the timeout is set at runtime, so it might be too late to set it once maildrop goes romping through filterfiles... CG --- Sam Varshavchik <mr...@co...> wrote: > Chris Gamache writes: > > > --- Mike Leone <tu...@mi...> wrote: > > > >> I would think the best thing to do would be to not send 200M+ sized > emails. > >> :-) Seriously. I know it sounds flippant, but once you get into that size, > >> that's what FTP is for. > > > > I figured as much. FTP requires the intelligence be on the sending end. > Right > > now the intelligence is on the receiving end... The imap folder is readable > > only by the user to which the file is sent. The files are pgp encrypted > before > > they are emailed. Maildrop runs as the receiving user. Qmail + Maildrop is > a > > great unattended file processing solution. :) > > You can adjust your maildrop script to check the $SIZE variable, and only > feed ripmime mail that's below a comfortable limit. > > -- > Sam > > > > ------------------------------------------------------- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > _______________________________________________ > Courier-maildrop mailing list > Cou...@li... > https://lists.sourceforge.net/lists/listinfo/courier-maildrop __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com |