Home » Kerio User Forums » Kerio Connect » autoreply, User: Global deliver rule (Where is this rule so I can modify it?????)
  •  
docwu

Messages: 1
Karma: 0
Send a private message to this user
Since newer spammers are registering -valid- mail domains, a few are getting through my SPAM filter. I am not using the Kerio spam filter, I have a separate spam filter "in front of" the Kerio Conenct server.

So these emails make it to KC and by some magic, KC recognizes something is wrong and in my log I see the message get delivered to the recipient..but then immediately the Sieve service send ....

Service: Sieve, From: <xxxx@xxxx.xxx>, To: <crap@garbage.com>, Size: 595, Report: autoreply, User: Global deliver rule, Subject: Re: Application, Msg-Id: <498334392-31780<_at_>mail.xxxxx.xxx>

The actual email addresses have been changed, xxxx.xxxx.xxx being the local recipient that received the non-blocked spam message.

My very simple question, asked twice already over the past couple of years is...
Where is this 'Global deliver rule' and how do I modify it.

What did this rule see to prompt it to send a NDR? and when it did see a problem, why did it deliver it in the first place?

It seems like there are a set of default rules somewhere that I do not have access to. At the very least I'd like the rule to do nothing when it find this issue. Sending a NDR to the spam email address just caused a bunch of NDR emails going back to the local recipient when KC cannot send the NDR.

Where is this rule and how do I modify it.
Where is this rule and how do I modify it.
Where is this rule and how do I modify it.
Where is this rule and how do I modify it.
Where is this rule and how do I modify it.

Seems a pretty simple question but two other people have unanswered posts on here about this.
Let's see if my time spent posting this gets any kind of -useful- response.


  •  
Maerad

Messages: 217
Karma: 38
Send a private message to this user
That is no global rule, the user just set an out of office msg with his client.

This is different from Exchange or Icewarp. Kerio has NO way for an admin (at least changing the config or local db) to see or config out of office rules a user defined. E.g. in Outlook you can set an out of office message, this is per user and you can't do shit about it as admin. Or if the user has rules defined.

Maybe take a look at MailServer\settings\config, there's a config.db, SQLite DB, could be opened with any DB reader.

Btw. this works as intended! Your Antispam functions as a transparent proxy, so if kerio won't see this as spam and you didn't filter it beforehand, it's recognized as normal mail and will get handled by it. The only option here is to tell the user to disable this crap. Nothing else will work, aside maybe from changing the antispam detection to a bit more agressive.

This is not Kerio's fault. You would have the same problem with any other mail server.

EDIT: Found it. Store\Mail\Your.Domain\User > filter.siv, open in notepad, it's the part with #!1 __WebmailAutoreply__

[Updated on: Fri, 12 October 2018 15:18]

Previous Topic: KoffRtfWrapper CPU usage
Next Topic: Help - server getting hammered
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Fri Dec 14 12:49:45 CET 2018

Total time taken to generate the page: 0.94484 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.