SPAM Problem


Badge +2
hi,

i have deployd the k2 solution on a test machine but when i initiate the process the notification email is reached on SPAM folder instead of INBOX
on destination user outlook.

Please advice

11 replies

Badge +5
Hi
This is probably because of content filtering. Make sure that the message body and subject don't contain any illegal content that will be picked up as spam. Blank subjects are also picked up as spam.
What mail client are you using?
Badge +2
hi,

The Email client is microsoft exchange.
The email subject is not blank and does not contains any illegal characters, is it a rule applied on exchange server ????

thx,
Badge +5
Exchange has a lot of built-in antispam features. You can have a look at the following article :
http://www.microsoft.com/exchange/techinfo/security/antispam.asp
for more information on how to fine-tune and configure the features.
Badge

Hi,


We have the same problem. This is not content related - the same email sent from yahoo or gmail gets through no problem. We have disable all spam settings we could find. Still no joy.


 Maybe the way that the email is sent? How does K2 send email? 

Badge +5

Hi,


K2 creates a MailMessage object from the System.Web.Mail namespace, then it sets all the required properties and sends the mail using the SMTP server defined in the Server.config file. What mail server and client are you using?


Regards

Badge +13

We had the same problem, and we have stopped the spam filter within Outlook.

We still use third party spam filters on Exchange. 

Badge +6

You may also want to ensure that the sender/from email account is a valid email syntax (user@mycompany.com) and/or valid user/email account within the domain. Using something like from="K2-Notify" as the sender is no longer enough it seems.

Badge +13
We used a valid "user@companydomain.com" syntax.
Badge +3

Sometimes having a hyperlink in an email will be detected as SPAM within Outlook.


Can you simply "add to safe senders" list ?    Within Outlook ?

Badge +2

We've been plagued with the same issue until I came across this knowledge base article:


http://blogs.technet.com/asiasupp/archive/2007/04/26/how-to-deploy-junk-e-mail-lists-throughout-your-organization.aspx


We put the junk.txt into our sysvol folder on our DC's so it's always up to date.


Give it a try!


Jonathan

Badge
We managed to resolve the problem by adding the K2 server as a "safe server" on our exchange server.

Reply