From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Any one with experience using getmail with postfix?
Date: Fri, 25 Nov 2022 21:01:12 +0800 [thread overview]
Message-ID: <0e592e68-8baf-de77-285f-2ed66ea3250c@iinet.net.au> (raw)
In-Reply-To: <9dcf8745-80dc-2074-8672-dc662371f0e5@youngman.org.uk>
On 25/11/22 20:37, Wols Lists wrote:
> On 25/11/2022 11:56, William Kenworthy wrote:
>> Hi,
>>
>> I am looking into replacing fetchmail with getmail on my mail
>> gateway system
>
> Are you using getmail, or getmail6?
>
> https://pyropus.ca./software/getmail/documentation.html#python3
>
> A quick "emerge --search getmail" shows that gentoo is distributing
> getmail6 under getmail's name - they are two completely different
> programs. I guess somebody should file a bug to get THAT fixed.
>
> The tldr is that the maintainer of getmail has not migrated to Python3
> - time is hard to find. getmail6 is a fork where somebody has fed it
> through 2to3 and not bugfixed it (properly). In other words, whether
> you choose getmail or getmail6, you have a problem.
>
> Made worse by the fact that many people - distros included! - don't
> realise that getmail and getmail6 are completely different entities.
>
> Cheers,
> Wol
>
I dont think it makes a difference - for my purposes it looks and works
exactly like getmail, but uses python3. I guess what I need is an MTA
that takes input on stdin, and outputs to a host:port
next prev parent reply other threads:[~2022-11-25 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 11:56 [gentoo-user] Any one with experience using getmail with postfix? William Kenworthy
2022-11-25 12:37 ` Wols Lists
2022-11-25 13:01 ` William Kenworthy [this message]
2022-11-25 15:01 ` Solved: GRe: " William Kenworthy
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=0e592e68-8baf-de77-285f-2ed66ea3250c@iinet.net.au \
--to=billk@iinet.net.au \
--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