On 01/19/2018 08:07 AM, RW wrote:
On Thu, 18 Jan 2018 18:49:52 -0500
Chip wrote:
Very well stated. Bravo!
The end point here is to examine the email headers that specifically
refer to dkim and spf signatures. Based on fail or pass, or some
combination in concert with the sender's email address, they get moved
into fail or pass folders.
...
But that is with spamassassin still identifying spam, which is
unnecessary in this case as this project will never attract spam - I
know that is hard to believe in, but it won't.
Then why do you care about spf and dkim?
Never say never. If you have some emails addresses out there that have
been around for a few years, then they will get on spammer's lists in
various ways.
Also, these emails being delivered to your cpanel VPS need to be direct
deliveries, not forwards or bcc's in order to correctly identify SPF and
DKIM. This means you must have a test domain or two in your control to
point the MX records directly to this VPS. This on it's own could
attract spam. Trust me. The spammers have ways of finding mail server
IPs and which domains are accepted by them so they can start dictionary
spam attacks. If you have a catchall mailbox setup, it will definitely
get spam. Even regular/single mailboxes will get spam if the VPS is
open on port 25 to the Internet.
--
David Jones
