Red Hat Bugzilla – Bug 129804
Evolution unable to connect to POP server after yum update
Last modified: 2008-08-02 19:40:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
Just After a fresh install from Fedora Core 2 CD's, evolution and
other mailers are working fine. But as the uptodate applet warns me
that a huge set of updates are available I updated my system with yum
(yum update). It's where the problems are appearing.
When I start evolution and click on [Send/Receive] button the 'Send &
Receive Mail' dialog pops up and hangs in the waiting state for the
When I click on the [Cancel] button of the dialog, a new dialog 'Enter
Password for myUsername@swing.be' prompts me for my password and
displays the message 'Unable to connect to POP server pop.swing.be.
Error sending password: Unknown error'
The last dialog endlessly comes back with the same error message each
time I click on the [OK] button.
The same behaviour appeared when I tried other mailers (mozilla-mailer
-1.7.2-0.2.0 and thunderbird-0.7.3) : they both hang when connecting
to the pop server.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. launch evolution from the Gnome Panel
2. click on the [Send/Receive] button
3. here is the bug; the mailer hangs
Expected Results: sucessful connection to POP server (obviously)
Created attachment 102728 [details]
As you can see in the attached log file there is a problem with the
dns related packets (bad udp cksum). The problem occurs while running
the 2.6.7 kernel version.
I solved the problem by opening the firewall for udp port 53 and
retricted the allowed sender ip to my ISP's dns servers. Then I
rebooted with kernel 2.6.5. All works fine.
I can now say that the problem is related to the 2.6.7 version of the
kernel but don't know exactly where the problem is.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Closing per lack of response. Also note that FC1 and FC2 are no longer
supported even by Fedora Legacy. If this still occurs on FC3 or FC4, please
assign to that version and Fedora Legacy. If it still occurs on FC5 or FC6,
please reopen and assign to the correct version.