[vchkpw] Two patch about qmail-remote logging and smtp auth user verification

2009-12-16 Thread Ismail YENIGUL 
Hello,

As Endersys, we released two patches for qmail.

1) qmail canonicalised recipient logging and more patch:
http://blog.endersys.com/2009/12/qmail-canonicalised-recipient-logging-and-more-patch/

2) qmail from address and SMTP-AUTH username check patch

http://blog.endersys.com/2009/12/qmail-from-address-and-smtp-auth-username-check-patch


Best Regards.

  

--
Ismail YENIGUL
Endersys Ltd.
Proje Yöneticisi / Project Manager

Phone :+90 216-4709423 | Mobile:+90 533 747 36 65
Fax   :+90 216-4709508 | web: http://www.endersys.com.tr
Blog:  http://blog.endersys.com Twitter:  http://www.twitter.com/endersys 
LPI: The #1 Linux Certification for IT Professionals
LPI (Linux Professional Institute) Turkey http://www.lpi-turkey.com

!DSPAM:4b28f46232713096414691!

RE: [vchkpw] Delivery of local message results in Aack,_child_crashed

2009-12-16 Thread Paul H. Giesberts 

Paul H. Giesberts wrote:
> Dear All,
> 
> I have installed the latest qmail-net as per "life with qmail" on a RHES 5.3, 
> then vpopmail-5.4.28, which I upgraded to 5.4.30. (And dovecot 1.2.8)
> 
> I get a "Aack,_child_crashed" upon mail delivery, when I create:  
> home/vpopmail/domains/mydomain.com/firstname.lastname/.qmail 
> 
> with a local delivery instruction in the .qmail file that reads: 
> /home/vpopmail/domains/mydomain.com/firstname.lastname/Maildir/
> 
> If I remove the .qmail file it works fine. If I create a .qmail file with a 
> forward to an external address it works fine. It's when the delivery 
> instruction is local that it fails (./Maildir/ does not work either).
> 
> Can you please help?
> 
> By the way, what I am after is a local delivery PLUS a forward for a user. 
> Also this is NOT yet a production server
> 
> Thanks in advance,
> Paul Giesberts
> 
> 
> 
> 
> 


try this:

go to http://www.mail-archive.com/vchkpw@inter7.com
and search for "aack, child crashed 5.4.30"

++jukka


Hi Jukka,

Thanks for your reply. I have seen that post and tried that fix on 5.4.28 and 
now I have tried it on 5.4.30. Unfortunately it has not cured the problem... 
Any other ideas?

Thanks again Paul.

!DSPAM:4b28a6e232711808316917!