Icedove version 38.4.0-1-deb7u1+7.0trisquel2 fails to connect to OpenMailBox.org's IMAP and POP3 servers

54 Antworten [Letzter Beitrag]
ADFENO
Offline
Beigetreten: 12/31/2012

Sorry for not using the issue tracker, but since I don't use the
Trisquel.info website that much (and I rarely have the time to), i
prefer to use e-mail and post in the forums because at least I receive
the notifications in one place.

The topic is self-explanatory: Icedove version
38.4.0-1-deb7u1+7.0trisquel2 fails to connect to OpenMailBox.org's IMAP
and POP3 servers.

I have tested with Geary version 0.6.0-0ubuntu2 and I can connect
successfully.

It happens both with TLS/SSL and STARTTLS.

Before updating from Icedove version 31.8.0-1~deb7u1+7.0trisquel2,
everything worked fine. However, since bugs can be affected by other
things, here is the log of my last package update using Aptitude (text
is in Brazilian Portuguese):

# Start of log
Aptitude 0.6.8.2: relatório de log
Sáb, 5 Dez 2015 12:04:11 -0200

IMPORTANTE: este log lista somente ações pretendidas; ações que falham
devido a problemas do dpkg podem não estar completas.
Serão instalados 33 pacotes e removidos 0 pacotes.
230 MB de espaço em disco serão usados
===============================================================================
[INSTALAR, DEPENDÊNCIAS] linux-headers-3.13.0-71:i386
[INSTALAR, DEPENDÊNCIAS] linux-headers-3.13.0-71-generic:i386
[INSTALAR, DEPENDÊNCIAS] linux-image-3.13.0-71-generic:i386
[INSTALAR, DEPENDÊNCIAS] linux-image-extra-3.13.0-71-generic:i386
[ATUALIZAÇÃO] icecat:i386 38.3.0-gnu2+7.0trisquel1 ->
38.4.0-gnu1+7.0trisquel1
[ATUALIZAÇÃO] icecat-locale-pt:i386 38.3.0-gnu2+7.0trisquel1 ->
38.4.0-gnu1+7.0trisquel1
[ATUALIZAÇÃO] icedove:i386 31.8.0-1~deb7u1+7.0trisquel2 ->
38.4.0-1~deb7u1+7.0trisquel2
[ATUALIZAÇÃO] icedove-l10n-pt-br:i386 1:31.2.0-1~deb7u1+7.0trisquel1 ->
1:38.0.1-1~deb7u1+7.0trisquel1
[ATUALIZAÇÃO] libgnutls-openssl27:i386 2.12.23-12ubuntu2.2 ->
2.12.23-12ubuntu2.3
[ATUALIZAÇÃO] libgnutls26:i386 2.12.23-12ubuntu2.2 ->
2.12.23-12ubuntu2.3
[ATUALIZAÇÃO] libpolkit-agent-1-0:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[ATUALIZAÇÃO] libpolkit-backend-1-0:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[ATUALIZAÇÃO] libpolkit-gobject-1-0:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[ATUALIZAÇÃO] linux-generic:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[ATUALIZAÇÃO] linux-generic-pae:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[ATUALIZAÇÃO] linux-headers-generic:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[ATUALIZAÇÃO] linux-headers-generic-pae:i386 3.13.0.68.74+7.0trisquel2
-> 3.13.0.71.77+7.0trisquel2
[ATUALIZAÇÃO] linux-image-generic:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[ATUALIZAÇÃO] linux-libc-dev:i386 3.13.0-68.111+7.0trisquel2 ->
3.13.0-71.114+7.0trisquel2
[ATUALIZAÇÃO] policykit-1:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[ATUALIZAÇÃO] qemu:i386 2.0.0+dfsg-2ubuntu1.20 -> 2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-keymaps:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system-arm:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system-common:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system-mips:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system-misc:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system-ppc:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system-sparc:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-system-x86:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-user:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] qemu-utils:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[ATUALIZAÇÃO] youtube-dl:i386 2015.11.24-1~webupd8~trusty1+7.0trisquel1
-> 2015.11.27.1-1~webupd8~trusty1+7.0trisquel1
===============================================================================

Log completo.
# End of log

jxself
Offline
Beigetreten: 09/13/2010

I can't help because the stuff you're sending is not English.

But, I can observe that you do seem to like to make long subjects and then say that it describes everything. :)

