6/7/2003 Getting tighter and tighter on spammers...

[MEELAN]

Originally posted by admin
lankan, added.. Thanks

But don't post these here just yet I will be making a forum just for this..

Is that forum ready now?

By the way, here is a problem from me. Advice me wat to do.

I have setup catch-all@mydomain.com to forward all mails to my local ISP email account. There is no mail box on my domain except this mail forward. But, my from address is always, say, lankan@mydomain.com. And I am sending the mail through mail.MYDOMAIN.com or mail1.MYDOMAIN.com or mail2.MYDOMAIN.com

Will I be allowed to send a mail through this setup to another user@HOSTEDELSEWHERE.com ?

I thried this and it denies saying
The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was 'SOME-ONE@slt.lk'. Subject 'This is a testing mail from MAIL1', Account: 'MAIL', Server: 'mail1.MYDOMAIN.com', Protocol: SMTP, Server Response: '553 sorry, that domain isn't allowed to be relayed thru this MTA (#5.7.1)', Port: 25, Secure(SSL): No, Server Error: 553, Error Number: 0x800CCC79

At time of my try, my IP was 203.94.94.232 which is a dynamic one, In case if you need it.

What can I do?

PS:Of course, I can use my local ISP SMTP or my own SMTP server which I am doing now. But, I can't expect my clients to do that

[Brangwyn]

I was just teasing about the Avatar, doesnt matter to me at all if someone uses the one I uploaded

We've been doing some testing lately, and to be honest enabling RBL's has seen our overall resource usage go up slightly on our own mail server and we've tried a few configurations, currently settled on Kerio mailserver at the moment, these are windows boxes not Qmail of course so YMMV we may just be unlucky in that most of our testing was simulated which may well be different than real world observations (guess we'll find out when we finally roll it off the test server and onto production). We believe the DNS lookups were actually the culprit by taking sufficient time on occasion that the server spent more time waiting for the lookup to complete than it would have to have received a few hundred bytes of an average email message and that seemed to translate to some timing issues when other servers were trying to open sessions with ours, possibly our software isn't multithreading as well as it should which could also be contributing to our findings.

I pretty much agree about the zero resource after it's been rejected but lets face it, a client is still going to connect every x minutes to check for mail and consume resources whether theres actually any mail in their mailbox or not, it just reduces the storage requirements and overall bandwidth usage of the server.

[Brangwyn]

Lankan, is your email client set to do a POP request before SMTP ? that could be the cause of your particular issue, I believe one of the things the guys have done is actually fix that so its working properly now which may be why it seemed to have just suddenly stop working for you.

Brangwyn, the bottleneck on mail servers (in general) is more often than not disk I/O. Since we depend on an MTA that's fairly filesystem-intensive, reducing disk traffic is desirable.

The DNS lookup latency can be overcome by arranging zone transfer access with the RBL provider and performing lookups on a local DNS server. Since pretty much any old piece of decrepit hardware with sufficient RAM can handle pure DNS, this is a viable and fast option.

[Brangwyn]

the bottleneck on mail servers (in general) is more often than not disk I/O.

True enough, that probably almost scales logarithmically with the total number of mailboxes being serviced too.

Some of the latency for us as well comes from the fact that a big percentage of the domain lookups we need to do aren't in our (NZ) zone files, so we've got to go over the other side of the world for data not already cached by our own servers (or multiple trips around the place if theres no glue).

The particular customer we were doing this for won't let us setup a local DNS either can't really understand why, but hey you do what your told by your customer right

[frederic]

Help!!!!!!!!!!!!!

All emails send from China are filtered by your SPAM SYSTEM!
I really impressed by your powerful Spam policy, however, ALL my business and customers are in China. Now the emails from China are banned, I shall have no BUSINESS AT ALL!

Do help me before our Monday comes, I shall have to face complaint bomber!

I hate spam, and all of our customers hate spam, too. But it is unreasonable to stop all emails because of the spam, especailly our customers are not to blame.

We do hope you will solve the problem in the next 8 hours, otherwise, we have disaster!

[MEELAN]

Originally posted by Brangwyn
Lankan, is your email client set to do a POP request before SMTP ? that could be the cause of your particular issue, I believe one of the things the guys have done is actually fix that so its working properly now which may be why it seemed to have just suddenly stop working for you.

