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:

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')

Yeah, I put "admin" and it worked. As the next filter, I also told it: "delete the message" because I didn't want it to try to resolve the domains and relay it.

That should help me a lot.

Thanks,

421-4.7.0 [68.84.251.204] Our system has detected an unusual amount of<cr><lf>
15:46:41.741: >> 421-4.7.0 unsolicited mail originating from your IP address. To protect our<cr><lf>
15:46:41.741: >> 421-4.7.0 users from spam, mail sent from your IP address has been temporarily<cr><lf>
15:46:41.741: >> 421-4.7.0 blocked. Please visit >
15:46:41.741: >> 421 4.7.0 to review our Bulk Email Senders Guidelines. 16si20569308pzk.52<cr><lf>

 Ah ha!  So i'm guessing gmail is blocking my email thinking it's spam. 

You got it and you really need to check out your IP address on blacklists as well. I just did a check and it appears that your IP address is on a DUL blacklist so you'll never be able to use MercuryE successfully.  You should convert to MercuryC and send through your ISPs SMTP host.  You are also on the FIVETEN blacklists but nobody same ever would use any of the FIVETEN blacklists to block. ;-)

IVETENWEBFORM		LISTED	miscellaneous address blocks that have sent spam here Return codes were: 127.0.0.2	86400	109
SORBS-DUHL		LISTED	Dynamic IP Addresses See: Detail Return codes were: 127.0.0.10	3599	375
Spamhaus-ZEN		LISTED	Detail Return codes were: 127.0.0.10	900	391

And i'm guessing i cant receive email because of what my MX servers are set as?

This needs to be fixed, the MX host should be pointing to your host mileka.com.  If you remove them entirely it will work as well.  That said I cannot even ping mileka.com or 68.84.251.204 so there is some major problem with connecting to you host as well.

1. See main help index ("Using the Mercury/32 loader utility") for a detailed explaination

2. Don't know, sorry.

3. I only know the -P parameter in order to specify the physical processor to use for Mercury.

Sven

Thank you for the tip Thomas.

I did not think of going the policy route. I will dust off my Pascal routinges and set to work. Because all of the messages come from the same source and should be similarly structured, it should be a relatively straightforward operation.

If the backup is at cause, you should probably see a file conflict occur. Filemon from sysinternals will show this for you.

Split the logs automatically into months in Mercury.ini with ~ 

like: logfile: D:\mail\logs\sys~y~m.log # Traffic logging file

Makes it much easier to maintain and purge old stuff.

Thanks A Million,

My server board went Kaput today, Foxconn G31 Micro for the 2nd time,

I am ordering an Intel G41, I hope it works better. Untill then, See you later,

Again, Thanks for the help.. I look forward to working with Mercury.

The original idea with an alias should work as well. The alias should be:

alias - the sender address you use

real address - your local mailbox name (without any domain part) 

This will, however, make it impossible to send any messages to the real external "sender address" through the Mercury server, they will all be redirected to your local mailbox. 

/Rolf 

The larger the inbox the more impact there is on performance. 4.6x and later are much faster in regards to all protocols, but especially from 4.0 to 4.6 there are so many stability fixes and performance benfits that there is every point in upgrading and getting a license.

Ok, thanks very much Rolf.  I'll revert to clients tech support with your findings.

Ron

Peter,

As instructed, I changed the "Mercury.ini" entry to "# MercuryX" so that the module doesn't load when I start M/32, but how does that help..? I need the scheduler to be working.

So, I enabled the MercuryX module and restart M/32... Guess what..? Nothing works again.

M/32 is not loading in "Off-line mode". It is already in "On-line mode", so I selected "Off-line" and On-line", but it makes no difference.

I'm going back to v4.62... Sorry.

Regards. SJS.