On Thu, Aug 04, 2022 at 02:51:14PM +0200, Matthias Apitz wrote: > El día Donnerstag, August 04, 2022 a las 12:23:08 +0000, Sam Kuper escribió: >> On Thu, Aug 04, 2022 at 12:14:04PM +0200, Matthias Apitz wrote: >>> El día Donnerstag, August 04, 2022 a las 10:07:47 +0000, Sam Kuper escribió: >>>> As a *temporary workaround*, maybe see if you can edit the >>>> GMail/GoogleMail settings so that a copy of each incoming email is >>>> forwarded to an email address you control that is hosted by a >>>> standards-compliant (and therefore Mutt-friendly) email hosting >>>> company. IIRC, the GMail settings interface has an option for this - >>>> or failing that, you can create a catch-all "filter" with a rule to >>>> forward the emails. >>> >>> Be prepared to run into troubles sending mails to GMail/GoogleMail. >>> Google requires very special DNS configs to accept mails for their >>> users. I gave up on this and do not send any mails to Google users >>> anymore. >> >> I don't see how these remarks relate to my suggestion above? > > The relation is: once you have the enail downloaded from another > hosting provider and you want reply upstream through it to > GMail/GoogleMail recipients ...
So... your comment *doesn't* relate to my suggestion above - which was about how to get *inbound* emails from Gmail/GoogleMail into Mutt. Sam
