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 want it even for clients in $mynetworks) and what is the > problem you think making it required will solve?
Peter Tselios replied: > 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. Backscatter is a symptom of another problem. Fix that problem rather than trying to block the symptom. > More important thought is the need to enable access to the MTA from other > networks too, so, I need the SMTP AUTH. How does that affect hosts in $mynetworks? You can have SMTP AUTH turned on but still allow unauthenticated mail from hosts within $mynetworks. -- Larry Stone lston...@stonejongleux.com http://www.stonejongleux.com/ The point it to block spam originating from zombie PCs in my networks. I already allow traffic from $mynetworks but that, unfortunately, includes spam. So, the point is to reduce that emails.
