Correct header references for HEADER content control

GordonM

posted Oct 23 '08 at 5:35 am

Dave - Yes, I think the rules are working correctly for me.

I am using:

if HEADER

"Received" CONTAINS ".ru ([" weight 51 tag "foreign"

... so no asterisk. I don't think that * should be used in simple string tests, only in regular expressions (unless one is trying to match a * in a string).

Other rules that I am finding useful are of the form:

if HEADER "Received" CONTAINS ".pt[" weight 51 tag "foreign"

if HEADER
"From" CONTAINS ".lv>" weight 51 tag "foreign"
if SENDER CONTAINS
"*.ro>" weight 51 tag "foreign"
if HEADER
"Received" CONTAINS ".do (" weight 51 tag "foreign"
if HEADER
"Received" CONTAINS ".kh)" weight 51 tag "foreign"

Gordon

Dave - Yes, I think the rules are working correctly for me.&nbsp;&nbsp; I am using: if HEADER "Received" CONTAINS ".ru ([" weight 51 tag "foreign" ... so no asterisk.&nbsp; I don't think that * should be used in simple string tests, only in regular expressions (unless one is trying to match a * in a string). Other rules&nbsp;that I am finding useful are of the form:&nbsp; <BLOCKQUOTE> if HEADER "Received" CONTAINS ".pt[" weight 51 tag "foreign" if HEADER "From" CONTAINS ".lv&gt;" weight 51 tag "foreign" if SENDER CONTAINS "*.ro&gt;" weight 51 tag "foreign" if HEADER "Received" CONTAINS ".do (" weight 51 tag "foreign" if HEADER "Received" CONTAINS ".kh)" weight 51 tag "foreign"</BLOCKQUOTE> Gordon &nbsp;

GordonM

posted Jan 24 '08 at 6:58 pm

I am trying to test "Received:" headers as a basis for filtering in Content Control. So far, this doesn't seem to be working properly.

There are some countries from which I don't want to receive mail. So one example of a line in my content control file is:

if HEADER "Received" CONTAINS "*.ru ([*" weight 51

The trigger weighting is 50.

However, mail from .ru is still being received. even though it contains the *.ru ([* sequence in one of the Received: lines of the header.

I have tried Received and Received: (with a colon) and this doesn't make any difference.

There is usually more than one Received: header in a typical message and I am wondering whether this may be an issue, given that a local "Received:" header usually shows first in the header and one containing the filtering characters is usually second.

I am using Mercury/32 v.4.52.

Any help muich appreciated.

Thank you

GordonM

I am trying to test "Received:" headers as a basis for filtering in Content Control.&nbsp; So far, this doesn't seem to be working properly. There are some countries from which I don't want to receive mail.&nbsp; So one example of a line in my content control file is: &nbsp;if HEADER "Received" CONTAINS "*.ru ([*" weight 51 The trigger weighting is 50.&nbsp; However, mail from .ru is still being received. even though it contains the *.ru ([* sequence in one of the Received: lines of the header. I have tried Received and Received: (with a colon) and this doesn't make any difference. There is usually more than one Received: header in&nbsp;a typical message and I am wondering whether this may be an issue, given that a local "Received:" header usually shows first in the header and one containing the filtering characters is usually second. I am using Mercury/32 v.4.52. Any help muich appreciated. Thank you GordonM

Thomas R. Stephenson

posted Jan 24 '08 at 7:28 pm

[quote user="GordonM"]

I am trying to test "Received:" headers as a basis for filtering in Content Control. So far, this doesn't seem to be working properly.

There are some countries from which I don't want to receive mail. So one example of a line in my content control file is:

if HEADER "Received" CONTAINS "*.ru ([*" weight 51

The trigger weighting is 50.

However, mail from .ru is still being received. even though it contains the *.ru ([* sequence in one of the Received: lines of the header.

I have tried Received and Received: (with a colon) and this doesn't make any difference.

There is usually more than one Received: header in a typical message and I am wondering whether this may be an issue, given that a local "Received:" header usually shows first in the header and one containing the filtering characters is usually second.

I am using Mercury/32 v.4.52.

Any help muich appreciated.

Thank you

GordonM

[/quote]

Does it actually contain "*.ru" or does it contain <something>.ru? If so try using ".ru" only.

[quote user="GordonM"]I am trying to test "Received:" headers as a basis for filtering in Content Control.&nbsp; So far, this doesn't seem to be working properly. There are some countries from which I don't want to receive mail.&nbsp; So one example of a line in my content control file is: &nbsp;if HEADER "Received" CONTAINS "*.ru ([*" weight 51 The trigger weighting is 50.&nbsp; However, mail from .ru is still being received. even though it contains the *.ru ([* sequence in one of the Received: lines of the header. I have tried Received and Received: (with a colon) and this doesn't make any difference. There is usually more than one Received: header in&nbsp;a typical message and I am wondering whether this may be an issue, given that a local "Received:" header usually shows first in the header and one containing the filtering characters is usually second. I am using Mercury/32 v.4.52. Any help muich appreciated. Thank you GordonM[/quote]&nbsp;Does it actually contain "*.ru"&nbsp; or does it contain &lt;something&gt;.ru?&nbsp; If so try using ".ru" only.&nbsp;

GordonM

posted Jan 24 '08 at 7:34 pm

Thomas - A recent header contained:

Received: from 83.239.45.189.modem-pool.kuban.ru ([83.239.45.189])
by prserv.net (kcin01) with SMTP
id <2008012416001010100o1oohe>; Thu, 24 Jan 2008 16:00:15 +0000

If I don't need the asterisks in the rule, I'll try the .ru alone.

Thank you for the quick reply.

GordonM

Thomas - A recent header contained: Received: from 83.239.45.189.modem-pool.kuban.ru ([83.239.45.189]) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; by prserv.net (kcin01) with SMTP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; id &lt;2008012416001010100o1oohe&gt;; Thu, 24 Jan 2008 16:00:15 +0000 If I don't need the&nbsp;asterisks in the rule, I'll try the .ru alone. Thank you for the quick reply. GordonM &nbsp;

Thomas R. Stephenson

posted Jan 24 '08 at 10:57 pm

I'd use ".ru " instead of ".ru" to ensure it only sees the .ru. The ".ru" will match mail.rull.com where the ".ru " will not.

I'd use ".ru " instead of ".ru" to ensure it only sees the .ru.&nbsp; The ".ru" will match mail.rull.com where the ".ru " will not.&nbsp;&nbsp;

GordonM

posted Jan 24 '08 at 11:44 pm

Thomas - Yes, I have done that. It's now a question of waiting to see if I get any mail with these sort of headers.

Thank you

GordonM

Thomas - Yes, I have done that.&nbsp; It's now a question of waiting to see if I get any mail with these sort of headers. Thank you GordonM

GordonM

posted Jan 30 '08 at 10:28 pm

Content control on unwanted national domains is now working very well. Thank you, Thomas

Content control on unwanted national domains is now working very well.&nbsp; Thank you, Thomas

Leizure

posted Oct 23 '08 at 12:13 am

Hi Gordon,

Did you manage to get this resolved as I'm having the same problem?

Regards

Dave.

Hi Gordon,Did you manage to get this resolved as I'm having the same problem?RegardsDave.

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history