Brangwyn:
Ok, there is no POP account to do any POP. I have only "catch-all" forward.

What to do now?

(DOn't worry it is not a practical problem for me. It was just a test for "catch-all" only email customers)

[Vixen]

I am at a loss how some people want to make this our problem when their customers utilize ISPs that are blocked because they are known to harbor/allow spammers. Personally, if I were on a network that was being blocked I would want to know so I could make a change. I guess other people do not see it this way.

I understand that innocent people get caught up in situations that they had nothing to do with but that is not an excuse (at least to me) for continuing to stay on a network that is considered a spamhaus.

Just my opinion.

[frederic]

You send a formal email / document to those main ISPs from which many spams are sent out. Or you can avenge them in your own way. I believe that those main ISPs have some way to filter or to block the spams.

At any rate, I personally think it is not reasonable to block all the emails sent out from China. In fact, this is more harm than benefit. Just like, someone is afraid of cheating in business, then gives up his business.

[glauco]

Hello,

a lot of people is advising me that my matrix hosted email accounts are unreachable.

I've done some testing: I'm still waiting for a couple of email messages (sent some hours ago) and for the third message I've received the following error:

- These recipients of your message have been processed by the mail server:
gla03@siliprandi.com; Failed; 5.1.3 (bad destination mailbox address syntax)


Remote MTA mail.a3ware.com: SMTP diagnostic: 553 tiscalinet.it banned for spam haven


There are about a million of Italian users using the tiscalinet.it SMTP server (it is the larger italian ADSL provider).

I'm waiting for a very very very important email message from godaddy, but I've received nothing. How can I know if it has been filtered out?

I've built an effective filtering strategy on my client and spam is no more an issue. But I am the ONLY person who can set up the proper whitelist for my incoming emails.

Matrixreseller CANNOT set up my personal whitelist.

So I'm the best point to build an effective spam filtering strategy for my accounts.

Please, get back to the previous email system that was working really fine for me.

Thanks in advance.


Glauco

Yes I agree,

I see your range of ip's of your clients listed are not blocked, in at least my config for those ip's,

However if somehow you are on one of those isp's I would be switching soon. Here is the current list of the networks I am blocking smtp for spam on the firewall side if you resellers would like to compare...


deny tcp 61.4.64.0 0.0.15.255 any eq smtp
deny tcp 61.28.0.0 0.0.63.255 any eq smtp
deny tcp 61.32.0.0 0.7.255.255 any eq smtp
deny tcp 61.40.0.0 0.3.255.255 any eq smtp
deny tcp 61.48.0.0 0.7.255.255 any eq smtp
deny tcp 61.72.0.0 0.7.255.255 any eq smtp
deny tcp 61.80.0.0 0.7.255.255 any eq smtp
deny tcp 61.96.0.0 0.15.255.255 any eq smtp
deny tcp 61.128.0.0 0.63.255.255 any eq smtp
deny tcp 61.232.0.0 0.3.255.255 any eq smtp
deny tcp 61.236.0.0 0.1.255.255 any eq smtp
deny tcp 61.240.0.0 0.3.255.255 any eq smtp
deny tcp 61.248.0.0 0.7.255.255 any eq smtp
deny tcp 128.134.0.0 0.0.255.255 any eq smtp
deny tcp 129.254.0.0 0.0.255.255 any eq smtp
deny tcp 134.75.0.0 0.0.255.255 any eq smtp
deny tcp 137.68.0.0 0.0.255.255 any eq smtp
deny tcp 141.223.0.0 0.0.255.255 any eq smtp
deny tcp 143.248.0.0 0.0.255.255 any eq smtp
deny tcp 147.6.0.0 0.0.255.255 any eq smtp
deny tcp 147.43.0.0 0.0.255.255 any eq smtp
deny tcp 147.46.0.0 0.1.255.255 any eq smtp
deny tcp 150.150.0.0 0.0.255.255 any eq smtp
deny tcp 150.183.0.0 0.0.255.255 any eq smtp
deny tcp 150.197.0.0 0.0.255.255 any eq smtp
deny tcp 152.99.0.0 0.0.255.255 any eq smtp
deny tcp 152.149.0.0 0.0.255.255 any eq smtp
deny tcp 154.10.0.0 0.0.255.255 any eq smtp
deny tcp 155.230.0.0 0.0.255.255 any eq smtp
deny tcp 156.147.0.0 0.0.255.255 any eq smtp
deny tcp 157.197.0.0 0.0.255.255 any eq smtp
deny tcp 158.44.0.0 0.0.255.255 any eq smtp
deny tcp 159.226.0.0 0.0.255.255 any eq smtp
deny tcp 161.122.0.0 0.0.255.255 any eq smtp
deny tcp 161.207.0.0 0.0.255.255 any eq smtp
deny tcp 162.105.0.0 0.0.255.255 any eq smtp
deny tcp 163.152.0.0 0.0.255.255 any eq smtp
deny tcp 163.180.0.0 0.0.255.255 any eq smtp
deny tcp 163.239.0.0 0.0.255.255 any eq smtp
deny tcp 164.124.0.0 0.1.255.255 any eq smtp
deny tcp 165.132.0.0 0.1.255.255 any eq smtp
deny tcp 165.141.0.0 0.0.255.255 any eq smtp
deny tcp 165.186.0.0 0.0.255.255 any eq smtp
deny tcp 165.194.0.0 0.0.255.255 any eq smtp
deny tcp 165.213.0.0 0.0.255.255 any eq smtp
deny tcp 165.229.0.0 0.0.255.255 any eq smtp
deny tcp 165.243.0.0 0.0.255.255 any eq smtp
deny tcp 165.244.0.0 0.0.255.255 any eq smtp
deny tcp 165.246.0.0 0.0.255.255 any eq smtp
deny tcp 166.79.0.0 0.0.255.255 any eq smtp
deny tcp 166.103.0.0 0.0.255.255 any eq smtp
deny tcp 166.104.0.0 0.0.255.255 any eq smtp
deny tcp 166.111.0.0 0.0.255.255 any eq smtp
deny tcp 166.125.0.0 0.0.255.255 any eq smtp
deny tcp 167.139.0.0 0.0.255.255 any eq smtp
deny tcp 168.78.0.0 0.0.255.255 any eq smtp
deny tcp 168.115.0.0 0.0.255.255 any eq smtp
deny tcp 168.126.0.0 0.0.255.255 any eq smtp
deny tcp 168.131.0.0 0.0.255.255 any eq smtp
deny tcp 168.154.0.0 0.0.255.255 any eq smtp
deny tcp 168.160.0.0 0.0.255.255 any eq smtp
deny tcp 168.188.0.0 0.0.255.255 any eq smtp
deny tcp 168.219.0.0 0.0.255.255 any eq smtp
deny tcp 168.248.0.0 0.1.255.255 any eq smtp
deny tcp 169.140.0.0 0.0.255.255 any eq smtp
deny tcp 192.5.90.0 0.0.0.255 any eq smtp
deny tcp 192.83.122.0 0.0.0.255 any eq smtp
deny tcp 192.100.2.0 0.0.0.255 any eq smtp
deny tcp 192.104.15.0 0.0.0.255 any eq smtp
deny tcp 192.124.154.0 0.0.0.255 any eq smtp
deny tcp 192.132.15.0 0.0.0.255 any eq smtp
deny tcp 192.132.247.0 0.0.0.255 any eq smtp
deny tcp 192.132.248.0 0.0.3.255 any eq smtp
deny tcp 192.188.170.0 0.0.0.255 any eq smtp
deny tcp 192.195.39.0 0.0.0.255 any eq smtp
deny tcp 192.195.40.0 0.0.0.255 any eq smtp
deny tcp 192.203.138.0 0.0.1.255 any eq smtp
deny tcp 192.203.140.0 0.0.3.255 any eq smtp
deny tcp 192.203.144.0 0.0.1.255 any eq smtp
deny tcp 192.203.146.0 0.0.0.255 any eq smtp
deny tcp 192.245.249.0 0.0.0.255 any eq smtp
deny tcp 192.245.250.0 0.0.1.255 any eq smtp
deny tcp 192.249.16.0 0.0.15.255 any eq smtp
deny tcp 198.17.7.0 0.0.0.255 any eq smtp
deny tcp 198.97.132.0 0.0.0.255 any eq smtp
deny tcp 198.178.187.0 0.0.0.255 any eq smtp
deny tcp 202.0.110.0 0.0.0.255 any eq smtp
deny tcp 202.0.160.0 0.0.15.255 any eq smtp
deny tcp 202.0.176.0 0.0.3.255 any eq smtp
deny tcp 202.3.77.0 0.0.0.255 any eq smtp
deny tcp 202.4.128.0 0.0.31.255 any eq smtp
deny tcp 202.4.252.0 0.0.3.255 any eq smtp
deny tcp 202.6.95.0 0.0.0.255 any eq smtp
deny tcp 202.14.88.0 0.0.0.255 any eq smtp
deny tcp 202.14.103.0 0.0.0.255 any eq smtp
deny tcp 202.14.165.0 0.0.0.255 any eq smtp
deny tcp 202.14.235.0 0.0.0.255 any eq smtp
deny tcp 202.14.236.0 0.0.1.255 any eq smtp
deny tcp 202.14.238.0 0.0.0.255 any eq smtp
deny tcp 202.20.82.0 0.0.1.255 any eq smtp
deny tcp 202.20.84.0 0.0.1.255 any eq smtp
deny tcp 202.20.86.0 0.0.0.255 any eq smtp
deny tcp 202.20.99.0 0.0.0.255 any eq smtp
deny tcp 202.20.119.0 0.0.0.255 any eq smtp
deny tcp 202.20.120.0 0.0.0.255 any eq smtp
deny tcp 202.20.128.0 0.0.127.255 any eq smtp
deny tcp 202.21.0.0 0.0.7.255 any eq smtp
deny tcp 202.22.248.0 0.0.7.255 any eq smtp
deny tcp 202.30.0.0 0.0.255.255 any eq smtp
deny tcp 202.38.0.0 0.0.15.255 any eq smtp
deny tcp 202.38.32.0 0.0.15.255 any eq smtp
deny tcp 202.38.64.0 0.0.63.255 any eq smtp
deny tcp 202.38.128.0 0.0.7.255 any eq smtp
deny tcp 202.38.136.0 0.0.1.255 any eq smtp
deny tcp 202.38.138.0 0.0.0.255 any eq smtp
deny tcp 202.38.140.0 0.0.3.255 any eq smtp
deny tcp 202.38.144.0 0.0.3.255 any eq smtp
deny tcp 202.38.149.0 0.0.0.255 any eq smtp
deny tcp 202.38.150.0 0.0.1.255 any eq smtp
deny tcp 202.38.152.0 0.0.3.255 any eq smtp
deny tcp 202.38.156.0 0.0.0.255 any eq smtp
deny tcp 202.38.158.0 0.0.1.255 any eq smtp
deny tcp 202.38.160.0 0.0.1.255 any eq smtp
deny tcp 202.38.164.0 0.0.3.255 any eq smtp
deny tcp 202.38.168.0 0.0.7.255 any eq smtp
deny tcp 202.38.176.0 0.0.1.255 any eq smtp
deny tcp 202.38.184.0 0.0.7.255 any eq smtp
deny tcp 202.38.192.0 0.0.63.255 any eq smtp
deny tcp 202.90.0.0 0.0.3.255 any eq smtp
deny tcp 202.90.252.0 0.0.3.255 any eq smtp
deny tcp 202.91.0.0 0.0.3.255 any eq smtp
deny tcp 202.91.128.0 0.0.3.255 any eq smtp
deny tcp 202.92.0.0 0.0.3.255 any eq smtp
deny tcp 202.92.252.0 0.0.3.255 any eq smtp
deny tcp 202.93.0.0 0.0.3.255 any eq smtp
deny tcp 202.93.252.0 0.0.3.255 any eq smtp
deny tcp 202.94.0.0 0.0.31.255 any eq smtp
deny tcp 202.95.0.0 0.0.31.255 any eq smtp
deny tcp 202.95.252.0 0.0.3.255 any eq smtp
deny tcp 202.96.0.0 0.15.255.255 any eq smtp
deny tcp 202.112.0.0 0.7.255.255 any eq smtp
deny tcp 202.120.0.0 0.1.255.255 any eq smtp
deny tcp 202.122.0.0 0.0.31.255 any eq smtp
deny tcp 202.122.32.0 0.0.7.255 any eq smtp
deny tcp 202.122.128.0 0.0.0.255 any eq smtp
deny tcp 202.127.0.0 0.0.63.255 any eq smtp
deny tcp 202.127.128.0 0.0.127.255 any eq smtp
deny tcp 202.130.0.0 0.0.31.255 any eq smtp
deny tcp 202.130.224.0 0.0.31.255 any eq smtp
deny tcp 202.131.208.0 0.0.15.255 any eq smtp
deny tcp 202.136.252.0 0.0.3.255 any eq smtp
deny tcp 202.168.160.0 0.0.15.255 any eq smtp
deny tcp 202.189.128.0 0.0.63.255 any eq smtp
deny tcp 202.192.0.0 0.15.255.255 any eq smtp
deny tcp 203.81.16.0 0.0.15.255 any eq smtp
deny tcp 203.87.224.0 0.0.31.255 any eq smtp
deny tcp 203.88.0.0 0.0.3.255 any eq smtp
deny tcp 203.89.0.0 0.0.3.255 any eq smtp
deny tcp 203.90.0.0 0.0.3.255 any eq smtp
deny tcp 203.91.0.0 0.0.3.255 any eq smtp
deny tcp 203.92.0.0 0.0.3.255 any eq smtp
deny tcp 203.93.0.0 0.0.31.255 any eq smtp
deny tcp 203.94.0.0 0.0.63.255 any eq smtp
deny tcp 203.95.0.0 0.0.7.255 any eq smtp
deny tcp 203.128.128.0 0.0.31.255 any eq smtp
deny tcp 203.175.192.0 0.0.63.255 any eq smtp
deny tcp 203.184.0.0 0.0.3.255 any eq smtp
deny tcp 203.192.0.0 0.0.31.255 any eq smtp
deny tcp 203.196.0.0 0.0.3.255 any eq smtp
deny tcp 203.207.64.0 0.0.63.255 any eq smtp
deny tcp 203.207.128.0 0.0.127.255 any eq smtp
deny tcp 203.208.0.0 0.0.15.255 any eq smtp
deny tcp 203.208.16.0 0.0.3.255 any eq smtp
deny tcp 203.212.0.0 0.0.15.255 any eq smtp
deny tcp 203.222.192.0 0.0.7.255 any eq smtp
deny tcp 203.223.0.0 0.0.15.255 any eq smtp
deny tcp 203.224.0.0 0.31.255.255 any eq smtp
deny tcp 210.5.0.0 0.0.31.255 any eq smtp
deny tcp 210.5.0.0 0.0.15.255 any eq smtp
deny tcp 210.12.0.0 0.1.255.255 any eq smtp
deny tcp 210.14.160.0 0.0.31.255 any eq smtp
deny tcp 210.14.192.0 0.0.63.255 any eq smtp
deny tcp 210.15.0.0 0.0.127.255 any eq smtp
deny tcp 210.15.128.0 0.0.63.255 any eq smtp
deny tcp 210.21.0.0 0.0.255.255 any eq smtp
deny tcp 210.22.0.0 0.0.255.255 any eq smtp
deny tcp 210.25.0.0 0.0.255.255 any eq smtp
deny tcp 210.26.0.0 0.1.255.255 any eq smtp
deny tcp 210.28.0.0 0.3.255.255 any eq smtp
deny tcp 210.32.0.0 0.15.255.255 any eq smtp
deny tcp 210.51.0.0 0.0.255.255 any eq smtp
deny tcp 210.52.0.0 0.1.255.255 any eq smtp
deny tcp 210.72.0.0 0.3.255.255 any eq smtp
deny tcp 210.76.0.0 0.1.255.255 any eq smtp
deny tcp 210.78.0.0 0.0.255.255 any eq smtp
deny tcp 210.79.224.0 0.0.31.255 any eq smtp
deny tcp 210.80.96.0 0.0.31.255 any eq smtp
deny tcp 210.82.0.0 0.1.255.255 any eq smtp
deny tcp 210.90.0.0 0.1.255.255 any eq smtp
deny tcp 210.92.0.0 0.3.255.255 any eq smtp
deny tcp 210.96.0.0 0.31.255.255 any eq smtp
deny tcp 210.178.0.0 0.1.255.255 any eq smtp
deny tcp 210.180.0.0 0.3.255.255 any eq smtp
deny tcp 210.192.0.0 0.0.31.255 any eq smtp
deny tcp 210.204.0.0 0.3.255.255 any eq smtp
deny tcp 210.211.0.0 0.0.15.255 any eq smtp
deny tcp 210.216.0.0 0.7.255.255 any eq smtp
deny tcp 211.32.0.0 0.31.255.255 any eq smtp
deny tcp 211.64.0.0 0.7.255.255 any eq smtp
deny tcp 211.80.0.0 0.15.255.255 any eq smtp
deny tcp 211.96.0.0 0.7.255.255 any eq smtp
deny tcp 211.104.0.0 0.7.255.255 any eq smtp
deny tcp 211.112.0.0 0.7.255.255 any eq smtp
deny tcp 211.136.0.0 0.7.255.255 any eq smtp
deny tcp 211.144.0.0 0.15.255.255 any eq smtp
deny tcp 211.160.0.0 0.7.255.255 any eq smtp
deny tcp 211.168.0.0 0.7.255.255 any eq smtp
deny tcp 211.176.0.0 0.15.255.255 any eq smtp
deny tcp 211.192.0.0 0.63.255.255 any eq smtp
deny tcp 218.0.0.0 0.31.255.255 any eq smtp
deny tcp 218.36.0.0 0.3.255.255 any eq smtp
deny tcp 218.48.0.0 0.7.255.255 any eq smtp
deny tcp 218.56.0.0 0.7.255.255 any eq smtp
deny tcp 218.64.0.0 0.31.255.255 any eq smtp
deny tcp 218.96.0.0 0.3.255.255 any eq smtp
deny tcp 218.104.0.0 0.3.255.255 any eq smtp
deny tcp 218.108.0.0 0.1.255.255 any eq smtp
deny tcp 218.144.0.0 0.15.255.255 any eq smtp
deny tcp 218.192.0.0 0.7.255.255 any eq smtp
deny tcp 218.200.0.0 0.3.255.255 any eq smtp
deny tcp 218.204.0.0 0.1.255.255 any eq smtp
deny tcp 218.232.0.0 0.7.255.255 any eq smtp
deny tcp 218.240.0.0 0.7.255.255 any eq smtp
deny tcp 219.72.0.0 0.0.255.255 any eq smtp
deny tcp 219.128.0.0 0.31.255.255 any eq smtp
deny tcp 219.216.0.0 0.7.255.255 any eq smtp
deny tcp 219.224.0.0 0.1.255.255 any eq smtp
deny tcp 219.226.0.0 0.0.255.255 any eq smtp
deny tcp 219.228.0.0 0.1.255.255 any eq smtp
deny tcp 219.232.0.0 0.7.255.255 any eq smtp
deny tcp 219.240.0.0 0.1.255.255 any eq smtp
deny tcp 219.242.0.0 0.1.255.255 any eq smtp
deny tcp 219.244.0.0 0.3.255.255 any eq smtp
deny tcp 219.248.0.0 0.7.255.255 any eq smtp
deny tcp 220.64.0.0 0.7.255.255 any eq smtp
deny tcp 220.72.0.0 0.7.255.255 any eq smtp
deny tcp 220.80.0.0 0.7.255.255 any eq smtp
deny tcp 220.88.0.0 0.3.255.255 any eq smtp
deny tcp 220.112.0.0 0.3.255.255 any eq smtp
deny tcp 220.116.0.0 0.3.255.255 any eq smtp
deny tcp 220.120.0.0 0.7.255.255 any eq smtp
deny tcp 220.160.0.0 0.31.255.255 any eq smtp
deny tcp 220.192.0.0 0.15.255.255 any eq smtp
deny tcp 220.248.0.0 0.7.255.255 any eq smtp
deny tcp 221.0.0.0 0.7.255.255 any eq smtp
deny tcp 221.7.128.0 0.0.127.255 any eq smtp
deny tcp 221.8.0.0 0.1.255.255 any eq smtp
deny tcp 221.10.0.0 0.0.255.255 any eq smtp
deny tcp 221.11.0.0 0.0.127.255 any eq smtp
deny tcp 221.11.128.0 0.0.63.255 any eq smtp
deny tcp 221.12.0.0 0.0.127.255 any eq smtp
deny tcp 221.12.128.0 0.0.63.255 any eq smtp
deny tcp 221.13.0.0 0.0.63.255 any eq smtp
deny tcp 221.13.64.0 0.0.31.255 any eq smtp
deny tcp 221.138.0.0 0.1.255.255 any eq smtp
deny tcp 221.140.0.0 0.15.255.255 any eq smtp
deny tcp 221.144.0.0 0.15.255.255 any eq smtp
deny tcp 221.160.0.0 0.7.255.255 any eq smtp
deny tcp 221.168.0.0 0.0.255.255 any eq smtp

[frederic]

Originally posted by Vixen
I understand that innocent people get caught up in situations that they had nothing to do with but that is not an excuse (at least to me) for continuing to stay on a network that is considered a spamhaus.

Just my opinion.

but blocking or filtering ALL emails from Chinanet is too much! All of our Chinese customers are affected by this spam systerm. If this policy goes on, we loose all of our business. It is not fair to us! there should be many better systerms than this simple and cruel anti-spam one.

[Vixen]

Originally posted by frederic
You send a formal email / document to those main ISPs from which many spams are sent out. Or you can avenge them in your own way. I believe that those main ISPs have some way to filter or to block the spams.

At any rate, I personally think it is not reasonable to block all the emails sent out from China. In fact, this is more harm than benefit. Just like, someone is afraid of cheating in business, then gives up his business.

It is not our responsibility to tell them to remove their spammers. If we are blocking their network by using the RBL list then many other companies are blocking them also. Therefore, I would think their legitimate customers would be complaining about their emails not getting through due their network being placed on the RBL list. If they do not care enough about their legitimate customers to get rid of the spammers, then maybe they should move to another ISP.

[Vixen]

Originally posted by glauco


Please, get back to the previous email system that was working really fine for me.

Thanks in advance.


Glauco

So, all customers not getting emails for DAYS or HOURS because spammers are backing up the mail servers is better than us blocking the spammers??

Customers complain when their email is slow or late. We block the spam to enable to legitimate mail to pass through as it should and now that is wrong??

I REALLY do not get you guys sometimes.

[jmbeach]

Originally posted by Vixen
I am at a loss how some people want to make this our problem when their customers utilize ISPs that are blocked because they are known to harbor/allow spammers. Personally, if I were on a network that was being blocked I would want to know so I could make a change. I guess other people do not see it this way.

I understand that innocent people get caught up in situations that they had nothing to do with but that is not an excuse (at least to me) for continuing to stay on a network that is considered a spamhaus.

Just my opinion.

I think the problem is a lot less simple than just switching providers. Perhaps some don't actually have a choice to switch. Then there's the fact that resellers now have to try and explain why this is happening, when before spam was present, but all mail got through. Customers are sure to leave by the truckload when they realize they can go elsewhere where there aren't these types of restrictions.

I think it's pretty clear that no spam filters are perfect, and Spamhaus and the like are no exception. There have to be any number of indiscriminate bans, and that's clearly going to affect many users.

I know there is that fine balance between protecting the mail servers, and how they perform, and fighting spam.

I can say I join the side of "let me handle spam"

In another post (or maybe it was here) there was mention that PSoft forgot to add some "SMTP before something" which may have caused the password prompting issue. If the password fiasco was a result of that and not spam, is it safe to say you don't need the filtering in place anymore?

Admittedly, my main business account has seen a drop in all emails, so I too am worried that the filters are too strict and I'm losing valuable mail. On the other side, an old email account of mine that has always received a lot of spam is still getting about the same amount, so I don't know if it's doing a whole lot.

I would be interested to know if it's possible for you to send us all the mail that is getting bounced back for spam issues. This way we could see what's going back before reaching us. It may not be possible to do, but would help us know to what extent it's working.

That's all - it's a lot, but all.