Am 03.03.2014 15:44, schrieb Ralf Hildebrandt: >> The error mesage being one of: >> >> TLS is required, but host %s refused to start TLS: %s >> TLS is required, but was not offered by host %s >> TLS is required, but our TLS engine is unavailable >> %s: TLS is required but unavailable, don't know why >> TLS is required, but unavailable >> Cannot start TLS: handshake failure >> >> If you are concerned about confusing error messages, making the >> soft error hard is obviously not sufficient. You will also need to >> massage the error message text. > > Exactly. Usually the users stop reading at the subject: of the bounce. > I know this to be true, since they keep resending the same mail over > and over again.
that may also be the MUA in case of a iPhone you can reject with whatever status code you like in case of sending without authentication and the device will try to do the same every 5 minutes i had a customer doing this for the same message of *3 months* until the device got stolen where i was able to say day and time from the maillog - don't remember how often i called the person and said he should fix his settings our delete that message on the device
