Pegasus Mail & Mercury

I am trying to track down an issue, which has been causing some problems with my SPAM filtering.  In doing this, I tried to insert some test headers, as part of the Global Filtering process, into messages to track progress through rule set.  However, none of these headers has showed up in any messages that I received, including test messages that I sent to myself.  In case I was missing something in the logic of the rule set, I added a header as the very first rule in Global Filtering.  This rule shows up in RULES.MER as:

Always AddHeader "X-Filter: Filtering rules started"

Unfortunately, this header isn't showing up either.

Can anyone suggest an explanation?

Thank you

Gordon

 

>  I am trying to track down an issue, which has been causing some problems with my SPAM filtering.  In doing this, I tried to insert
> some test headers, as part of the Global Filtering process, into messages to track progress through rule set.  However, none of these
> headers has showed up in any messages that I received, including test messages that I sent to myself.  In case I was missing something in
> the logic of the rule set, I added a header as the very first rule in Global Filtering.  This rule shows up in RULES.MER as:
>
> Always AddHeader "X-Filter: Filtering rules started"
>
> Unfortunately, this header isn't showing up either.

How are you receiving the mail?  MercuryD?  MercuryS?

How are you delivering the mail?  Core only?  Filter that takes it out of the normal delivery process?

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.

Thomas - I am receiving the mail with Mercury D.  I am not sure that I understand your question with regard to delivery.  Typically what happens in the filtering process is that various rules are applied and eventually the mail is moved to a specified user, unless it is recognized as possible SPAM, in which case, after exiting the filtering rules, several Policies are applied.  Maybe that is what you refer to as "Filter that takes it out of the normal delivery process".

Thank you

Gordon

Yep.

and eventually the mail is moved to a specified user

The only way an added header will be in the delivered message is if it passes through all filter rules & is delivered by the core process to the users folder.

Anything that is copied or moved by a rule will only get the original message.

Thanks, DLN.  It was dawning on me that this must be happening.  It's not a problem for the filtering processes that I am using, but it is going to prevent me from using headers as tags to follow through the steps of the filtering rules.  I have to think of a different way to do this, given that I have so far failed to determine why a small number of messages are causing problems to the filtering process.

Actually, now I think about it, maybe what I am trying to do with these headers is going to work.  This is because the messages that are causing problems to the processing are among the very few that go through the whole filtering rule set and are then passed on to Policies.  So I haven't copied or moved these particular messages.  My test messages were not of this type.  I am going to have to either manufacture a spam-like message, which isn't deleted by any filtering rules, or wait till a get some real spam with this characteristic. I am only dealing with the last half percent or so of spam messages, so I get very few a day to work on.

Thank you

Gordon

Make your own.

Use an old spam, add "glue headers" at the top, and drop into the queue folder.

Thanks DLN.  I'll give it a try.

Gordon

> Thomas - I am receiving the mail with Mercury D.  I am not sure that I understand your question with regard to delivery.  Typically what
> happens in the filtering process is that various rules are applied and eventually the mail is moved to a specified user, unless it is
> recognized as possible SPAM, in which case, after exiting the filtering rules, several Policies are applied.  Maybe that is what you
> refer to as "Filter that takes it out of the normal delivery process".

The "MOVE" functions takes it out of the normal deliver process and essentially deletes all the header adds.  Use a an alias to get the mail delivered to the proper user by core and the header add will work.

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.