Icedove not fetching mail

Sanukk · 08-07-2015, 07:06 PM

Hi All,

Icedove was working fine (for years), but has suddenly stopped fetching mail. It says connecting to <mailserver> at the bottom, but doesn't actually do anything. I tried deleting the password thinking that may be something to do with it, but when I try to check for mail now, it flashes up connected to <server>, but doesn't ask for my password.

I have the same account set up on my phone, which still connects without issue, so I know it's not a server side issue. I can telnet in without issue, so I know it's not something odd with the computer, but I still can't get at my mail with Icedove. There are no errors, so I'm not really sure where to even start looking for a solution.

Any ideas on how to fix this? I have urgent mails to deal with.

~S

frankbell · 08-07-2015, 08:20 PM

I assume you've doublechecked all your settings.

Try starting icedove from the command line; it might throw some helpful error messages.

Another troubleshooting step might be to create a new user and configure icedove for that user. If it can connect, there may be something screwy in your hidden icedove configuration directory in your /home.

The Debian wiki has some tips on how to debug Icedove.

Sanukk · 08-08-2015, 04:24 AM

Quote:

Originally Posted by frankbell

I assume you've doublechecked all your settings.

Several times now.

Quote:

Try starting icedove from the command line; it might throw some helpful error messages.

One of the first things I did, no error or warning messages given.

Quote:

Another troubleshooting step might be to create a new user and configure icedove for that user. If it can connect, there may be something screwy in your hidden icedove configuration directory in your /home.

Same problem here.

Quote:

The Debian wiki has some tips on how to debug Icedove.

Here is the debug file https://www.dropbox.com/s/0rblpjwst2...e_dbg.txt?dl=0 I can't make any sense of it though.

Thanks for your help so far.

~S

273 · 08-08-2015, 05:02 AM

Perhaps this has something to do with it, or not?

Quote:

Originally Posted by apt-listchanges

icedove (34.0~b1-1) experimental; urgency=low

Due to the BEAST vulnerability Icedove does not support SSLv3 encrypted
connections by default any longer.

However you can still reactivate SSLv3 as described in README.Debian.

Mozilla also implemented the possibility to adjust the fallback strategy
for TLS based connections to work against the POODLE attacks.

Please read README.Debian for further information on changing the TLS fallback
behavior.

-- Carsten Schoenert <c.schoenert@t-online.de> Wed, 12 Nov 2014 19:38:00 +0100

icedove (33.0~b1-1) experimental; urgency=low

Mozilla implemented TLS 1.2 in NSS version 3.15.1 and Thunderbird 31.0 uses
this as the default. Thunderbird/Icedove is fall back to older TLS versions
if the server is requesting this.

This means every connection from Thunderbird/Icedove to a mail server will
start using TLS 1.2 and want fall back through 1.1 and 1.0 to SSLv3 if you
have configured TLS/SSL or STARTTLS for your connections.

Some users reported trouble by this behavior. In case you are unable to get
or sent any mails anymore from or to your mail server please ensure that
your email provider is fully supporting TLS 1.2 if possible.

There were reports that this causes problems with some providers (Bug
#761245). This is usually indicated by:

"connection to SMTP server was lost in the middle of the transaction."

For information on how to fix that check README.Debian.

-- Carsten Schoenert <c.schoenert@t-online.de> Wed, 15 Oct 2014 18:38:00 +0200

Sanukk · 08-08-2015, 06:59 AM

Quote:

Originally Posted by 273

Perhaps this has something to do with it, or not?

I just tried setting security.tls.version.min to 0 as suggested, no luck ;^<

273 · 08-08-2015, 09:56 AM

Sorry, I thought it worth a try.

Sanukk · 08-09-2015, 10:45 AM

Quote:

Originally Posted by 273

Sorry, I thought it worth a try.

Indeed it was, and thank you for the suggestion.

I'm still stuck with out my mail on the machine I need it on though ;^<

Sanukk · 08-11-2015, 10:03 AM

Hi,

I've installed evolution (which I don't like at all) as a stopgap until IceDove gets fixed, but as that works fine with exactly the same settings, that rules out it being anything odd with the machine/firewall/whatever and it is definitely a problem with IceDove.

Anybody got any other ideas how to fix this?

~S

273 · 08-11-2015, 12:20 PM

Other than renaming your icedove settings directory and trying again, I'm out of ideas for now.