Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 26 subscribers
  • Views 4174 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MTA: some messages aren't delivered to the internal Exchange server

Adriano Almeida
Hi,
 
Some e-mail messages aren't sent to the internal server by the MTA.
 
The status is Delivered, but the message simply disappears between the MTA and Exchange.
 


This thread was automatically locked due to age.
Parents
  • 0

    Adriano,

    connect to XG cli using putty, then choose option 5 > 3 and type the following command:

    service awarrenmta:debug -ds nosync (to put the MTA into debug mode) and check the awarrentmta.log inside /var/tslog after few days when you think that the message disappeard and see if you see something interesting.

    Thanks

Reply
  • 0

    Adriano,

    connect to XG cli using putty, then choose option 5 > 3 and type the following command:

    service awarrenmta:debug -ds nosync (to put the MTA into debug mode) and check the awarrentmta.log inside /var/tslog after few days when you think that the message disappeard and see if you see something interesting.

    Thanks

Children
  • 0 in reply to lferrara
    Hi Lferrara,
     
    I monitored a message and got this:
     
    MESSAGE Dec 08 14:02:26 [0x20006ef0]: [0x20006ef00] FROM: sender@external.com, TO: recipient@internal.com
    MESSAGE Dec 08 14:02:26 [0x20006ef0]: [0x20006ef00] (recipient@internal.com) SF Policy Action: ACCEPT
    MESSAGE Dec 08 14:02:26 [0x20006ef0]: Mail Transaction Started from XXX.XXX.XXX.XXX:46854 to YYY.YYY.YYY.YYY: 25 (fdid: 3413)
    MESSAGE Dec 08 14:02:32 [0x20006ef0]: [0xc0000eea] Mail sent successfully with 250 2.6.0 <8645d2f84e7c_7d0293415e6983cd3d1ad@external-alias.mail> Queued mail for delivery
    ERROR Dec 08 14:02:32 [3875384128]: insert_reason_for_action: REASON: Mail sent successfully.
     
    Since I have to solve the problem immediately, I will have to migrate to Legacy Mode and test the MTA again at another time.
     
    Thank you,
     
    Adriano
  • 0 in reply to Adriano Almeida

    Adriano Almeida said:
    Hi Lferrara,
     
    I monitored a message and got this:
     
    MESSAGE Dec 08 14:02:26 [0x20006ef0]: [0x20006ef00] FROM: sender@external.com, TO: recipient@internal.com
    MESSAGE Dec 08 14:02:26 [0x20006ef0]: [0x20006ef00] (recipient@internal.com) SF Policy Action: ACCEPT
    MESSAGE Dec 08 14:02:26 [0x20006ef0]: Mail Transaction Started from XXX.XXX.XXX.XXX:46854 to YYY.YYY.YYY.YYY: 25 (fdid: 3413)
    MESSAGE Dec 08 14:02:32 [0x20006ef0]: [0xc0000eea] Mail sent successfully with 250 2.6.0 <8645d2f84e7c_7d0293415e6983cd3d1ad@external-alias.mail> Queued mail for delivery
    ERROR Dec 08 14:02:32 [3875384128]: insert_reason_for_action: REASON: Mail sent successfully.
     

    Mail sent successfully but with error at the beginning, strange!
    A tcpdump would help. Open a ticket with Support!