>> Check whether the domain account home directory has global read and
>> execute permissions. When receiving mail, courieresmtpd runs as
>> the courier user. If it has read and execute permissions on the
>> home directory it will refuse to accept any mail that does not have
>> a matching .courier-username file.
> > I made all home directories world readable (the .courier files already
> were),
And what about the world execute permissions?
All directory permissions are 755. All file permissions are 644. And mail is still initially accepted for nonexistent .courier-usernames in these domains, which results in the undesirable double bounce.
I'll remain skeptical, and you'll have to prove your assertions by showing some hard evidence, because that's not how Courier works.
sqwebmail.com is a virtual domain on my server.
EHLO default 250-mail.courier-mta.com Ok. 250-STARTTLS 250-XVERP=Courier 250-XEXDATA 250-XSECURITY=NONE,STARTTLS 250-PIPELINING 250-8BITMIME 250-SIZE 250 DSN MAIL FROM:<> 250 Ok. RCPT TO:<[EMAIL PROTECTED]> 250 Ok. RCPT TO:<[EMAIL PROTECTED]> 550 User unknown.
You either have:
1) A .courier-default file, which accepts all addresses and reject deliveries as a result of internal processing.
2) The parent directory, or the parent directory's parent directory does not have the required permissions for the esmtp server to check whether the correct .courier file exists.
pgp00000.pgp
Description: PGP signature
