We have all homedirecories, e.g.

//server/home/company/last_name/

this

path would like %homepath% in Windows (for each user), and after the

homepath is the pmail-folder with the mails. (also %homepath%\pmail\ )

Also we only need some variable which does the same like %homepath% in windows

The mailbox directories in Mercury must be in the same location, i.e. \\server\home\company\last_name\pmail  so the only variable you can use the the ~8 or ~n  in the place of the last_name.  If you have multiple paths to different servers and directories them that means each of these must be managed by their own Mercury/32 installation. 

I'm not even positive you can still use the \\server\home\company\~n\pmail format for the mailbox directory spec since it is not really officially supported except with NDS in a Netware setup.  I have used it in the past and it did work for me but I've not used it in at least a couple of years.

This daemon from the download section will fix the problem:

/Rolf 

[quote user="newcomer"]Hello all, I am new to mercury mail server. It is very cool. But I am facing a problem.

Every mail I send from my desktop app (java app, using java mail api) is reported as spam, both by gmail and yahoo.

Is there any work around?

Yes, instead of using MercuryE use MercuryC for sending via your ISP's SMTP server as a relay host.

Am I missing something?

Not sure but if you use session logging to capture the TCP/IP level transactions you might find out exactly why.  I suspect through that you do not have a fixed IP address and they are rejecting your connection using one of the many DUL blacklists.

Any solution will be highly appreciated.

Thank you very much.[/quote]

Got it,

 Thanks a lot

Once the IMAP account is setup in each client, it's just a matter of 'drag & drop' from the clients mailstore.

[quote user="evilphish"]AV software isnt even installed on this machine.[/quote]

[quote user="giu"]Hi to all i want to know if is possible to create in Mercury server username with dot ex :  admin.lan 

I try to create it but system not accept

The usernames become directory names and should not include periods.  You can have addresses like First.Middle.Last@domain.com though.  See configuration | Mercury core | Advanced for details.

thank to all ![/quote]

It took me a few days to get back to everyone.  Here's what I have found out.

 First, the "Suppress validation of 'From' field..." option does affect whether the  filters are applied.  As an experiment, I enabled suppression, and no longer received notifications of invalid addresses.  Instead, notification was skipped and my filter deleted the email, as shown below.

Fri 15, 12:22:24: Job MG00003B: sender address 'charlesnn@softwaremeadows.com' is invalid
   * Job killed by filtering rule.

 To prove it, I disabled only that setting, and began receiving notifications again.

Fri 15, 13:56:45: Job MG00004F: sender address 'charlesnn@softwaremeadows.com' is invalid
Fri 15, 13:56:56: Job MG000051: from <> (local)
   * Recipient <charlesnn@softwaremeadows.com> unknown
Fri 15, 13:56:56: Job MG000051: Processing failed deliveries and generating notifications
   Mail Delivery System <> - Notification discarded - potential loop.
Fri 15, 13:57:07: Job MG000053: from postmaster@flattland.com (local)
   To: charles (local) -OK

With that said, based on Thomas' advice, I'm going to

• Disable  "Suppress validation of 'From' field...", which is the default
• Disable "Accept mail for invalid local addresses", which is also the default.  I had it enabled because, at one time, I accepted any email to the domain.

Thanks for the help.  If I run into trouble, I'll post again.

Charles

Ok. Thank you very much for time and support.

All works fine, when I create one topmost rule to forward message, lower rule to move or delete. summary action is : Detected, deleted (killed by rule), forwarded. Exactly this sequence.

Rule is: If this regular expression "X-SPAMHALTER: SPAM detected!" (without quotes) occurs in messages headers only, then move to another (local) user "spams" (without quotes).

Now trying with directory. Not work.

Clean installation :-)

Working config is- topmost forward rule, next delete rule. Works fine. I left it as it, but hane no clean sense :-). In core process I see "job killed by filtering rule" and then send to spams.

Thank You for responses.

A.

