Search Results matching tag 'filtering rule'

Filter invalid commands

Kevin Hastings — Sat, 30 Jun 2012 03:15:04 GMT

T 20120626 113131 4fe5770e Connection from 208.122.116.51

T 20120626 113131 4fe5770e GET / HTTP/1.0

T 20120626 113131 4fe5770e

T 20120626 113135 4fe5770e Connection closed with 208.122.116.51, 4 sec. elapsed.

If I add:

H, "GET*", DS

to transflt.mer will that stop this kind of transaction quicker? because there is no HELO greeting so I am unsure. Also if it won't work could you suggest something else that might?

Thanks.

Mercury 32 V. 4.61

Theresa Williams — Thu, 15 Dec 2011 20:24:38 GMT

Is there a filtering rule that I can create to only send email to a specific email address between a certain amount of time?

Thanks.

Theresa Williams

Huge RULES.MER file causing "Infinite rule processing loop detected"

mfaria — Wed, 23 Nov 2011 15:30:39 GMT

I have a huge RULES.MER file.

And it will increase in size because I use it to eliminate SPAM and SPAM is increasing and increasing and increasing and ...

I now that this may not be the better way to manage SPAM but tom it works. I use SpamHalter in conjunction with the rules and I am happy with the solution.

But from some time ago I started getting the message "Infinite rule processing loop detected" and the rules processor stops processing the email message.

After doing a bunch of testing with my rules, I am pretty sure that the rules processor stops processing after a fixed number of rules and give up showing the infinite loop message.

I'm sure that an infinite loop wasn't achieved.

My question is : is there a way to increase the number of the processed rules before an infinite loop is assumed ?

[[]] Maurício Ventura Faria

Logging of incoming connection failures

Greenman — Thu, 04 Aug 2011 10:36:31 GMT

I had a situation recently where Mercury/32 was rejecting messages based on the transaction filtering available under the MercuryS compliance section. The default TRANSFLT.MER file was enabled and was rejecting connections (S, "*for job*", BS, "554 Possibly employment spam - please change and re-send."), for no good reason that I could see (*for job* was not present). I sorted it out by whitelisting a range of IP addresses. These IP addresses are those used by our email filtering service provider.

I would not have been aware of these rejections until too late if I had not configured appropriate SMTP failure reporting from our service provider's customer portal. Luckily, I fixed the issue before I was informed by staff that there was a problem.

I know that we can check the logs generated by Mercury/32 but there are 1000's of them. What would be useful is the ability for Mercury/32 to email a report that lists incoming and outgoing SMTP/POP3/IMAP failures. Outgoing failures are relatively easy to identify for SMTP, but it would still be useful to have everything collated in a single daily report, or a report that can be generated on demand. Such reporting, or even tracking by Mercury/32 itself would be quite vaulable.

Printing using filter rules

Strabo — Sun, 07 Nov 2010 21:45:40 GMT

Evening all.

I'm playing with global rulesatm, specifically printing. I found this thread from back in 2008 which talks about printing attachments, but I'm more concerned with non-plain-text emails.Is there any way for mercury to nicely print HTML emails? If not i've planned a script to run instead which will go something like this:

called by "run" filter for specific email address
check script isn't already running (if so end)
for each .cnm in local-users-direcotry

open file as a text stream
insert <html> & <pre> tags around header
deal with message body as best we can
create file array

push each attachment through a binary stream and save them
add each filename to the file array (including that of the original with .html extension)

print each file in array using its default app (if possible)
delete each file in array and delete the original email

It feels like overkill to have to go that far but i can see a better way to do it using the rules.

Any thoughts?