Like "Do you know any [Bit]Torrent site used to inform to others about LEGALLY SHAREABLE non-functional data, and whose recommendations don't rely on file formats and codecs used mainly by non-free software?"

As a SUBJECT line. Wow. You know that your entire message shouldn't go into the subject line, right? That's what the message body is for. :)

ADFENO
Offline
Beigetreten: 12/31/2012

Here's the human-translated version of the log:

# Start of log
Aptitude 0.6.8.2: log report
Sat, 5th Dec 2015 12:04:11 -0200

IMPORTANT: this log lists only intended actions; actions which failed
due to problems of dpkg could not be completed.
33 packages will be installed and 0 will be removed.
230 MB of disk space will be used
===============================================================================
[INSTALL, DEPENDENCIES] linux-headers-3.13.0-71:i386
[INSTALL, DEPENDENCIES] linux-headers-3.13.0-71-generic:i386
[INSTALL, DEPENDENCIES] linux-image-3.13.0-71-generic:i386
[INSTALL, DEPENDENCIES] linux-image-extra-3.13.0-71-generic:i386
[UPDATE] icecat:i386 38.3.0-gnu2+7.0trisquel1 ->
38.4.0-gnu1+7.0trisquel1
[UPDATE] icecat-locale-pt:i386 38.3.0-gnu2+7.0trisquel1 ->
38.4.0-gnu1+7.0trisquel1
[UPDATE] icedove:i386 31.8.0-1~deb7u1+7.0trisquel2 ->
38.4.0-1~deb7u1+7.0trisquel2
[UPDATE] icedove-l10n-pt-br:i386 1:31.2.0-1~deb7u1+7.0trisquel1 ->
1:38.0.1-1~deb7u1+7.0trisquel1
[UPDATE] libgnutls-openssl27:i386 2.12.23-12ubuntu2.2 ->
2.12.23-12ubuntu2.3
[UPDATE] libgnutls26:i386 2.12.23-12ubuntu2.2 -> 2.12.23-12ubuntu2.3
[UPDATE] libpolkit-agent-1-0:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[UPDATE] libpolkit-backend-1-0:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[UPDATE] libpolkit-gobject-1-0:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[UPDATE] linux-generic:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[UPDATE] linux-generic-pae:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[UPDATE] linux-headers-generic:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[UPDATE] linux-headers-generic-pae:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[UPDATE] linux-image-generic:i386 3.13.0.68.74+7.0trisquel2 ->
3.13.0.71.77+7.0trisquel2
[UPDATE] linux-libc-dev:i386 3.13.0-68.111+7.0trisquel2 ->
3.13.0-71.114+7.0trisquel2
[UPDATE] policykit-1:i386 0.105-4ubuntu2.14.04.1 ->
0.105-4ubuntu3.14.04.1
[UPDATE] qemu:i386 2.0.0+dfsg-2ubuntu1.20 -> 2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-keymaps:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system-arm:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system-common:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system-mips:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system-misc:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system-ppc:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system-sparc:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-system-x86:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-user:i386 2.0.0+dfsg-2ubuntu1.20 -> 2.0.0+dfsg-2ubuntu1.21
[UPDATE] qemu-utils:i386 2.0.0+dfsg-2ubuntu1.20 ->
2.0.0+dfsg-2ubuntu1.21
[UPDATE] youtube-dl:i386 2015.11.24-1~webupd8~trusty1+7.0trisquel1 ->
2015.11.27.1-1~webupd8~trusty1+7.0trisquel1
===============================================================================

Log completed.
# End of log

As for the e-mail subjects, I like them to be as informative as
possible for a subject. Leaving only the descriptive parts in the
e-mail body.

I think that it's better than "Help!" or "Problems with Icedove" (means
that there's a problem, but doesn't really tell what's happening),
unless I can't really find a better way to describe the topic (which is
rare, but happens when I'm really out of time).

jxself
Offline
Beigetreten: 09/13/2010

"As for the e-mail subjects, I like them to be as informative as
possible for a subject. Leaving only the descriptive parts in the
e-mail body.

I think that it's better than "Help!" or "Problems with Icedove" (means
that there's a problem, but doesn't really tell what's happening),
unless I can't really find a better way to describe the topic (which is
rare, but happens when I'm really out of time)."

Yes, subjects like "Help!" are not very useful but putting the entire message into the subject is, at the same time, too much. The subject should be a descriptive summary only, not the entire message. :)

