On Wednesday 08 February 2006 00:58, Bo Andresen wrote: > On Tuesday 07 February 2006 23:32, Bo Andresen wrote: > > > Your mail problem is addressed at > > > http://bugs.gentoo.org/show_bug.cgi?id=116637 > > > > Before I close this thread (now that I can get mails using the custom > > module), I would like to know whether someway knows an easy way in which > > to apply the patch proposed in the bug #116637? > > Now (I think) I figured out how to patch it. Just copied the > portage-2.1_pre4-r1 to an overlay, downloaded the patch to FILESDIR, added > the following line to src_unpack() and reemerged portage. > > patch ${WORKDIR}/${PN}-${PV}/pym/elog_modules/mod_mail.py > ${FILESDIR}/mod_mail.patch > > It doesn't solve the problem at home though. As I understand it the error > message: > > "!!! An error occured while trying to send > logmail:\n{'[EMAIL PROTECTED]': (504, '<portage>: Sender address > rejected: need fully-qualified address')}" > > is the result of hostname -d returning nothing? I don't know how to solve > that problem. Tomorrow will show whether the patch solves the problem at > the universitet network where hostname -d does return a hostname that has > been set up correctly be the dhcp server.
>From http://bugs.gentoo.org/show_bug.cgi?id=116637#c2 """ this bug hit me too, however i was not able to fix it with your patch. i think this is because of line 48 in mod_mail.py: myconn.sendmail("portage", myrecipient, mymessage.as_string()) as you see, portage is still hardcoded there. I replaced it with "[EMAIL PROTECTED]" and got my mails :) """ The system sends the mail to "portage", but it requires a FQDN. It seems this is not automatically expanded to "portage@<localdomain>" So I doubt hostname -d has any effect on it, but I haven't actually checked the code). You could do the same as Simon and replace "portage" with a valid email address untill this is fixed. -- gentoo-user@gentoo.org mailing list