On Wed, 2006-08-30 at 16:35 +0200, Josip Rodin wrote: > On Fri, Oct 03, 2003 at 11:22:11PM -0400, Greg Folkert wrote: > > [EMAIL PROTECTED]:~$ maildrop -V2 -m .mailfilter > > maildrop: Timeout quota exceeded. > > [EMAIL PROTECTED]:~$ maildrop -V2 -M .mailfilter > > maildrop: Changing to /home/greg > > maildrop: Timeout quota exceeded. > > [EMAIL PROTECTED]:~$ maildrop -V2 .mailfilter > > maildrop: Timeout quota exceeded. > > [EMAIL PROTECTED]:~$ maildrop -V2 > > maildrop: Timeout quota exceeded. > > I went re-reading old bug reports, and it just struck me - you're getting > the timeout because you aren't passing any data to it. > Pipe something to it, and then test -V something.
I understand this, my bad on it. More in a bit. > > Here is the transport for maildrop run out of EXIM: > > > > maildrop_pipe: > > debug_print = "T: maildrop_pipe for [EMAIL PROTECTED]" > > driver = pipe > > path = "/bin:/usr/bin:/usr/local/bin" > > command = "/usr/bin/maildrop" > > return_path_add > > delivery_date_add > > envelope_to_add > > I also noticed that this transport doesn't have a user definition of > any kind. You can add these options: > > user = $local_part > group = mail > > so that Exim runs maildrop as the user who receives the e-mail. > Otherwise, I'd wager that it would try to deliver mail as the system user > "Debian-exim", which doesn't sound like something you'd want for all users. The entry in the default exim4 config is as follows, as confirmed by Marc Haber and Andreas Metzler: [EMAIL PROTECTED]:transport]$ pwd /etc/exim4/conf.d/transport [EMAIL PROTECTED]:transport]$ cat 30_exim4-config_maildrop_pipe maildrop_pipe: debug_print = "T: maildrop_pipe for [EMAIL PROTECTED]" driver = pipe path = "/bin:/usr/bin:/usr/local/bin" command = "/usr/bin/maildrop -d" return_path_add delivery_date_add envelope_to_add This is one of the transports that are default in the config. One would thing that maildrop and the courier-maildrop packages woudl function the same. That is why I included the information about the other package in the bug report. I gave up on trying to use the "maildrop" package and just used the courier-maildrop package. Just to move on and get things done. It maybe that maildrop and courier-maildrop are not interchangeable... but when they conflict and are seen as equivalents for things, it would be hard pressed to not assume this. If you see fit, you may close this, unless you really want to fix it to work the way it should with exim4 out of the box. Either by adding a commented out part for the "maildrop" package in the default exim transport (/etc/exim4/conf.d/transport/etc/exim4/conf.d/transport) or by changing maildrop to work with the method. Either way, I don't really mean to belittle this issue, just that those are really the only two options that I see existing. Thanks for checking up on the old bugs, I knew it was out there, just drifted to the background. I thank you for work you do. -- greg, [EMAIL PROTECTED] The technology that is Stronger, better, faster: Linux
signature.asc
Description: This is a digitally signed message part
