> Do you know how I have to configure the  different modules of Mercury?
>
> example
>
> step 1
>
> Outlook account have to be configured with the smtp server ip adres of the Mecury Server

That works and you should see the action on the MercuryS screen and log.  Turn on session logging in MercuryS to verify that the mail is received.

>
> Step 2
>
> MercuryS SMTP Server has to be configured.
>
>  Announce myself as : < What should this be?>

Your registered host name associated with the IP address of your connection.

> Ip Adres interface used : < ip adres of the interface where Mecury is running on or localhost?>

Leave it blank

> Other specific parameters to send also to hotmail accounts


> Step 3
>
> Configure MercuryE SMTP Client end to end
>
> Identify myself as: < What should this be? >

You registered host name associated with the sending IP address.  You can leave this black and it will use the host name you have set in the general section.


> Name servers : < A DNS servers ip adres, or default gateway adres>

The IP address(es) of your DNS host(s) should be entered here.  The default gateway setup is a Winsock setting and is not material to MercuryE

There is nothing specific here but you must have a fixed IP address and host name with a PTR record to send via MercuryE.  Your ISP also must allow you to send via port 25 to other hosts.

I have now switched the X-Originating-IP spam recognition process to Policy from filtering.  This now allows me to make a decision on whether to delete a message or not.  I have recognized a few issues, but these are minor, e.g. the national IP address range databases that I am using are not 100% accurate (I encountered one IP address which wasn't in my US database, but an address look-up on the web identified it as US) and I will probably add NZ to the admitted address ranges (David's TheThousand address was identified as Spam!).

I have one issue that I would like advice on.  I am using global filtering, which is then followed by my Policy check for Spam.  I had assumed that messages that were deleted by filtering and messages that were moved to another user by filtering would not be exposed to the Policy check.  However, any remaining messages would be tested by Policy.  Is this correct?  I am asking this as a couple of messages from new, but non-Spam addresses are being subjected to the policy check.  I didn't expect this, as I have moved them to another user, prior to the Policy check.

Gordon

An attachment is part of the message as recieved by Mercury and will be part of the message file (.CNM file) in the mailbox directory. One file can contain a number of different MIME parts. It's up to your email client to handle the attachment in a sensible way when you collect your mail from Mercury.

/Rolf  

Mercury won't mind what client program is used as long as the mail protocols (SMTP, POP3, IMAP) are implemented properly.

/Rolf

Since my understanding of mail servers is nowhere near as good as Thomas's, what I would do, providing there aren't too many recent emails, is:

• Ask all users to move any filed mails back into their Inbox - each mail will then be a separate .cnm file in the user's folder. Close all clients
• Shut down Mercury
  
• Move the current working folders (everything in  .. MERCURY/MAIL/) to a temporary location
  
• Copy  /MAIL and sub-folders and contents from the old system into the new one, in place of the ones you moved
  
• Copy (not move) all each user's recent .cnm files from the temporary location into their folder on the restored system. Ignore other files.
  
• On restarting, the original stored mail should all be filed where it was 2 weeks ago, and the last 2 weeks will be in the inbox ready to file.

Mail in folders (other than Inbox) is in .pmm files, with .pnm files as indexes. I wouldn't try editing these - but putting mail back in the inbox during the copy gets round that.

If for any reason it doesn't work, you can replace the recent mail from the temporary location and you're back where you were.

Chris

> Graciaspor responder.
>
> Prove cambiando a MercuryC pero tampoco resulto. Es más  con el mercuryC ya no envia a hotmail, yahoo.
>
> Me parece que el correo si es eviado pero el servidor de destino parace que lo rechaza. Puede suceder esa situación?. Que en lo q tendria q hacer si se diera  esa situacion??

Google Translate

Prove MercuryC but changing it is not. Moreover the MercuryC no longer send to hotmail, yahoo.

I think the mail eviado but if the destination server that rejects it seems. It may happen that?. Q in which q would have done if given this situation?

