Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Show reason for 'Rejected message by MTA'

Created: 30 Apr 2014 | 2 comments
NoelAT's picture
1 Agree
0 Disagree
+1 1 Vote
Login to vote

We do not receive mails from a few mail gateways.

In the 'Message Audit Logs' you can find mails with action 'Rejected message by MTA',
but there is no clue why this message was rejected.

It could be because of:

  • Connection Classification
  • Directory Harvest Attack
  • Email Virus Attack
  • Local Bad Sender IP
  • Symantec Global Bad Senders
  • etc
Idea Filed Under:

Comments 2 CommentsJump to latest comment

Erick_Souza's picture

Hi NoelAT,

If is possible to you, try to identifiy if there is the CISCO ASA router, before SMG.
EX: Internet > CISCO ASA > SMG.

If there is try to follow this technote:
Messages aborted from one sender domain on a Symantec Messaging Gateway versions 8.0 and above
http://www.symantec.com/docs/TECH166750

0
Login to vote
NoelAT's picture

Hi Erick, thx for the answer.

No, there is no CISCO router involved. Also the action taken is called 'Rejected message by MTA' and not 'Abort message'.

I see the IPS of our firewall has blocked TLS-Connections from external mailservers with an old openssl version. We had to deactivate this IPS protection. However the messaging gateway now continously block connecitons from these IP-addresses with 'Rejected message by MTA', and i have no clue exactly why.

0
Login to vote