Hi. Am Freitag, 19. Oktober 2007 schrieb Gordon Messmer: > 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.
Okay. > > 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. Hm, it's not that specific, I think. :) makehosteddomains(8) sais: | If this domain is listed, instead, in /etc/courier/hosteddomains, then the | address <[EMAIL PROTECTED]> is delivered to a local mailbox named | "[EMAIL PROTECTED]". | [...] | Courier's LDAP and MySQL authentication modules will use the full E-mail | address to query the LDAP or MySQL server for the location of the local | mailbox that correspond to the E-mail address. There is not any word about extensions or dashes, but the term "literally" is not in there, you're right. :) > The man page for > dot-courier isn't specific about locals or hosteddomains because it > applies to both. Yes, that's clear. > > 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. Okay... I'll stay at my position that for "webinterface-customers", this must be unintuitive. For me as I know courier's local delivery rules, that is not an issue. :) But if I had only customers like me, I wouldn't need hosteddomains at all, locals and aliases would be my choice. ;-) So my suggestion is that either extensions for hosteddomains should be configurable globally or that a "user-foo goes to alias before rejection"-algorithm should be implemented (configurable). But okay, disabling extension-catchall works for me now and I can live with extension addresses not working at all for now. cu, Bernd -- Wir Deutschen haben einen genetischen Defekt. Wenn wir Licht am Ende des Tunnels sehen, machen wir den Tunnel länger.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- 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
