Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 6829 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

Connected to x.x.x.x but connection died. Possible duplicate! timed out (#4.4.2)

Marshall
Guys...  I'm getting notifications from an external sender getting these bounce backs from their mail server:
.................................
Hi. This is the qmail-send program at smtp1.icglink.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
Connected to 111.111.111.111 but connection died. Possible duplicate! timed
out (#4.4.2)
I'm not going to try again; this message has been in the queue too long.
.................................
Obviously I've changed the domain name and IP Address above.  

I've looked into this error and found there may be a config error on the Astaro.  I read this article: RFC 1047 (rfc1047) - Duplicate messages and SMTP  Which talks about the smtp session timeout value between the initial SMTP 250 response and then the "." is supposed to happen at the end of the session.  Please take a look at the article and let me know if there is a way to configure this timeout value on the Astaro SMTP proxy.  V7.302 on ASG 525.

Thanks for any help,
The Marshall


This thread was automatically locked due to age.
Parents
  • 0
    I don't believe that this is your problem.  Have you created an exception for their domain?  If you look in the 'SMTP log', why did the Astaro reject the attempt to deliver the email?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    I have se same problem 


    > > juan.perez@***x.com>:
    > > Connected to 165.98.*.* but connection died. Possible
    > > duplicate! (#4.4.2)
    > > I'm not going to try again; this message has been in the
    > > queue too long.
    > >
    > > :
    > > Connected to 165.98.*.*   but connection died. Possible
    > > duplicate! (#4.4.2)
    > > I'm not going to try again; this message has been in the
    > > queue too long. 

    Astaro v7.304
Reply
  • 0 in reply to BAlfson
    I have se same problem 


    > > juan.perez@***x.com>:
    > > Connected to 165.98.*.* but connection died. Possible
    > > duplicate! (#4.4.2)
    > > I'm not going to try again; this message has been in the
    > > queue too long.
    > >
    > > :
    > > Connected to 165.98.*.*   but connection died. Possible
    > > duplicate! (#4.4.2)
    > > I'm not going to try again; this message has been in the
    > > queue too long. 

    Astaro v7.304
Children
No Data
Cookie Information Banner