Thank you, Rolf and Thomas.

I shall do some more experiments and will post the results.

 Chris

We're running behind a similar setup, with absolutely no problems.

mx pointers point at the appliance, and mail.domain.com pointers point at each individual Mercury installation - works as expected with load balancing.

It depends what you want ClamAV to scan for. The main ClamAV signatures (ClamWall does not have a database) cover malware and phishing mails pretty well. The 3rd party signatures (ClamSup supports 14 different 3rd party signature sets for ClamAV at the moment if I didn't miscount) cover a lot more types of unwanted mail like spam and are also very efficient.

Best regards,

Nico

Yes.  With my domain users having only create rights to the directory.

Thanks Thomas,

I'm going to do a test and see how it works. I appreciate the experience. The only problem I can foresee is that the Mercury loader might not permit the closing of Mercury.

I don't even understand the terminology of running Mercury as a service using NT Wrapper. I don't imagine it is necessary for me.

Many thanks once again. You are always so helpful and I appreciate it.

Best regards,

Ellie

As the original post didn't mention servers accessing mailboxes on the same disk system I assumed they were supposed to be entirely separate. It's true though that using a shared mail directory with two servers can work, but as you say there are a number of complications with that.

/Rolf
 

I would use the MercD client for business POP accounts only, which you don't use.

For staff personal accounts they should put them in their own Pegasus profile (or use another client, or better yet, check them at home on their own time [6])

Thank you. Hans.  I'll try  that.

Gordon

[quote user="RTB"]Want to 'move' an incoming mail  If header "T" contains "ask@domain.org" Move "joe@domain.org"[/quote]

It should be just Move "joe"  - you should put the name of a local user in a copy or move statement.

[quote user="Sturmer"]

About two hours ago my Mercury32 mail server stopped receiving mail after receiving mail without a problem for almost three weeks now. I'm using Mercury32 4.62 on windows XP SP2. I'm using MercuryC to relay outgoing mail through my ISP. Ports 25, 110, 143, and 587 are forwarded through my router. Here are my MX records that point to my IP.

I can connect to your host and it looks normal. What do you mean "stopped receiving mail?  What kind of error did you get? 

 I have a few comments here.

<!-- -->

#  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:          mail.cfocapitalpartners.com    # 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:\MERCURY\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\MERCURY\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\MERCURY\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
C:\MERCURY\mercurys.dll
C:\MERCURY\mercuryc.dll
C:\MERCURY\mercuryp.dll
C:\MERCURY\mercuryd.dll
C:\MERCURY\mercuryx.dll

[Mercury]
failfile:      C:\MERCURY\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   C:\MERCURY\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     C:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file
synfile:       C:\MERCURY\Mercury\SYNONYM.MER    # User synonym database
listfile:      C:\MERCURY\Mercury\LISTS.MER    # List of lists
logfile:       C:\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:\MERCURY\Scratch    # Where we can write temp files
returnlines:   15    # How many lines of failed messages to return
postmaster:    Admin    # 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
Failfile : C:\MERCURY\Mercury\FAILURE.MER
Poll : 30
Scratch : C:\MERCURY\scratch
ReturnLines : 15
Timeout : 600
ESMTP : 1
SMTP_Username: *****
SMTP_Password: *****
POP3_Auth : 0
Logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log
Log_Verbose : 0
Session_logging : C:\MERCURY\Sessions\MercuryC
Session_logmode : 0

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

[MercuryD]
Session_logging : C:\MERCURY\Sessions\MercuryD\    # Directory for session log files
Session_logmode : 0
Scratch : C:\MERCURY\Scratch\MercuryD
# Timeout : 30
# Poll : 120               # How often to check hosts for new mail (seconds)

[MercuryS]
Debug : 1
Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log
Size : 104857600
Timeout : 30
Relay : 0
Strict_Relay : 1
Alt_Server_Port : 587
Allow_Illegals : 0
SMTP_Authentication : 3
Auth_File : remote
Session_logging : C:\MERCURY\Sessions\MercuryS
Session_logmode : 1
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 288
No_VRFY : 1
SMTP_ConnFlags : 0

[MercuryP]
Scratch : C:\MERCURY\Scratch\MercuryP
Logfile : C:\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:\MERCURY\Sessions\MercuryP
Session_logmode : 1
Timeout : 600

[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]
cfocapitalpartners: cfocapitalpartners
cfocapitalpartners: cfocapitalpartners.com
portmontsia: portmontsia
portmontsia: portmontsia.net
cfoconsulting: cfoconsulting
cfoconsulting: cfoconsulting.org

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        C:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         C:\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file
Notify:          C:\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:\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:\MERCURY\Scratch\MercuryI
logfile : C:\MERCURY\Logs\MercuryI\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\MERCURY\Sessions\MercuryI\   # Directory for session log files
Session_logmode : 0
Timeout : 120
Server_Port : 143
Idle_Timeout : 1800

[MercuryB]
Scratch : C:\MERCURY\Scratch\MercuryB
logfile : C:\MERCURY\Logs\MercuryB\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\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[/quote]

[quote user="peterelliott11"]Right then, still doing it.

 Here is the details out of the Mercury.Ini file

 [MercuryC]
Host : smtp1.mail.com
Failfile : C:\MERCURY\Mercury\FAILURE.MER
HELO : Peter Elliott
Poll : 30
Scratch : C:\MERCURY\scratch
ReturnLines : 15
Timeout : 30
ESMTP : 1
SMTP_Username: peter.j.elliott:XXXBLANKEDXXX.com#mail.com
SMTP_Password: XXXBLANKEDXXX
POP3_Auth : 0
POP3_Host : pop1.mail.com
Logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log
Log_Verbose : 1
Session_logging : C:\MERCURY\Sessions\MercuryC
Session_logmode : 1

 On SMTP username, when I check the details in MercuryC after I shut it down and restart it, the #mail.com disappears and I have to re-enter it before the server sends messages out.

 However, the entry remains in the .INI file regardless, it's as if the program is 'forgetting' everything after .com[/quote]

I believe that Mercury/32 treats the # as a special comment character in the file.  Everything after the # is treated as a comment and so not used in the username.  I tested this and sure enough the #mail.com is trimmed from the username string.  That said I believe that most ISPs that use special characters in a username will generally allow you to use another character for the # (say like an underscore) that would perform the same task.

Thank you, again, Rolf.  Unfortunately, these are not fake usernames associated with my Mercury server.  They are usernames associated with one of the ISPs that I use.  They may or may not be fake.  The significance is that I see quite a lot of SPAM with multiple usernames (all starting with "g" as the first letter, presumably because the first letter of my usename starts with "g") at that ISP and it seems a good clue that the message is SPAM, as none of my correspondents use that ISP.

I looked at Graywall recently and gained the impression that I couldn't use it effectively, as quite a bit of my mail gets forwarded from another ISP to the one that I directly connect to with Mercury's Distributing POP3 Client.  I haven't tried SpamHalter so far, as I am having a fair amount of success with what I am currently doing.  Basically, I only accept mail without question from addresses that I have listed in Mercury's userlists and whitelist.  This allows me to have zero SPAM to my and my wife's user accounts.  Everything else is considered to be SPAM (which is deleted without any manual inspection) or potentially SPAM, which goes to a SPAM account.  It's the SPAM account that I have to work on to create rules to recognize real SPAM.  Of course, when people change their e-mail addresses without telling me, their messages end up as possible SPAM in the SPAM account.  This doesn't happen very often.

Gordon

[quote user="GLM"]Hello,

The MX servers of one of our main clients are experiencing a weird problem: our TCP connection at their port 25 is correctly established, but their 220 reply comes after a big delay (about 4 minutes). Of course, our MercuryE timeouts. I know there is a setting to control MercuryE's TCP/IP timeout. I am wondering if there is a setting to force MercuryE to wait ("indefinitely") for their first 220 reply.

Thanks in advance.

Gonzalo López Menéndez

GADD-GRUPO MEANA, S.A.[/quote]

Local mailboxes are stored in the location indicated by "Local mailbox directory path" in Configuration / Mercury core module. In that folder there will be one sub-folder for each local user.

Messages for non-local recipients will be in the Queue directory while being processed, but will not be stored on the server after that.

/Rolf 

Problem resolved..

Discovered that the C:\Temp directory was missing  so Clam was failing when trying to write to it. Restored the directory and all is well.

Thanks again

[quote user="Peter Strömblad"]There are no problems reaching:  from Sweden at the moment.[/quote]

Peter when I select the "Buy mercury online" button in http://community.pmail.com/pmail/MercuryPricing.aspx it goes to persephone and that's not correct since david changed the server to hera.

thanks rolf, finally i get the answer. it is because of the windows firewall. i turn off the firewall and then everything going to be ok. so thanks for the support. now i can sleep with one peace. any problem that will come out i will let the forums know about it. thanks a lot everybody.

Thomas,

The headers (helper and list unsubscribe) are in there ok.  It's the Mailing list Settings - Distribution - Signature File that does not show up on emails sent to the list if the originating email is sent as HTML vs plain text.

Again, I did not ugrade to latest version yet.

Thanks,

MP 

Great, thanks very much!

[quote user="David Winge"]

I moved the mail folders back to the old box and Mercury/32 is working fine, I removed it from the new server and did a fresh reinstall and it too seems to be working. In order to migrate from one server to the other, which files do I need to copy? I am also moving it from drive C: on one machine to D: on the other. Or if there is a FAQ somewhere on how to do this please point me that direction.

The only thing I do is copy the installation from one system to the other but I always use the C: drive.  If you are using the D: drive then everything pointing to the C: drive in the config files and mercury.ini needs to be changed.  The mercury.ini is pretty easy but there are a number of other config files that may need to be changed especially filters and MercuryD.  Also if the mailboxes are in c:\mercury\mail then there may also be pointers in the mailboxes pointing to the other drive letter as well.

Is there any reason you could not copy the installation to the c: drive?  If not I would try doing a completely new install only copying the user mailboxes and have everything else brand new.  If this works you can try copying the rules.mer and other config files one at a time until you are sure it's working.

Thank you kindly, David

[/quote]