On Thursday, February 26, 2004 at 11:46 Jan Reilink wrote:
[local delivery, catch-all, forwards]
Is this a known issue, is there a solution?
The problem is that you are setting the catchall for example.com to a postmaster address.
As you are probably aware, upon creating a domain with vadddomain, there is one e-mail account which is always created and cannot be deleted with qmailadmin: postmaster.
What you need to be aware of, is that the catch-all only works for e-mail sent to addresses within a domain that are _NOT_ already defined as forwards or regular accounts. Thus, your setup will always fail as the postmaster account is always there.
Yes, but what about: :/var/vpopmail/domains/example.com# cat .qmail-default | /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]
:/var/vpopmail/domains/anotherexample.com# cat .qmail-postmaster &[EMAIL PROTECTED]
Email sent directly to [EMAIL PROTECTED] is nicely forwarded to [EMAIL PROTECTED], but email sent to [EMAIL PROTECTED] (which is caught by the catch-all [EMAIL PROTECTED]) is delivered locally to this Maildir.
In our system, postmaster@ is a normal emailaddress which can be used by the customer.
You could remedy this by setting the catch-all address of example.com to an non-existant address in example2.com, such as [EMAIL PROTECTED]
True, I already knew about this solution but "it doesn't fit in our system", because it involves manually adding and editing dot-qmail files (trust me, you don't want to do this for +20.000 virtual domains :-)
Someone on the qmail mailinglist answerd: <http://marc.theaimsgroup.com/?l=qmail&m=107824934618016&w=2> <q> Update vpopmail to ver. 5.2.2 and it will magically work, I ran into this last weekend. </q>
I'll test with vpopmail ver 5.2.2. when this server goes live on March 13, unfortunaly I can't test it sooner.
Anyway, thanks for your answer.
-- Met vriendelijke groet / Best regards, Jan Reilink, VEVIDA Nederland BV
Postbus 329, 9700 AH GRONINGEN, +31(0)50 - 5492234