Mzee
Offline
Beigetreten: 07/10/2013

I agree about the subject issue. Please keep it short and simple. ;-)

@Topic: I have a similar issue since I recently updated to a newer Thunderbird version. I'm not able to send e-mails with attachment any more. That's a VERY annoying thing for me and I already had to change to claws-mail even though I don't like its style too much. However, claws-mail works like a charm with the very same server settings as Icedove.

The error message I keep getting is:

"Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) [any SMTP server here...] was lost in the middle of the transaction. Try again."

Mangy Dog

I am a member!

I am a translator!

Offline
Beigetreten: 03/15/2015
ADFENO
Offline
Beigetreten: 12/31/2012

Wow! Some people are experiencing this strange behaviour when using
OpenMailBox's SMTP server, while I'm having trouble with POP and IMAP
just for OpenMailBox (so far, I also tested with a brand new Hotmail
account, and it works well, I'll try deleting the configuration files
to see if I can manage something).

Triqel
Offline
Beigetreten: 12/06/2014

Yes I noticed same problem. I can't read or write my mails via IMAP account with SSL/TLS. Status bar only says connecting server... Sometimes when I have waited minutes can see content of the mails.

Everything works well with version 31.

By default Icedove 38 has as "maximum # of server connections to cache" 5 via edit>account settings>server settings>advanced when it had 1 in Icedove 31. When I changed the parameter back to 1 the situation is still same as told above.

Has someone test this also in Debian 8?

Mangy Dog

I am a member!

I am a translator!

Offline
Beigetreten: 03/15/2015

ADFENO
By the looks of Openmailbox Forum
https://www.openmailbox.org/forum/viewtopic.php?id=1437
Quite some other users are having issues
https://trisquel.info/en/forum/problems-acceding-openmailboxorg

You could try to Ping your IMAP/POP servers
#ping -c 10

here's the result of Ping for
http://whois.domaintools.com/openmailbox.org


# ping -c 10 62.4.1.33
PING 62.4.1.33 (62.4.1.33) 56(84) bytes of data.
64 bytes from 62.4.1.33: icmp_seq=1 ttl=54 time=45.0 ms
64 bytes from 62.4.1.33: icmp_seq=2 ttl=54 time=44.3 ms
64 bytes from 62.4.1.33: icmp_seq=3 ttl=54 time=44.1 ms
64 bytes from 62.4.1.33: icmp_seq=4 ttl=54 time=44.7 ms
64 bytes from 62.4.1.33: icmp_seq=5 ttl=54 time=44.0 ms
64 bytes from 62.4.1.33: icmp_seq=6 ttl=54 time=43.8 ms
64 bytes from 62.4.1.33: icmp_seq=7 ttl=54 time=44.3 ms
64 bytes from 62.4.1.33: icmp_seq=8 ttl=54 time=44.0 ms
64 bytes from 62.4.1.33: icmp_seq=9 ttl=54 time=44.7 ms
64 bytes from 62.4.1.33: icmp_seq=10 ttl=54 time=44.2 ms
--- 62.4.1.33 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 43.801/44.349/45.031/0.400 ms

jeanLuc
Offline
Beigetreten: 11/14/2015

Hello,

Same problem with IceDove 38.
Before upgrading from previous release everything works well.

Now with IceDove 38, there is issue only when sending e-mails with attachment, error is :
"L'envoi du message a échoué.
Le message n'a pas pu être envoyé car la connexion au serveur sortant (SMTP) « smtp.orange.fr » a été perdue pendant la transaction. Veuillez essayer à nouveau."

Sorry it is in french, in english that could be :
"Sending of the message failed.
The message could not be sent because the connection to Outgoing server (SMTP) « smtp.orange.fr » was lost during the transaction. Try again."

Thank you for your help.

Jean-Luc.

Sasaki
Offline
Beigetreten: 08/11/2014

hello

I have the same issue with icedove 38.4.0 with openmailbox and mailoo.org. I can't receive emails from these servers but i can send from the client.

Trisquel 7 32bit version

edit : a workaround from the spanish forum https://trisquel.info/fr/forum/problemas-con-icedove-3840

downgrading to version 31.8.0 via synaptic (select icedove, packages, force version..., select 31.8.0 and apply)

Triqel
Offline
Beigetreten: 12/06/2014

This is Trisquel forum but whether this is same issue with other distros as Debian 8?