I assume you are saying that the mail is not getting to Hotmail and Yahoo even when using your ISP's mail server.

I now need to have both your host name and IP address as well as the ISP's host name and IP address.

Supongo que usted está diciendo que el correo no está llegando a Hotmail y Yahoo, incluso cuando se utiliza servidor de correo del ISP.

Tiene la necesidad de que tanto su nombre de host y dirección IP, así como el nombre de host del ISP y la dirección IP.

Note: this translation is not very good and I really hope some Spanish speaker would step in here with some real translations.  ;-(

Thanks that explains it !!

I had copied this rule and changed the match.

H, "*.*", BSN, "554"
So this rule drops anything with out a '.'

Thanks :)

 eg.  group member (a) gets email 1, member (b) gets the next email

sent to the group, member (c) get's the next and then back to (a)

again?  I'm trying to make sure all members of a sales team get fair

distribution of email sales leads.

The only way I can see to do this is manually.  Mail goes to the sales manager and the sales manager routes the mail to each salesman.

 

Deagol,

I've now done exactly the same installation on a Windows 2003 server, and everything works. My issues must be specific to IIS 5.

Thanks for your help.

Richard

 

As Paul says, it's a badly formatted message. The log line DATA - 45 lines, 1100 bytes. indicates that Mercury has reached the end of the message. The end of a message body is indicated by sending "<CRLF>.<CRLF>" . Anything received after that will be considered a command and not part of the message.

/Rolf

 

Sure enough!  I updated ClamAV and things are working properly now!

Thanks for the quick response!

 

Charlie

  ~~~

Hello,

Just an update on this, it appears I have a few things incorrect.

It appears that you only need to create an INI file if there is not an AD user for the mailbox you want to create.

 "The ini file is only needed when you want to

create a mailbox that doesn't have a corresponding user in the AD."

Mailbox names must match AD user names, so I would still  have to change the mailbox names and edit security when I move to MS OS.

Thomas, Frank mentioned that he would try to contact you.

Thanks,

 Mark

 

 

 

 

 

Install Mercury, with module MercuryS and MercuryC. Then within the core you have list management.

Well, "triggered by a regular expression" in filtering seems to do the job.  The only issue remaining seems to be to minimize false positives, e.g. if someone sends me an email discussing SPAM and includes the characters charset="koir-8".  I think that this can largely be eliminated by knowing where these characters can appear on a line (there would be an unfortunate case if body text in a wanted e-mail included charset etc at the beginning of a line).  There seem to be several variations, e.g. charset on a line with Content-Type, charset on a separate line preceded by a tab or spaces, and the charset name surrounded by double-quotes or not.

Gordon

 

Lingering mailboxes means that Mercury will keep a copy of the mailbox image in RAM for a specified amount of time in case the IMAP clients connects again. It's mainly useful if you use a webmail program or some other IMAP client with limited cache functions.

It should be safe to increase the value to 600 as long as you have sufficient free RAM to handle it. Around 300 KB per mailbox is required.

It's been suggested that mixing POP3 access with having lingering mailboxes could cause problems. I haven't tested that myself so I can't say if there is a risk with it - maybe someone else has more information.

/Rolf 

Just clear Queue and Scratch directories before starting Mercury again. And make sure the file mercury.ini isn't damaged. If it appears to be damaged you can make a copy of mercury.bak and rename it to mercury.ini.

There is usually no need to reinstall Mercury unless you have had some bad kind of disk crash. If so you can download the Mercury installer and update Mercury without touching other parts of XAMPP.

/Rolf

> I am a total newbie to mercury mail. I installed it on a server using
> Scenario 1: Permanent internet connection. I did not create any
> mailboxes - all emails sent to this server are to be forwarded.

You must create at least one mailbox, the local user that handles the postmaster cannot be forwarded for obvious reasons.

>
> Using the alias configuration, I set up an email forwarder which
> redirects email sent to me@mydomain.com to
> myrealemail@myrealdomain.com. Using the Send mail message capability
> from within the Mercury console, I sent an email to me and it wound up
> in my inbox.

