[workaround found] Evolution won't authenticate on SMTP

acidicX · 2014-10-17 07:40:59

Hi there,

since the gnome update yesterday, evolution won't use any SMTP auth when sending emails. This basically means I cannot send emails with evolution. Anyone else having the same problem?

Cheers,
acidicX

Last edited by acidicX (2014-10-19 13:00:49)

Henry78 · 2014-10-17 15:02:46

Yes, same problem here. Tried it with two differen SMTP accounts. Both accounts need SMPT authentication. Verified sending and settings using Thunderbird.

[update]
Looks like the password for SMTP auth isn't fetched from keyring. Sending fails with "Authentication required"

[update 2]
I deleted all evolution passwords from gnome-keyring. Created a fresh account.
Password is stored in keyring upon account update (recieve).

This is logged, if I start evolution with CAMEL_DEBUG="smtp"

sending : EHLO abel

(evolution:10537): camel-WARNING **: CamelSmtpTransport::authenticate_sync() reported failure without setting its GError
sending : MAIL FROM:<henry78@gmx.at>
sending : QUIT
received: 221 gmx.com Service closing transmission channel

Last edited by Henry78 (2014-10-17 15:16:13)

Henry78 · 2014-10-17 15:05:37

There's no report in Arch-bugzilla yet, Gnome-bugzilla is not reachabel atm ...

Last edited by Henry78 (2014-10-17 15:07:49)

acidicX · 2014-10-17 15:26:43

I'm getting the same:

(evolution:3727): camel-WARNING **: CamelSmtpTransport::authenticate_sync() reported failure without setting its GError

I've checked the gnome bugzilla a few hours ago, there was no report there at that time.

Henry78 · 2014-10-17 15:37:42

I'll create one if Gnome bugzilla is available again.

Just wondering that we're only two users reporting this problem.

acidicX · 2014-10-17 15:44:08

I'm wondering why evolution didn't get a bump too (to 3.14), it might be an Arch issue?

I've just opened one on the arch bugtracker to be sure this is an upstream problem:
https://bugs.archlinux.org/task/42423

Henry78 · 2014-10-17 15:45:08

No, there isn't an upstream version either, see ftp://ftp.gnome.org/pub/gnome/sources/evolution/

acidicX · 2014-10-17 15:46:22

well there is a 3.13 one... on Arch it's still on 3.12
ftp://ftp.gnome.org/pub/gnome/sources/evolution/3.13/

Henry78 · 2014-10-17 15:47:12

Gnome uses odd numbers for development versions. And even numbers for stable versions. At the time Gnome 3.14 was released, evolution bumped to 3.12.7

Last edited by Henry78 (2014-10-17 15:47:58)

acidicX · 2014-10-17 15:48:34

Oh all right. Didn't know that! But maybe it's already fixed in the dev version?

vanquish · 2014-10-17 18:14:56

same problem here. very annoying. can't send any email. even a downgrade of evolution didn't work.

dmesg:

evolution[1275]: segfault at b24 ip 0000xxxxxxx sp 0000xxxxxxx error 4 in libglib-2.0.so.0.4200.0[xxxxxx+10c000]

maybe it's library related. -.-

i'll try the dev branch of gnome ... in the next few days ... i have to send emails ... not just whatsapp. oO

acidicX · 2014-10-18 10:12:04

tim pointed out on the bugtracker that changing from LOGIN to PLAIN as SMTP auth method works as a workaround.
It also works on my end. PLAIN seems to be the better choice anyhow, as it does one step less compared to LOGIN (and both use no encryption anyway).
As my SMTP supports both PLAIN and LOGIN auth methods, I still consider this a bug though.

Henry78 · 2014-10-18 10:18:19

Confirmed, that changing SMTP auth from LOGIN to PLAIN circumvents this problem.

whompus · 2014-10-18 10:43:04

My mail provider disabled SSL 3.0 so probably related to that. More info here

http://blog.fastmail.fm

vanquish · 2014-10-18 12:55:44

acidicX wrote:

tim pointed out on the bugtracker that changing from LOGIN to PLAIN as SMTP auth method works as a workaround.
It also works on my end. PLAIN seems to be the better choice anyhow, as it does one step less compared to LOGIN (and both use no encryption anyway).
As my SMTP supports both PLAIN and LOGIN auth methods, I still consider this a bug though.

