Community Discussions and Support

The perfect forum for general discussions or technical questions about Mercury Mail Server.

0
-1
closed
FJR posted Mar 1 '11 at 2:48 pm

> Is it possible to force a Reply-To header on a mailing list?  I'm seeing that some clients default replys to the list, while others default to the sender.

Shure? If "Reply to list" isn't set, answer should be send to FROM. SENDER is the header for the mailadress of sending instance - most times the adress of the mailserver. It's for automated routines ... not for mailclients.

> I see there is an option to "force replies to go to the list"

Forces mailserver setting a (new) REPLY-TO to mailinglist ...

> but what about forcing them to the sender?

To your mailserver?

A mailclient should look for REPLY-TO and - if not present - take FROM for replying. But - as with Pegasus - there is no problem telling the mailclient to ignore REPLY-TO ...

I never had problems with that feature on restricted lists. Are there replies not sent to FROM or in case of error to mailadress defined for ERRORS-TO?

Hope this helps

    Olaf

 

0
-1
closed
pauls posted Jan 22 '11 at 6:12 pm

I know I was getting emails through using Mercury before my W7 re-install. I know I was doing substantial 'testing' of Mercury's functions and parameters without it ever crashing. Now I'm NOT having that success at all.


I apologize I think I have shown bad attitude in coming in to this wanting to prove it was some sort of a uninstall/reinstall application problem. 


Thomas is correct. I am barred from the SMTP "E" system. I must have been using SMTP "C" when I was having successes. 


I have switched to SMTP C. The crashes are back. I start Merc the first time and can go through everything. I send my email. It crashes. I restart, it crashes. I clear the Queue and can sucessfully restart I can then go through it (until I try to send another email). The crashes are too fast to read the messages in the consoles. After it all: 1) there are a few queue entries for the one email, 2) no mercury C logging entries,

3) 1 mercury C session entry  ...

22:18:33.843: --- Sat Jan 22 22:18:33 2011 ---
22:18:33.843: Connect to '(null)', timeout 30.
22:22:51.385: --- Sat Jan 22 22:22:51 2011 ---
22:22:51.385: Connect to '(null)', timeout 30.
22:24:50.211: --- Sat Jan 22 22:24:50 2011 ---
22:24:50.211: Connect to '(null)', timeout 30.

It certainly crashed in less than 30 seconds!

Yes, there are STRANGE things going on with my ports that I am looking into more before I conclude anything, but hope someone can reason the problem from the only messages I can find.


0
-1
closed
Thomas R. Stephenson posted Jan 20 '11 at 12:07 am

> From this posting, I have verified that the dm= entry is indeed processed prior to the mailing list entry.  Frankly, this is a bug
> IMHO.

The mail for a mailing list uses the list name and the domain as listed in Configuration | Mercury core | "Internet name for this system" and that should never be a domain mail box.  To address a mailing list is will be <listname.from lists.mer>@<internet.name.for.this.system>

I'm not sure what you are doing here with the dummy domain to get access to the lists.

0
-1

Posted to the list as well - added info here for those that are forum centric.

 

Finally got it to behave with version 4.62 and an outgoing rule filter. I

do use the interface to create my rules and somewhat condensed what each

entry does so that it didn't line wrap terribly in my post(s).

 

Here is what works perfectly for me (not the syntax of ORULES.MER):

 

[Headers] NOT From [Contains] postmaster@MyDomain.org

[Action] GOTO 550END

[Headers] NOT To [Contains] MyAddress@MyDomain.org

[Action] GOTO 550END
 
[Headers] Subject [Contains] Postmaster Notify:

Delivery Failure. [Action] Logical AND
 
[Expression] *550 No such

recipient* (Body only) [Action] delete message

 

[Label] 550END

 

............

Maybe I had a syntax error in my previous line "Expression Received: *by

mta2.MyDomain.org* ..." or there is a limit on the number of consecutive

"Logical AND" results that work [the help files lead me to believe that there is

no limit on that].

 

Thanks to K.T. for having me test with a single line delete rule to test if

that even functioned correctly (it did and got me on the right track).

 

