Chris T wrote: > Yup. That seemed to work fine, although I'm struggling to get the > authentication to work with the postfix relay. Do you happen to know if > you need to compile from source with auth built in if you want > authentication to work. The docs are a little... basic
I honestly do not know, since I've never tried to do authN SMTP with it. It also looks like it only supports LOGIN and CRAM-MD5 according to the man page, so I can't really test it as our SMTP server doesn't do either of those. Try this, though: /usr/sbin/ssmtp -auUSERNAME -apPASSWORD root Enter some data and hit enter twice to end. For me, this spat out the error: ssmtp: Server didn't accept AUTH LOGIN (504 5.3.3 AUTH mechanism LOGIN not available) Maybe it'll give you something equally useful. Hopefully, if it's compiled without authN support, it'll complain about that. You may also want to do: export HISTCONTROL=ignorespace first. If you then put a space before /usr/sbin/ssmtp it won't save that command in your shell history, so your password won't be written in your history file for anyone with the right perms to see. Mmmmmm. bash. > Thanks for your help Sure thing. Sorry I can't be of more assistance, but I suspect that ssmtp is supposed to solve a very simple problem and thus doesn't offer much in the way of advanced SMTP capabilities. If you can't get it to do this, I'd suggest looking into setting up Postfix as a satellite host and not listening on port 25 for the world to hit. Thanks, Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
