Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 5 subscribers
  • Views 18566 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

UTM 9.351-3 SMTP proxy stops delivering, exim-out not running

EWIT

Our Sophos UTM 220 is running SMTP anti-spam proxy, and has been running well for many months. After the recent firmware update to 9.351-3 the SMTP proxy frequently stops delivering mail.

Messages are logged as moving to the work queue, but exim-out never actually picks up the messages and spools them for delivery. To clear the stuck mail I have to stop SMTPD, clear the retry timeout database, and restart SMTPD.

We are only using this for inbound filtering, and it's delivering to our in-house SMTP server, nothing very complicated.

exim-out ends with a simple message:

2015:11:23-10:31:15 firewall exim-out[29473]: 2015-11-23 10:31:15 End queue run: pid=29473

But the "start queue run" message doesn't reappear until after I restart the SMTP service. Obviously I can't babysit this thing all day. Any ideas?

 



This thread was automatically locked due to age.
Parents
  • 0
    I've had support look into this THREE times already this month; most recent was today, while nearly 1,000 emails stacked up on the UTM over 2 hours. We checked every possible log file and no problems were apparent.

    After restarting smtpd, the messages moved into the spool and were delivered in minutes.

    I've enabled SMTP debug logging (not sure why support didn't recommend that...) and hope to catch the problem happening. Maybe I just need to schedule smtpd to restart every hour? Sad.

    Very, very disappointed with this. Maybe the UTM 220 can't handle the mail load of 50 employees?
Reply
  • 0
    I've had support look into this THREE times already this month; most recent was today, while nearly 1,000 emails stacked up on the UTM over 2 hours. We checked every possible log file and no problems were apparent.

    After restarting smtpd, the messages moved into the spool and were delivered in minutes.

    I've enabled SMTP debug logging (not sure why support didn't recommend that...) and hope to catch the problem happening. Maybe I just need to schedule smtpd to restart every hour? Sad.

    Very, very disappointed with this. Maybe the UTM 220 can't handle the mail load of 50 employees?
Children
No Data
Unfiltered HTML