Regards to all

 

0
-1

[quote user="Mischief"]
Here is the log of me emailing a hotmail account.  It ended up in the receipients junk box.  My email has no rules or alias associated with it.
[/quote]

[quote user="Thomas R. Stephenson"]
You said that you were changing the address in the message to info@.. and I do not see that change here.
[/quote]

I tried using my own account that has no rules or aliases setup.  I can recreate the same issue my customer is having with my own account. So I know it is not user specific and doesn't have anything to do with the alias I gave him.

Here is the SMTP Client Log of the email

18:39:08: processing job MO000017
Resolved MX for 'hotmail.com' to 65.55.37.120
Connecting to 65.55.37.120
MAIL FROM:
RCPT TO:janelle_benning@hotmail.com
DATA
[2724 bytes] Message accepted for delivery by 65.55.37.120.
18:39:15: 7 seconds elapased, closing connection

Here is the mercury.ini file.

[General]
myname:          dcwebsolutions.ca    # 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]
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:\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]
logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\MERCURY\Sessions\MercuryC\    # Directory for session log files
Session_logmode : 0
host:             # mail mail host which relays for us
scratch:     C:\MERCURY\scratch           # 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:\MERCURY\Mercury\FAILURE.MER  # Delivery failure template
esmtp:       1                    # Yes, we want to use ESMTP extensions

[MercuryE]
HELO : dcwebsolutions.ca
Session_logging : C:\MERCURY\Sessions\MercuryE
Session_logmode : 0
Poll : 15
Timeout : 60
Logfile : C:\MERCURY\Logs\MercuryE\~y-~m-~d.log
Log_Verbose : 0
DNS_Timeout : 20
DNS_Retries : 4
Transcripts : 1
MaxThreads : 10

[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
Timeout : 30
Relay : 0
Strict_Relay : 0
Alt_Server_Port : 587
Allow_Illegals : 0
SMTP_Authentication : 1
Auth_File : PWD
Session_logging : C:\MERCURY\Sessions\MercuryS
Session_logmode : 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:\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 : 0
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]
dcwebsolutions: dcwebsolutions
dcwebsolutions: dcwebsolutions.ca
underRconstruction: underRconstruction.com
underRconstruction: underRconstruction.ca
vidicsbullies: vidicsbullies.com
vidicsbullies: vidicsbullies.ca