this workaround saved me a lot of time. thank you for this information.

acidicX · 2014-10-19 12:59:50

whompus wrote:

My mail provider disabled SSL 3.0 so probably related to that. More info here
http://blog.fastmail.fm

No I don't think it is related. First, I was sending emails just before the Evo/Gnome update and directly after it (and then the error occured). I don't think that both of my SMTP providers did their openssl update at exactly the same time.
Second, and more importantly, the LOGIN or PLAIN signin comes after the TLS negotiation, so if TLS would fail there would be another error, and PLAIN would not work either.

@vanquish you're welcome

jlp2 · 2014-10-20 08:30:02

It seem there is a Fix Upstream

https://bugzilla.redhat.com/show_bug.cgi?id=1153385

Last edited by jlp2 (2014-10-20 12:14:05)

jancici · 2014-10-20 12:23:18

well, I have problems to send out emails from evolution too.
but my problem is that my public IP has not reverse hostname.

this is a message:
the reported error was "RCPT TO ......@....... failed: Client host rejected: cannot find your reverse hostname [my public IP]

later I find out that if I switch off ssl/tls and setup plain password I can send email.
in case that I have ssl/tlc on and plain pass I am getting error "an unexpected TLS packet was received"

panchtatvam · 2014-10-22 17:46:01

acidicX wrote:

tim pointed out on the bugtracker that changing from LOGIN to PLAIN as SMTP auth method works as a workaround.
It also works on my end. PLAIN seems to be the better choice anyhow, as it does one step less compared to LOGIN (and both use no encryption anyway).
As my SMTP supports both PLAIN and LOGIN auth methods, I still consider this a bug though.

हाँ । केवल सादे का प्रयोग करने पर कार्य करता है मेरा जीमेल खाता ।

Yeah. Only in plain mode does my Gmail account works.

jancici · 2014-11-04 15:37:40

It is bit strange
I have new PC so I have fresh instalation of evolution and this is not a problem. I can send email over smtp with SSL and encrupted pass.
On old PC I have still problem with sending, I need to use smtp without SSL.

any idea?

Arch Linux

#1 2014-10-17 07:40:59

[workaround found] Evolution won't authenticate on SMTP

#2 2014-10-17 15:02:46

Re: [workaround found] Evolution won't authenticate on SMTP

#3 2014-10-17 15:05:37

Re: [workaround found] Evolution won't authenticate on SMTP

#4 2014-10-17 15:26:43

Re: [workaround found] Evolution won't authenticate on SMTP

#5 2014-10-17 15:37:42

Re: [workaround found] Evolution won't authenticate on SMTP

#6 2014-10-17 15:44:08

Re: [workaround found] Evolution won't authenticate on SMTP

#7 2014-10-17 15:45:08

Re: [workaround found] Evolution won't authenticate on SMTP

#8 2014-10-17 15:46:22

Re: [workaround found] Evolution won't authenticate on SMTP

#9 2014-10-17 15:47:12

Re: [workaround found] Evolution won't authenticate on SMTP

#10 2014-10-17 15:48:34

Re: [workaround found] Evolution won't authenticate on SMTP

#11 2014-10-17 18:14:56

Re: [workaround found] Evolution won't authenticate on SMTP

#12 2014-10-18 10:12:04

Re: [workaround found] Evolution won't authenticate on SMTP

#13 2014-10-18 10:18:19

Re: [workaround found] Evolution won't authenticate on SMTP

#14 2014-10-18 10:43:04

Re: [workaround found] Evolution won't authenticate on SMTP

#15 2014-10-18 12:55:44

Re: [workaround found] Evolution won't authenticate on SMTP

#16 2014-10-19 12:59:50

Re: [workaround found] Evolution won't authenticate on SMTP

#17 2014-10-20 08:30:02

Re: [workaround found] Evolution won't authenticate on SMTP

#18 2014-10-20 12:23:18

Re: [workaround found] Evolution won't authenticate on SMTP

#19 2014-10-22 17:46:01

Re: [workaround found] Evolution won't authenticate on SMTP

#20 2014-11-04 15:37:40

Re: [workaround found] Evolution won't authenticate on SMTP

Board footer