reject-missing-sender-mx
2008/5/23, Kyle Quillen <[EMAIL PROTECTED]>: > > When you say option checking mx what exactly do you mean? > > Thanks > q > > > > On Fri, 2008-05-23 at 18:57 +0200, nightduke wrote: > > But have you detected spam are from USA? > > Have you check your logs? Do you know who is messing your server? > > You can try stats at your maillog file also if you use mrtg can find > > more information too. > > > > Do you have rbl list working? Graylisting on? option cheking mx ? Many > > options... > > > > Spamassassin uses a lot of recourses. > > > > It's a nightmare to block certain of ips, but a very big nightmare > > will be blocking a whole country.Don't you work with companys at USA? > > > > I hope this help, it's an idea, don't get angry with myself. > > > > Nightduke > > > > 2008/5/23, Bgs <[EMAIL PROTECTED]>: > > > > > > > > > Hi, > > > > > > You can probably tune on the settings first I think. I had an Athlon XP, > > > 1.5GB, sata software raid1 server which topped at 8million spam/day. Of > > > course it was very loaded but still no lost mail. With your config and > > > ~1.1 million mail/day you should be ok. > > > > > > But to get back to your original question: There are multiple levels > > > where you can do it. Deciding which to use depends on the type of > > > filtering you'd like to achieve. Here are them from low to high: > > > > > > - Get a geoip db, get the US ranges and do a separate chain in your > > > firewall and whitelist those. update it about once a week. I use this to > > > block Chinese traffic on some servers. You'd just do the opposite. > > > - Patch the kernel and add geoip support and drop all non-us traffic to > > > your smtp port. > > > - Patch the kernel and do an AS based filtering. You will still need to > > > get the AS list. > > > - Similar to the above iptables chain you could do a similar thing from > > > tcpserver or ipvsd. > > > > > > > > > You could also set up some IP limiter which will block much of your spam > > > traffic while not blocking the non-us world in general. > > > > > > The ways of the Net are endless :D > > > > > > Regards > > > Bgs > > > > > > > > > > > > Kyle Quillen wrote: > > > > When you say do it on the IP level what do you mean? > > > > > > > > > > > > Well based on my spamassassin graphs it is about 8000 messages on a ten > > > > minute average. spamassassin is what is killing me. > > > > > > > > Thoughts? > > > > > > > > Thanks > > > > Kyle > > > > > > > > > > > > > > > > On Fri, 2008-05-23 at 17:25 +0200, Bgs wrote: > > > >> Hi, > > > >> > > > >> > > > >> I think you'd better do it on IP level.... much more efficient. > > > >> > > > >> May I ask how big is that traffic that causes the problem? mail/day, > > > >> cuncurrent connections, etc. > > > >> > > > >> > > > >> Regards > > > >> Bgs > > > >> > > > >> Kyle Quillen wrote: > > > >>> Hello all, > > > >>> > > > >>> I am dealing a very high load on one of my servers and it is causing > > > >>> all > > > >>> kinds of issues. It is a qmail toaster box with 6 gigs of ram and > > > >>> quadcore 3.2 ghz processors. What I am wanting to know is there a way > > > >>> that I can block all non-us ips in spamdyke? > > > >>> > > > _______________________________________________ > > > spamdyke-users mailing list > > > [email protected] > > > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > > > > > _______________________________________________ > > spamdyke-users mailing list > > [email protected] > > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > > > -- > Thanks, > Kyle Quillen > Lightspeed Wireless > [EMAIL PROTECTED] > 330.473.1231 ext.202 > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
