Implementing Zen (Discussion and feedback) - Page 2

jjarrett · 10-17-2009, 02:24 PM

Thanks, 'dog...yeah I know...just annoying to pay for a private IP address then get blocked because the whole Class C (or whatever) gets blocked.

More importantly, can we get a Zen update?

I just did my weekly e-mail download...ugh....

**NexDog** · 10-17-2009, 10:15 PM

Pretty disappointed with the lack of interest.

jjarrett · 10-18-2009, 10:22 AM

Well, you can always implement it with the caveat that 2/3rds of those with an opinion voted for it...though that's easy for me to say since I won't have to take the support phone calls.

lharvey · 10-18-2009, 09:50 PM

Well that's too bad.

Geez....

j-z · 10-29-2009, 12:21 PM

I can see where this is going. I'll get an email from every client, every time they get one of these. They aren't going to get it, not matter how plain of English it's written. So I'll be the one dealing with all these (that's how my rapport with client's is) and that would likely be a nightmare.

If this does get implemented I'd want a way to police my client's email activities -- a way to make sure they aren't sending out bulk emails to thousands at a time (not spam, but big newsletter mailings to their clients). As much as I try to keep my clients from doing that there's going to be that one that will. In other words, I want to be able to be proactive, not reactive.

tmcleroy · 11-02-2009, 01:59 PM

Hi Laurence, First off I am all for clamping down on spam and hard. I have thought for a long time that in general the way email was designed is very very poor.

I did not respond but I think you know where I stand as I asked for Zen.spamhaus back in July and an upgrade of the SpamAssassin engine. When you put it on back then my spam went way down. I would say, however, the implementation prior to the September upgrade on PION seemed better than the implementation now--after the upgrade of the SpamAssassin engine from 3.18 to 3.23. I cannot explain why that would be--though I do not know all the things that went on behind the scenes.

My experience may be different than others as I have a few professional people that I support. In this day of Blackberry, IPhone etc. mail is coming into their phones too and spam is a real problem. I have only been with you folks for a few months. Prior to that I was with an Australian firm Webstrike that decided to close. They used an Alligate gateway, had an excellent setup and spam was minimal. I also really liked their graylisting and Spam Digest features--one email containing all mail marked as spam each day that you could respond to to whitelist, blacklist or retrieve individual email. http://www.alligate.com/ So I come from knowing that spam can be controlled and handled well to.

To your article points:
1) Some people might have issues sending you mail. If they are savvy enough they can click the link in the bounced mail and delist quickly but alot of people are not going to do that. Some might contact their host or ISP to get it resolved. Some just might not send that email.

2) You (or your users) might not be able to send mail. The upside of this downside is that you are all web savvy and know to delist.

These issues I would say in most cases happen because the email or the server is compromised. The root problem is the compromise that needs to be addressed. If spam is coming from the sender's email or servers they should know that and get if fixed. I am not sure I want their email and hundreds of spam from their server in my account and Blackberry.

I have not had any problems to date with my email blocked in sending unless I have tried to bounce it off my ISP's servers without having set up with them properly. Then again, on my ISP email account I get no spam. However, if I am blocked and my email or servers have been compromised I should know that and get it fixed.

Thomas