Thanks Rolf !

It was the Mercury.Bak file.   It was zero length but I restored it from backup as you suggested and all is good agian.

 

Whew!

Got it working [:D]

 

Then promptly broke it  [:'(]

Rolf,  thanks a million! That works pretty fine! You're my hero of the day! The file based forwarding wasn't activated - so I did and with the forwarding and deliver-also statements I got exactly what I want!

Best regards

hightc

 

As the users were added from within Mercury this should not be needed:

"Mercury saves changes made by its own user dialog as soon as you click OK, so we recommend that you do all your user administration from within Mercury." (Mercury help)

I added a new user here and there was no problem to access the new mailbox with POP3 directly without restart.

Do you run any kind of anti-virus software that might interfere with Mercury's access to the mailbox directories?

/Rolf 

All,

Recap of my issues.  Setup basic mailing list, Moderator only can post, sending mail to list from Outlook 2003. 

Have a disclaimer and links for removal from the list in a signature file for the list. 

The signature file is attached normally ONLY if you send it as PLAIN TEXT and WITHOUT any attachment.

It seems to me that it would be common for users of a distribution list to send attachments and disclaimers?

How are you all doing it?

I know you mentioned that Outlook does the multi-part thing, however, if my antivirus software can stick a "disclaimer" on every processed email wtihout requiring "plain text", I cannot understand why Mercury can't?

I have tried getting aroud this by setting up a Global (or outgoing) filter, to INSERT A TEXT FRAGMENT (disclaimer) to all emails from the Mailing List address. 

This does not work either, it "breaks" the list.  The CORE will process the mail to the list, but then it does nothing. It will not send the messages to the list members.

I'm guessing this is a bug and should be reported or tested.

Thanks much,

Mark

  

Chriscw:  I am very interested to know how this can be done as well, as

I see this coming down the pike soon enough for us.  We currently have

people coming in via a SSL-VPN and using IMAP4 from thier PCs, but more

and more are using the smartphones so there must be a way to get this

done.

There is but there are a lot of bad IMAP4 clients out there as has been noted in this thread.  Get a good IMAP4 client and the problem pretty much goes away.

Thomas,

[quote user="Thomas R. Stephenson"]

If it could not find the user and the mail was being received via SMTP then it probably would be bounced back to the sender as undeliverable.  If receiving mail via MercuryD  and could not write any mail to a local directory it should still be on the POP3 host.

[/quote]

Thanks' for taking the time to answer the Email was received via MercuryD, but the Email aren't on the POP3 HOST, my guess is that all the mail has been return to the sender with the mention that the user didn't exist. A suggestion for David, in that case it will preferable to keep the EMAIL locally until the postmaster cure the problem !. We will plan to upgrade to the latest version of mercury and buy a 12 users license !

Best Regards,

Sylvain

 

 

 

yes, when their pop3 connection times out, since transmission of a 50MB message is blown up to between 75 and 150MB depending on content encoding

Do I understand you both correctly in that I do not have to have the

client on all machines, just the one and run the client across the

network? See, the way I've handled it up to now is to have a copy of

the client on each machine, each pointing to the same home mailbox.

With PMail you can have a single copy with only the shortcut on each system.  In this case you would not be running either POP3 or IMAP4, you would be accessing the mail directly.  I assume you could also do something similar with a single instance of  an IMAP4 client like T-Bird but I've not tested this.  I've always installed the POP3/IMAP4 client on each machine.

Yes it seems like something is blocking me locally. Still, I even tried switching the firewall off (with Internet disconnected) and still wasnt able to connect to a mail account. Funny thing is tough, some bot tried earlier and it looks like it already had more success than me -.- 


Connection from 200.137.194.19eight
* User staff, username or password failure (1 of 2)
1 sec. elapsed, connection closed

Connection from 200.137.194.19eight
* User administrator, username or password failure (1 of 2)
1 sec. elapsed, connection closed

Connection from 200.137.194.19eight
* User sales, username or password failure (1 of 2)
1 sec. elapsed, connection closed

Connection from 200.137.194.19eight
* User sales, username or password failure (1 of 2)
0 sec. elapsed, connection closed

Connection from 200.137.194.19eight
* User recruit, username or password failure (1 of 2)
0 sec. elapsed, connection closed

Connection from 200.137.194.19eight
* User alias, username or password failure (1 of 2)
0 sec. elapsed, connection closed

Connection from 200.137.194.19eight
* User office, username or password failure (1 of 2)
0 sec. elapsed, connection closed

Connection from 200.137.194.19eight
* User samba, username or password failure (1 of 2)
0 sec. elapsed, connection closed

Connection from 200.137.194.19eight 
User test, (2) 14 messages, 27197 bytes      (<- thats actually less funny. Can anyone tell me if the mails have been transmitted successfully? 0 seconds look too short for that. and yes, I changed the name of the test account... stupid idea.)
0 sec. elapsed, connection closed 

...and a few more

 

Ill try to figure out whats blocking my login attempts locally.

 

[quote user="dilberts_left_nut"]

Your mail server should be assigned a static ip (either manually or via DHCP Static Lease) otherwise, if the assigned IP changes your port 25 forward will be pointing at a vacuum or the wrong machine.

What response do you get to:

telnet 127.0.0.1 25

?

[/quote]

I do have a fix local IP, still, I closed Port 110 after this incident. CMD says that telnet is not recognized. I think that's a Vista/Win7 thing where this command is blocked. I just cant remember right now where the settings for this are hidden. Maybe I should wait till I reinstall WinXP where I exactly know how what works.

Thanks to both of you for your help so far. 

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]

cfocapitalpartners.com	MX	mail.cfocapitalpartners.com	0	3600	[]
mail.cfocapitalpartners.com	A	74.79.132.182		3600	[delete]