[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

 

0
-1
closed
pauls posted Jan 15 '11 at 4:20 am

I found my problem. It turns out that 'someone' changed my firewall settings on me (after 'someone' disabled the firewall I was soon to replace, anyway) and there was something that Mercury didn't like about Windows 7 firewall 'public' settings, for which. I apologize, I have investigated no further than to turn that off (for now anyway).

I may be following your recommendations as through it all I'm now getting 'core' errors on my admin mail file. But first I gotta get to why 'someone' now keeps turning that firewall setting back on on me (grrrrrrrrrrr). Thank you, Rolf!



0
-1
closed
Rolf Lindby posted Jan 13 '11 at 9:32 pm

This is fixed in current versions of Mercury, so please upgrade. The removed attachment will be replaced with at text like this:

This section of the message has been deleted by the mail system -
it originally contained the following data:

   Content type:         application/zip
   Content description:  (None)

   Filename:            Test.zip 

The rule may remove MIME parts you want to keep as well, so you may need to check that there is a filename (a regular expression looking for "?*" will do it).

/Rolf 

0
-1
closed
Rolf Lindby posted Jan 24 '11 at 7:12 pm

Did you check MercuryS logs for connection attempts? It actually looks very much like there is some other program answering on port 25 on your server (assuming that you are trying to send, not receive).

/Rolf

0
-1
closed
PaulW posted Jan 12 '11 at 12:13 am

[quote user="MartinTruckenbrodt"]what willl happen if I'm deleteing the CNM files manually?[/quote]

Well, you will get rid of the message - that is what a mail client will do in deleting an email in the mailbox. So long as you don't have the mailbox open using another client I don't think it will cause a problem.

0
-1
closed
Rolf Lindby posted Jan 11 '11 at 1:12 am

This is not an error message from Mercury but from the receiving SMTP server.

There are two ways to change how messages are sent to list members. In Distribution you can have Mercury create up to 20 separate jobs for delivery ("fanout"), in Error handling you can select VERP-based to have separate delivery for each member. From Mercury help:

"VERP-based error handling   VERP stands for "Variable Envelope Return-path Processing": when using this method, every recipient in the list gets a separate copy of every message sent to the list, and in that copy of the message, a special version of the Return-path field is created that allows Mercury to work out the individual list and subscriber from any errors that get returned to it."

/Rolf 

0
-1
closed
MartinTruckenbrodt posted Jan 11 '11 at 9:13 am

Hello Chris,

thank you very much for the answer!

I've done a Outgoing & Always trigger rule. I've selected the action 'Copy message to another user' and put in the name of the user.

Bye Martin

0
-1
closed
Rolf Lindby posted Jan 6 '11 at 11:18 pm

Disable MercuryX unless you actually use it. If you use it you will need to download this patch:

http://community.pmail.com/files/folders/patches/entry24194.aspx

/Rolf 

0
-1
closed
Rolf Lindby posted Jan 4 '11 at 3:48 am

The From header is normally set by the program that creates the message, in this case Pegasus Mail, so that's where you should look for the sender address. If you can't find it, please post to the Pegasus Community Support forum about it.

/Rolf 

0
-1

Hello all,

This was posted on the old mail list, but I think that list is little frequented, so am x-posting
here in the hopes that I can get this sorted quickly. Thanks in advance for any help.

I thought I would narrow down one of the issues that I am having with Mercury to make it hopefully a bit less to wade through.

I am a listmum on a group and need, from time to time, to send out emails from the email address
that is received by all listmums.This email is forwarded to each of our main email accounts, and I
am able to receive them, at this point, with no problems. Obviously I cannot poll that email
account, as the mail is forwarded to me.

I have listed the domain in the various configurations in my list of domains in the mercury.ini file. I am using Pegasus Mail.
iistudio: prodig.org
iistudio: prodig
iistudio: mail.prodig.org

I have an identity set up for this purpose and need that email address to be the 'from' address as well
as the 'reply to' address. I have also set it  to auto cc emails sent from that address to the listmoms@prodig.org email,
so all listmums are aware of any issues I am dealing with on my 'watch'.

I am not, however, able to send emails through Mercury using the sender's address as this listmum
address (listmoms(at)prodig.org). I need that to be the 'from' address as well as the 'reply to'
address. I have it set to auto cc emails sent from that address to the listmoms(at)prodig.org email,
so all listmums are aware of any issues I am dealing with on my 'watch'.

 Currently I am getting the following 4 error messages for each mail, when I send from that email
address as Mercury is refusing to process them. It says:

  --- Problems not related to specific addresses in the message:
   Job has invalid or illegal from address.
 *** listmoms(at)prodig.org

 *** "Ellie Kennard - duty Prodig Listmum" <listmoms(at)prodig.org>
   User "Ellie Kennard - duty Prodig Listmum" <listmoms(at)pr not known at this site.

--- Problems not related to specific addresses in the message:
   Job has invalid or illegal from address.
   *** Ellie(at)iistudio.com

  *** "Ellie Kennard - duty Prodig Listmum" <listmoms(at)prodig.org>
   User "Ellie Kennard - duty Prodig Listmum" <listmoms(at)pr not known at this site.

The strange thing is that Ellie(at)iistudio.com is a valid address on the system and one that I use regularly with no
difficulty.

How can I make this work, does anyone have any ideas? I do not have a fixed ip address (ISP only allows them for
business accounts which cost a fortune) but seem to have no difficulties in sending (now) from
a gmail address. I used to be able to do this with no problems but have made several changes to the
Mercury.ini file (under direction from Thomas Stephenson etc., who is,I think, away) and now am unable to make
this work.


Cheers!

Ellie

2.31k
13.66k
8
Actions
Hide topic messages
Enable infinite scrolling
Previous
Next
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft