Should I set up SPF, DKIM, DMARC, or forward email to Gmail account?

[WWGD]

TL;DR Summary

Tired of (seemingly) excessive Spam, email spoofing scam. Should I set protocols or forward mail through filter

Ok, so now occasional spam, scam mails in my Outlook account have become almost weekly, and I want to reduce them to the degree feasible. Ive had my account spoofed too. Upon reading, seems setting up the triplet SPF, DKIM, DMARC, will lower such junk. Another option is forwarding my Outlook emails to a Gmail account. This would provide double-filtering and it's simpler to implement. The three above protocols are implemented in gmail under the hood. The latter seems preferable, less effort. Just to see what others here think. TIA.

 

[FactChecker]

Ok, so now occasional spam, scam mails in my Outlook account have become almost weekly,

"almost weekly"?!? You lucky dog! I get several a day, and occasionally I get dozens in a batch. They are usually easy to recognize from the title. It's a routine thing to delete them.

 

[WWGD]

"almost weekly"?!? You lucky dog! I get several a day, and occasionally I get dozens in a batch. They are usually easy to recognize from the title. It's a routine thing to delete them.

Well, I agreed , until my email account started being spoofed. I don't mind making the effort to implement a few protocols or forward my messages. Do you get yours in an Outlook or a Gmail ( or other) accounts?

 

[Greg Bernhardt]

DMARC is a super pain in the rear and hardly does anything but load up my email with provider reports daily. You should however set up SPF and DKIM. Those are essential these days to not land in the spam box.

 

[WWGD]

DMARC is a super pain in the rear and hardly does anything but load up my email with provider reports daily. You should however set up SPF and DKIM. Those are essential these days to not land in the spam box.

Thank you. the reason for for the forwarding was to avoid Outlook's reputation as "Your Grandma's email program". I will combine SPF, DKIM with Tron Script and Rkill as a basic security setup; using them after starting in Safe Mode, if needed. Safe Mode, RKill, then Tron Script( Which sounds like a German pronounciation of " Transcript " in English)

 

[jack action]

Upon reading, seems setting up the triplet SPF, DKIM, DMARC, will lower such junk.

All of these protocols are used to identify a sender. If an email server can verify the identity of the sender, it will either flag it as spam or even reject it. Hotmail and Gmail are both doing this [basic] verification on all incoming emails. They also, of course, identify themselves appropriately with all outgoing emails.

To lower junk with them, you must classify the undesired emails as spam to help the spam filters do their job.

To get full control, you should make a filter for a whitelist for your inbox, a blacklist for deleting already known undesirable emails, and send the rest to your spam folder by default for you to review carefully before answering them.

• Spam filtering tips for Outlook email inboxes
• Filter junk email and spam in Outlook
• Manage email messages by using rules in Outlook

DMARC is a super pain in the rear and hardly does anything but load up my email with provider reports daily.

If the daily reports are no longer relevant, you can remove the rua and ruf tags (containing your email address) from your SPF record. Those tags are optional:

rua: Addresses to which aggregate feedback is to be sent (comma-
separated plain-text list of DMARC URIs; OPTIONAL). [...] A
Mail Receiver MUST implement support for a "mailto:" URI, i.e.,
the ability to send a DMARC report via electronic mail. If not
provided, Mail Receivers MUST NOT generate aggregate feedback
reports. URIs not supported by Mail Receivers MUST be ignored.
[...]

ruf: Addresses to which message-specific failure information is to
be reported (comma-separated plain-text list of DMARC URIs;
OPTIONAL). If present, the Domain Owner is requesting Mail
Receivers to send detailed failure reports about messages that
fail the DMARC evaluation in specific ways (see the "fo" tag
above). [...] A Mail Receiver
MUST implement support for a "mailto:" URI, i.e., the ability to
send a DMARC report via electronic mail. If not provided, Mail
Receivers MUST NOT generate failure reports. [...]