From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Alternate Incoming Mail Server
Date: Tue, 7 Apr 2020 21:14:59 -0600 [thread overview]
Message-ID: <7aee1ef7-c81c-fc17-f8f5-8a286098a30c@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <3290988.V25eIC5XRa@eve>
On 4/6/20 10:49 PM, J. Roeleveld wrote:
> I am afraid most (if not all) ISPs will reject emails if the reverse
> DNS does not match.
My experience has been that there needs to be something for both the
forward and reverse DNS. Hopefully they match each other and — and what
I call — round resolve each other. Ideally, they round resolve /and/
match the SMTP HELO / EHLO name.
I think you can get away with at least the first part. There will
likely be warnings, but they probably won't prevent email delivery in
and of themselves.
> Using a dynamic range is another "spam" indicator and will also get
> your emails blocked by (nearly) all ISPs.
Yep.
If it's not blatant blocking of believed to be dynamic clients (how is
left up to the reader's imagination), you start to run into additional
filtering that may or may not reject the message.
> I would suggest putting your outbound SMTP server on a cheap VM hosted
> somewhere else. Or you get an outbound SMTP-service that allows you
> to decide on domain name and email addresses.
Unfortunately the spammers have made many such cheap VMs IP net blocks
have bad reputations. I'm starting to see more people blocking the
cheaper VPS providers.
--
Grant. . . .
unix || die
prev parent reply other threads:[~2020-04-08 3:15 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 12:35 [gentoo-user] Alternate Incoming Mail Server Ashley Dixon
2020-04-06 12:41 ` Michael Orlitzky
2020-04-06 13:08 ` Ashley Dixon
2020-04-06 13:15 ` Michael Orlitzky
2020-04-06 13:24 ` Ashley Dixon
2020-04-06 16:18 ` [gentoo-user] " Ian Zimmerman
2020-04-06 16:25 ` Ashley Dixon
2020-04-06 19:03 ` Rich Freeman
2020-04-06 19:16 ` Michael Orlitzky
2020-04-06 20:06 ` Grant Taylor
2020-04-08 21:36 ` Neil Bothwick
2020-04-08 21:49 ` Grant Taylor
2020-04-08 22:06 ` Michael Orlitzky
2020-04-08 22:13 ` Ashley Dixon
2020-04-08 22:22 ` Michael Orlitzky
2020-04-09 1:15 ` Grant Taylor
2020-04-06 20:02 ` Grant Taylor
2020-04-06 23:34 ` Rich Freeman
2020-04-11 20:08 ` [gentoo-user] " antlists
2020-04-11 20:17 ` Michael Orlitzky
2020-04-11 20:41 ` Grant Taylor
2020-04-11 20:45 ` Ashley Dixon
2020-04-11 20:50 ` Michael Orlitzky
2020-04-11 20:33 ` Grant Taylor
2020-04-11 22:13 ` antlists
2020-04-12 2:14 ` Grant Taylor
2020-04-06 15:24 ` J. Roeleveld
2020-04-06 15:34 ` Ashley Dixon
2020-04-06 15:51 ` Robert Bridge
2020-04-06 16:02 ` Michael Orlitzky
2020-04-06 16:19 ` J. Roeleveld
2020-04-06 16:43 ` Michael Orlitzky
2020-04-06 17:02 ` Grant Taylor
2020-04-06 17:14 ` Michael Orlitzky
2020-04-06 17:19 ` J. Roeleveld
2020-04-06 17:24 ` Robert Bridge
2020-04-06 17:27 ` Michael Orlitzky
2020-04-06 17:25 ` Michael Orlitzky
2020-04-06 17:32 ` J. Roeleveld
2020-04-06 17:35 ` Michael Orlitzky
2020-04-06 18:13 ` Stefan Schmiedl
2020-04-07 17:10 ` Michael
2020-04-07 18:34 ` Michael Orlitzky
2020-04-07 18:54 ` Stefan Schmiedl
2020-04-07 19:11 ` Michael Orlitzky
2020-04-07 18:35 ` Stefan Schmiedl
2020-04-07 4:37 ` J. Roeleveld
2020-04-06 17:44 ` Grant Taylor
2020-04-06 17:55 ` Michael Orlitzky
2020-04-06 19:59 ` Grant Taylor
2020-04-06 20:55 ` Michael Orlitzky
2020-04-06 17:00 ` Grant Taylor
2020-04-06 17:34 ` Grant Taylor
2020-04-06 21:17 ` Ashley Dixon
2020-04-06 22:12 ` Grant Taylor
2020-04-07 4:49 ` J. Roeleveld
2020-04-07 10:53 ` Ashley Dixon
2020-04-08 3:18 ` Grant Taylor
2020-04-08 13:39 ` [gentoo-user] " Grant Edwards
2020-04-08 14:11 ` Ashley Dixon
2020-04-08 16:03 ` Grant Taylor
2020-04-08 16:34 ` Grant Edwards
2020-04-08 14:50 ` [gentoo-user] " Neil Bothwick
2020-04-11 19:57 ` antlists
2020-04-08 3:14 ` Grant Taylor [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=7aee1ef7-c81c-fc17-f8f5-8a286098a30c@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--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