Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Reject unknown sender domain (“foo@imaginarydomain.com”) – after all, if I can resolve their domain, then I couldn reply to them anyway, right?

0
Posted

Reject unknown sender domain (“foo@imaginarydomain.com”) – after all, if I can resolve their domain, then I couldn reply to them anyway, right?

0

• Let everyone who makes it this far continue on to step 3. 3. Recipient Filtering • Reject non-FQDN recipient domains (they’d bounce anyway). • Reject unknown recipient domains (same as above). • Allow authenticated users to send their mail and stop processing. • Allow hosts on my LAN to send their mail and stop processing. • Reject mail from anyone else that isn’t to one of my domains, or one I’m an MX for. • Use SPF to reject spoofed email. • Use the relays.ordb.org, list.dsbl.org, and sbl-xbl.spamhaus.org DNS blackhole lists. • Greylist all email not coming in from or going out to peer MXes. • Pass everything else to step 4. 4. Content Filtering and Delivery • Use ClamAV to reject viruses. This takes a big load off SpamAssassin. • Use SpamAssassin to tag messages. • Use Cyrus’s Sieve to reject high-probability spam, put medium-probability messages into a “review” folder, and filter everything else into the appropriate folders. I reject over 95% of all incoming mail before it ever g

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123