Gnus development mailing list
 help / color / mirror / Atom feed
From: Tim Landscheidt <tim@tim-landscheidt.de>
To: ding@gnus.org
Subject: Re: gmail+SMTP (oauth2)
Date: Wed, 18 May 2022 19:59:26 +0000	[thread overview]
Message-ID: <87czgak3xd.fsf@vagabond.tim-landscheidt.de> (raw)
In-Reply-To: <8735h86rvm.fsf@mat.ucm.es>

Uwe Brauer <oub@mat.ucm.es> wrote:

> Today I got the unofficial approval to forward my email to an account of
> my choice, if I can't access my mail with TLS (SSL or the gmail app
> password anymore)

> However I have been warned that the message should have a from field
> with a domain of my university. (@mat.ucm.es for example).

> Now I could either use

>     1. The smtpmail (or sendmail) program of my linux machine (not sure
>        about MacOS

>     2. Or use a SMTP service that allows me to use a different form
>        field, once the address has been verified. Gmail did this in the
>        past (and maybe still does it).

> In any case I have been warned that my mails could be blacklisted.

> Anybody has experience with such a service/setting?

mat.ucm.es's SPF record (cf. for example
https://www.spf-record.de/spf-lookup/mat.ucm.es) recommends
that mails from servers not listed explicitly there should
"soft-fail", i. e. be accepted, but marked as, eh, "suspi-
cious".  So sending mails with that address from other ser-
vers will probably cause them to end up in some spam folder
or being discarded, with the recipients probably having very
little to no chance in hell to persuade their administrators
to accept your mails.

So, personally, I wouldn't invest any energy in that direc-
tion because that is a battle that you cannot win and if you
use that mail address for work, i. e. those mails are impor-
tant, you need a (reasonably) reliable solution.

Tim



      reply	other threads:[~2022-05-18 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 16:33 Uwe Brauer
2022-05-18 19:59 ` Tim Landscheidt [this message]

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=87czgak3xd.fsf@vagabond.tim-landscheidt.de \
    --to=tim@tim-landscheidt.de \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).