Bernd Wurst wrote: > 2. If a catchall is present, I would think that bernd-foo goes to the > catchall. But it gets rejected anyway.
It's not currently possible to do that. The [EMAIL PROTECTED] only works for users that don't exist. "bernd-foo" is an extension to a user that does exist. > According to the docs, a useraccount "[EMAIL PROTECTED]" is looked up > literally and > an [EMAIL PROTECTED] acts as a catchall. I did not find anything saying that > [EMAIL PROTECTED] goed to [EMAIL PROTECTED]'s ~/.courier-foo. I'm not aware of any documentation that says that hosteddomain addresses are looked up "literally". The man page for courier should only be taken to indicate that mailboxes in hosteddomains are looked up with the domain left on, while local domains are stripped off. The man page for dot-courier isn't specific about locals or hosteddomains because it applies to both. > 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! You may not provide them that access, but that doesn't mean that the capability should be written out of courier. Doing so would make hosteddomains significantly less flexible than locals. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
