Originally Posted by
Funkstar
And how on earth would the client have any effect on a forum.
Originally Posted by
peterb
It is still badly worded - the message implies that it is the mail client that is at fault. Perhaps the authentication e mail bounced at some point in the delivery chain. If that is the case, the message is pointless as it points the user in the wrong direction.
Agreed, but to address Funkstar's comment above, it is perfectly conceivable for an email server to reject mail from mis-configured email clients. My own email server frequently takes exception to mail from mis-configured Outlook and Outlook Express clients that have been mis-configured and don't HELO with a FQDN hostname as required by the RFC specifications. In fact, checking my logs shows that about 30% of all incoming mail to my server (~1000 messages per day) is rejected on this basis so I would say that mis-configured email clients are far more common than one might at first suspect. It's useful to drop mail from such mis-configured email clients as most are spambots, not genuine/legitimate mail clients, but it does happen.
For example, here's one from earlier today in my logs trying to HELO with my own server's IP address:
Code:
Mar 24 02:17:54 jessie postfix/smtpd[9502]: connect from unknown[193.200.50.2]
Mar 24 02:17:54 jessie postfix/smtpd[9502]: NOQUEUE: reject: RCPT from unknown[193.200.50.2]: 504 5.5.2 <xxx.xxx.xxx.xxx>: Helo command rejected: need fully-qualified hostname; from=<support@microsoft.com> to=<support@microsoft.com> proto=SMTP helo=<xxx.xxx.xxx.xxx>