[quote user="kannanEswar"]

Hi PaulW,

 Thanks for the reply.

1. When i am sending mail from program to exchange server (smtp.ihostexchange.net), working fine and email delivered successfully.[/quote]

ihostexchange.net appears to be a hosted Exchange service and not a server hosted on your network - is that correct? 

[quote]My need is i want to send emails to users from C# program using mercury service instead of exchange server.[/quote]

Are these users local (on the same network as the server) or remote (on the internet)?

If local - you will have to maintain accounts for them on the server, but how are they going to collect them from Mercury? POP3 ? IMAP ?

If remote - you can either open your router ports up so they can collect like local users above, or use MercuryC with a relay server to deliver them over the internet.  (The second option is probably easier to set up and requires less maintenance.)

[quote]2.  I have setup the user with name "websupport". And also predefined user admin is present there.

             From email address: support@mydomain.com

             To email address:  kannan@mydomain.com [/quote]

You are using 2 local names (support & kannan) but you have defined completely different names (websupport & admin).  What's going on?  Is mydomain.com the domain name in "local domains" section of the configuration?  If so, each and every name you use must be set up as a local user.

On a general point it is very difficult to help you if you obscure the actual user and domain information and don't explain the configuration you are using.  I suggest you use the extensive help that is provided in the program and read the relevant sections of the manual you will find in the Mercury\docs sub-directory.  Then if there are any specific items that are not clear, ask a question about that item.  Configuring and maintaining a mailserver for a non-standard installation can be a challenging and time-consuming project, and requires complete understanding of all the elements of email handing and network architecture.

Thanks for the suggestions Olaf.

 We were not using SSL for our IMAP connections to the server and they are on port 143.  I will investigate the SPA settings in Outlook to see what they are.  

I did discover that outlook appears to default to checking for emails only once ever half hour. 

Does not really say much about anything :-(

Thx

Konrad

Yes, I heard about that... Thx

Mercury is actually by default already set up for normal usage. During setup you get information about MercuryE (direct SMTP delivery) and MercuryC (using a relay server) and can choose what is best for you. The only thing you really need to adjust is the local domains information. If the information about this in the installation program isn't sufficient you can get more in Mercury help or the enclosed PDF manual. If needed you can install some of the included antispam and antivirus addons, or wait to decide about this later.

There are of course a number of things outside of Mercury that need to be set up as well. You need to make sure no firewall is blocking access, forward the relevant ports from the Internet router, and exclude all Mercury directories from realtime virus scanning.

If you after doing all that still have problems I would suggest posting the contents of your mercury.ini file here so we can review the settings.

Heard this "should be available in v5" a lot ;-). Can't wait to get it... Any word on the time line/roadmap?

Thx

Konrad

Been working with MS Exchange for a long time now - want to look for alternatives for home as well as for enterprise. And for being a very happy user of Pegasus Mail back in the times, I am looking at Mercury.

But... I want to run it on a *NIX server or Windows 2012 R2 server... and reading this thread scares me a bit. When is Mercury 4.7 (EDIT: sorry...i mean ver.5) expected to be available? And will it support Win2012 R2 fully?

Best regards, Lars. 

All MIME parts in a message (HTML text, plain text, attachments or whatever) are stored together by Mercury and extracted when needed. I'm not sure how Thunderbird handles attachments here though. It seems there might be some issues around, like those described here: 

Thanks for the suggestion. I had a similar thought and emptied my entire inbox into some archival folders I have set up on the IMAP server. I now have new emails coming into the in-box (about a dozen in each of two different accounts), but still have the same trouble with headers not being synchronized with the corresponding messages. Repair folder always seems to fix the problem, but it's only temporary. I left a message on a Thunderbird forum asking about the same problem (https://getsatisfaction.com/mozilla_messaging/topics/mapping_between_message_headers_and_messages_is_corrupt?rfm=1), but it doesn't look like there is much activity on that site. Do you know of a better community forum for Thunderbird help?

Thanks so much for your help. 

-- Opticswalt 

[quote user="Greenman"]Resetting/editing pconfig files is a pita because I have to copy them to a 32bit machine, make the changes then copy them back to the 64bit server.[/quote]

There's an easier way - install DOSbox on the 64-bit machine and then you can run pconfig.

See this thread

[quote user="bollero"]Ok, when started mercury - one tip - can use only one click, this will open transfer module. If double click, two mercury will appear and error message will see. Frank
[/quote]

Frank,  I am not sure I understand what your original problem was, or if you have fixed it.  Post again if there is still an issue.

It is a good tip not to have more than one version of Mercury running from the same directory!

That's exactly my setup! But I think what you meant was to put "loader" instead of "Mercury" in the startup folder. This way at least Mercury would re-launch after a crash. 

In a way I am glad that I am not the only one having this problem. I am running Mercury on a Win2k3 server and I am having problems with crashes and corrupted IMAP folders that I believe are due to:

1. concurrent IMAP connections from Android and Outlook.

2. large IMAP folder size (>1.5GB). The large folders are usually "Sent/Sent Messages/Sent Items" and "Trash/Deleted Items/Deleted Messages", which make matter worse because they are constantly in use.

Android and iOS devices do not terminate IMAP connections properly, which compounded the problem as more and more of these devices are now connecting to Mercury. Add this to the time it takes to handle large folder and it stresses Mercury. When Mercury is stressed, just about anything would push it over and crash it. And it seems that when it crashes too many times consecutively, it moves everything in the queue to a sub-folder, thinking that something in the queue could be causing the crashes, by then there would have been a lot of zero size files in the queue.

For me at least, toggling the "affinity" to get it to run on two CPUs did not improve performance, but unchecking the "Enable support for SSL/TLS secure connections" checkbox did help slightly.

Just a note though: the largest folder size for me is 4GB instead of 2GB, and mine have both IMAP and POP enabled. 

regards,

Philip 

I have run into apps that weren't designed to recognize and utilize multiple cores.  Back when dual cores first came out I wanted to force some apps to run on the 2nd processor.  Changing the affinity worked, as you have discovered, but it is not sticky.  I found a utility that provided the capability of triggering an app with a specified processor affinity.   Unfortunately I don't remember what the utility was called.  I thought I might have it in my downloads folder but I don't.  I just did a quick web search and it appears that Win7 has the capability via the command line.  See here:

[quote user="chriscw"]We do run Spamhalter on the server but not clamwall I could never work out how to get it to work.  I guess that now we have a few Outlook users Ii maybe should have another go.[/quote]

For me Clamwall is a 'must have' first line protection for incoming mail.  I use some of the Sanesecurity signatures as well to catch spam as well as viruses.

Post on these forums if you are still having problems setting it up - the windows binaries from ClamAV are now very stable.

Have a look at this thread and see if one of the relaying options might work in your case:

If a message is CC'd to you by the sender the reply should go to the sender. If however a message is forwarded to you by one of the original recipients, the sender in that case is that recipient, not the original sender.

It's the email client that sets the reply-to header and it could be that different clients handle it in different ways. Mercury will deliver according to the SMTP envelope provided by the email client.

OK thank you for your informations!

Regards, Franz

To bypass the connection limit you will need to use SMTP, POP3 and IMAP to connect to the server. The integrated PMail/Mercury setup requires file sharing access.  The "force through server" option will write local messages to the Mercury queue rather than directly to the recipient mailbox directory.

Also, you can turn on session logging in MercP and examine the entire conversation to see exactly what is being asked for by the client and what is provided by the server.

There are some standard template files included with Mercury, for instance failure.mer. So for example, try replacing "Content-type: Text/plain; charset=US-ASCII" with "Content-type: Text/plain; charset=utf-8".