Re: Σχετ: Implement SMTP Auth in a non-disruptive way?

Please do not top-post on this list. I wrote: I this is a good spot for the standard response of please don't tell us what your proposed solution is, please tell us what is the problem you are trying to solve. In other words, why do you suddenly need SMTP AUTH (and I'm assuming here you

Σχετ: Σχετ: Implement SMTP Auth in a non-disruptive way?

Please do not top-post on this list. I wrote: I this is a good spot for the standard response of please don't tell us what your proposed solution is, please tell us what is the problem you are trying to solve. In other words, why do you suddenly need SMTP AUTH (and I'm assuming here you

Σχετ: Implement SMTP Auth in a non-disruptive way?

Well, There are a number of reasons. Like for example, stopping emails from non-existed users, or stopping email bombing from zombie PCs.  The majority of emails in the queues of my MTA is backscatter and one of the ways to reduce it is SMTP Auth. More important thought is the need to enable

Σχετ: Implement SMTP Auth in a non-disruptive way?

Well, I believe you meaning: reject_unauthenticated_sender_login_mismatch. I tried that on my test env, but I did not add the permit_sasl_authenticated and I had issues. Now, it's better, thanks! I still need the DSN style message back for those users and I hope to have some ideas. -