public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PORTAGE_ELOG error
Date: Tue, 25 Jul 2006 22:38:42 +0200	[thread overview]
Message-ID: <44C68152.9090108@mid.email-server.info> (raw)
In-Reply-To: <200607252120.48575.michaelkintzios@gmail.com>

Mick schrieb:
> On Tuesday 25 July 2006 19:42, Alexander Skwar wrote:
>> Grant schrieb:
>> >> >  I thought this
>> >> > thread was saying using SMTP was optional.
>> >>
>> >> You misunderstood. This thread was about, *WHERE* SMTP is used.
>> >> IMO, it's wrong that portage even CAN use SMTP. But nearly always,
>> >> you'll need to use some SMTP server to get your mail out. But
>> >> with the /usr/sbin/sendmail interface, it's conceivable to send
>> >> out the mail WITHOUT the use of SMTP (eg. if the mail is sent from
>> >> the host with UUCP).
>> >
>> > Can I set my portage elog mail to be sent with UUCP?
>>
>> Yes, by employing a sending program, which can do UUCP. /usr/sbin/sendmail
>> could be such a programm.
> 
> Is there some way of sending such messages to a local MUA without them leaving 
> the box?

How's the MUA accessing the mailbox? Is it /var/spool/mail/$username?

Anyway, the answer is: Yes. Use /usr/sbin/sendmail as the "mailserver"
in you MAILURI.

You cannot use SSMTP as your MTA (/usr/sbin/sendmail), though. You might
want to check out esmtp, as it can do local delivery by using an MDA like
procmail. With esmtp, such a scenario would be possible.

>  If I understand this correctly in all options discussed here the 
> messages will leave the box via SMTP/UUCP, reach the ISP servers, then the 
> relevant (e.g. mail.yahoo.com) mailserver and finally back to the local box 
> as incoming mail on the user MUA.

That's probably the flow which can be found most often, yes. But it's
not necessary to be that way.

Alexander Skwar
-- 
Have an adequate day.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-25 21:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22 16:21 [gentoo-user] PORTAGE_ELOG error Grant
2006-07-22 16:40 ` Alexander Skwar
2006-07-22 17:07   ` Grant
2006-07-22 18:17     ` Alexander Skwar
2006-07-22 20:42       ` Neil Bothwick
2006-07-22 22:01         ` Alexander Skwar
     [not found]           ` <20060723120542.228d2b9e@hactar.digimed.co.uk>
2006-07-23 12:27             ` Alexander Skwar
2006-07-23 15:33               ` Neil Bothwick
2006-07-23 19:02                 ` Alexander Skwar
2006-07-24 14:05                   ` Neil Bothwick
2006-07-24 15:06                     ` Alexander Skwar
2006-07-24  5:51 ` Alexander Skwar
2006-07-24 14:44   ` Grant
2006-07-24 15:07     ` Alexander Skwar
2006-07-25 16:52       ` Grant
2006-07-25 17:50         ` Neil Bothwick
2006-07-25 18:16         ` Alexander Skwar
2006-07-25 18:36           ` Grant
2006-07-25 18:42             ` Alexander Skwar
2006-07-25 20:20               ` Mick
2006-07-25 20:38                 ` Alexander Skwar [this message]
2006-07-28 17:53             ` Enrico Weigelt
2006-07-24 17:15   ` Tro
2006-07-24 18:08     ` Alexander Skwar
2006-07-24 19:25       ` Mick
2006-07-24 19:57         ` Peter Ruskin
2006-07-24 22:38       ` Alexander Skwar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44C68152.9090108@mid.email-server.info \
    --to=listen@alexander.skwar.name \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox