SMTP Relaying - Fail Les
    SMTP Relaying - Fail Synametrics Support
        SMTP Relaying - Fail Anonymous
            SMTP Relaying - Fail Synametrics Support
                SMTP Relaying - Fail Anonymous

From: Les
Date: 8/13/24 2:36 PM
Topic: SMTP Relaying - Fail
Type: General Discussions
Post a follow up

Hello,

I have smtp proxy configured with AD Integration in v9.3 and this is working perfectly fine. Due to the deprecation message of smtp proxy, I decided to test out smtp server. I am experiencing an issue with the SMTP server configuration when I add 192.168.1.* to the Host/IP settings in the relay configuration.. email in the queue is sent, but I receive about 30 odd notifications relating to :

  • Possible forgery attempted for an outbound message
    • The following message was sent from the system, which can be perceived as a forged message by the receiving end. Your public IP address can get blacklisted if this problem is not fixed.

 

How can I resolve this issue, considering that the SMTP proxy setup does not exhibit this symptom?

Image attached of configuration, for reference purposes.

Les

Top

From: Synametrics Support
Date: 8/13/24 3:12 PM
Topic: SMTP Relaying - Fail
Type: General Discussions
Post a follow up

Les,

Your description talks about two problems:

  1. Relaying denied
  2. Possible Forgery attempt

These problems are not related to each other. 

Problem #1

I assume this problem occurs with inbound emails. Let me know if this is incorrect and the message is outbound. In this case, the "Relaying denied" message comes from your downstream server, not Xeams.

Is the recipient's domain configured locally on your downstream server?

Problem #2

A forgery alert is only sent for outbound emails. Consider the following example:

Sender: leslie_fleming@xyz.com
Recipient: afriend@gmail.com

Xeams will generate an alert if xyz.com is not specified as a local domain in Xeams.

 

 

 

Top

From: Anonymous
Date: 8/13/24 5:22 PM
Topic: SMTP Relaying - Fail
Type: General Discussions
Post a follow up

My GW 192.168.1.1 uses port forwarding for smtp traffic to my Xeams server 192.168.1.5 on port 25. Good traffic is then sent on to my MX Exchange server 192.168.1.4 also on port 25. This is the flow currently in place and working with smtp proxy configuration. Is there further changes required at my MS Exchange end in order to receive smtp traffic on port 25 from Xeams when using  SMTP configuration? Based on the image I attached, have I miss configured the SMTP configuration in anyway?

 

Thanks for your help and best regards.

 

Les 

Top

From: Synametrics Support
Date: 8/13/24 8:02 PM
Topic: SMTP Relaying - Fail
Type: General Discussions
Post a follow up

Les,

Go to Server Configuration/SMTP Configuration and select the Domains tab. Do you have your domain name configured to forward emails to 192.168.1.4?

If yes, compose a support email from your web interface using the method mentioned on https://www.xeams.com/supportcontact.htm and ensure the log files are included. 

Top

From: Anonymous
Date: 8/15/24 10:10 AM
Topic: SMTP Relaying - Fail
Type: General Discussions
Post a follow up

Yes, my domain is configured to forward to n.n.1.4. I have raised a support ticket based on the info provided.

 

Thanks very much the help to date.

 

Les

Top