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

How to deterime the cause for rejected after DATA

Hi,

is it possbiel to get to know, what triggered the AMG to reject a message? I have a client who deperately waits for a message that gets continously rejected on the AMG. The smtp_proxy logs shows this:

2009:03:23-10:21:40 astaro01 exim[28111]: 2009-03-23 10:21:40 1LlgLk-0007JP-1S id="1003" severity="info" sys="SecureMail" sub="smtp" name="email rejected" srcip="212.1.38.25" from="foo%40bar" to="bar%40foo" subject="PreSafe" queueid="1LlgLk-0007JP-1S" size="123815" reason="as" extra="confirmed"
2009:03:23-10:21:40 astaro01 exim[28111]: [1\48] 2009-03-23 10:21:40 1LlgLk-0007JP-1S H=mx2.jvm.de [212.1.38.25]:40157 F= rejected after DATA

Thanks,
budy


This thread was automatically locked due to age.
  • Dave, please submit a support request to Astaro.
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Dave, This question was asked in a little different way on another thread, and I thought of this one.  Your Astaro correctly rejected this email because, according to the CommTouch spam qualifier, it is "confirmed" spam.  If that is not the case, then you'll need to create an exception for 'Anti-Spam checking' for *@softek.co.uk.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Hi Forum,

    just as an update: we have logged a call to Astaro three weeks ago. It looks like the "blacklists" from Commtouch have been revised in the meantime. We did not get any more rejected mails from customers during the past 3 weeks. 

    So this seems to be fixed by Commtouch. (no official information - just what I think). Perhaps this is the reason for Astaro not giving any statements to that issue here nor to the call.

    I hope in a future release the troubleshooting information of such a case will be more detailed. AND I hope there will be a way to disable any single engine to be able to work around any future hickups one of the lists shows.

    Regards, Thomas