Bug 217567
| Summary: | 'Send/Receive' - SMTP or IMAP stuck | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Warren Sturm <warren.sturm> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6 | CC: | gnomeuser, paul, peter, tmus |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | evolution-data-server-1.8.2-2.fc6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-01-15 18:06:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Warren Sturm
2006-11-28 17:53:27 UTC
I have the same exact problem here. evolution-webcal-2.7.1-6 evolution-sharp-0.11.1-10.fc6 evolution-data-server-1.8.1-2.fc6 evolution-2.8.1.1-3.fc6 *** Bug 217620 has been marked as a duplicate of this bug. *** Some what the same problem on my machine, however I have it 100% reproducable and even forcefully shutting down and restart Evolution will not allow for mail to be sent. Tested the same account using Thunderbird on the same machine and there is no problem sending mail in that client. I've been using IMAPS as mail account for a ver long time, and have yet to encounter such a bug in Evolution (using the same versions as posted in comment #1). The one thing immediately I notice that is different about this though is that Warren is using the Xen setup, whereas I've elected to disable it at install time. David or Ricardo: Does this make a difference for you? Also, does electing to use or not to use SSL/TLS support for your account change the result (if your mail server supports it)? Ok, I just hit this bug earlier this evening and it's a complete pain in the butt. `evolution --force-shutdown` works around it (as running Evolution again then works okay). This is really really odd. My mail server is configured to use IMAP and SMTP over a TLS connection. And it's not like Development escapes unharmed from this: evolution-2.9.2-3.fc7 evolution-data-server-1.9.2-3.fc7 Are also affected. I still timeout regardless of TLS/SSL setting, this is on x86_64, no Xen. Same problem here. This is on x86_64, but I'm sending mail using SMTP over an SSH tunnel. I run IMAP over the same tunnel, but have only seen this hang on the SMTP part (if I can trust the "complete" IMAP status). I can reproduce in less than 15 seconds every time by continuously hitting the "Send / Receive" button. Tried to reproduce usinng --debug, but nothing is put in the debug log at hang time. evolution-2.8.2.1-2.fc6 evolution-data-server-1.8.2-1.fc6 Same hebaviour seen here: I'm using SMTP with TLS and also IMAPS. The server is on the same LAN and I don't believe it's a network timeout issue. Both the IMAP and SMTP parts are prone to hanging - IMAP says 'Updating', SMTP says 'Waiting', though SMTP hangs are more frequesnt. I also use LDAP over SSL if that makes any difference. The IMAP server is dovecot and the SMTP server is sendmail. evolution.x86_64 2.8.2.1-2.fc6 evolution-data-server.x86_64 1.8.2-1.fc6 evolution-data-server-1.8.2-2.fc6 appears to fix this for me. I've been hitting the send/receive button so many times, it would have crashed for me many times earlier. Now it just keeps sending and recieving - Yay! -- from the changelog -- * Wed Jan 10 2007 Matthew Barnes <mbarnes> - 1.8.2-2.fc6 - Add patch for RH bug #208724 (hang on send/receive). -- -- Awesome! Glad it's working for you. I'll wait until the package hits Fedora Updates to close this bug. After getting hit twice in a short span of minutes I bit the bullet and tried the updates-testing version of the data-server and did not have any problems for the rest of the day. The e-d-s package in updates-testing has also resolved this issue for me. Thanks! |