SuperTramp83

I am a translator!

Offline
Beigetreten: 10/31/2014

no issue whatsoever on Debian 8 stable.

ADFENO
Offline
Beigetreten: 12/31/2012

Some more background information:

I began searching for this problem a bit further, and many people which
had this problem in previous versions of Thunderbird (note: previous
versions) received various advices ranging from deleting messages that
where already received by the mail client through the webmail access,
to disabling the firewall being used.

So I went ahead to deleting the past emails received, with no good
results.

Then I decided to try the firewall approach, but instead of disabling
it, I decided to leave it be and just study what the firewall which I
use (Iptables) could possibly be doing.

I have the Iptables input chain policy set to drop packets unless
the packet matches the rules I made, provided that the target
through which it jumps to isn't also a terminative and denying one to
drop or reject the packet, it should not be dropped nor
rejected.

It's important to note that I don't have terminative and denying targets
for input packets which are transfered through TCP or UDP, just for ICMP
types (based on the IETF recommendations for ICMP packet
filtering[1][2], as my computer is in the recipient of the packet
when it's the passive victim, or the sender of the packet when it's
the active victim). Except, of course, a very first rule in the input
chain that terminatively accepts all non-ICMP packets that are
associated with an outgoing connection (that is, the output, whose
policy is to accept packets).

I rarely use the non-terminative logging target, except for logging
denial of service attacks (either if I'm a passive victim or an active
victim) or for testing purposes like this situation right now.

So I went ahead and appended to the input chain a rule to the
non-terminative log target which logs the matches to "/var/log/syslog"
with a user supplied prefix like "[IPTABLES] INPUT DROP: ".

Note for "append": As far as I know, it means "insert at the very end".
For Iptables, "the very end" would be before the chain policy would be
applied. End of note.

And so I manually configured Icedove with my IMAP login, closed
Icedove to start the test only when clicking on the "Inbox" folder of
the IMAP account (otherwise it would connect automatically to the IMAP
server).

Then I opened "/var/log/syslog", took the last timestamp since system
startup (that strange number between square brackets), opened Icedove,
forced it to connect to the IMAP server, forced it again just to make
sure that the erroneous message about unsupported authentication method
appears again, and with this simple GNU Sed and GNU Less trick:

sed --quiet '/149826\.837933/,${!d; p}' "/var/log/syslog" | less

Note (one paragraph long): This command tells GNU Sed to select from the
line that matches the 149826.837933 timestamp (the backslash/"\" is
needed before the dot because we don't want to match any single
character but a literal dot) to the last line ($), delete everything
(d) expect the selection (!) and print it (p), the brackets are just
for the "beauty" of the code as I hate unreadable code structures. End
of note.

I get regular messages (each 10 minutes or so) that look like this,
even without Icedove opened (note that the entry with the 149826.837933
timestamp was manually removed):

Dec 9 16:19:43 trisquel kernel: [149951.695846] [IPTABLES] INPUT DROP:
IN=wlan0 OUT= MAC=[Wireless interface_MAC address] SRC=[My router's
coinfiguration IP address] DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0
TTL=1 ID=0 DF PROTO=2

Note that in the SRC field I get the routers configuration IP address,
that is the IP address I generally use to access the router's
configuration, and the DST field is a destination not yet know by me,
unless it's a mask of some sort. So I'm thinking that this log isn't
related to this problem at all, being just a distraction, since it's
also logged when I'm not using Icedove.

So my guess is the following: Icedove is indeed receiving
response from the IMAP server, but Icedove is unable to understand the
response correctly. Considering, of course, that the response is not
malformed, as it's well interpreted by other email clients, unless the
service provider of the IMAP server really messed up with something on
his end, which is, as noted, unlikely.

REFERENCES

[1] https://tools.ietf.org/html/draft-ietf-opsec-icmp-filtering-04

[2] Note for [1]: The draft is actually expired, but it's still a good
piece of documentation.

jdenz
Offline
Beigetreten: 11/18/2011

@ADFENO I like what you've done here. I was also forced to downgrade IceDove and hope a true fix for whatever is causing this problem in Trisquel or the updated IceDove version is discovered soon.

Please keep us updated if you find anything and thanks for your work on this!

ADFENO
Offline
Beigetreten: 12/31/2012

Thank you very much.

