public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Setting up fetchmail to feed postfix
Date: Tue, 28 Nov 2017 00:23:12 +0000	[thread overview]
Message-ID: <1654583.xvCePxTXQf@peak> (raw)
In-Reply-To: <20171127221434.6d6f5d45@digimed.co.uk>

On Monday, 27 November 2017 22:14:34 GMT Neil Bothwick wrote:
> On Mon, 27 Nov 2017 09:48:11 -0800, Ian Zimmerman wrote:
> > > These few lines save you from all the potential hassle that sharing
> > > read/write access to the same files could bring. Dovecot will ensure
> > > that indexes are up to date when mail is delivered, and that alone is
> > > reason enough for me.
> > 
> > Do you really need lmtp for that, though?  As far as I remember simply
> > piping the messages to the /usr/lib/dovecot/deliver program, as the
> > deilivery mechanism, will ensure the same thing.  I don't know postfix
> > much though, so maybe that's hard to do with postfix,
> > unlike my pet exim.
> 
> In that case, why bother with Postfix at all. Can't fetchmail send mails
> directly to an MDA? I use getmail and it doesn't need Postfix at all.

In my case, postfix collates emails from other boxes on the LAN.

-- 
Regards,
Peter.



  reply	other threads:[~2017-11-28  0:23 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 15:39 [gentoo-user] Setting up fetchmail to feed postfix Peter Humphrey
2017-11-24 16:08 ` Wols Lists
2017-11-24 16:34   ` Peter Humphrey
2017-11-24 18:10     ` Matthias Hanft
2017-11-27 13:44       ` Peter Humphrey
2017-11-30  0:39         ` Peter Humphrey
2017-11-30  6:46           ` J. Roeleveld
2017-11-30  8:13           ` Neil Bothwick
2017-11-24 16:16 ` Ralph Seichter
2017-11-24 16:40   ` Peter Humphrey
2017-11-24 17:29     ` Ralph Seichter
2017-11-24 17:30   ` Rich Freeman
2017-11-24 17:52     ` Ralph Seichter
2017-11-27 13:44       ` Peter Humphrey
2017-11-27 16:13         ` Ralph Seichter
2017-11-27 17:48           ` [gentoo-user] " Ian Zimmerman
2017-11-27 19:10             ` Ralph Seichter
2017-11-27 22:14             ` Neil Bothwick
2017-11-28  0:23               ` Peter Humphrey [this message]
2017-11-26 10:25     ` [gentoo-user] " J. Roeleveld
2017-11-24 22:24 ` Neil Bothwick
2017-11-25  8:43   ` Marc Joliet
2017-11-25  9:04     ` Neil Bothwick
2017-11-25  9:23       ` Marc Joliet
2017-11-25 16:20         ` Jalus Bilieyich
2017-11-26  2:30           ` Peter Humphrey
2017-11-26  6:58             ` Alan McKinnon
2017-11-26 10:45               ` Peter Humphrey
2017-11-26 15:58               ` Jalus Bilieyich
2017-11-26  8:52             ` Neil Bothwick
2017-11-26 10:00             ` Ralph Seichter
2017-11-26 11:00               ` Peter Humphrey
2017-11-26 17:46               ` [gentoo-user] " Ian Zimmerman
2017-11-26 18:46                 ` Ralph Seichter
2017-11-26 19:35                   ` Jack
2017-11-26 20:58                   ` Wols Lists
2017-11-26 21:46                     ` Rich Freeman
2017-11-26 23:05                       ` Ian Zimmerman
2017-11-26 23:18                         ` Rich Freeman
2017-11-26 10:22             ` [gentoo-user] " J. Roeleveld
2017-11-26 15:25               ` Mick

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=1654583.xvCePxTXQf@peak \
    --to=peter@prh.myzen.co.uk \
    --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