From: Byung-Hee HWANG <soyeomul@doraji.xyz>
To: The Gnus <ding@gnus.org>
Subject: Re: off-topic reputation
Date: Tue, 15 Feb 2022 20:02:09 +0900 [thread overview]
Message-ID: <xhmtud0bdfy.fsf@yw> (raw)
In-Reply-To: <xhmzgn1sg14.fsf@betla> (Byung-Hee HWANG's message of "Tue, 08 Feb 2022 21:23:51 +0900")
Byung-Hee HWANG <soyeomul@doraji.xyz> writes:
>> No SPF!
>> No DMARC!
>
> By the way, DKIM is INTERNET STANDATD -- RFC 6376. So i respect DKIM
> signature, as very special thing!
>
> Therefore, final attitude is using Gnus and DKIM.
>
> It is the real best reputation on the email world.
Sorry to all.
Today i had to setup SPF for @doraji.xyz as you know 10 hours ago. There
is a story. Let me say that:
... on the phone ...
me: "i sent mail to you"
help desk: "not recevied"
me: "you check spam foler?"
help desk: "not receviced, too"
me: "hey please really?!"
help desk: "NOT RECEVIED!!!"
me: "ok i got it see you later"
3 seconds later, i did have setup SPF record in cloudflare:
#+begin_src text
v=spf1 include:_spf.google.com +all
#+end_src
then try email again with subject "[RESEND]..."
... on the phone ...
me: "i sent mail again 3 minutes ago"
help desk: "yeh! now recevied mail with [RESEND]..."
me: "ok thanks!"
That's today's my story in South Korea.
So for a while i have to go with both DKIM and SPF, ...
Sincerely, Gnus fan Byung-Hee
--
황병희, 대숲농장
경북 울진군 평해읍 평오곡길 213-12 [36363]
비상 연락망: 010-7558-5952
next prev parent reply other threads:[~2022-02-15 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 1:21 황병희
2022-02-08 1:28 ` Byung-Hee HWANG
2022-02-11 1:00 ` Emanuel Berg
2022-02-11 5:26 ` Byung-Hee HWANG
2022-02-08 12:23 ` Byung-Hee HWANG
2022-02-15 11:02 ` Byung-Hee HWANG [this message]
2022-02-15 11:09 ` Emanuel Berg
2022-02-15 11:21 ` Emanuel Berg
2022-02-15 11:43 ` Byung-Hee HWANG
2022-02-16 5:25 ` Emanuel Berg
2022-02-16 10:10 ` Byung-Hee HWANG
2022-02-18 3:35 ` Emanuel Berg
2022-02-18 13:21 ` Byung-Hee HWANG
2022-02-22 5:08 ` Byung-Hee HWANG
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=xhmtud0bdfy.fsf@yw \
--to=soyeomul@doraji.xyz \
--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).