| 1 |
On Mon, 6 Sep 2010 11:32:16 +0100 |
| 2 |
Stroller wrote: |
| 3 |
|
| 4 |
> |
| 5 |
> On 5 Sep 2010, at 17:54, David Relson wrote: |
| 6 |
> >> ... |
| 7 |
> >>>>> I've got it without that, Portage 2.1.8.3. |
| 8 |
> >>>>> |
| 9 |
> >>>>> $ grep ELOG /etc/make.conf |
| 10 |
> >>>>> PORTAGE_ELOG_CLASSES="warn error log" |
| 11 |
> >>>>> PORTAGE_ELOG_SYSTEM="save mail" |
| 12 |
> >>>>> PORTAGE_ELOG_MAILURI="root" |
| 13 |
> >>>>> PORTAGE_ELOG_MAILFROM="portage@hex" |
| 14 |
> >>>>> $ |
| 15 |
> >>>>> |
| 16 |
> >>>>> Works fine here. |
| 17 |
> >> |
| 18 |
> >> I assumed he would also have to be running a sendmail-replacement |
| 19 |
> >> for the example he gave to work: |
| 20 |
> >> |
| 21 |
> >>> echo "testing userid@××××××××.com" | \ |
| 22 |
> >>> mail -s"testing userid@××××××××.com" userid@××××××××.com |
| 23 |
> >> |
| 24 |
> >> I kinda assumed his problem was that `mail` would provide a valid |
| 25 |
> >> sender address, whereas the upstream ISP might reject mails from |
| 26 |
> >> portage with a dodgy from address. |
| 27 |
> >> ... |
| 28 |
> > |
| 29 |
> > OP here ... |
| 30 |
> > |
| 31 |
> > Having my own domain, I run my own mailserver -- but it's not on my |
| 32 |
> > gentoo development machine. I read the emerge python code, |
| 33 |
> > specifically mail.py, to find how PORTAGE_ELOG_MAILURI is handled. |
| 34 |
> > Reading the code lead me to (finally) realize that I need to have a |
| 35 |
> > PORTAGE_ELOG_MAILURI value with two (2) fields separated by a space |
| 36 |
> > character. |
| 37 |
> |
| 38 |
> What version of portage, please? I certainly don't have that here, |
| 39 |
> and it seems to be working. |
| 40 |
> |
| 41 |
> Stroller. 2.2_rc75 |
| 42 |
|
| 43 |
I'm running the latest and greatest 2.2_rc7. Are you running a mail |
| 44 |
server on your local machine? My not doing so is why I need the space. |
Archives