Page 1 of 1
Warning logged when sending email. 0.5.0 beta 1
Posted: December 9th, 2009, 2:45 pm
by wiggy9906
I have installed 0.5.0b1 over 0.4.12 (Vista x64). When a download completes it's configured to send an email.
The email is sent and recieved in my inbox but the error "2009-12-09 18:58:59,700 ERROR: Failed to send e-mail" is placed in the warning logs.
The same error is produced when clicking "test email". The test email is received in my inbox. I'm using my ISPs mail server with no authentication. I have not altered any settings since updating 0.4.12
Not a problem as the mail is received. But just wondering if it's my setup or a bug in 0.5.0b1
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 9th, 2009, 2:51 pm
by shypike
Very strange, I have never seen it and I send emails for everything.
Through my ISP and gmail.
On the other hand there are so many ISP and so many ways
to tweak email protocols that we cannot test all.
Maybe it's better not to issue warning or errors about this,
but you would also like to know if notification went wrong.
Do do have any more details.
Could you try to set logging to "debug", try a test email
and email the log files?
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 9th, 2009, 3:05 pm
by wiggy9906
Hi Shypike,
Thanks for your reply.
I have changed log level to debug and sent another test mail. Here's the output to the log file.
Code: Select all
2009-12-09 19:56:19,759::INFO::[interface:2505] Sending testmail
2009-12-09 19:56:19,779::INFO::[email:55] Connecting to server smtp.ntlworld.com:25
2009-12-09 19:56:21,842::DEBUG::[email:68] Non-SSL mail server detected reconnecting to server smtp.ntlworld.com:25
2009-12-09 19:56:28,102::ERROR::[email:106] Failed to send e-mail
Anything else I can do the assist?
EDIT - Just to confirm I did receive the email.
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 9th, 2009, 3:48 pm
by wiggy9906
I have used telnet to send an email to see the responses from the mail server.
C:\telnet smtp.ntlworld.com 25
220 ESMTP server ready
HELO test.local
250 aamtaout03-winn.ispmail.ntl.com
MAIL FROM: [email protected]
250 Sender Ok
RCPT TO: [email protected]
250 Recipient Ok
DATA
354 Ok Send data ending with .
test message
.
250 Message received:
[email protected]
After the
. there is a 10 second delay before the 250 Message received is shown. The logs show that the Failed to send e-mail message is logged after 7 seconds.
Could it be that sabnzbd is not waiting long enough for a response from the server?
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 9th, 2009, 5:10 pm
by shypike
Don't you think 10 seconds is a bit outrageous?
How long are we supposed to wait?
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 9th, 2009, 6:13 pm
by wiggy9906
I think the delay is while the mail runs is run through the spam checks. Has the time it waits changed from 0.4.12 to 0.5.1b2? Perhaps the update is a coincidence and there's a problem with the SMTP servers. I'll try again tomorrow. Failing that I can always use gmail rather than my ISP servers.
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 10th, 2009, 2:51 am
by shypike
The email code hasn't really changed between 0.4.12 and 0.5.0.
At least nothing relating to the actual email protocol.
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 10th, 2009, 6:43 pm
by switch
Found an issue with the global timeout being set to 4 seconds (from 120!). This may be the cause of your problem.
The fix should be in the next beta (beta4+)
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 11th, 2009, 4:03 am
by wiggy9906
great news. Thanks for looking at this.
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: December 19th, 2009, 10:38 am
by wiggy9906
I can confirm the warning is no longer generated in 0.5.0b4.
Re: Warning logged when sending email. 0.5.0 beta 1
Posted: January 12th, 2010, 9:18 am
by Clay
I actually got this several times last night. I'm also using GMail - I'll turn on debugging, see if I get the details on what caused it.