I know there's a possibility of using smtpd sasl authenticated header but I
don't really trust in that way...
Oh, because the client might provide a fake one?
On 20.05.21 22:41, ego...@ramattack.net wrote:
Yep. We use dedicated ip addresses for each customer (just for providing a
good service, of course not for allowing outgoing spam) and we do it with
FILTER and the corresponding smtp client instance. So, we were using SASL
auth domain for routing each customer mail properly. A standard header,
could be faked by a MUA or script... so for this purpose, a standard
known header, is not the best idea I assume...
Thanks a lot for your time Wietse. I’ll check the possibility of using a
custom header later removed.
smtpd_sasl_authenticated_header should put the authenticated user to
Received: header which at least spamassassin know when to trust and when not
to.
What is it you want to do when delivering mail from different users?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
LSD will make your ECS screen display 16.7 million colors
