>> >> > That kind of delivery limits the access to this mails to the local >> >> > maschine. If I want to read local I don't need mails, I could just >> >> > read the logfiles from portage in /var/log/ >> >> > >> >> > But I am aware that solving this problem is nothing that portage has >> >> > to do, as it is no problem with portage at all. >> >> > >> >> > My mail was just to show that not everyone has a local mailserver >> >> > running on his maschine. >> >> > >> >> > Greetings >> >> > >> >> > Sebastian >> >> >> >> then let it store everything as elog and read that with elogv. >> >> >> >> mail is just an additional bonus feature. >> > >> > His initial mail said that he would like a copy of elogs to go to his >> > inbox at his ISP. Later mails imply he might want to read them over IMAP >> > so they are accessible at multiple locations. >> > >> > Sebastian, >> > >> > Have you looked at ssmtp? Very light, very small and you can protect your >> > login password with Unix file permissions instead of leaving them open in >> > make.conf >> >> Could I use ssmtp to send elog mail to my email address? I wouldn't >> even need a login password if this is all I use it for, right? > > Yes. > > ssmtp is an email sender, it knows how to talk smtp to receiving servers or to > relays. It doesn't receive mails. > > If the relay you use requires a username/password or ssl, it supports that > too.
So I need a relay somewhere along with ssmtp to get a message to an email address? > [The receiving smtp server likely does not require a username/password, but it > is equally likely to not accept connection direct from you, hence you should > use your ISPs mail relay] I likely can't use my ISP's mail relay when traveling, right? - Grant
