From: William Kenworthy <bill@kenworthy.id.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] google SMTP with postfix - Password not accepted
Date: Sun, 15 Oct 2023 10:43:00 +0800 [thread overview]
Message-ID: <ed285069-4edb-472b-b999-de9bcae37d10@kenworthy.id.au> (raw)
In-Reply-To: <12312097.O9o76ZdvQC@wstn>
On 14/10/23 21:28, Peter Humphrey wrote:
> On Saturday, 14 October 2023 12:26:29 BST I wrote:
>
>> Perhaps I should switch to getmail...
> On the other hand, I'd prefer to stick with fetchmail for my Zen POP3
> account,
> since it's working well. Then I could use getmail to fetch my gmail mail.
> Would that be safe?
>
> If it works I could move Zen mail to getmail later, at my leisure.
> (That's the
> only sort of time I have these days... :( )
>
getmail works fine with gmail - just follow their instructions to configure.
getmail itself is a bit flakey - using it with hydroxide as a proton
bridge it keeps going to sleep(need to restart getmail every hour), and
on 3 accounts with my ISP I get random crashes with no indication why.
But with gmail and ventraip.mail its quite stable. On the plus side imap
getmail IDLE works ... I had problems with fetchmail so moved to getmail.
BillK
next prev parent reply other threads:[~2023-10-15 2:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 5:29 [gentoo-user] google SMTP with postfix - Password not accepted thelma
2023-06-20 8:30 ` Michael
2023-06-20 8:55 ` William Kenworthy
2023-10-14 5:02 ` Peter Humphrey
2023-10-14 7:04 ` Neil Bothwick
2023-10-14 11:26 ` Peter Humphrey
2023-10-14 13:28 ` Peter Humphrey
2023-10-14 21:59 ` Neil Bothwick
2023-10-15 2:43 ` William Kenworthy [this message]
2023-10-15 12:33 ` Peter Humphrey
2023-10-15 9:45 ` Michael
2023-10-15 12:31 ` Peter Humphrey
2023-06-20 18:09 ` thelma
2023-06-20 18:26 ` Matt Connell
2023-06-21 5:45 ` thelma
2023-06-20 9:11 ` Dr Rainer Woitok
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=ed285069-4edb-472b-b999-de9bcae37d10@kenworthy.id.au \
--to=bill@kenworthy.id.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