There is lazy HTML detection in Mercury content control, though, and there is a whitelist function there as well.

/Rolf 

Thanks Thomas for your quick reply.

You were right about the files being locked. I've couldn't identify which process locked it. But I tried rebooting the Mercury server and it didn't help. I then rebooted the Netware server containing the user PMAIL folders (after requesting all users to shutdown their pc's), and that did the trick.

On behalf of my clients many thanks...

As for the other two fields (Sender: and X-Envelope-To:), neither

are in the headers section. It might help if I clarified that I'm using

Mercury's POP3 D connector for retrieval on these accounts, not SMTP.

As for 4.01b, I just noticed the new version of Mercury and I have

put upgrading on my todo list. Will the new version install on top of

the old and maintain configurations or will it need to be a clean

uninstall/reinstall with a manual reconfiguration of all options?

Just install as an upgrade over the current setup.  Have to shut down Mercury while you do the upgrade but other than that it should take seconds to do.

[quote user="caraudiovideo"]Thanks, that is leading me in the right direction. Would it be easier for me to simply set up multiple instances of Mercury? I only have 1 external IP and can only forward traffic to one internal IP.

instance1: domain1.com on ip 192.168.1.2

instance2: domain2.com on ip 192.168.1.2[/quote]

Multiple instances of Mercury is required but the servers should be running on different ports if all are on the same system.  One of the servers would be the gateway server and puts mail into domain mailboxes for the domains not served on the system.  The other systems would get the mail via SMTP to the different SMTP ports (i.e. 8025, 2525, 1025, etc) using WSMTPEx.exe or pulled from the gateway system via MercuryD.  I like the push via WSMTPEx but the pull via MercuryD works as well as long as you use the X-Envelope-To: header for mail delivery.

Really strange, you do not have over half of the sections in the normal mercury.ini file.  Try just adding the following to this file and see what happens.

[MercuryC]
Host :
Failfile : C:\MERCURY\Mercury\FAILURE.MER
Poll : 30
Scratch : C:\MERCURY\Mercury
ReturnLines : 15
Timeout : 300
ESMTP : 1
Server_Port : 587
SMTP_Username:
SMTP_Password:
SMTP_ConnFlags : 4
POP3_Auth : 0
Logfile : c:\mercury\logs\mercuryc\MercuryC.log
Log_Verbose : 0
Session_logging : c:\mercury\logs\mercuryc
Session_logmode : 1

[MercuryE]
Poll : 15
Timeout : 60

[MercuryD]
Scratch : C:\MERCURY\scratch
Timeout : 300
Poll : 100

[MercuryS]
Debug : 1
Logfile : C:\MERCURY\Logs\MERCURYS\mercuryS.LOG
Timeout : 300
Relay : 0
Strict_Relay : 1
Alt_Server_Port : 587
Allow_Illegals : 0
SMTP_Authentication : 1
Auth_File : c:\mercury\pass.txt
Session_logging : c:\mercury\logs\mercurys
Session_logmode : 1
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 0
No_VRFY : 0
SMTP_ConnFlags : 0

You will have to go through and reconfigure all of the protocols but this may not work even then.  If it does not then you will have to re-install as new over the current program to get a valid mercury.ini file.  You might though want to check the mercury.bak and mercury.bk1 files to see if these are good mercury.ini files . 

[quote user="Mann07"]

I don´t understand why real data would help. The Mercury-Machine is inside our network, no way to access it from the internet. Also no public DNS-Records for it. Its just fetching mail from our exchange-server and should deliver it through our exchange-server...

You did not make that clear at all.  If this is true then the data you have provided is real data.

I get the same error (sender adress is invalid) when I enter

Local host or server                      Internet name
computername                             computername
computername                             publicdomain.com[/quote]

