-DDASH_EXT to enable the dash_ext patch for extended mail addresses
...Am I wrong in thinking that native qmail-1.03 already has the ability to support email addresses such as [EMAIL PROTECTED] On my old installation I successfully used extension addresses without having to patch the distribution. Thanks in advance for an answer to this.
I pose this question while troubleshooting a problem I'm having with deliveries to a user called 'sancho-spam' on my qmail-ldap server. I believe I have my qmail-ldap configuration correct, and here are some snippets from the output of qmail-showctl:
user-ext delimiter: -. ldapdefaultdotmode: Default dot mode for ldap users is both.
Some information from qmail-ldaplookup on this user:
qmailDotMode: both homeDirectory: /var/vmail/sancho
# ls -lA /var/vmail/sancho -rw-r--r-- 1 vmail vmail 11 Jul 10 00:24 .qmail-spam drwx------ 20 vmail vmail 512 Nov 23 15:15 Maildir
# cat /var/vmail/sancho/.qmail-spam #### Leave this commented out to silently drop mail going #### to [EMAIL PROTECTED]
But attempting to deliver mail to '[EMAIL PROTECTED]' results in the following log entry:
@400000003fc1312c0da143f4 new msg 8064060
@400000003fc1312c0da2ca94 info msg 8064060: bytes 996 from <[EMAIL PROTECTED]> qp 6783 uid 1023
@400000003fc1312c0dce08e4 starting delivery 23: msg 8064060 to local [EMAIL PROTECTED]
@400000003fc1312c0dcf936c status: local 1/10 remote 0/20
@400000003fc1312c0e98ea64 delivery 23: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400000003fc1312c0ebe44e4 status: local 0/10 remote 0/20
@400000003fc1312c0f425964 bounce msg 8064060 qp 13184
@400000003fc1312c0f4bcb5c end msg 8064060
The bounce:
<[EMAIL PROTECTED]>: Sorry, no mailbox here by that name. (#5.1.1)
Why won't these dot-qmail deliveries work?
TIA
DS
