SABnzbd Forums

sander wrote: 91 10.302784 195.241.79.132 192.168.178.32 SMTP S: 554 SMTP synchronization error

This will be very hard to diagnose as I don't get it with any mail server so far.
This doesn't happen when you have just one recipient?
Does it happen in the first or the last email?
What if there are three?

rembo10 wrote: I'm on OS X if it makes a difference.
is using the whole email address field as the $to variable within the email

OSX makes no difference, I'll test it explicitly, but I'm quite sure.
The $to variable is correct, it holds just one address.
Easy to check if you would use it again in the email body.

with one mail destination, the error happens, but ... at the beginning of the smtp session. 

FWIW: the client (so: SABnzbd) starts by sending a strange line with 'binary' characters. I've never seen that in SMTP sessions.

see screendump.

Most of this is going on inside Python's email library, so that would be bad news.
I assume you're not using SSL email?

shypike wrote: Most of this is going on inside Python's email library, so that would be bad news.
I assume you're not using SSL email?

I have not selected SSL email (is that possible at all?)

sander wrote: I have not selected SSL email (is that possible at all?)

You cannot select it, but SABnzbd will first try an SSL connection.
If that fails, it will use a plain connection.
You should be able to see it in the (debug) logging.

I tried it using smtp.gmail.com with my username & pw, still the same problem. This was with the stock template.

My own Wireshark sessions show nothing wrong.
I think it must be ISP specific.

Did you guys try GMail with server smtp.gmail.com:587 ?

Just tried with gmail.smtp.com:587, same problem

My settings are:

Email Notification on Job Completion: Always
Email Templates Folder:

SMTP Server: smtp.gmail.com:587
Email Recipient: [email protected], [email protected]
Email Sender: [email protected]
User Name: [email protected]
Password: **********

I will try to monitor it with wireshark - I've never used it before so I'm not really sure what to look for / what's relevant

Thanks for looking into this though, your program is amazing

Wireshark isn't easy, especially setting up filtering.
What I did was set a scheduled "pause-post processing" in the past.
This will make SABnzbd delay post processing.
Download a small job until it's in the History waiting to be post-processed.
Start Wireshark and start a capture. Note that Wireshark probably needs sudo.
Remove the "pause" from the scheduler.
Wait for the email to be sent and then stop Wireshark's capture.
Look for any error messages.

One problem is that SABnzbd will always try to use SSL (and non-optional for GMail), which largely defeats Wireshark.

I'll try again on OSX (didn't test this email issue on it yet).

Works fine on my Mac Mini too.