Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-25-2009, 12:07 PM
Senior Member
 
Posts: 50
Default email in deferred queue

One of our user received a valid email from registrations@pahgcc.memfirstweb.net. But when he replied this email, I find the replied email is stucked in deferred queue. The Reason is: connect to pahgcc.memfirstweb.net[208.118.238.44]:25:connection timed out

Does anyone know why this issue happens? Is any possible to setup on server to send a notice or bounce the replied email to sender after 24~48 hour if replied email stuck in deferred queue?

Thanks so much!
Reply With Quote
  #2 (permalink)  
Old 11-25-2009, 01:09 PM
Moderator
 
Posts: 1,147
Default

Take a look at this thread: Automatically Drop Deffered Mail -PM to thread
It details what configuration options are relevant to the deferred queue lifetime, and how to edit them.
Reply With Quote
  #3 (permalink)  
Old 11-25-2009, 01:13 PM
Moderator
 
Posts: 1,147
Default

Also this message in particular is because "pahgcc.memfirstweb.net" has no MX record. My guess would be that the memfirstweb.net mail server is incorrectly configured and is sending email out with the wrong domain. Since it didn't find a MX record it looks like Zimbra is trying to connect to the A record, but that doesn't respond to port 25.
Reply With Quote
  #4 (permalink)  
Old 11-25-2009, 01:20 PM
Senior Member
 
Posts: 50
Thumbs up

Quote:
Originally Posted by ArcaneMagus View Post
Also this message in particular is because "pahgcc.memfirstweb.net" has no MX record. My guess would be that the memfirstweb.net mail server is incorrectly configured and is sending email out with the wrong domain. Since it didn't find a MX record it looks like Zimbra is trying to connect to the A record, but that doesn't respond to port 25.
Hi ArcaneMagus, very appreciate your reply. Wish you have a Happy Thanks Giving Holiday!
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.