See bug 556267. We should: - Note that in the config file, e.g. as <authentication>client-IP-address</> (Supported by TB 3.1, but then we don't do any auth, don't send password.) or <authentication>password-cleartext</> <restriction>client-IP-address</> - In the client, somehow react to it. E.g. warn the user, or automatically select the global preferred server (if existing) instead of this one.
SHouldn't this be evangelism as I believe most of these smtp servers are open on port 25. We should push ISPs to migrate to startssl/ssl on 587 open from both inside and outside - as this would also reduce the volume of spam sent from such servers.
> Shouldn't this be evangelism It is: "See bug 556267" But what do we do in the meantime and for those ISP who refuse to react? Granted, this may be WONTFIX.
You need to log in before you can comment on or make changes to this bug.