Much better is to use one of the tools to do this via forwarding

These are NOT a true MX host function since it does not queue and wait for the receiving system to be online to send the mail.  That said, WSMTPEx will keep retrying if the connection to the server and port cannot be made.  I have not tested how long it will continue retrying.   

1.  First of all is the simplest, you simply re-write the domain in the mercury.ini [Rewrite] section.

[Rewrite]
none-tstephenson.com: [192.168.1.3]

I really was surprised when this one worked since it truly simple and has been there
all along.  You learn something new every day.  The brackets are required when using
an IP address.  This forwards all mail for anyuser@none-stephenson.com to
anyuser@[192.168.1.3] using the normal Mercury/32 send process via port 25. 
Works quite well when using MercuryE, cannot work when using MercuryC unless the
IP address is a routable IP address.  You must re-boot Mercury/32 for each change
since this is only read at startup.  

2.  The second one is the daemon MercFwd and it essentially does the same thing as
the rewrite but this can be done dynamically by changing the domains section.  The
[Domains] entry of  

daemon:c:\mercury\mercfwd.dll;[192.168.1.3]: none-tstephenson.com

does essentially the same thing as the rewrite above.  Again it uses Mercury to deliver
the mail via port 25 and so you cannot use this with MercuryC when using non-
routable IP addresses.  

3.  The third one is the program WSMTPEx.exe (SMTPEX.NLM for Netware)  and this a a
separate program that takes mail for a email account and forwards it to any port and
any hostname/IP address.  I use this with my domains to forward the mail to a Linux
system (must use high ports as non-root) and to a second instance of Mercury/32
running on my system (can't share port 25)  Here's a sample of the ini file I use for
forwarding all mail to Mercury/32 running on Ubuntu v8.10 and Wine.  

 #  You can rename this tool, but name of following section must remain [WSMTPEx]
[WSMTPEx]
Version=0.10
#  TCP port, on which SMTP server listens
Port=8025
#  Number of seconds to delay between searches for emails
LoopDelay=30
#  Folder, under which is most of user's mailboxes
UserFolder=
Domains=1
# Users mail address domain part
Domain1=linux-tstephenson.com
LogName=c:\Mercury\WSMTPEx.log
SMTPServer=192.168.1.4
MailBoxes=1
Badmails=c:\pmail\mail\BadMail

[linux-tstephenson.com]
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
Mb1addr=dm:ubunto
Mb1dir=c:\pmail\mail\ubunto


This takes all the mail in the domain account "UBUNTO"  and sends it to port 8025 on
192.168.1.4 to be received by MercuryS.  The directory BADMAIL I have specified
must exist.  You can run multiple instances of this tool and and it can be run as a
service.  If run as a service and running multiple instances the name of the program
should be changed.  I use WSE-UBUNTO to rename the program and ini file for this
one.  

Many thanks to Petr Jaklin for the development of these tools.  You can get these
tools at the community download areas or directly from Petr Jaklin's site
http://www.3net.cz/software/softe.htm  

>
> Next, I sent a message from my computer to me@mydomain.com. Looking at
> the Mercury SMTP server console window, I see that the message did
> make it to the server. However, it reported 'user <me@mydomain.com>
> not known'. I also received a bounce email which stated:

Looks like the alias was wrong.  I do this all the time when receiving mail for non-local users.  Could you provide exactly what was entered as the alias?

Clearly it was not en fault in the component nor in mercury. [:D]

But for any reason the mailboxfolder didn't anymore exists.

It'seems en error in another script. [:^)]

 Thanks

 

k , works fine , thank you guys :)

The setup is Pegasus sending mail using SMTP and START TLS, and Mercury S receiving it. Sender and receiver are on different different ISPs. Most of the time this works perfectly.

Once in a while, the sender's internet connection becomes heavily congested (too many YouTube users) and 'ping' response times from the sender PC to its nearest ISP router are 3000 milliseconds or more (normally it's 3-5 milliseconds).

