hi,
a quick mail to discuss two features introduced by the snapshot I just
published as the man page bits are not committed yet:
The following three lines:
- add initial support for the senders map feature
- introduce K_MAILADDRMAP lookup service
- senders map feature now support 1:n
introduce a new feature "senders map" which lets you define what FROM is
a user allowed to use at the smtp level:
table sm { gilles = "[email protected],[email protected],@pool.ps" }
listen on [...] senders <sm>
with this, user authenticated as 'gilles' may send as [email protected],
[email protected] or any user @pool.ps
Note that it doesn't do masquerading, the content of the message will be
unaltered, this is ONLY a SMTP LEVEL filter.
Side-note: it is an exhaustive list, a user not part of the list will be
considered as disallowed to send.
This one:
- introduce received-auth option to add authenticated user to Received
header
introduces a new behaviour when using:
listen on [...] received-auth
The Received header prepended by the local server will contain two
additional keywords on the TLS line.
Example without it:
TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO
Example of !auth session with it:
TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO
auth=no
Example of authenticated session with it:
TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO
auth=yes user=gilles
There are other goodies in this snapshot btw ;-p
--
Gilles Chehade
https://www.poolp.org @poolpOrg
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
