hi everyone

I am having some issues receiving mail after setting up mercury mail but can seem to send out mail fine. 

I am running it on windows 10 x86 and ports 25, 143, 110 and 443 have been opened  and rules applied in my AVG firewall.

here is a copy of my ini file below...

 #  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:          localhost    # 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:\XAMPP\MERCURYMAIL\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\XAMPP\MERCURYMAIL\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\XAMPP\MERCURYMAIL\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:\xampp\MERCURYMAIL\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   C:\xampp\MERCURYMAIL\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     C:\xampp\MERCURYMAIL\Mercury\ALIAS.MER    # System-wide alias file
synfile:       C:\xampp\MERCURYMAIL\Mercury\SYNONYM.MER    # User synonym database
listfile:      C:\xampp\MERCURYMAIL\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:       C:\xampp\MERCURYMAIL\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]
# Session_logging:  G:\           # Directory to write session transcripts
host:             # mail mail host which relays for us
scratch:     C:\xampp\MERCURYMAIL\Mercury   # Where we can write temp files
poll:        30                   # Seconds between queue polling cycles
returnlines: 15                   # How many lines of failed messages to return
failfile:    C:\xampp\MERCURYMAIL\Mercury\FAILURE.MER  # Delivery failure template
esmtp:       1                    # Yes, we want to use ESMTP extensions

[MercuryE]
Poll : 15
Timeout : 60
Nameservers : 208.67.222.222,208.67.220.220
Log_Verbose : 0
DNS_Timeout : 20
DNS_Retries : 4
Transcripts : 1
MaxThreads : 10

[MercuryD]
scratch              :     C:\xampp\MERCURYMAIL\Mercury
# Timeout : 30
# Poll : 120               # How often to check hosts for new mail (seconds)

[MercuryS]
Debug : 1
Logfile : C:\xampp\MERCURYMAIL\Logs\MERCURYS.LOG
Timeout : 30
Relay : 1
Strict_Relay : 0
Interface : 127.0.0.1
Allow_Illegals : 0
SMTP_Authentication : 0
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 288
No_VRFY : 0
SMTP_ConnFlags : 0

[MercuryP]
Scratch : C:\xampp\MERCURYMAIL\Mercury
Stack : 32768
Mark_Read : 1
SSL_Mode : 0
Login_Disabled : 0
UIDL_nul_list : 1
New_UIDs : 0
No_NUL_passwords : 1
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]
localhost: localhost
localhost: 127.0.0.1
localhost: finchkeeper.com

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        C:\xampp\MERCURYMAIL\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\xampp\MERCURYMAIL\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\xampp\MERCURYMAIL\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         C:\xampp\MERCURYMAIL\Logs\MAISER.LOG   # Mail server log file
Notify:          C:\xampp\MERCURYMAIL\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:\xampp\MERCURYMAIL\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

[MercuryI]
Scratch : C:\xampp\MERCURYMAIL\SCRATCH
Timeout : 120
Server_Port : 143
Idle_Timeout : 1800
SSL_Mode : 0
Login_Disabled : 0
No_NUL_passwords : 1

[MercuryB]
Scratch : C:\xampp\MERCURYMAIL\SCRATCH
# Logfile : o:\mail\tmp\mercuryb.log
Timeout : 120
Server_Port : 2224
# Session_logging : o:\mail\mercury\mblogs
# Session_logmode : 0
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

 any help would be much appreciated, thanks

Hi,

Is it possible to create a subfolder of a folder ?

I using IMAP connectivity to mercury  4.8 (windows 10)

Thanks.

Hi,

Can't figure this one out, only happens to this one single email address.

Any ideas?

Thanks,

MP

 I have encountered a delivery problem due to Greylisting so am presenting the following for some feedback and suggestions on workarounds (Mercury v4.8, MercuryE, no SSL):

 The delivery failured notice contains multiple entries of:

   450 4.2.0 <username@acousti.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/acousti.com.html

   450 4.1.1 <username@acousti.com>: Recipient address rejected: unverified address: Address verification in progress

Following the link I get to this help information which I am hoping for an explanation of.  From: http://projects.puremagic.com/greylisting/

I run a mailserver, and some users say we are being blocked. How do I get off your list?

We do not run a blacklist. There is no centralized list to request checking of your server, or to request removal from. The reason your mailserver is getting blocked is most likely that it does not properly handle 45x SMTP error codes, and does not retry delivery within a reasonable amount of time after receiving such a code. Please read the whitepaper for further technical information. Please, don't contact us asking for removal. Since there is nothing to remove you from, any requests for removal will be ignored.

 Thanks.

