| 1 |
On 4 Sep 2010, at 15:32, Neil Bothwick wrote: |
| 2 |
> On Sat, 4 Sep 2010 12:15:01 +0100, Stroller wrote: |
| 3 |
> |
| 4 |
>>> Needed to use: |
| 5 |
>>> |
| 6 |
>>> PORTAGE_ELOG_MAILURI="userid@××××××××.com mymailserver.com" |
| 7 |
>> |
| 8 |
>> I've got it without that, Portage 2.1.8.3. |
| 9 |
>> |
| 10 |
>> $ grep ELOG /etc/make.conf |
| 11 |
>> PORTAGE_ELOG_CLASSES="warn error log" |
| 12 |
>> PORTAGE_ELOG_SYSTEM="save mail" |
| 13 |
>> PORTAGE_ELOG_MAILURI="root" |
| 14 |
>> PORTAGE_ELOG_MAILFROM="portage@hex" |
| 15 |
>> $ |
| 16 |
>> |
| 17 |
>> Works fine here. |
| 18 |
> |
| 19 |
> Are you running a mailserver on localhost? |
| 20 |
|
| 21 |
Well, David's problem is SOLVED now, so I'm not sure that it matters, |
| 22 |
but yes. |
| 23 |
|
| 24 |
I assumed he would also have to be running a sendmail-replacement for |
| 25 |
the example he gave to work: |
| 26 |
|
| 27 |
> echo "testing userid@××××××××.com" | \ |
| 28 |
> mail -s"testing userid@××××××××.com" userid@××××××××.com |
| 29 |
|
| 30 |
I kinda assumed his problem was that `mail` would provide a valid |
| 31 |
sender address, whereas the upstream ISP might reject mails from |
| 32 |
portage with a dodgy from address. |
| 33 |
|
| 34 |
Stroller. |
Archives