<p>[quote user="ubecker"] [Domains] 10.203.63.3: ourdomain.com [/quote]</p><p>That definitely looks wrong to me, in a similar way to the error I made. See page 12 of the 4.73 manual - I think (guessing a bit as you've scrambled your domain name) yours should probably look like</p><p>[Domains]</p><p>ourdomain:  ourdomain</p><p>ourdomain:  ourdomain.com</p><p>ourdomain:  [10.203.63.3] </p><p>I'm not sure about the colons - they are there in my mercury.ini but the current manual doesn't seem to show any? </p><p>Chris </p>

<p>Hello,</p><p> we use the latest registered Mercury and had a problem yesterday. Some incoming mail were rejected  with the error "554 Command rejected for site-specific policy reasons"</p><p>Problem is, we don't know, why these mails became rejected.</p><p>An extract of the log file, all addresses are neutralized.</p><p>T 20110804 144731 4e3a5f48 Connection from 192.168.17.10 T 20110804 144732 4e3a5f48 EHLO savsms.ourdomain.com T 20110804 144732 4e3a5f48 MAIL FROM:<xxx.x@xxx.xz> SIZE=358230 T 20110804 144732 4e3a5f48 RCPT TO:<yyy@ourdomain.com> T 20110804 144732 4e3a5f48 DATA T 20110804 144732 4e3a5f48 DATA - 4669 lines, 2558 bytes. E 20110804 144732 4e3a5f48 555 Message rejected: site policy does not permit empty 'Subject' fields. T 20110804 144732 4e3a5f48 RSET </p><p>We have this policy, the rejecting is ok </p><p>T 20110804 144732 4e3a5f48 MAIL FROM:<aaa.aaa@bbb.com> SIZE=10472 T 20110804 144732 4e3a5f48 RCPT TO:<zzz@ourdomain.com> T 20110804 144732 4e3a5f48 DATA T 20110804 144732 4e3a5f48 DATA - 260 lines, 0 bytes. E 20110804 144732 4e3a5f48 554 Command rejected for site-specific policy reasons. T 20110804 144735 4e3a5f48 RSET T 20110804 144735 4e3a5f48 MAIL FROM:<1234@ddd.de> SIZE=14672 T 20110804 144735 4e3a5f48 RCPT TO:<abc@ourdomain.com> T 20110804 144735 4e3a5f48 DATA T 20110804 144735 4e3a5f48 DATA - 147 lines, 0 bytes. E 20110804 144735 4e3a5f48 554 Command rejected for site-specific policy reasons. T 20110804 144737 4e3a5f48 RSET T 20110804 144737 4e3a5f48 MAIL FROM:<1234@ddd.de> SIZE=16622 T 20110804 144737 4e3a5f48 RCPT TO:<abc@ourdomain.com> T 20110804 144737 4e3a5f48 DATA T 20110804 144737 4e3a5f48 DATA - 162 lines, 0 bytes. E 20110804 144737 4e3a5f48 554 Command rejected for site-specific policy reasons. T 20110804 144742 4e3a5f48 QUIT</p><p>What are the reasons for these 3 mails? They normaly meat the requirements of a good mail and normaly are accepted.</p><p>All 4 mail have the same nr.  4e3a5f48, is that normal? </p><p> </p><p>T 20110804 144742 4e3a5f48 Connection closed with 192.168.17.10, 11 sec. elapsed. </p><p> </p><p>Thanks for any help </p><p>Regards</p><p>Uwe Becker </p>

[quote user="ubecker"]<p>Hello,</p><p> we use the latest registered Mercury and had a problem yesterday. Some incoming mail were rejected  with the error "554 Command rejected for site-specific policy reasons"</p><p>Problem is, we don't know, why these mails became rejected.</p><p>An extract of the log file, all addresses are neutralized.</p><p>T 20110804 144731 4e3a5f48 Connection from 192.168.17.10 T 20110804 144732 4e3a5f48 EHLO savsms.ourdomain.com</p><p>[/quote]A connection from a local machine?</p><p>Is this a "spam assassin virtual appliance"? </p><p>[quote] T 20110804 144732 4e3a5f48 MAIL FROM:<xxx.x@xxx.xz> SIZE=358230 T 20110804 144732 4e3a5f48 RCPT TO:<yyy@ourdomain.com> T 20110804 144732 4e3a5f48 DATA T 20110804 144732 4e3a5f48 DATA - 4669 lines, 2558 bytes. E 20110804 144732 4e3a5f48 555 Message rejected: site policy does not permit empty 'Subject' fields. T 20110804 144732 4e3a5f48 RSET </p><p>We have this policy, the rejecting is ok </p><p>T 20110804 144732 4e3a5f48 MAIL FROM:<aaa.aaa@bbb.com> SIZE=10472 T 20110804 144732 4e3a5f48 RCPT TO:<zzz@ourdomain.com> T 20110804 144732 4e3a5f48 DATA T 20110804 144732 4e3a5f48 DATA - 260 lines, 0 bytes. E 20110804 144732 4e3a5f48 554 Command rejected for site-specific policy reasons. T 20110804 144735 4e3a5f48 RSET T 20110804 144735 4e3a5f48 MAIL FROM:<1234@ddd.de> SIZE=14672 T 20110804 144735 4e3a5f48 RCPT TO:<abc@ourdomain.com> T 20110804 144735 4e3a5f48 DATA T 20110804 144735 4e3a5f48 DATA - 147 lines, 0 bytes. E 20110804 144735 4e3a5f48 554 Command rejected for site-specific policy reasons. T 20110804 144737 4e3a5f48 RSET T 20110804 144737 4e3a5f48 MAIL FROM:<1234@ddd.de> SIZE=16622 T 20110804 144737 4e3a5f48 RCPT TO:<abc@ourdomain.com> T 20110804 144737 4e3a5f48 DATA T 20110804 144737 4e3a5f48 DATA - 162 lines, 0 bytes. E 20110804 144737 4e3a5f48 554 Command rejected for site-specific policy reasons. T 20110804 144742 4e3a5f48 QUIT</p><p>What are the reasons for these 3 mails? They normaly meat the requirements of a good mail and normaly are accepted.</p><p>All 4 mail have the same nr.  4e3a5f48, is that normal?</p><p>[/quote] I haven't seen that particular reject message, however it is probably related to the initial rejection and all further commands are being rejected.</p><p>All the mails are being attempted in the same SMTP session as the originally rejected message (hence the same session id).</p><p>A MercS session log will provide more detail. </p><p>Can you configure your "appliance" to send each mail separately?</p><p>Or better yet, remove it and let Mercury handle anti-spam.</p><p>A properly trained Spamhalter daemon along with the other tools available will (in my experience) be superior to your appliance.[quote] </p><p> </p><p>T 20110804 144742 4e3a5f48 Connection closed with 192.168.17.10, 11 sec. elapsed. </p><p> </p><p>Thanks for any help </p><p>Regards</p><p>Uwe Becker </p>[/quote]

<p>I once had strange messages like this; there was no logic to them at all. </p><p>The reason turned out to be that I had some errors in the [Domains] section of my mercury.ini</p><p>You might like to post your mercury.ini for comments? </p><p> Chris </p>

A connection from a local machine?<p>Is this a "spam assassin virtual appliance"? </p><p>[quote] </p><p>No, it is an appliance, Symantec Brightmail Antivirus and AntiSpam  </p><p> [/quote] </p><p> </p><p>I haven't seen that particular reject message, however it is probably related to the initial rejection and all further commands are being rejected.</p><p>All the mails are being attempted in the same SMTP session as the originally rejected message (hence the same session id).</p><p>A MercS session log will provide more detail. </p><p>Can you configure your "appliance" to send each mail separately?</p><p>Or better yet, remove it and let Mercury handle anti-spam.</p><p>A properly trained Spamhalter daemon along with the other tools available will (in my experience) be superior to your appliance.</p><p>[quote] </p><p>We don't have a more detailed session log for this error.</p><p>The Symantec appliance sends each mail separately, this error never before appeared, we switched to  Mercury 4.73 a couple weeks ago. </p><p> The appliance also works as a virus filter, the team Mercury and Symnatec worked fine for years.</p><p>Regards</p><p>Uwe </p>[/quote]

[quote user="Chris Bolton"]<p>I once had strange messages like this; there was no logic to them at all. </p><p>The reason turned out to be that I had some errors in the [Domains] section of my mercury.ini</p><p>You might like to post your mercury.ini for comments? </p><p> Chris </p><p>[/quote]</p><p>Thanks for your assistance, the domain name is neutralzed, everything else is original </p><p>the mercury.ini file: </p>#  MERCURY.INI generated by Mercury Setup # # #  Sample Bindery Mode MERCURY.INI file (in fact, the one I use on #  my production server). This one implements most of the possible #  switches for each module, but you can edit it to do less if you #  wish. All the fields shown below are described in the file #  MGUIDE.HLP which is supplied in the Mercury archive. # #  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. # [General] myname:          ourdomain.com    # Canonical name for this server timezone:        +0100    # Time Zone to add to date fields file_api:        1    # Use the file api instead of queues mailqueue:       D:\MERCURY\QUEUE    # Where mail should be put for delivery smtpqueue:       D:\MERCURY\QUEUE    # Where the SMTP client should look for mail newmail_path:    D:\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:      d:\MERCURY\Mercury\FAILURE.MER    # Delivery failure notification template confirmfile:   d:\MERCURY\Mercury\CONFIRM.MER    # Delivery confirmation template aliasfile:     d:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file synfile:       d:\MERCURY\Mercury\SYNONYM.MER    # User synonym database listfile:      d:\MERCURY\Mercury\LISTS.MER    # List of lists 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 bitnethost:    cunyvm.cuny.edu    # Relay host for '.bitnet' rewrites poll:          10   # Seconds between queue polling cycles scratch:       d:\MERCURY\Scratch    # Where we can write temp files returnlines:   15    # How many lines of failed messages to return postmaster:    ubecker    # NetWare UIC of postmaster broadcast:     0    # 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:   2    # Period between job retries (minutes) MaxRetries:    25    # 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:   1    # 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:    1    # 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 : 213.139.128.58 Failfile : d:\MERCURY\Mercury\FAILURE.MER HELO : mail.ourdomain.com Poll : 30 Scratch : d:\MERCURY\Mercury ReturnLines : 15 Timeout : 45 ESMTP : 0 POP3_Auth : 0 Logfile : d:\mercury\logs\smtp.log Log_Verbose : 1 Session_logging : d:\mercury\logs\smtp Session_logmode : 0 [MercuryE] HELO : mail.ourdomain.com Session_logging : d:\mercury\logs Session_logmode : 0 Poll : 30 Timeout : 120 Nameservers : 194.25.0.70,8.8.8.8,194.145.226.26 Logfile : d:\mercury\logs\smtp\SMTP~M~D.log Log_Verbose : 0 DNS_Timeout : 40 DNS_Retries : 10 Transcripts : 0 MaxThreads : 15 [MercuryD] Scratch : d:\MERCURY\Mercury Timeout : 30 Poll : 30 [MercuryS] Debug : 1 HELO : mail.ourdomain.com Logfile : d:\MERCURY\Logs\MER~M~D.LOG Size : 20000000 Timeout : 45 Relay : 0 Strict_Relay : 0 8BitMime : 1 Allow_Illegals : 0 SMTP_Authentication : 0 Killfile : d:\mercury\killfile Session_logging : d:\mercury\logs Session_logmode : 0 Compliance_Settings : 216 Maximum_Failed_Rcpts : 4 Max_Relay_Attempts : 4 SSL_Mode : 0 ST_Blacklisting : 288 No_VRFY : 0 Compliance_Exceptions : d:\mercury\ausnahmen [MercuryP] Scratch : d:\MERCURY\Mercury Logfile : d:\mercury\logs\pop3\pop~M~D.log Stack : 32768 Mark_Read : 1 SSL_Mode : 0 Login_Disabled : 0 Session_logging : d:\mercury\logs\pop3\seeburger.log Session_logmode : 0 Timeout : 60 [MercuryX] # 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] 10.203.63.3: ourdomain.com [Maiser] Maiser:          Maiser   # 'Username' of mail server account Helpfile:        d:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests Lookupfile:      d:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command Send_dir:        d:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command Logfile:         d:\MERCURY\Logs\MAISER.LOG   # Mail server log file Notify:          d:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands NoList:          Y   # If 'Y', disable the 'list' command Local_only:      Y   # If 'Y', local 'notify' commands only Admin_Passwords: d:\mercury\maiser.pw   # File for mail server administrator passwords [MercuryH] Logfile              :     d:\MERCURY\Logs\MERCURYH.LOG # Addressbook : \\CLIO\SYS\SYSTEM\MERCURY\PH.PMR # MOTD : \\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT # Administrator : postmaster@clio.pmail.gen.nz Timeout : 30 [Groups] [Rewrite] [Statistics] StatFlags:    10  # Statistical reporting settings StatMail:     ubecker@ourdomain.com  # Address to send stat log files STF_Hours:    24  # How often to write stat log files STM_Hours:    24  # How often to e-mail stat log files [MercuryI] Timeout : 30 Server_Port : 143 Idle_Timeout : 1800 SSL_Mode : 0 Login_Disabled : 0

<p>> Thanks for your assistance, the domain name is neutralized, everything else is original</p><p>Why did you do that?  The actual domain name might be the most critical item in solving the problem. </p>

[quote user="Thomas R. Stephenson"]<p>> Thanks for your assistance, the domain name is neutralized, everything else is original</p><p>Why did you do that?  The actual domain name might be the most critical item in solving the problem. </p><p>[/quote]</p><p>Because I don't want our company mailserver configuration visible for everybody on the web.</p><p>I just did "replace domain-name.com with ourdomain.com"</p><p>Mercury works fine for years, this error appeared after we updated to Mercury 4.73 from 4.0?</p><p>Regards</p><p>Uwe </p>

<p>It may be a good idea to modify [Domains] a bit (see Mercury help), but the thing that caused the rejections is apparently that several of the message content restrictions (MercuryS configuration, Compliance) have been selected. I can't say which one triggered in this case, but uncheck all if there isn't a special reason for you to keep them.</p><p>/Rolf</p>

[quote user="ubecker"] <p>T 20110804 144732 4e3a5f48 DATA - 4669 lines, 2558 bytes. T 20110804 144732 4e3a5f48 DATA - 260 lines, 0 bytes. T 20110804 144735 4e3a5f48 DATA - 147 lines, 0 bytes.[/quote]</p><p>Those look odd ... more lines than bytes!</p><p> - Vince </p>