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 access to the MTA from other networks too, so, I need the SMTP AUTH. ----- Αρχικό μήνυμα ----- Απο: Larry Stone <lston...@stonejongleux.com> Προς: Peter Tselios <s91...@yahoo.gr> Κοιν.: Postfix Users <postfix-users@postfix.org> Στάλθηκε: 4:32 μ.μ. Τετάρτη, 8 Φεβρουαρίου 2012 Θεμα: Re: Implement SMTP Auth in a non-disruptive way? On Wed, 8 Feb 2012, Peter Tselios wrote: > So far I have not implemented SMTP Auth for various reasons (on of them was > the fact that I had no Postfix installed). Anyway, I would like to implement > it, but since I have a relatively large base (>200K emails), I would like to > do it in a non-disruptive way. I was thinking to implement something like a > "bounce" message for each outgoing mail without authentication. That message > will not stop the delivery of the email, but it will, simply, inform > unauthenticated users about the fact that in a few days they will be forced > to do so. When D-day comes, I would like to return to unauthenticated users > a custom DSN, not the build-in error. > > Is there any way to do it? If not, is there any other way to do it? 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 want it even for clients in $mynetworks) and what is the problem you think making it required will solve? -- Larry Stone lston...@stonejongleux.com
