Not sure if these are supported at all or not but I have some troubles setting up the ssmtp service from unmenu.

 

I've set all my settings and checked them like 10 times so that casing, password etc is not faulty.

 

My settings are basically:

 

YOUR_EMAIL_ACCT="[email protected]"
EMAIL_HUB="smtp.gmail.com:587"
USE_TLS="YES"
AUTH_USER="secondary.account"
AUTH_PASS="secret"
MAIL_DOMAIN="[email protected]"
FROM_LINE_OVERRIDE="YES"
REWRITE_DOMAIN=""

 

Whenever i log onto the machine and try sending the test mail all I get back is:

Mail being sent to root.  With any luck, it will be forwarded properly.
send-mail: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 d12sm2081439bkw.19)

 

I go there and visit http://www.google.com/accounts/DisplayUnlockCaptcha from my normal comp (my comp and the unraid server share external IP anyway) and unlock [email protected] with password and captcha. Still the error above won't go away.

 

When you save those settings, they are saved in

/usr/local/etc/ssmtp/ssmtp.conf

 

Look there to see if they have been saved correctly.  It should look like this:

 

[email protected]

mailhub=smtp.gmail.com:587

hostname=localhost

UseSTARTTLS=YES

AuthUser=my_email

AuthPass=my_password

FromLineOverride=YES

 

works just fine.

 

To debug, invoke ssmtp directly as in this example

echo -e "Subject: another test\n\nThis is the email body." | ssmtp -d root

 

It will show the interactive communications with the email provider.

If I log into the server with putty and copy paste AuthUser and AuthPass into a gmail login window I get in just fine.

 

However if I invoke smtp directly I get this log:

root@SICILY:/usr/local/etc/ssmtp# echo -e "Subject: another test\n\nThis is the email body." | ssmtp -d root
[<-] 220 mx.google.com ESMTP t10sm2120659bkj.16
[->] EHLO [email protected]
[<-] 250 ENHANCEDSTATUSCODES
[->] STARTTLS
[<-] 220 2.0.0 Ready to start TLS
[->] EHLO [email protected]
[<-] 250 ENHANCEDSTATUSCODES
[->] AUTH LOGIN
[<-] 334 WXNlcm7hbWU6
[->] dHJhY2tlci5yZVTtaW6l
[<-] 334 YGDzC3dvcmQ6
[<-] 535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 t10sm2120659bkj.16
ssmtp: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 t10sm2120659bkj.16)

 

 

and a cat of /usr/local/etc/ssmtp/ssmtp.conf give this:

[email protected]
mailhub=smtp.gmail.com:587
[email protected]
UseSTARTTLS=YES
AuthUser=don.unraid
AuthPass=secret
FromLineOverride=YES

 

And no the password in there is not secret for real I changed that but I've checked for trailing spaces and I've tried the copy paste in my browser from this file and it works flawlessly

 

are you saying it now works? (with the edited version of ssmtp.conf ? )

Oh sorry, no.

 

The debug output above still ends with: ssmtp: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 t10sm2120659bkj.16)

 

On a side note I can't get vi to conform with my keyboard and pressing for example [END] changes casing on the current character and [DEL] changes casing on the character before the inputmarker etc. That made for some interesting rewrites of the file before I got it right

It sounds as if you've still got it wrong...

 

Use the editor build into

mc

if vi is beyond you.

The DEL and END keys on the keyboard have never been mapped on any version I've ever used (with perhaps the window's "vim" version as an exception, but I've never tried those keys in vim, as I know real "vi" commands )

Never really used vi, always went with vim (now also thanks to you ). There is a cat of the conf file (/usr/local/etc/ssmtp/ssmtp.conf) above, in my head that would send a mail to [email protected] via gmails smtp using the [email protected] account.

 

As I wrote using for example putty to visit the server and by copying and pasting the AuthUser + AuthPass I get into the gmail account just fine and can send messages. don.unraid is working just fine for gitosis, svn, redmine etc to send and receive with for so I don't see why it would mess this time. Perhaps it's used too much for google to approve but I find that hard to believe.

Found the error so just gonna write it here for those who encounters it.

 

ssmtp does not work for gmail if your gmail password has space

Found the error so just gonna write it here for those who encounters it.

 

ssmtp does not work for gmail if your gmail password has space

glad you figured it out.

Another "informative" post (mostly for those running into the same problem in the future): I now also know that # and some other chars frakks ssmtp on unraid up if you're trying to use gmail.

Thank you so much!  Sorry to bring the thread back from nowhere, but I was having this issue and just couldn't figure it out... turns out its all about the passwords' inclusion of special characters.  Might need to get a "disposable" account setup with a weak password.