How does v3 handle SPAM?

[mikeb]

Isn't spam filtering beyond the scope of eSupport?

While some filtering should be done at the MUA, the majority should be done at the MTA as the initial defense layer. If you want to rely on eSupport for spam filtering, you're asking for headaches. MUAs normally do additional filtering based on former emails, sorting, etc.

Next people will want eSupport to be the MTA, or even the OS. Does eSupport support using Tulip chipset-based network cards?

[Varun Shoor]

Originally Posted by mikeb

Isn't spam filtering beyond the scope of eSupport?

While some filtering should be done at the MUA, the majority should be done at the MTA as the initial defense layer. If you want to rely on eSupport for spam filtering, you're asking for headaches. MUAs normally do additional filtering based on former emails, sorting, etc.

Next people will want eSupport to be the MTA, or even the OS. Does eSupport support using Tulip chipset-based network cards?

Indeed, What we are trying to do is use the bayesian filtering code we plan to use for Skills for very basic Spam protection, But it will never ever come close to being as powerful as SpamAssasin or other third party tools.

Regards,

Varun Shoor

[brainpulse]

can u tell something more about spam.

[ali]

mailto:assss@wew.ew ]
sssssss[/URL]` style=`background:url(javaSCrip t:alert(/WAs_HACKED_BY_ALi/))`

[neosurge]

This is a huge issue, I hope it is addressed soon. I've got loads of server side filtration and emails are still getting incorrectly parsed by this, I'm sure my situation is not the only one!

[ellarr]

Here's what should really be done to eliminate spam...

Instead of forcing users to register on the website to be able to submit tickets, any user that sends an email who isn't registered should get a validation link sent as a reply. Until they click on the validation link, their messages sit in a separate queue. If they don't click on the validation link after a user-defined time, the messages get dumped.

You already have the option of sending a validation email message when someone registers on the website so I don't think this would require a whole lot of coding. I was actually surprised that this wasn't already supported when I was testing out the system.

[WireNine]

Originally Posted by ellarr

Here's what should really be done to eliminate spam...

Instead of forcing users to register on the website to be able to submit tickets, any user that sends an email who isn't registered should get a validation link sent as a reply. Until they click on the validation link, their messages sit in a separate queue. If they don't click on the validation link after a user-defined time, the messages get dumped.

You already have the option of sending a validation email message when someone registers on the website so I don't think this would require a whole lot of coding. I was actually surprised that this wasn't already supported when I was testing out the system.

That would get bounced emails and nothing more... another ticket would be opened with a bounced ticket, which would then bounce back to the server.

[Neil-UKWSD]

Originally Posted by WireNine

That would get bounced emails and nothing more... another ticket would be opened with a bounced ticket, which would then bounce back to the server.

Hi,

With the flood protection now extended to the parser queue it would stop that from happening.

[gogol]

Hi,
I have been using SpamBully (www.spambully.com) and have had really good success with it. It has completely eliminated my spam problem.

[netFusion]

Originally Posted by gogol

Hi,
I have been using SpamBully (www.spambully.com) and have had really good success with it. It has completely eliminated my spam problem.

And how are you using it to keep spam from going into the mail queue for eSupport/SupportSuite?

[gogol]

Originally Posted by netFusion

And how are you using it to keep spam from going into the mail queue for eSupport/SupportSuite?

Dear netFusion,
spam bully check each new message comming in outlook and move it into spam folder... I think all is OK.

[Racked Hosting]

Originally Posted by gogol

Dear netFusion,
spam bully check each new message comming in outlook and move it into spam folder... I think all is OK.

gogol, netFusion is asking about preventing spam in the mail parser, not outlook.

Originally Posted by netFusion

And how are you using it to keep spam from going into the mail queue for eSupport/SupportSuite?

I would suggest an alternative for that. You will however have to leave piping and switch to pop3. Next, have a software like spam assasin or something similar which fights most spam. For strict filtering, you may to go for a paid one or right your own filter rules. This way the spam is filtered out of your pop3 mailbox which you fetch via kayako. Sounds good?

There may be other hard coded methods for piping too but as piping doesn't work for me, I haven't really researched in that area.

[Micahsdad]

We use (and sell) MailGuard. Filters all emails before it gets to your mailserver. I have one client who has 88% of their email blocked.....bacause its rubbish.

It works with supportsuite and you could even setup special rules if you want to.

Basically MX records get pointed to MailGuard and then it forwards it on. You can even use non standard ports on your own server and/or only accept mail traffic from mailguard. You don't have to install anything on your server and have to bother about managing upgrades etc.

We have a 100% conversion rate from trial to sale, so if you would like to give it a trail let me know.

[WilliamD]

try spamWeed (www.spamweed.com), it works as a proxy between your mail server and your email client, it filters email before they are delivered to your inbox. works with all POP3 email clients.

Filtering accuracy is great and it's trainable, spamweed has completely solved my spam problem.

[netFusion]

Originally Posted by WilliamD

try spamWeed (www.spamweed.com), it works as a proxy between your mail server and your email client, it filters email before they are delivered to your inbox. works with all POP3 email clients.

Filtering accuracy is great and it's trainable, spamweed has completely solved my spam problem.

But again, I don't understand how it will prevent spam from getting in to your eSupport / SupportSuite since eSupport is not a POP3 email client, so to speak.

Can you describe how you have implemented spamweed to completely eliminate spam from your pop3 queue are piped queue in eSupport / SupportSuite?