[gentoo-user] problem with PORTAGE_ELOG_MAILURI

[gentoo-user] problem with PORTAGE_ELOG_MAILURI

[David Relson]

I'm trying to setup mailing of emerge logs, but it's failing for
reasons I don't grasp. 

In /etc/make.conf I have the following:

PORTAGE_ELOG_MAILURI="userid@mydomain.com"

Running emerge, for example "emerge -1 uptimed" give the following
message:

!!! A network error occured while trying to send logmail:
[Errno 111] Connection refused
Sure you configured PORTAGE_ELOG_MAILURI correctly?

As a test, from a bash command line I have run:

echo "testing userid@mydomain.com" | \
mail -s"testing  userid@mydomain.com" userid@mydomain.com

The command line test works fine which indicates that the value of
PORTAGE_ELOG_MAILURI is correct.  However emerge is giving the message
shown above. 

Any thoughts on what I've done wrong?

Regards,

David

[gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[David Relson]

Needed to use:

PORTAGE_ELOG_MAILURI="userid@mydomain.com mymailserver.com"

On Fri, 3 Sep 2010 21:01:24 -0400
David Relson wrote:

> I'm trying to setup mailing of emerge logs, but it's failing for
> reasons I don't grasp. 
> 
> In /etc/make.conf I have the following:
> 
> PORTAGE_ELOG_MAILURI="userid@mydomain.com"
> 
> Running emerge, for example "emerge -1 uptimed" give the following
> message:
> 
> !!! A network error occured while trying to send logmail:
> [Errno 111] Connection refused
> Sure you configured PORTAGE_ELOG_MAILURI correctly?
> 
> As a test, from a bash command line I have run:
> 
> echo "testing userid@mydomain.com" | \
> mail -s"testing  userid@mydomain.com" userid@mydomain.com
> 
> The command line test works fine which indicates that the value of
> PORTAGE_ELOG_MAILURI is correct.  However emerge is giving the message
> shown above. 
> 
> Any thoughts on what I've done wrong?
> 
> Regards,
> 
> David

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[Stroller]

On 4 Sep 2010, at 04:53, David Relson wrote:

> Needed to use:
>
> PORTAGE_ELOG_MAILURI="userid@mydomain.com 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="portage@hex"
$

Works fine here.

Stroller.

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[Stroller]

On 4 Sep 2010, at 12:15, Stroller wrote:
> On 4 Sep 2010, at 04:53, David Relson wrote:
>
>> Needed to use:
>>
>> PORTAGE_ELOG_MAILURI="userid@mydomain.com 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="portage@hex"
> $
>
> Works fine here.

Ooops. Didn't see your subject "solved".

Stroller.

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 510 bytes --]

On Sat, 4 Sep 2010 12:15:01 +0100, Stroller wrote:

> > Needed to use:
> >
> > PORTAGE_ELOG_MAILURI="userid@mydomain.com 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="portage@hex"
> $
> 
> Works fine here.

Are you running a mailserver on localhost?


-- 
Neil Bothwick

If you can't be kind, be vague.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[Stroller]

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="userid@mydomain.com 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="portage@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 userid@mydomain.com" | \
> mail -s"testing  userid@mydomain.com" userid@mydomain.com

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.

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[David Relson]

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="userid@mydomain.com 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="portage@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 userid@mydomain.com" | \
> > mail -s"testing  userid@mydomain.com" userid@mydomain.com
> 
> 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

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[Alex Schuster]

David Relson writes:

> 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.

There is some documentation in /usr/share/portage/config/make.conf.example:

# PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
#                       module. In most cases listing the recipient address and
#                       the receiving mailserver should be sufficient, but you can
#                       also use advanced settings like authentication or TLS. The
#                       full syntax is:
#                           address [[user:passwd@]mailserver[:port]]
#                       where
#                           address:    recipient address
#                           user:       username for smtp auth (defaults to none)
#                           passwd:     password for smtp auth (defaults to none)
#                           mailserver: smtp server that should be used to deliver
                                        the mail (defaults to localhost)
#                                       alternatively this can also be a the path to a
                                        sendmail binary if you don't want to use smtp
#                           port:       port to use on the given smtp server (defaults
                                        to 25, values > 100000 indicate that starttls
                                        should be used on (port-100000))
#                       Examples:
#PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
#PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain)
#PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader exercise ;)

	Wonko

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[Stroller]

On 5 Sep 2010, at 17:54, David Relson wrote:
>> ...
>>>>> 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="portage@hex"
>>>>> $
>>>>>
>>>>> Works fine here.
>>
>> I assumed he would also have to be running a sendmail-replacement
>> for the example he gave to work:
>>
>>> echo "testing userid@mydomain.com" | \
>>> mail -s"testing  userid@mydomain.com" userid@mydomain.com
>>
>> 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.
>> ...
>
> 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.

What version of portage, please? I certainly don't have that here, and  
it seems to be working.

Stroller.

Re: [gentoo-user] SOLVED: problem with PORTAGE_ELOG_MAILURI

[David Relson]

On Mon, 6 Sep 2010 11:32:16 +0100
Stroller wrote:

> 
> On 5 Sep 2010, at 17:54, David Relson wrote:
> >> ...
> >>>>> 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="portage@hex"
> >>>>> $
> >>>>>
> >>>>> Works fine here.
> >>
> >> I assumed he would also have to be running a sendmail-replacement
> >> for the example he gave to work:
> >>
> >>> echo "testing userid@mydomain.com" | \
> >>> mail -s"testing  userid@mydomain.com" userid@mydomain.com
> >>
> >> 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.
> >> ...
> >
> > 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.
> 
> What version of portage, please? I certainly don't have that here,
> and it seems to be working.
> 
> Stroller. 2.2_rc75

I'm running the latest and greatest 2.2_rc7.  Are you running a mail
server on your local machine?  My not doing so is why I need the space.