1 |
On Sun, 5 Sep 2010 10:14:18 +0100 |
2 |
Stroller wrote: |
3 |
|
4 |
> |
5 |
> On 4 Sep 2010, at 15:32, Neil Bothwick wrote: |
6 |
> > On Sat, 4 Sep 2010 12:15:01 +0100, Stroller wrote: |
7 |
> > |
8 |
> >>> Needed to use: |
9 |
> >>> |
10 |
> >>> PORTAGE_ELOG_MAILURI="userid@××××××××.com mymailserver.com" |
11 |
> >> |
12 |
> >> I've got it without that, Portage 2.1.8.3. |
13 |
> >> |
14 |
> >> $ grep ELOG /etc/make.conf |
15 |
> >> PORTAGE_ELOG_CLASSES="warn error log" |
16 |
> >> PORTAGE_ELOG_SYSTEM="save mail" |
17 |
> >> PORTAGE_ELOG_MAILURI="root" |
18 |
> >> PORTAGE_ELOG_MAILFROM="portage@hex" |
19 |
> >> $ |
20 |
> >> |
21 |
> >> Works fine here. |
22 |
> > |
23 |
> > Are you running a mailserver on localhost? |
24 |
> |
25 |
> Well, David's problem is SOLVED now, so I'm not sure that it |
26 |
> matters, but yes. |
27 |
> |
28 |
> I assumed he would also have to be running a sendmail-replacement |
29 |
> for the example he gave to work: |
30 |
> |
31 |
> > echo "testing userid@××××××××.com" | \ |
32 |
> > mail -s"testing userid@××××××××.com" userid@××××××××.com |
33 |
> |
34 |
> I kinda assumed his problem was that `mail` would provide a valid |
35 |
> sender address, whereas the upstream ISP might reject mails from |
36 |
> portage with a dodgy from address. |
37 |
> |
38 |
> Stroller. |
39 |
> |
40 |
|
41 |
OP here ... |
42 |
|
43 |
Having my own domain, I run my own mailserver -- but it's not on my |
44 |
gentoo development machine. I read the emerge python code, |
45 |
specifically mail.py, to find how PORTAGE_ELOG_MAILURI is handled. |
46 |
Reading the code lead me to (finally) realize that I need to have a |
47 |
PORTAGE_ELOG_MAILURI value with two (2) fields separated by a space |
48 |
character. |
49 |
|
50 |
David |