Sorry for not replying quickly enough. I though that our community's activities were quiet due to the upcoming celebrations, because I didn't receive any email from this forum's mailing list for quite a while, but my thoughts were wrong, as the community is still active in the forum, it's just the mail forwarding that seems to be malfunctioning for some reason.

Although not being a programmer, I try to do my best using the limited knowledge I have. Despite the lack of time to dedicate myself to the Trisquel project.

I'll try to keep you all updated whenever I make other tests or find other interesting things. I would like to use the issue tracker for the sake of organization, but as far as I recall, it's not possible to receive messages from the issue tracker by email (and my last experience was four months ago, and so please update me if this feature was implemented in the issue tracker, as I'm willing to use the issue tracker once it allows me to at least receive messages sent to it to my email).

ADFENO
Offline
Beigetreten: 12/31/2012

Thank you very much.

Sorry for not replying quickly enough. I though that our community's
activities were quiet due to the upcoming celebrations, because I didn't
receive any email from this forum's mailing list for quite a while, but my
thoughts were wrong, as the community is still active in the forum, it's just
the mail forwarding that seems to be malfunctioning for some reason.

Although not being a programmer, I try to do my best using the limited
knowledge I have. Despite the lack of time to dedicate myself to the Trisquel
project.

I'll try to keep you all updated whenever I make other tests or find other
interesting things. I would like to use the issue tracker for the sake of
organization, but as far as I recall, it's not possible to receive messages
from the issue tracker by email (and my last experience was four months ago,
and so please update me if this feature was implemented in the issue tracker,
as I'm willing to use the issue tracker once it allows me to at least receive
messages sent to it to my email).

jdenz
Offline
Beigetreten: 11/18/2011

@ADFENO I like what you've done here. I was also forced to downgrade IceDove
and hope a true fix for whatever is causing this problem in Trisquel or the
updated IceDove version is discovered soon.

Please keep us updated if you find anything and thanks for your work on this!

fbit

I am a member!

Offline
Beigetreten: 07/07/2013

I can confirm this issue.

I have downgraded Icedove for now and things are back to normal.

---------

_Fix_

$ apt-cache showpkg icedove

(to show available package versions and choose one)

$ apt-get install icedove=[full version number]

(where [full version number] is the version you want to downgrade to)

In my case:

$ sudo apt-get install icedove-31.8.0-1~deb7u1+7.0trisquel2

---------

_Result_

I can send e-mails with attachments again.

Edit:

Just realized...

$ apt-mark hold [package-name]

in order to prevent upgrades.

Mzee
Offline
Beigetreten: 07/10/2013

Thank you so much! That did the trick for me. However, this can only be a temporary workaround and will hopefully be fixed very soon.

Mzee
Offline
Beigetreten: 07/10/2013

Thank you so much! That did the trick for me. However, this can only be a
temporary workaround and will hopefully be fixed very soon.

Sasaki
Offline
Beigetreten: 08/11/2014

Just to say that all of this can be done in a grahical way within synaptic :

So, for newcomers in linux :

open synaptic package manager
select icedove package
click on package/force version
don't forget to block the version to prevent the updater from installing the newest version until this is fixed

Mzee
Offline
Beigetreten: 07/10/2013

I just opened a ticket for this issue. It can be found here: https://trisquel.info/en/issues/16300

Triqel
Offline
Beigetreten: 12/06/2014

Version 38.5 has been released. Does it fix this problem?

Mzee
Offline
Beigetreten: 07/10/2013

I'm wondering the same. Has anybody tried it?

oysterboy

I am a member!

I am a translator!

Offline
Beigetreten: 02/01/2011

The problem is still there with the latest version of Icedove, which seems to have problems dealing with emails with attachments. I use KMail when that problem occurs, as a temporary workaround.

oysterboy

I am a member!

I am a translator!

Offline
Beigetreten: 02/01/2011

The problem is still there with the latest version of Icedove, which seems to
have problems dealing with emails with attachments. I use KMail when that
problem occurs, as a temporary workaround.

Mzee
Offline
Beigetreten: 07/10/2013

I'm wondering the same. Has anybody tried it?

ADFENO
Offline
Beigetreten: 12/31/2012

Today I made a quick test using version 38.5.0-1~deb7u1+7.0trisquel2 of Icedove.

The test involved removing my existing receiving account setup (be it IMAP or POP3), opening the errors console (which can be located at the Icedove's menu, in the Tools menu, or by pressing Ctrl + Shift + J), making the errors console display every message, and the configure the receiving account again. Note that since I have issues with the receiving process, I didn't remove the sending account information, otherwise I would have to configure other sending account just to be able to remove and reconfigure the one I would normally use.

So in the errors console I get the following messages before using the automatic server configuration discovery for the account:

# Start of log.
While registering XPCOM module file:///usr/lib/icedove/components/libdbusservice.so, trying to re-register CID '{75a500a2-0030-40f7-86f8-63f225b940ae}' already registered by .

Hour: 04-01-2016 20:41:45
Alert: Mutation events shouldn't be used anymore. Instead, use MutationObserver.
Source file: chrome://calendar/content/widgets/calendar-widgets.xml
Line: 496

Hour: 04-01-2016 20:41:46
Error: TypeError: tab is undefined
Source file: chrome://messenger/content/tabmail.xml
Line: 1067
# End of log.

Then, during the usage of the automatic server configuration discovery for the account:

# Start of log.
Hour: 04-01-2016 20:43:27
Error: The XML file doesn't contain an email account configuration.
Source file: resource:///modules/errUtils.js
Line: 35

# Last message repeats 2 times.

Hour: 04-01-2016 20:43:31
Error: Not Found
Source file: resource:///modules/errUtils.js
Line: 35

Hour: 04-01-2016 20:43:32
Error: MX lookup would be no different from domain
Source file: resource:///modules/errUtils.js
Line: 35
# End of log.

Then, as OpenMailBox users might already know, once the discovery is finished, we need to supply our email address as the username for the IMAP, POP3, and SMTP servers, and so I did, and after inserting my password and unchecking "Remember password", I was expecting some feedback in the errors console. Surprisingly, nothing showed up in the errors console. However, the bug still persists since a normal user will face a warning telling him that the username or password are incorrect, and which will not allow the window to close even after the "Finish" but is clicked. The window only closes if the user cancels the configuration or configures the account manually using the advanced configuration. But still after configuring the account, he won't be able to receive emails (for those who are unable to receive, at least).

Interestingly, when telling Icedove to enter the advanced configuration, the errors console shows the following:

# Start of log.
Hour: 04-01-2016 21:08:58
Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790" data: no]
Source file: chrome://messenger/content/folderPane.js
Line: 2792

# Last message repeats 1 times.
# End of log.

When I accept the configuration and click at the inbox of my still-not-loaded IMAP account, the errors console shows the following:

# Start of log.
Hour: 04-01-2016 21:13:00
Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790" data: no]
Source file: chrome://messenger/content/folderPane.js
Line: 2792

# Last message repeats approximately 53 times.
# End of log.

I hope this has proven to be useful, even if it serves to rule something out (that is, to discard some possibility which is in the minds of the developers).

Todo: Do the same procedure with a previous version of Icedove that used to behave well, in order to check whether the errors presented here are unique to the upgraded version or not.

ADFENO
Offline
Beigetreten: 12/31/2012

Today I made a quick test using version 38.5.0-1~deb7u1+7.0trisquel2 of
Icedove.

The test involved removing my existing receiving account setup (be it IMAP or
POP3), opening the errors console (which can be located at the Icedove's
menu, in the Tools menu, or by pressing Ctrl + Shift + J), making the errors
console display every message, and the configure the receiving account again.
Note that since I have issues with the receiving process, I didn't remove the
sending account information, otherwise I would have to configure other
sending account just to be able to remove and reconfigure the one I would
normally use.

So in the errors console I get the following messages before using the
automatic server configuration discovery for the account:

# Start of log.
While registering XPCOM module
file:///usr/lib/icedove/components/libdbusservice.so, trying to re-register
CID '{75a500a2-0030-40f7-86f8-63f225b940ae}' already registered by .

Hour: 04-01-2016 20:41:45
Alert: Mutation events shouldn't be used anymore. Instead, use
MutationObserver.
Source file: chrome://calendar/content/widgets/calendar-widgets.xml
Line: 496

Hour: 04-01-2016 20:41:46
Error: TypeError: tab is undefined
Source file: chrome://messenger/content/tabmail.xml
Line: 1067
# End of log.

Then, during the usage of the automatic server configuration discovery for
the account:

# Start of log.
Hour: 04-01-2016 20:43:27
Error: The XML file doesn't contain an email account configuration.
Source file: resource:///modules/errUtils.js
Line: 35

# Last message repeats 2 times.

Hour: 04-01-2016 20:43:31
Error: Not Found
Source file: resource:///modules/errUtils.js
Line: 35

Hour: 04-01-2016 20:43:32
Error: MX lookup would be no different from domain
Source file: resource:///modules/errUtils.js
Line: 35
# End of log.

Then, as OpenMailBox users might already know, once the discovery is
finished, we need to supply our email address as the username for the IMAP,
POP3, and SMTP servers, and so I did, and after inserting my password and
unchecking "Remember password", I was expecting some feedback in the errors
console. Surprisingly, nothing showed up in the errors console. However, the
bug still persists since a normal user will face a warning telling him that
the username or password are incorrect, and which will not allow the window
to close even after the "Finish" but is clicked. The window only closes if
the user cancels the configuration or configures the account manually using
the advanced configuration. But still after configuring the account, he won't
be able to receive emails (for those who are unable to receive, at least).

Interestingly, when telling Icedove to enter the advanced configuration, the
errors console shows the following:

# Start of log.
Hour: 04-01-2016 21:08:58
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790"
data: no]
Source file: chrome://messenger/content/folderPane.js
Line: 2792

# Last message repeats 1 times.
# End of log.

When I accept the configuration and click at the inbox of my still-not-loaded
IMAP account, the errors console shows the following:

# Start of log.
Hour: 04-01-2016 21:13:00
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790"
data: no]
Source file: chrome://messenger/content/folderPane.js
Line: 2792

