Hi Matus, Sorry for the relay answering. I need to receive authenticated email in Postfix. Later send it to to Amavis and in the returning from Amavis instance, I need to use different smtp clients of Postfix for each customer.
If I do that without Amavis, in the first smtpd with sasl I can know which customer is connecting. If don’t have SASL, becomes dificult to know which customer has send each mail (because I don’t have something like an authenticated User and that can be known vía policy parameters). Finally, I will obviously do all checks for having a sellar set up env. By the way, I’m thinking (and checking) a new possibility. I’m going to try to modify Postfix source code, for being able to have available the message-id of each email between the policy params, although I know it can only be available at the END-OF-DATA stage of the policy.m Best regards, Egoitz, > El 21 may 2021, a las 15:19, Matus UHLAR - fantomas <[email protected]> > escribió: > > ATENCION > ATENCION > ATENCION!!! Este correo se ha enviado desde fuera de la organizacion. No > pinche en los enlaces ni abra los adjuntos a no ser que reconozca el > remitente y sepa que el contenido es seguro. > >> On 21.05.21 14:43, [email protected] wrote: >> I don't need Spamassassin to trust wether a mail comes from >> authenticated source or not. > > I provided an example of how to find out the authenticated user by using > existing solution, e.g. smtpd_sasl_auth_enable=yes. > >> I needed to know which one, is the authenticated user has sent an email >> in the smtpd instance returning from Amavis for being able to give that >> mail an action with a poilcy. > > I know this - you have already explained what you want to know. > > But you haven't answered my question, which is: what exactly you need it > for? > > Maybe we'd have better tip for you. > >> By the way, I would say that the fact of entering a very known header in >> an email as you know, is absolutely simple so I think it's not perhaps >> the best idea to trust only in that header. But I think Wietse put me in >> the correct way and now I think I have a good idea :) > > I wonder that you are willing to accept random header that can be faked by > sending client, instead of using header that can be trusted. > > ...are you sure you will only match the first header in the mail? > > maybe you could use STRIP, IGNORE or REPLACE instead of PREPEND, or use both > STRIP/IGNORE in header_checks and PREPEND in policy filter, which makes sure > the header you use will be deleted from input stream. > > but still explaining what you want could lead to better solution for your > problem. > -- > Matus UHLAR - fantomas, [email protected] ; 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. > Boost your system's speed by 500% - DEL C:\WINDOWS\*.*
