Jerry Stuckle <jstuc...@attglobal.net> writes:
> For instance, MUAs typically connect on port 587 (at least that is the
> recommendation), while MTAs always use port 25. Additionally, MUAs
> should always be validated with signon/password, to prevent the server
> from becoming an open relay.
1: You would have to require auth on port 25 just in case a MUA
connects on that port. Since you could reasonably do this
exclusively for connections from authorised clients (i. e. clients
on your LAN), it doesn't seem very useful (unless you need to be
afraid of misbehaving clients on your own LAN).
2: When nothing but authorised clients (like non-misbehaving MUAs on the
LAN) can connect to port 587, how does your MTA become an open relay
by not requiring authentication on port 587?
3: How do you deal with messages not generated by MUAs when you have
blocked your MTA against the LAN through requiring auth?
--
Hallowed are the Debians!
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/878ukshj3r....@yun.yagibdah.de