(p.s. i'm running v4.72)

Mercury outoing filtering rule problem

slogmeister — Tue, 21 Sep 2010 18:10:10 GMT

I'm using Mercury/32 4.72 on Windows 2008 Enterprise. I'm only using MercuryS and MercuryC as all I want is an SMTP relay. I have *no* users outside of the required Admin and there are only two email addresses that matter.

I set up an outgoing filter to forward all messages with "one@company.com" in the "To" header (exact match) to "two@company.com"

"company.com" is NOT the domain that Mercury is servicing.

When I send an email to one@company.com, it is endlessly forwarded to two@company.com - thousands upon thousands of times. Obviously I only want it forwarded once.

Any clue what I'm doing wrong?

Filter Rules - List membership scan for recipients and add recipients to list

TMuecker — Sun, 28 Feb 2010 21:06:29 GMT

Hello,

we want to generate a automatic whitelist from all external recipients, to whom local users send emails. With further filter rules it would be possible to exclude local users from whitelist, whose email addresses are often used from spammers.

Therefore a filter action would be useful: Recipients AddToList ""

Also a new filter condition could be helpful: If recipient(s) ListScan "" action

The difference to the scan for a sender is, that many recipients exist. This task is done in Content Control with the "recipient matches" but cannot be used with lists now.

Best Regards Torsten

Re: Filter rulez...

erikdr — Sat, 20 Feb 2010 17:32:43 GMT

Okay, NOW things get a bit more clear, I misread the Move...

New rules file limited to:

Mercury Global Rules
If header "T" contains "sandya" Copy "sandya"
If size > 1000000 SkipNext ""
If header "F" contains "*" Forward "erikdr@mywebmail.com"

And indeed forward works. However not everything under control yet, far from that - still doing something wrong with poor sandya...

Below the MercuryP session log from her machine connecting:

18:18:50.928: Connection from 192.168.0.134, Sat Feb 20 18:18:50 2010
18:18:50.928: << +OK <8404928.13479@AnchorVista.NOR>, POP3 server ready.<cr><lf>
18:18:50.943: >> USER sandya<cr><lf>
18:18:50.943: << +OK sandya is known here.<cr><lf>
18:18:50.943: >> PASS xxxxx<cr><lf>
18:18:50.943: << +OK Welcome! 0 messages (0 bytes)<cr><lf>
18:18:50.943: >> STAT<cr><lf>
18:18:50.943: << +OK 0 0<cr><lf>
18:18:50.943: >> QUIT<cr><lf>
18:18:50.943: << +OK AnchorVista.NOR Server closing down.<cr><lf>
18:18:50.943: --- Connection closed normally at Sat Feb 20 18:18:50 2010. ---
18:18:50.943:

And it shows _0_ messages whilst for sure I had incoming test mail for her.

So the Mercury.ini file also to spot other places where I might have made mistakes...

Tnx again,

<Erik>

# MERCURY.INI generated by Mercury Setup
#
#
# Sample Bindery Mode / Standalone Mode MERCURY.INI file.
# This sample file implements most of the possible switches for each
# module, but you can edit it to do less if you wish.
#
# Anything after a '#' to the end of the line is a comment and
# is stripped out before parsing. Trailing and leading whitespace
# is also stripped before parsing. Many sample commands have been
# left in this file commented out for reference purposes.
#
# Note that in general, manual modification of this file is NOT
# RECOMMENDED - use the Mercury "Configuration" menu to change the
# program's settings wherever possible.
#

[General]
myname:          AnchorVista.NOR    # Canonical name for this server
timezone:        +0000    # Time Zone to add to date fields
file_api:        1    # Use the file api instead of queues
mailqueue:       C:\PROGFILES\MERCURY\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\PROGFILES\MERCURY\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\PROGFILES\MERCURY\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
# MERCURYS.DLL
MERCURYP.DLL
# MERCURYE.DLL
MERCURYC.DLL
MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
# MERCURYW.DLL
MERCURYX.DLL
# MERCURYI.DLL
# MERCURYB.DLL

[Mercury]
failfile:      C:\ProgFiles\MERCURY\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   C:\ProgFiles\MERCURY\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     C:\ProgFiles\MERCURY\Mercury\ALIAS.MER    # System-wide alias file
synfile:       C:\ProgFiles\MERCURY\Mercury\SYNONYM.MER    # User synonym database
listfile:      C:\ProgFiles\MERCURY\Mercury\LISTS.MER    # List of lists
logfile:       C:\ProgFiles\MERCURY\Logs\Core\~y-~m-~d.log    # Traffic logging file
logwidth:      30    # Width of address fields in logfile
retpath:       1    # Do/Don't use 'return-path' for errors
maxhops:       30    # Used to detect mailing loops
gullible:      0    # If NZ, don't validate 'From' fields
poll:          10   # Seconds between queue polling cycles
scratch:       C:\ProgFiles\MERCURY\Scratch    # Where we can write temp files
returnlines:   15    # How many lines of failed messages to return
postmaster:    lorderik    # NetWare UIC of postmaster
broadcast:     1    # Yes, we want broadcast notifications, but
receipts:      0    # ... no broadcasts for receipt confirmations
PM_notify:     1    # Do/Don't send errors to the postmaster
change_owner: 1    # Change message ownership to recipient
auto_tzone:    1    # If NZ, obtain timezone information from OS
LogLevel:      15    # System message reporting level
LogMax:        100    # Maximum number of system messages to store
RetryPeriod:   30    # Period between job retries (minutes)
MaxRetries:    16    # Maximum number of times a job can fail
TwoPasses:     1    # If NZ, process submission queue in 2 passes
Autoaddress:   0    # If NZ, auto-generate user addresses based on name
Daily_exit:    0    # If NZ, auto-restart each day after maintenance
No_Areply:     0    # If NZ, disable automatic replies system-wide
Alt_Forward:   0    # If NZ, allow alternate forwarding specification
Maint_hour:    2    # Hour for daily maintenance (24-hour clock)
Maint_min:     0    # Minute for daily maintenance
Retry_Mode:    0    # If NZ, use progressive backoff for queue retries
Local_DSNs:    1    # If NZ generate Delivery Status for local users only
DSN_time1:     10800    # Seconds deferred before first DSN is sent
DSN_time2:     86400    # Seconds deferred before second DSN is sent
DSN_time3:     259200    # Seconds deferred before third DSN is sent
Host_in_title: 0    # If NZ, show hostname in system tray and taskbar
Lingering:     0    # Enable or disable 'lingering mailboxes'
Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down
Alert_Host:    notify.pmail.com    # Host to check for licensee advisories
Alert_Interval: 720   # Frequency in minutes (min 240) for checks
Alert_Flags:   3    # Flags controlling advisory checks

[MercuryC]
Host : mail.chello.nl
Failfile : C:\ProgFiles\MERCURY\Mercury\FAILURE.MER
Poll : 30
Scratch : C:\ProgFiles\MERCURY\scratch
ReturnLines : 15
Timeout : 30
ESMTP : 1
POP3_Auth : 0
Logfile : C:\ProgFiles\MERCURY\Logs\MercuryC\~y-~m-~d.log
Log_Verbose : 0
Session_logging : C:\ProgFiles\MERCURY\Sessions\MercuryC
Session_logmode : 1

[MercuryE]
Poll : 15
Timeout : 60
logfile : C:\ProgFiles\MERCURY\Logs\MercuryE\~y-~m-~d.log # Traffic logging file
Session_logging : C:\ProgFiles\MERCURY\Sessions\MercuryE\ # Directory for session log files
Session_logmode : 0
# Nameservers : 139.80.64.1

[MercuryD]
Scratch : C:\ProgFiles\MERCURY\Scratch\MercuryD
Timeout : 30
Poll : 1200
Session_logging : C:\ProgFiles\MERCURY\Sessions\MercuryD
Session_logmode : 0

[MercuryS]
logfile : C:\ProgFiles\MERCURY\Logs\MercuryS\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\ProgFiles\MERCURY\Sessions\MercuryS\    # Directory for session log files
Session_logmode : 0
debug:       1                    # Whether or not to show session progress
# allow:       192.156.225.2        # A machine we WILL permit to connect
# refuse:      192.156.225.0        # A group of machines we WON'T permit.
# size:        1500000
Relay : 0         # Control non-local relaying

[MercuryP]
Scratch : C:\ProgFiles\MERCURY\Scratch\MercuryP
Logfile : C:\ProgFiles\MERCURY\Logs\MercuryP\~y-~m-~d.log
Stack : 32768
Mark_Read : 1
SSL_Mode : 0
Login_Disabled : 0
UIDL_nul_list : 1
New_UIDs : 1
No_NUL_passwords : 1
Session_logging : C:\ProgFiles\MERCURY\Sessions\MercuryP
Session_logmode : 1
Timeout : 60

[MercuryX]
Drain_queues: 1
# Cmd_Delay: 10
# Cmd_Wait: 1
# IE4_Dialling: 0
# Use_ETRN: 1
# Clients_only: 1
# Sunday: 0800,1800,3,15,30,60
# Monday: 0830,2100,5,15,60,60
# Tuesday: 0830,2100,5,15,60,60
# Wednesday: 1500,1900,2,30,5,30
# Thursday: 0900,1900,2,30,0,0
# Friday: 0830,2100,5,15,60,60
# Saturday: 1031,1035,2,45,-1,0

# [Groups]
# testgroup : TESTGRP

[Domains]
AnchorVista: AnchorVista
AnchorVista: AnchorVista.NOR

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        C:\ProgFiles\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\ProgFiles\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\ProgFiles\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         C:\ProgFiles\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file
Notify:          C:\ProgFiles\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands
NoList:          N   # If 'Y', disable the 'list' command
Local_only:      Y   # If 'Y', local 'notify' commands only

[MercuryH]
logfile : C:\ProgFiles\MERCURY\Logs\MercuryH\~y-~m-~d.log # Traffic logging file
# Addressbook : \\CLIO\SYS\SYSTEM\MERCURY\PH.PMR
# MOTD : \\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT
# Administrator : postmaster@clio.pmail.gen.nz
Timeout : 30

[MercuryI]
Scratch : C:\ProgFiles\MERCURY\Scratch\MercuryI
logfile : C:\ProgFiles\MERCURY\Logs\MercuryI\~y-~m-~d.log # Traffic logging file
Session_logging : C:\ProgFiles\MERCURY\Sessions\MercuryI\ # Directory for session log files
Session_logmode : 0
Timeout : 120
Server_Port : 143
Idle_Timeout : 1800

[MercuryB]
Scratch : C:\ProgFiles\MERCURY\Scratch\MercuryB
logfile : C:\ProgFiles\MERCURY\Logs\MercuryB\~y-~m-~d.log # Traffic logging file
Session_logging : C:\ProgFiles\MERCURY\Sessions\MercuryB\ # Directory for session log files
Session_logmode : 0
Timeout : 120
Server_Port : 80
Idle_Timeout : 1800
# URL_Base : enter_your_domain_here

[Groups]

[Rewrite]

[Statistics]
StatFlags:    0 # Statistical reporting settings
STF_Hours:    24 # How often to write stat log files
STM_Hours:    24 # How often to e-mail stat log files

Filter rulez...

erikdr — Sat, 20 Feb 2010 10:59:58 GMT

Okay, goofing a bit again, part of the learning curve...

The global filtering rules I try not to use solely for distributing to the correct PC/mailbox but also for auto-forward to webmail, handy during office hours.

Basically 2 rules:

a) If size > 1 M then skip next rule

b) If To-header contains * then forward to erikdr@webmailaddress.nl

Response of core module:

* Job killed by filtering rule (but that's really the forward, incoming mail seems to work)

Where to find the INIfiles so that I can post here, how to turn on session logging? Any clues already?

Tnx,

<Erik>

Managing Local User

kcoulter — Tue, 22 Sep 2009 12:25:08 GMT

I am using Mercury/32 v4.6 and PopFile Control Center to filter our mail

I have a local user that I have tried to eliminate all incoming mail - so far it hasn't worked - I have deleted the address using manage local users

I also went to Configuration / Mercury SMTP Server / General and made sure that "Accept mail for invalid local addresses" was unchecked

I am still getting messages getting through to the the specific address.

I am at a loss - I even created filters after all the above and I am still having troubles

Our phone company recently changed our IP address - would that have anything to do with my problem

Any insight would be greatly appreciated - I am fairly new to managing a mial server