 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Avoid expansion a...| From | Sent On | Attachments |
|---|---|---|
| Bernd Wurst | Oct 15, 2007 6:34 am | |
| Bernd Wurst | Oct 15, 2007 6:52 am | |
| Gordon Messmer | Oct 17, 2007 3:02 pm | |
| Bernd Wurst | Oct 18, 2007 10:58 am | |
| Gordon Messmer | Oct 18, 2007 9:14 pm | |
| Bernd Wurst | Oct 18, 2007 10:13 pm | |
| Gordon Messmer | Oct 18, 2007 10:37 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [courier-users] Avoid expansion addresses for hosteddomains | Actions... |
|---|---|---|
| From: | Bernd Wurst (ber...@bwurst.org) | |
| Date: | Oct 18, 2007 10:13:07 pm | |
| List: | net.sourceforge.lists.courier-users | |
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 alias@hosteddomain 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 "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.
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 <us...@example.com> is delivered to a local mailbox named | "us...@example.com". | [...] | 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.