![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Your proposal would fix the problem, but end up tossing a large quantity of babies out with the bathwater. The problem is that for the case of a mailing list, you have *4* (at least) things to keep track of:
There are many comercial email servers that require the people sending email with their server to log into the server using a valid username and pass before doing so. I doubt they are losing any valid emails. All it does is to keep unauthorized users from using the server without a valid password. The reason to require that the sender address in the outgoing email matches the email address refrenced in the account is to keep people from sending spam from these email servers and using fraudulant return and/or sender address. I fail to see how this throws out any babies. perhaps I am missing something.
Harald
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.