On 22/10/08 18:17:21, Jonathan wrote: > Problem: > I can't send email using this system. I have to use > a work around from KMail (set up like I had it before > all this, just simple POP3 client). This means I can't > send emails from my computer over the net. I think > port 25 is blocked, so It needs to take the email > (which does appear in the sent folder) and then pump it > up to the ISP with SMTP. Seems to be plenty of people > saying that is what needs to happen, but no one who is > willing to explain how that actually works, with any > recent setup. > Any ideas?
G'day Jon, What you need is an application that relays to your upstream MX server. I have used, and still use, both msmtp and EMail-Relay for this exact purpose. I use msmtp for sending a single mail and I use EMail-Relay for sending out batched mail. Msmtp works in the usual way: message body from stdin, a config file, miscellaneous command-line switches and arguments, output to upsteam MX server. EMail-Relay was set up to ease the task of adding corporate disclaimers etc (hiss, boo) and is best used to flush an "outbound" mail queue. It has a second executable which adds the mail to the queue. Msmtp is one of the better examples of "take a message as input and send it on its way" whereas EM-R works well in daemon mode. While there are many alternatives to msmtp the only real alternatives to EM-R are nullmailer (which can be a bear to set up) and masqmail (which I have not used but once saw recommended on the lkml). Both msmtp and EM-R will handle the usual methods of authentication with the upstream MX server. HTH, Robert Thorsby It is impossible to make anything foolproof because fools are ingenious. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