# Last message repeats approximately 53 times.
# End of log.

I hope this has proven to be useful, even if it serves to rule something out
(that is, to discard some possibility which is in the minds of the
developers).

Todo: Do the same procedure with a previous version of Icedove that used to
behave well, in order to check whether the errors presented here are unique
to the upgraded version or not.

Triqel
Offline
Beigetreten: 12/06/2014

Have you experiences with version 38.6?

jdenz
Offline
Beigetreten: 11/18/2011

Thanks again, @ADFENO.

I upgraded to 38.5.0-1~deb7u1+7.0trisquel2 and still have the same error:

"Sending of the message failed.
The message could not be sent using Outgoing server (SMTP) [*****.com] for an unknown reason. Please verify that your Outgoing server (SMTP) settings are correct and try again."

I also tried using Thunderbird and sending from the account I was having problems with worked without problems.

Why isn't this problem happening to more people? Why am I able to send from some accounts but not others? Why does it work on Thunderbird but not Icedove?

Mzee
Offline
Beigetreten: 07/10/2013

I just opened a ticket for this issue. It can be found here:
https://trisquel.info/en/issues/16300

Triqel
Offline
Beigetreten: 12/06/2014

Version 38.5 has been released. Does it fix this problem?

jdenz
Offline
Beigetreten: 11/18/2011

