Jean-Christophe Boggio writes:
Ok, I think I clearly see my mistakes.
I wonder if I can have the following behaviour :
- I have some real accounts on thefreecat.org and I want them delivered
normally.
- I want unknown accounts for thefreecat.org delivered to a catchall. This
way, when I r
Ok, I think I clearly see my mistakes.
I wonder if I can have the following behaviour :
- I have some real accounts on thefreecat.org and I want them delivered
normally.
- I want unknown accounts for thefreecat.org delivered to a catchall. This
way, when I register myself on, say, toyota.com
Jean-Christophe Boggio writes:
Correct. Does this affect what users courier sees ? IOW, in which
cases does courier answer "User xxx unknown" (regarding the presence of
the .courier-default file) ?
Never. Because the presence of .courier-default specifies that any local
address will be accep
Thanks for you answer Sam,
Sam Varshavchik wrote :
> Correct. Virtual domain aliases are processed first.
Would be good to have this info in
http://www.courier-mta.org/makealiases.html
>> - why don't the "@domain.com: user" aliases work as I expect ?
> You probably have a .courier-default file i
Jean-Christophe Boggio writes:
So, for the domains who want a catchall, I have a "@domain.com: user" line in
my aliases.
But I keep getting "550 User xxx unknown" (I have run makealiases with no
error
several times)
domain.com is in my /etc/courier/locals
saka.domain.com is the name of the s
Hello,
There are a few things I don't understand with the way aliases work :
I serve several domains and want different behaviours for them :
- some want a catchall
- some don't (so I can't use the /etc/courier/aliasdir/.courier-default trick)
I WANT the "550 User xxx unknown" for these domain
