Hi Gordon.

Am Donnerstag, 18. Oktober 2007 schrieb Gordon Messmer:

Yes, but ... no. :)

I want my customers to have a choice:

1. If no catchall ("alias") is present, bernd-foo should be rejected. That's what I wanted in my first message and what I got now. 2. If a catchall is present, I would think that bernd-foo goes to the catchall. But it gets rejected anyway.

I solved the first one by *not* creating a .courier-default in the vmail-user's home ("home of ber...@suessmost.de"). But to enable catchall-addresses at all, I need another vmail-home-directory ("home of ali...@suessmost.de") where a .courier-default resides to accept any mail to the catchall-account. My database tells courier the different home-directory for all accounts starting with "alias@".

It seems like courier first divides the account (opposed to the docs, btw!) in local and domain-part, then splits at every dash in the local part and searches for accounts (.courier-files) with the same algorithm that is used on local delivery accounts.

According to the docs, a useraccount "local@host" is looked up literally and an alias@host acts as a catchall. I did not find anything saying that local-foo@host goed to local@host's ~/.courier-foo.

From the point of view of customers that use virtual mail deliveries, they do not control the presence and content of .courier-files. They only control the presence of accounts available for authdaemon. So the magic-dash-splitting is (IMHO!) weird and unintuitive for hosteddomains. It's great for local accounts, anyway!

Got what I mean? ;-)

cu, Bernd