Thanks again, @ADFENO.

I upgraded to 38.5.0-1~deb7u1+7.0trisquel2 and still have the same error:

"Sending of the message failed.
The message could not be sent using Outgoing server (SMTP) [*****.com] for an
unknown reason. Please verify that your Outgoing server (SMTP) settings are
correct and try again."

I also tried using Thunderbird and sending from the account I was having
problems with worked without problems.

Why isn't this problem happening to more people? Why am I able to send from
some accounts but not others? Why does it work on Thunderbird but not
Icedove?

Triqel
Offline
Beigetreten: 12/06/2014

Version 38.6 has been released. Does it fix this problem when the latest upgrades have installed at the same?

Mzee
Offline
Beigetreten: 07/10/2013

I would also like to get an update about this issue. Is it finally solved and safe to upgrade to this version again? Thanks a lot for any feedback.

ADFENO
Offline
Beigetreten: 12/31/2012

Sorry for not answering for a long time. I'had to send my old faithful computer for maintenance/cleanup. Once I get it back with my system back and folders in place, I'll get back to testing.

Jane
Offline
Beigetreten: 09/02/2014

Thank you Adfeno, Sasaki, fbit and everyone!

I have not been able to send emails from my Openmailbox and RiseUp accounts for months. But now I have downgraded Icedove with

sudo apt-get install icedove=31.8.0-1~deb7u1+7.0trisquel2

and it works!

I hope the ticket Mzee opened gets solved so that we can update the software when needed.

SuperTramp83

I am a translator!

Offline
Beigetreten: 10/31/2014

Just a remainder that riseup mail works perfectly fine with TorBB. The old mail interface (squirrel mail) doesn't even need javascript to work.

