Re: Adding a header on incoming mail, unintended consequences?

2022-02-13 Thread Nick Tait
On 14/02/22 15:27, John Levine wrote: It appears that joea- lists said: So, back to my pondering. If I were, via some means, to add "Reply-To: The-right-list" this should solve the problem described above. However my "email foo (as distinct from "email fu" stops well short of knowing what

Re: Adding a header on incoming mail, unintended consequences?

2022-02-13 Thread John Levine
It appears that joea- lists said: >So, back to my pondering. If I were, via some means, to add "Reply-To: >The-right-list" this should solve the problem described above. >However my "email foo (as distinct from "email fu" stops well short of knowing >what this might break upon replying with

Adding a header on incoming mail, unintended consequences?

2022-02-13 Thread joea- lists
I was pondering adding a header item on certain incoming mail. Specifically mail from some lists that do not arrive with an explicit "Reply-To: Some-list". One might ask why? Well certain older email clients (MUA's?) choose to, upon a "reply" to select the address of the person that posted to

Re: Clarify SASL Error Log Msg

2022-02-13 Thread Bill Cole
On 2022-02-13 at 12:00:39 UTC-0500 (Sun, 13 Feb 2022 12:00:39 -0500) is rumored to have said: [...] postfix/smtpd[1940626]: connect from unknown[5.34.207.103] postfix/smtpd[1940626]: warning: unknown[5.34.207.103]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 postfix/smtpd[1940626]:

Re: Clarify SASL Error Log Msg

2022-02-13 Thread Wietse Venema
post...@ptld.com: > Just to clarify, does this error mean they requested SASL login and postfix > told them it wasn't enabled? > I am under the belief SASL logins are disabled on port 25. > (smtpd_sasl_auth_enable = no) > Or does it mean postfix allowed them to provide login details and it

Re: Clarify SASL Error Log Msg

2022-02-13 Thread Viktor Dukhovni
On Sun, Feb 13, 2022 at 11:56:27AM -0500, post...@ptld.com wrote: > Just to clarify, does this error mean they requested SASL login and > postfix told them it wasn't enabled? I am under the belief SASL > logins are disabled on port 25. Are you sure the connection was to port 25? Is submission

Re: Clarify SASL Error Log Msg

2022-02-13 Thread postfix
> On 02-13-2022 11:56 am, post...@ptld.com wrote: > Just to clarify, does this error mean they requested SASL login and postfix > told them it wasn't > enabled? > I am under the belief SASL logins are disabled on port 25. > (smtpd_sasl_auth_enable = > no) > Or does it mean postfix allowed them

Clarify SASL Error Log Msg

2022-02-13 Thread postfix
Just to clarify, does this error mean they requested SASL login and postfix told them it wasn't enabled? I am under the belief SASL logins are disabled on port 25. (smtpd_sasl_auth_enable = no) Or does it mean postfix allowed them to provide login details and it failed because of bad user/pass?

Re: Rewriting @localhost to @$myhostname

2022-02-13 Thread Matus UHLAR - fantomas
michael.osi...@siemens.com: I am currently migrating from a sendmail-based relay to Postfix 3.6.3. Sendmail has the feature to automatically rewrite @localhost to @$myhostname automatically. As far as I have seen Postfix doesn't do this with trivial-rewrite(8) by default nor is a config option