Path: csiph.com!news.mixmin.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Ben Bacarisse Newsgroups: gnu.emacs.help Subject: Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Date: Wed, 05 Apr 2023 21:43:29 +0100 Organization: A noiseless patient Spider Lines: 42 Message-ID: <87ilea5aby.fsf@bsb.me.uk> References: <87edp0zjmr.fsf@bsb.me.uk> <87ileb8ty6.fsf@127.0.0.1> <87ileb88ud.fsf@bsb.me.uk> <87bkk28hzl.fsf@127.0.0.1> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: dont-email.me; posting-host="e8b392b78b32fe2629f9cd7ce6361b53"; logging-data="37817"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+IaOTZ9bna8Gt4AGmzsbDDu3SsS9+kLLM=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cancel-Lock: sha1:LY9aJ3Fv/cqsxE18xYUY4LBXnEs= sha1:trdWu8KD7iFMh3BJURJUl2Qm6hM= X-BSB-Auth: 1.cc14677df09732dbdbbe.20230405214329BST.87ilea5aby.fsf@bsb.me.uk Xref: csiph.com gnu.emacs.help:60733 HASM writes: > ben> Postfix chooses the account based on the address in the mail being > ben> sent. > > I do this too, but that's a different subject. For me postfix not only > chooses an account to send "from" but also the relay to use with "to". Of course. I'm not sure what you thought I meant. Once postfix has the mail, it relays it based on the from header. >>> The password map needs to be updated periodically, as the keys expire > >> But I don't have to do this. > > Guess I have to update my setup. As described, e.g. here: > > https://mmogilvi.users.sourceforge.net/software/oauthbearer.html I don't do it that way. I went the route described as step 1 in that document: 1. Configure your gmail (or equivalent) account to enable IMAP and/or POP access. If it will let you set up an "application password" instead of OAUTH2, that would generally be a whole lot simpler and arguably just as secure. but for SMTP sending. Thanks for the link. One day I am sure I will be forced to do it the hard way. > it seems that both fetchmail and postfix can now renew the oauth2 token, > but this wasn't the case when I implemented my solution. At the time it > was only possible by patching fetchmail (and maybe postfix), which I > didn't want to do and maintain. When I did it, there was no oauth2 (as far as I can recall) and I've used the same setup, unchanged, since then. -- Ben.