Jane
Offline
Beigetreten: 09/02/2014

Oh! My Lightning extension (an integrated calendar for Icedove) does not work now, it says it is incompatible with Icedove 31.8.0

Let's wait for the resolution of the ticket
https://trisquel.info/en/issues/16300

lembas
Offline
Beigetreten: 05/13/2010

One can monkey with the compatibility parameters of extensions. Sometimes the declared parameters are too strict and it will work just fine outside of those.

If you wish to try, the .xpi is just an archive you can open with e.g. file-roller. Inside you'll find an install.rdf file which defines among other things maxversion.

pragmatist

I am a member!

Offline
Beigetreten: 03/03/2016

I've had a lot of problems with icedove. It worked for multiple email addresses, then just one, now none!. I haven't worked too hard at fixing it, since there are so many alternatives.

I've used openmailbox with: pine, mutt, evolution, claws-mail, icedove, and geary. I could access it with all of those clients at one point or another.

My solution for now is I use one email client per email address. I'm using geary or evolution for gmail and I'm using claws-mail for openmailbox.

Geary is my favorite as it is clean and simple. However, it crashes randomly unfortunately--segmentation fault. Even when it works, it is a little to light for my taste--I want just a few more features. Lately I'm using geary in XFCE and it hasn't crashed yet. It did crash in several other window managers (fluxbox, i3wm, trisquel)

Several times I've considered getting a different email account because of all of this, and I may still. However, I've already used this email address in several important places and would rather not have to change it.

Has anybody had perfect success with the "web clients"? If not, what problems does it have.

Magic Banana

I am a member!

Offline
Beigetreten: 07/24/2010

I'm using geary or evolution for gmail and I'm using claws-mail for openmailbox.

I have configured two email accounts in Evolution. I used to have three. No problem at all. I have trouble seeing any advantage in using several email clients: more RAM usage, contacts are not shared (are they), etc.

pragmatist

I am a member!

Offline
Beigetreten: 03/03/2016

Thanks. As I said, I was able to get all them to work with two accounts. I found it was buggy, so I chose this method. You are probably right that this would not be a good solution for anybody but me. Works for me though!

Edit: I should mention that I'm intending on getting rid of gmail, so it will be just one client anyway

pragmatist

I am a member!

Offline
Beigetreten: 03/03/2016

What has your experience been with icedove?

Magic Banana

I am a member!

Offline
Beigetreten: 07/24/2010

I have never used it.

pragmatist

I am a member!

Offline
Beigetreten: 03/03/2016

Do you use openmailbox?

Edit: Also, what is your window manager? Are you using the default Trisquel?

Magic Banana

I am a member!

Offline
Beigetreten: 07/24/2010

I do not use openmailbox. I use my university email.

I use Trisquel 7 with GNOME Shell.

Sasaki
Offline
Beigetreten: 08/11/2014

I can see the issue has been opened here in trisquel.info, but has it been done there : https://wiki.debian.org/Icedove#Reporting_Bugs ?

And maybe it comes from the upstream thunderbird ?

By the more, has someone tried to expose the problem to openmailbox maintainer ?

healinghawk
Offline
Beigetreten: 02/15/2016

I don't give a hoot in Hell for anything but getting off this list. I
don't want to go to the effort and wasted time of trying to help fix
it. I just want off. I sent my unsubscribe post but I'm still getting
trisquel posts. The Trisquel mail bomb ruined Thunderbird, so now the
Junk file is the only place that gets mail and when I try to move it, it
is lost. Thanks a lot, whoever did that. I have not filed a bug
report, but my response to having 20MB of mail dumped into my inbox all
at once may have gone in as a bug report. It's not a bug. Whoever runs
the site finally figured out how to make it work, but didn't know how to
prevent what effectively was a DoS attack. I can't use Trisquel due to
being unable to turn off the narrator before I run out of patience, but
it hasn't been a problem until this DoS attack. I regret not
unsubscribing in time to prevent this.

Tommy Tolson

On 04/18/2016 12:07 PM, name at domain wrote:
> I can see the issue has been opened here in trisquel.info, but has it
> been done there : https://wiki.debian.org/Icedove#Reporting_Bugs ?
>
> And maybe it comes from the upstream thunderbird ?
>
> Bt the more, has someone tried to expose the problem to openmailbox
> maintainer ?
>
>