miked01

Q: Delayed inbound email between Sonicwall ES300 and Yosemite server

I currently have a setup consisting of a Yosemite email server with a Sonicwall ES300 as a relay.

Under moderate to heavy email traffic, I've been noticing that inbound emails (from the ES300 to the Yosemite server) begin to queue up on the ES300 with the message of ECONNRESET. This queue will sometimes rise as high as 200 emails and will eventually all clear out at once (sometimes after an hour or so). Email will flow correctly for a short period before the queue will begin to build again. This does not affect outbound or internal email. During times of low email usage (weekends), emails are rarely queued.

 

I've experienced this issue as well with an older server running 10.6. I'm not sure wether this is something that needs to be corrected on the Yosemite server or the ES300.

 

I'm curious if anyone has experienced similar issues. Is there something within main.cf or master.cf that could be rate limiting the IP of the ES300? If this is the case, it would have to be something in the default configuration since I haven't configured anything out of the ordinary. My other theory is that this could be due to high CPU usage on the ES300 causing connection issues.

 

Any help or ideas would be greatly appreciated.

 

Thanks!

Mac mini, OS X Yosemite (10.10.1)

Posted on Jan 25, 2015 6:54 PM

Close

Q: Delayed inbound email between Sonicwall ES300 and Yosemite server

  • All replies
  • Helpful answers

  • by John Lockwood,Helpful

    John Lockwood John Lockwood Jan 26, 2015 5:31 AM in response to miked01
    Level 6 (9,324 points)
    Servers Enterprise
    Jan 26, 2015 5:31 AM in response to miked01

    The web interface System Status page for the SonicWall will show CPU usage so you can see if it is running high. You can also on newer models go to the Diagnostics page and run the Multi-Core monitor to see a real time chart of CPU usage.

     

    Some systems will impose a delay on connections if they 'decide' that the connections are suspicious e.g. possible spam or hacking attacks. You could temporarily as a test try disabling any anti-spam or anti-spoofing features you may currently have enabled. Apple's OS X also has a software firewall which can do much the same thing. See the following.

     

    OS X Server: About the Firewall service - Apple Support

    OS X Server: How to enable the adaptive firewall - Apple Support

     

    Other than that, your SonicWall should be covered by a support/extended warranty agreement, this would allow you to contact SonicWall directly for support. They can then with your permission look at your SonicWall logs to provide you assistance.

  • by miked01,

    miked01 miked01 Jan 26, 2015 11:54 AM in response to John Lockwood
    Level 1 (0 points)
    Jan 26, 2015 11:54 AM in response to John Lockwood

    Thanks for the quick response, John!

     

    I've corrected the CPU usage issue, but the queuing of emails wasn't affected.

    I was able to confirm that the Yosemite server was not receiving mail related traffic from the ES300 during these periods, so I believe this issue is indeed with the ES300 and NOT the Yosemite server.

     

    However, I was able to change the retry interval to make this situation better until I hear by from SonicWall support.