1,574
edits
Changes
From SME Server
Jump to navigationJump to search→Receiving
====Receiving====
====Receiving====
If SME server does not receive mail, then you need to ensure that SMTP connections reach your SME server (DNS settings, router configuration, ISP port blocks) and then you need to examine /var/log/qpsmtpd/current logs to determine what SME server does with the incoming connections. Most problems are DNS, router or ISP issues, and have nothing to do with SME server operation or configuration.
If SME server does not receive mail, then you need to ensure that SMTP connections reach your SME server (DNS settings, router configuration, ISP port blocks) and then you need to examine /var/log/qpsmtpd/current logs to determine what SME server does with the incoming connections. Most problems are DNS, router or ISP issues, and have nothing to do with SME server operation or configuration.
=====qpsmtpd Connection Timed Out errors=====
See [[Bugzilla:6888]] and [[Bugzilla:2360]]
A qpsmtpd timeout error may arise, this is not an issue that is caused by SME server directly, however it can become an issue depending on hardware and configuration settings that are contained in and around other enviroments.
It is discussed under various names
*Path MTU Discovery Blackhole http://www.phildev.net/mss/mss-talk.pdf
*Path MTU Discovery Failures http://www.wand.net.nz/~mluckie/pubs/debugging-pmtud.imc2005.pdf
*TCP Problems with Path MTU Discovery http://www.ietf.org/rfc/rfc2923.txt
As discussed in [[Bugzilla:6888]] a workaround was found that may help in mitigating the issue.
Ensure the MTU setting on your local (gateway) router is set to 1492, then set the MTU on your SME server to 1400 using the following:
config setprop InternalInterface MTU 1400
signal-event post-upgrade; signal-event reboot
====Webmail broken after upgrade====
====Webmail broken after upgrade====
