Re: wildcards alias?

On Wed 16/Jul/2025 04:19:50 +0200 Sam Varshavchik wrote:
> JLX2 writes:
> 
>> so I was thinking of something like
>>
>> somestring....key...@mydomain : user
>> ....user...key....eos@mydomain : user
>> user...key[x-z0-9]{min,max}@mydomain : user
>>
>> [...]
>>
>> I don't want that login@mydomain be usable (to prevent user spread login 
info on some web site)


The login name doesn't have to be the From: header field, as long as the mail 
client supports it.


> Be prepared to do some script writing on your own: writing your own 
> authentication module, which will take an arbitrary local address, and map it 
> to a home directory, userid, and groupid. So, take whatever algorithm you want 
> to use and implement it.


Another way is to do aliases as new user records.  Using MySQL backend, for 
example, while the domain part of the address must be one of the served 
domains, the user part can be anything.  As long as the home directory points 
to the same location, messages are delivered there and the user can see them 
after logging in with any alias.  The password can be the same or a different 
one.  Uid/gid must suite the user (in a virtual environment they are fixed.)

Yet another way is to use a catch-all script as a local filter, which can 
decide whether an incoming destination address is someone's alias or not.  The 
only drawback is that the script can only reject by return code; that is, its 
bounce message is always "571 Delivery not authorized, message refused."


Best
Ale
-- 







_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users