>>Am I wrong here ? > > > I do not know, ASSP is looking if $LocalAddressesValid is set (Accept > Remote Sender with Valid Local Addresses). If you have set that, > external mails from Valid Local Addresses will not trigger > maxSMTPdomainIP.
That's an option, but I don't like it. I don't consider "Remote Sender with Valid Local Addresses as NOT spoofed". But I don't consider it spoofed. I'm neutral to that. If there is no spf record is because remote senders ARE allowed to use that domain. But I can't tell for sure it's a legit use and not a spammer forging it. So skipping delaying is not an option here, it's one of the best antispam features at the moment. My problem is in the example [EMAIL PROTECTED] to [EMAIL PROTECTED] A spam attack like the one I was experiencing yesterday (using from==recipient) would have ddosed that domain. That's why I suggested adding localdomains to maxSMTPdomainIPWL. Zero problems if you have a spf record, and you limit the risk of a ddos when you can't set a spf record for your domains. If my analisys is correct I could easily *block* all of your domains (when a spf record is not set) just having a few (default 10) different PCs spoofing the sender as [EMAIL PROTECTED] Or just wait for the next spamrun with sender==recipient ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