I assume you are getting the mail via POP3 from the exchange host and are trying to have this mail sent to a mailing list.  If so the domain of the message must match the domain set in Configuration | mercury core | Internet name for this system.  That is, if info is a mailing list and not a user then the system name must be publicdomain.com before this will be sent to maiser to check to see if there is a mailing list called info. One problem may arise though since the sender address is going to be using the domain publicdomain.com the exchange server may reject the mail do to an invalid sender domain.

It would help a lot if you were to provide your mercury.ini and lists.mer file for analysis as well. 

You appear to have set your client to use APOP authentication.

Either set your client to use regular POP3 user/pass authentication or set the APOP secret in Mercury.

MercUpW.exe offers some extra functionality (sending email notifications etc), but unless you need that loader.exe should do. You should not run both, anyway. With the upcoming 4.71 release of Mercury it will as well be possible for registered users to run Mercury as a service that can be automatically restarted by the service handler in Windows in case of unexpected stops.

/Rolf 

[quote user="yuni_asih"]

outgoing email is doesn't work, there is an error message in mercuryE "553 we do not relay non local mail"

[/quote]

[quote]

hi Thomas,

 when i tried to send email from outlook express, there is an error message from symantec Email Proxy

"your email message was enable to be sent because your mail server rejected the sender : 421 Service not available,closing channel"

please advice

thanks

[/quote]

These are error messages from MercuryS, your SMTP server, that receives the message from your mail client and other mail servers.

MercuryE is the SMTP client module that sends outgoing mail to external mail servers.

The "421 Service not available,closing channel" is because you have MercS paused.

the "553 we do not relay non local mail" is because you have not set up Authentication to allow relaying or a Connection Control exemption to allow relaying.

[quote user="KJATL"]

Hello,

 This is my first foray into the world of Mercury. I was following a tutorial that involved testing a mail() PHP function using Mercury as the mail server. I believe the script is okay because it echos feedback  "Message has been sent". Currently I have 28 items "pending" This is what i'm working with where xxx is the first part of my email address:

I ass-u-me that use are using XAMPP.

php.ini :

 [mail function]
SMTP = localhost
smtp_port = 25
sendmail_from = Admin@192.168.1.10

This form of the address is invalid, the IP address must be enclosed in [] to make it a literal address. Use Admin@[192.168.1.10]

MercuryS output:

Connection from 127.0.0.1, Wed Apr 29 23:26:41 2009
HELO kkk

Should be a host name like [192.168.1.10] instead of kkk   It will work here since Mercury/32 really does not care.

MAIL FROM:<localhost>

Should be Admin@[192.168.1.10] instead of localhost

RCPT TO:<xxx@gmail.com>
DATA
DATA - 6 lines, 185 bytes.
QUIT
0 sec. elapsed, connection closed Wed Apr 29 23:26:41 2009

Connection from 127.0.0.1, Wed Apr 29 23:30:36 2009
HELO kkk

MAIL FROM:<Admin@192.168.1.10>
RCPT TO:<xxx@gmail.com>
DATA
DATA - 6 lines, 185 bytes.
QUIT
0 sec. elapsed, connection closed Wed Apr 29 23:30:36 2009
 

 Mercury Core:

 Wed 29, 23:27:03: Job MG000041: from postmaster@[192.168.1.10] (non-local)
   Created outgoing job with ID MO000042
   To: Admin@[192.168.1.10] (non-local) -OK

Job was accepted and since [192.168.1.10] is not in the domains list then it's sent to the queue for delivery off server.  Can't go anywhere though since the address is a non-routable IP address.

Wed 29, 23:30:43: Job MG000043: from Admin@192.168.1.10 (non-local)
   Created outgoing job with ID MO000044
   To: xxx@gmail.com (non-local) -OK

Job accepted and sent to queue for processing by MercuryC

 Does anyone have any idea what I need to work on first?

Probably the outgoing protocol MercuryC used to send SMTP to the outside world via a relay host.  MercuryE will not work since you have no fixed IP address and host name.  Without a fixed IP address and host name 90% of the receiving SMTP hosts will reject your connection as spam.[/quote]