Re: [vchkpw] Maildrop failures with vdelivermail

2005-03-13 Thread Tom Collins
On Mar 13, 2005, at 10:58 AM, Paul Oehler wrote:
To sum up, the problem occurs at seemingly random times (but often),  
when running vdelivermail from the Maildrop filter file.  As Matt  
described, the error as it appears in the qmail-send log looks like:

2005-02-18 21:58:22.285783500 delivery 181: deferral:  
Sorry,_no_mailbox_here_by_that_name._vpopmail_(#5.1.1)/maildrop: 
_error_writing_to_mailbox./

Clearly this should be a bounce aka failure, not a deferral, but  
maildrop determines there is a problem when calling vdelivermail, so  
it returns with exitcode 75 which causes the deferral.

I believe the source of this problem was identifed back in June by  
someone posting to the Maildrop mailing list, although there were no  
responses. See:
http://sourceforge.net/mailarchive/message.php?msg_id=8664909

To sum up again, he says the problem is because vdelivermail exits,  
before it read the pipe completly.  vdelivermail simply checks whether  
the receipient is valid, and if not,
exits at once, causing a SIGPIPE in maildrop.
It should be possible to update vdelivermail to scan through to the end  
of the message before exiting.  It might add some additional overhead,  
but I think that it would avoid the SIGPIPE.

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
You don't need a laptop to troubleshoot high-speed Internet:  
sniffter.com



Re: [vchkpw] Maildrop failures with vdelivermail

2005-03-13 Thread Paul Oehler
To sum up again, he says the problem is because vdelivermail exits, 
before it read the pipe completly.  vdelivermail simply checks whether 
the receipient is valid, and if not,
exits at once, causing a SIGPIPE in maildrop.
It should be possible to update vdelivermail to scan through to the end 
of the message before exiting.  It might add some additional overhead, 
but I think that it would avoid the SIGPIPE.

Tom, thanks for the response.  I made the change to vdelivermail.c, 
recompiled, and the problem does indeed appear to have disappeared.  I don't 
know if there's a specific way to make a patch, but here's a diff of the 
5.4.9 vdelivermail.c against the one w/ my changes:

1027a1028
while((read(0,msgbuf,MSG_BUF_SIZE))0);
1054a1056
while((read(0,msgbuf,MSG_BUF_SIZE))0);
Is this acceptable?
Thanks,
Paul
--
Paul Oehler
NEXCESS.NET Internet Solutions
http://nexcess.net
304 1/2 S. State St.
Ann Arbor, MI  48104
1.866.NEXCESS 



Re: [vchkpw] Maildrop failures with vdelivermail

2005-03-13 Thread Tom Collins
On Mar 13, 2005, at 2:08 PM, Paul Oehler wrote:
Tom, thanks for the response.  I made the change to vdelivermail.c, 
recompiled, and the problem does indeed appear to have disappeared.  I 
don't know if there's a specific way to make a patch, but here's a 
diff of the 5.4.9 vdelivermail.c against the one w/ my changes:

1027a1028
while((read(0,msgbuf,MSG_BUF_SIZE))0);
1054a1056
while((read(0,msgbuf,MSG_BUF_SIZE))0);
Is this acceptable?
A unified diff (diff -u) is better, since it provides context for the 
changes and makes it easier for someone to manually make the change.

I have a mostly re-written vdelivermail in testing right now.  If you 
send me a unified diff, I'll make sure the change gets added.

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
You don't need a laptop to troubleshoot high-speed Internet: 
sniffter.com



Re: [vchkpw] Maildrop failures with vdelivermail

2005-03-13 Thread Paul Oehler
A unified diff (diff -u) is better, since it provides context for the 
changes and makes it easier for someone to manually make the change.
Here's a unified diff against the 5.4.9 version.  Let me know if you need 
anything different.

Paul
--
Paul Oehler
NEXCESS.NET Internet Solutions
http://nexcess.net
304 1/2 S. State St.
Ann Arbor, MI  48104
1.866.NEXCESS 


maildrop-sigpipe.patch
Description: Binary data