public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Local mail delivery agent (MDA) wanted
Date: Wed, 15 Dec 2021 13:38:40 -0700	[thread overview]
Message-ID: <9aab08f6-5766-7ebf-5aa1-5106c9a059db@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <MW2PR07MB4058057A592ADD9F96526287D2769@MW2PR07MB4058.namprd07.prod.outlook.com>

On 12/15/21 1:21 PM, Laurence Perkins wrote:
> So one thing that's annoyed me for a while is that there are several 
> things which will pull in nullmailer to accept local mails, but don't 
> pull in anything to do local delivery (And I'm not sure if nullmailer 
> can even pass things to local delivery) so your local delivery mails 
> by default just stack up in the nullmailer outbound queue unless you 
> configure it to pass them off to an external mail system.
> 
> Since the most commonly used of these programs are things like cron 
> where local delivery is probably the only thing most users would 
> care about it might be nice if the default configuration were one 
> that does that, and then those who want local mail relayed elsewhere 
> still don't have any significant extra setup work to do.

The idea of having a default mail configuration that would deliver 
locally originated messages (e.g. from cron) to local user's mailboxes 
(mbox) in /var(/spool)/mail makes sense to me.

I don't think I'd /personally/ us it b/c I run full MTAs on all my 
systems.  But that's /me/.  I realize that I'm atypical.

But I would +1 a simple config that does local delivery from "<foo> | 
mail ${USER}" to end up in "/var/spool/mail/${USER}".



-- 
Grant. . . .
unix || die


  reply	other threads:[~2021-12-15 20:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 13:25 [gentoo-user] Local mail delivery agent (MDA) wanted Frank Steinmetzger
2021-12-12 14:23 ` Alexey Mishustin
2021-12-12 23:36 ` William Kenworthy
2021-12-13  9:36   ` Peter Humphrey
2021-12-13  9:50     ` William Kenworthy
2021-12-13 19:40 ` tastytea
2021-12-13 20:11   ` Grant Taylor
2021-12-13 21:34   ` Frank Steinmetzger
2021-12-13 22:12     ` Frank Steinmetzger
2021-12-13 23:49       ` tastytea
2021-12-14 23:34       ` Grant Taylor
2021-12-15 20:21         ` Laurence Perkins
2021-12-15 20:38           ` Grant Taylor [this message]
2021-12-15  3:26 ` Ralph Seichter
2021-12-18 23:00 ` Frank Steinmetzger
2021-12-19  2:19   ` Grant Taylor
2021-12-19 14:23     ` Frank Steinmetzger
2021-12-20 19:08     ` Frank Steinmetzger
2021-12-20 19:10       ` Frank Steinmetzger
2021-12-20 20:00       ` Grant Taylor
2021-12-20 22:09         ` Frank Steinmetzger
2021-12-20 22:28           ` Grant Taylor
2021-12-20 22:37             ` Wol
2021-12-20 23:38               ` Grant Taylor

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=9aab08f6-5766-7ebf-5aa1-5106c9a059db@spamtrap.tnetconsulting.net \
    --to=gtaylor@gentoo.tnetconsulting.net \
    --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