From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Setting up fetchmail to feed postfix
Date: Fri, 24 Nov 2017 16:40:30 +0000 [thread overview]
Message-ID: <2211118.669JShTMR6@peak> (raw)
In-Reply-To: <67a25925-c802-460d-99da-84a3b8cacc2a@monksofcool.net>
On Friday, 24 November 2017 16:16:15 GMT Ralph Seichter wrote:
> On 24.11.17 16:39, Peter Humphrey wrote:
> > I'm trying an evasion, which is to use fetchmail to retrieve emails
> > from my ISP and deliver them to postfix, which can then serve them
> > via IMAP.
>
> Postfix is an MTA and does neither store email nor lets you access email
> via IMAP. There must be an IMAP server in your mix somewhere (e.g.
> Dovecot or Courier).
Yes, of course. Postfix feeds Dovecot here.
> > I still don't know what to add to /etc/ conf.d/fetchmail, nor whether
> > I need a ~/.fetchmailrc or an /etc/fetchmailrc file (no sample comes
> > with the ebuild).
> Your needs depend on what you are trying to achieve, and you have been a
> bit vague on the details.
That's because I don't yet know enough to know what questions to ask; that's
why I hoped I'd be pointed to a general guide or explanation.
I thought I was clear enough: I want fetchmail to fetch POP mail and feed it
into the local postfix (and of course dovecot) mail system. What else do you
need?
> If you plan to use a single fetchmail process,
> ~foo/.fetchmailrc (with foo being the user you want to run fetchmail as)
> usually suffices.
I assume you mean ~/.fetchmailrc, a file in my home directory, no?
--
Regards,
Peter.
next prev parent reply other threads:[~2017-11-24 16:40 UTC|newest]
Thread overview: 43+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2017-11-26 7:25 roger.cahn
2017-11-26 7:26 roger.cahn
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=2211118.669JShTMR6@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