When this kind of congestion is happening, Mercury S consistently times out on receiving. TCP timeout for Pegasus and Mercury S is set to 90 seconds, and yet the TCP log for Mercury S shows an error after only 6 seconds. If I disable START TLS on the sender (Pegasus), email flows without error, so there seems to be a problem with how the Mercury SSL code handles timeouts.

Below are the first three lines and the tail ends of the Mercury and Pegasus Session logs. The first few lines show that the sender and receiver clocks are in synch, so the times at the tail end are meaningful. You can see Mercury gave up way before 90 seconds had elapsed, and that some packets were taking about 3 seconds to travel between sender and receiver (the '354 OK' line was received by Pegasus 3 seconds after it was sent) . Actual IP addresses have been changed.

Mercury S log:

15:47:47.282: Connection from 999.999.210.200, Wed Aug 05 15:47:47 2009<lf>
15:47:47.282: << 220-mail.receiver.com ESMTP server ready.<cr><lf>220-Use of this server for unauthorised relaying of mail is forbidden.<cr><lf>
15:47:50.625: >> EHLO cedar.sender.com<cr><lf>

[stuff deleted]

15:48:08.511: << 235 Authentication successful.<cr><lf>
15:48:10.235: >> MAIL FROM:<subelman@sender.com.com><cr><lf>
15:48:10.235: << 250 Sender OK - send RCPTs.<cr><lf>
15:48:14.559: >> RCPT TO:<subelman@receiver.com><cr><lf>
15:48:14.559: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
15:48:17.125: >> DATA<cr><lf>
15:48:17.125: << 354 OK, send data, end with CRLF.CRLF<cr><lf>
15:48:23.083: 18: SSL read error -25 (locus 0, type 0, code 0, 'Timeout on read (select()) after 1 secon')
15:48:24.514: --- Connection closed normally at Wed Aug 05 15:48:24 2009. ---
15:48:24.514:

Pegasus Log:

15:47:47.421 [*] Connection established to 000.000.145.173
15:47:50.781 >> 0045 220-mail.receiver.com ESMTP server ready.\0D\0A
15:47:50.781 >> 0072 220-Use of this server for unauthorised relaying of mail is forbidden.\0D\0A
15:47:50.781 << 0023 EHLO cedar.sender.com\0D\0A

[Stuff deleted]

 15:48:10.375 >> 0032 235 Authentication successful.\0D\0A
15:48:10.375 << 0037 MAIL FROM:<subelman@sender.com>\0D\0A
15:48:14.703 >> 0029 250 Sender OK - send RCPTs.\0D\0A
15:48:14.703 << 0031 RCPT TO:<subelman@receiver.com>\0D\0A
15:48:17.265 >> 0039 250 Recipient OK - send RCPT or DATA.\0D\0A
15:48:17.265 << 0006 DATA\0D\0A
15:48:20.656 >> 0039 354 OK, send data, end with CRLF.CRLF\0D\0A
15:48:20.656 << 0052 From: "Eduardo Subelman" <subelman@sender.com>\0D\0A
15:48:20.656 << 0052 Organization: No organization at all..\0D\0A
  [about 500 more lines of email body deleted from here]
15:48:20.656 << 0020 <div align="left">\0D\0A
15:48:20.656 << 0014 &nbsp;</div>\0D\0A
15:48:20.656 << 0009 </body>\0D\0A
15:48:20.656 << 0009 </html>\0D\0A
15:48:20.656 << 0003 .\0D\0A
15:48:26.187 24: SSL flush error -42 (locus 0, type 0, code 10054, 'WSAECONNRESET: Connection was reset by the remote host executing a close')
15:48:26.187 18: SSL read error -42 (locus 0, type 0, code 10054, 'WSAECONNRESET: Connection was reset by the remote host executing a close')
15:48:28.406 << 0006 QUIT\0D\0A
15:48:28.406 19: SSL write error -42 (locus 0, type 0, code 10054, 'WSAECONNRESET: Connection was reset by the remote host executing a close')