The only version of NSYNONYM.EXE (generate synonym database for/from nds user objects) available is a 16bit program, which cannot run on 64bit Windows systems. I need a version of nsynonym.exe compiled as a 32bit program, so we can retire our old Windows Server 2003. Since Windows Server 2003 is approaching it's end-of-life, this problem ist getting more urgent every day.

The strange thing is, the new Mercury 4.80 beta actually contains a 32bit version of ch_syn.exe, which gerenates synonyms from a Bindery database. Surely there are more NDS installations than old NetWare Bindery setups using Mercury.

Greetings

Markus

Mercury 4.8 on Win7

I am finding that some of the windows related to configuration are too small to accommodate all of the text and cannot be re-sized.  Examples are the windows for Mercury S and the IMAP4 server.  Is this a known issue?

Gordon

This post follows on from the thread I started related to window sizing for some configuration windows.  Having apparently solved that issue, my Mercury server is now non-functional.  The issue is that, as soon as Mercury starts, I get a BEX (Buffer overflow exception error).  The only options available are to close Mercury or search for a solution (and none found).  This error occurs consistently every time Mercury starts, so I cannot use it.

It seems that BEX errors arise because of the built-in Data Execution Protection (DEP) feature of Windows 7 (64-bit).   With the 64-bit version of Win7, it is possible to selectively exclude programs from DEP.  I added the Mercury Loader to the exclusion list but the DEP management system wouldn't let me exclude mercury.exe.

I have tried a System Restore back to 20 June and restoration was successful, but that didn't cure the BEX problem.

I can't think of anything else other than to reinstall Mercury.  Any other suggestions would be most welcome.

Gordon

I have been having trouble with Mercury D deleting duplicated messages for months now and I have simply accepted and got on with something else but it has been bugging me.  

Where I have other users on my network who have been CC'd in a message from a supplier/customer.... only one

copy gets through and it is pot luck as to who gets it. The help files suggests using 'Check Only in Special Headers..'

This does prevent the duplicate messages from being deleted. However, this affects the Mercury Core Process module- 

When POP3 mail has been processed the Core module no longer displays who the email is from.... so am I right in assuming this is the correct operation if you specify special headers and ulitmately this is a failing in the operation of MERCURY...?

ie. either I lose duplicate messages without special header processing OR I get the messages duplicated to other users on my network but I have to accept that the senders details are no longer displayed in the Mercury Core module....

Thank you. 

Guy

I have been using Mercury for several years and recently noticed that some of the logs are becoming rather large. The SMTP Client log folder has now reached 7.8GB!  Although much smaller, the MecuryS SMTP server log file is 77MB.  I am presuming that there is little reason to keep all of the history.  Can the SMTP client folder be emptied of files?  If the MercuryS file is deleted, will Mercury recreate it or should I just remove its contents and leave the file in place?

Thank you

Gordon

Hello,

 I've been testing Mercury/32 and it is a great mail server.  Now that the newest version can be run as a native windows service, I think it meets all of my needs.  I do have a couple questions about how the GUI works with this version.

1.  If I have Mercury running as a service, can I launch the GUI to view real time logs or do troubleshooting?  Once I'm done can I just exit out of the GUI and Mercury will still be running as a service?

2. If #1 above does not work, do I have to stop Mercury service then launch the GUI to view real time.  Once I'm done with the GUI, I exit then start the Mercury service?

3. If I need to make changes, can I make the changes in the GUI then restart the Mercury service?  I assume so.

 Thanks for you help!

In Mercury 4.7x  a "Sender" field was added to every E-Mail, that was sent from  the Mercury listserver.
Thismeant thatalways"Maiserinorder of ..."has been displayedineachemail,butalloweda clear identificationtoavoid multipleprocessing.

InMercury4.8, this field isnotsetandwe need for ourpolicies(scripts)another option now.
Could we usethe field "X-listname"anddelete them afterprocessing?How does it affectif wedelete this fieldduring the processingofe-mail?

Operation:
Weuse theMercury listserver as our projectserver.Each listcorresponds toaconstruction project.
Just ourpart of thecommunication is done viathe server,which is why our users have to know whothe emailoriginallyget even.
We usethePolicyCMDscriptswithFindand especially Sed to modify the e-mails and allow this. 

Thanks, Torsten

