GMS was in the process of receiving a message from a remote mail server or mail client and a security feature was activated. The message claims to be from someone who has an account on this system but either:
- The IP address of the client is not recognized as being able to send email from this domain; or
- The mail client has not successfully logged into POP3 or IMAP4 before trying to send email (GMS Anti-Spam required); or
- The mail client has not authenticated using the AUTH command before starting to send the email (GMS Anti-Spam required).
GMS will either reject the message permanently or temporarily depending upon its configuration. This security feature stops other people using your domain name to send email through your server. It helps to ensure that systems sending email from your domain really are from mail clients that are within your company. By rejecting the message at the MAIL clause, GMS is saving considerable network bandwidth because the message body has not been sent over the network.
In this case session Undefined has received a connection from the mail client at Undefined and is trying to send email apparently from Undefined. The mail client or remote server said
and GMS responded with
To resolve this issue you will need to either add the IP address to those recognized as local or purchase GMS Anti-Spam.
The global variable "AllowedSenderIP" holds a list of IP addresses deemed local and "AllowedSenderIPMes" contains the message sent to the remote server.
To add the IP of the sender to the list of IP addresses deemed acceptable to send with a from domain matching the domain on the server go to GMS Anti-Spam > Connect > Local Clients and add the relevant IP address.
- What is the SMTP HELO/EHLO clause?
- What is IP and what wildcards can be used?
- What is SMTP Response Code Theory?
- What is a mail client?
- What is POP before SMTP?
Keywords:AUTH, secruity, anti-spam, IP checks, IP allowed, AllowedSenderIPMes reject