On Sun, 5 Sep 2010 10:14:18 +0100 Stroller wrote: > > On 4 Sep 2010, at 15:32, Neil Bothwick wrote: > > On Sat, 4 Sep 2010 12:15:01 +0100, Stroller wrote: > > > >>> Needed to use: > >>> > >>> PORTAGE_ELOG_MAILURI="[email protected] mymailserver.com" > >> > >> I've got it without that, Portage 2.1.8.3. > >> > >> $ grep ELOG /etc/make.conf > >> PORTAGE_ELOG_CLASSES="warn error log" > >> PORTAGE_ELOG_SYSTEM="save mail" > >> PORTAGE_ELOG_MAILURI="root" > >> PORTAGE_ELOG_MAILFROM="port...@hex" > >> $ > >> > >> Works fine here. > > > > Are you running a mailserver on localhost? > > Well, David's problem is SOLVED now, so I'm not sure that it > matters, but yes. > > I assumed he would also have to be running a sendmail-replacement > for the example he gave to work: > > > echo "testing [email protected]" | \ > > mail -s"testing [email protected]" [email protected] > > I kinda assumed his problem was that `mail` would provide a valid > sender address, whereas the upstream ISP might reject mails from > portage with a dodgy from address. > > Stroller. >
OP here ... Having my own domain, I run my own mailserver -- but it's not on my gentoo development machine. I read the emerge python code, specifically mail.py, to find how PORTAGE_ELOG_MAILURI is handled. Reading the code lead me to (finally) realize that I need to have a PORTAGE_ELOG_MAILURI value with two (2) fields separated by a space character. David