Having trouble working out how to set up a domain mailbox again (don't ask). I have edited the fields through the GUI but here is what's in my INI file.

[Domains]
reiner: reiner
reiner: rnr.id.au
reiner: [218.215.189.224]
DM=reiner: rnr.id.au
reiner: mail.rnr.id.au

If I send an email to reiner@rnr.id.au it works (and I can retrieve via POP3) but for anything else Mercury says "user <...> not known".

This stuff is the most important but its always been very confusing. 

One of my users started receiving the following error when attempting to send to an address that she did not have problems with last week.

550 5.7.64 TenantAttribution; Relay Access Denied

Can anyone explain what is causing this?  MercuryE is handling the sending, Pegasus Mail is the client.

Update:  I have since found out that the phone has been disconnected at the business these emails were being sent to.  Users says email sent last week were not responded and these were follow-ups.  I now assume this business has closed.  I'm still curious about this delivery failure message though.

Once Spamhalter has recognized and marked a message as spam, it will redirect this spam message to spam folder. But sometimes we have a false positive in our spam folder. How could I process this e-mail so that it could be forwarded to the initial addressee?

I have already tried to forward it firstly to our no_spam folder of Spamhalter. The mail will be processed and removed by Spamhalter from the no_spam folder for updating its spam database. So far so good, but after that I'm still not able to forward the mail from the spam folder to its original destination after database update and restart of Mercury+Spamhalter. It comes again and again back to the spam folder. Of course, the mail has been marked by Spamhalter. But I cannot manually change every false positive raw file to delete the spam classification inside.

Further I have tried to add the affected sender's address from the false positive to the "exclusion from processing" list of Spamhalter. But also this doesn't take any effect. The forwarded mail comes back to the spam folder as a copy of itself.

Also within the Spamhalter manual I didn't find anything in this regard. Only the sentence: "If you have a false positive message, forward it to the nospam correction address".

Cheers

Joerg

I have a small question with folded header lines:

10:32:01.942: >> Subject:<cr><lf>
10:32:01.942: >>  =?utf-8?q?Sommerferien_2016_-_1=2E_Teil=3A_Herzlichen_Gl=C3=BCckwunsch_Na?=<cr><lf>

                          DATA

10:32:02.223: << 555 Message rejected: site policy does not permit empty 'Subject' fields.<cr><lf>

Bug or Feature?

I have a MercuryC module using a third-party email relay service. I have a couple users who have their emails forwarding to an external (gmail) account.  

A problem surfaced when there was a rejection from the relay service one day.  A couple messages arrived for my forward-all-emails-to-gmail users, which MercuryC tried to forward to their gmail accounts.  The relay service rejected, which requeued the messages, PLUS added a delivery failure notice to these users to the queue - which it then attempted to forward to their gmail account, creating more failure noticed.  Long story short, 3 emails quickly ballooned to >8100 messages in the queue!  When the issue with the relay service was resolved, it ate up my 150 message per day limit in a matter of seconds.  I cleared the MERCURY\QUEUE folder, so problem solved. 

But is there a way to prevent this from happening again?  Ie, can I prevent delivery notification failures from being forwarded, or not generate delivery notification failures when the error on MercuryC is that the relay service is refusing the connection, not an endpoint-failure? 

Good day all.

I am investigating the possibility of using a paid filtering service offered by DuoCircle to run as our MX, which then in turn delivers legitimate mail to our local Mercury32 server. I already have all users required to authenticate over SMTP in order to send out email from phones, tablets etc. I will now add the list of DuoCircle servers to the allowed connection list, followed by a “deny all” rule which will block any other direct delivery to our server. My question is as follows: What do I need to do so that my users who may be connecting from outside our network (from home ADSL or 3G data or similar) are still able to use our Mercury SMTP as their outgoing server? Will an authenticated user’s rights trump a connection refusal rule?

Any information would be much appreciated.

We are struggling with issues related to Mercury and IMAP connections.  For a long time have observed that Mercury appears to have problems with more than 1 simultaneous connections to the IMAP server.  Today I observe behavior that somewhat explains what is going on.  This time it happens to me, however looking back explains what I have seen with other users many times.  At one point earlier in the day I had connections with a Windows PC and at the same time with an Android tablet.  I see the familiar 'Folder in user by other connections' message from Thunderbird on the PC.  Next I power the Android tablet all the way off.  After a long time (hours) still see the same error even though I am sure I have the only IMAP client connecting to Mercury.  For the sake of test, I disconnect my connection to the Internet at this end such that my IP address no longer exists and no connection is possible for over 15 minutes.  FWIW the TCPIP timeout in Mercury is set at 120 sec, I tried decreasing it to 60 seconds for test, still the same.  Now, at least 2 hours after powering the Android tablet off and in the mean time totally disconnecting this end from the Internet (I am remote from the server), the Current connections window in Mercury still shows the connection.  Looks very much like Mercury is not capable of dealing with dropped connections correctly. 

At this point help is desperately needed.  David, Peter, anyone suggestions please!

Gus