It seems to me that NTWrapper is no longer available.
The developer-site is down, and I was not able to find this software.

For those who have the same problem, and for some reason can 't buy a licence, here is another solution that works with Windows 7 64 Bit.

• Download XYNTService.exe
  I found a copy here ... http://www.bitwiseim.com/wiki/index.php?title=Trick:_BitWise_Routing_Server_as_a_Windows_Service
• Follow the manual on the following site ... http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=719&av=49654
  

Had the same problem with Pegasus and Thunderbird both configured that MercuryI only supports trays (not like directories on filessytsem capable holding directories and files: folders holding mails and subfolders). Created them with Pegasus and all seemed good. closed Pegasus and opened Thunderbird. All seemed good too. Next day opened Pegasus @work and all trays have been at root.

OK ... tried deleting the trays - which resulted in .

Created a hierarchie of trays and folders some days later and it seems to be stable. May be your moving of trays resulted in same stability (didn't try that, so don't know if it had worked in my case)?!

May be it is an initial problem on new IMAP-Mailboxes or first time creating a tray with subtrays? Just my suggestions ...

bye   Olaf

Dear David,

[quote user="David Harris"]Looking at the code, there is definitely message-id generation going on in Pegasus Mail,[/quote]

That's correct (but not the point in discussion about Mercury/32 and creating MIDs)  ...

[quote]although for some reason it's controlled by the setting of an internal system flag, and I can't see clearly what the default value of that flag would be. There also doesn't seem to be anywhere in the UI to change it, although it *appears* that it should always be turned on by default.[/quote]

... if you want Pegasus to create a MID. For some reasons we don't Pegasus want to do it (see other posting in same thread).

The default value of "general system flags" is 0. Via UI you may only change it to 1 by activating session logging. I suppose default is 0, because otherwise SYSLOG.PM will increase endless.

[quote]Suggest to him (not as a solution, just as a curiosity) that he look in his PMAIL.INI file and find the entry called "General system flags": it can have the values 0, 1, 2, or 3. If it's 3, tell him to set it to 1. If it's 2, tell him to set it to 0. This will tell the program to generate message IDs. On my system, it has the value "1", which turns on system message logging. If it was a value other than 1 or 0, could you let me know?[/quote]

I know all about that flag and it was 2 - as wanted!!! But that's not the point in that thread and I think, there is no need for you to change anything on that in the code of Pegasus. Works fine and as designed! The changes should be done in Mercury/32 for the case, that no MID is in a mail from a local user to a local user.

[quote]Should definitely be working, though.[/quote]

It does ... as designed by you. [:D]

@Thomas

[quote user="Thomas R. Stephenson"]I've set the flags to 1 and it's creating a message-id for mail to local users when mail is sent via MercuryS using the built-in mailer.  Here's the raw view as received.[/quote]

I know ... but we don't want Pegasus to create a MID and some mailclients (even on smartphones) used here don't do it too. Mercury/NLM, which I used until some weeks ago, did create MIDs for the problematic case (local to local), but Mercury/32 doesn't do that any more. That's my point and I hope David is willing to change that for next version of Mercury (obviously 4.74).

Cheers

     Olaf

Hallo Thomas

[quote user="Thomas R. Stephenson"]Mercury maiser creates a new message, it does not just bounce a message.  It removes all addresses in the message body to ensure that the list mail only goes to the list members.  The To: field is being corrected to the actual setting of the list.  These addresses are made comments in the the message.  This is all by design.[/quote]

Hmm ... reads like having a designdiscussion. I'm on many mailinglists and some of them administered by me (i.e. the german Mailinglist for Pegasus mail), most of them on majordomo and mailman ... and even had that lists on Mercury/NLM before. None of them behaves like that ... it is very (!!!) unusual.

I've built some mailutilities with perl, PHP (long before they had modules or libraries for that). I used it with Mercury/NLM simply placing ready to send mails as files in the queuedirectory. All you need to do is to add a envelope with mailadresses for sender and recepient(s). In case of maiser you may wish to add headers like sender, errors-to, reply-to, may be some list-headers, change return-path and add some received-lines. Thats all. The other headers don't need to be touched.The recepients are in envelope - nowwhere else, that's all you need to enshure only listmenbers get the mail. So - why does mercury touch and manipulate the other headers? There is no reason at all!

[quote]If you really need to maintain the addresses in the original body of the message  then use a real Mercury account and a FORWARD file in that account to bounce the mail.[/quote]

For shure I'm not the only maintainer who needs this information and most times he may not have access to my Mercury/32. And I don't want to have thousands of mails forwarded to have probably that one I have to maintain. It's not my private playground at home - it's the mailserver of a faculty. I was willing to buy a big license of Mercury/32 ... but the more bugs or unusual behavior I find while testing the more I get in doubt.

Sorry, but there is a simple rule in mailhandling: never touch headers that you don't realy need to touch!

bye   Olaf

Thanks for the help with login details. I forgot!

I am sure You have right about the bracket and that sort of things, But I can tell You, that without having changing anything, I can now send email to what ever address I will.

I dont understand what have happend, but now everything is working. also from magento!?

OK.

Time to move... 

Thanks.

Hi Fulwoodblade,

We experienced problems with Mercury after reduction of the mail retrieving frequency of Mercury X. Mercury is running on a Win Server 2003 R2 (32 bit) with 4 GB RAM. When setting the frequence to "0" (means permanently retrieving) Mercury crashes from time to time (at least once per week) allthough the windows process was still running. Also with deactivated Mercury X, where the Mercury C and D modules use their own timer, Mercury crashes from time to time. It seems Mercury becomes instable when the poll frequence is set lower than the TCP timeout.

Now I have reactivated Mercury X and have set the retrieving intervall to 1 minute with a 30 second TCP timeout. Now it works stable again.

 Brgds

Joerg

Edit: Now, appr. half a hour later our Mercury crashed again. There must be another event which causes to the Mercury crash. Please refer to my connected post:

http://community.pmail.com/forums/thread/31830.aspx

You're right. MSE don't really notify you if the website your visiting is infected or not. And that we still need another software for that. I hope there's a free software for that since I'm on a tight budget as of now. =)

While using POP3 (I asume you do) choose your POP3 definition.

On GENERAL you will see a button with "Delete messages from server if sucessfully received" (or something like that - translated from german). Deselect that button.

bye   Olaf

If your problem is, that you will read the emails without Pegasus Mail on your system, than you can link .CNR and .CNB to any software, that is able to read EML-Files.
For reasons of security we did not link new mail files (.CNM). It is however just as possible.

We use this feature to search by help of Windows explorer in Pegasus Mail systemwide folders and noticeboards. 

For Outlook Express or Windows Mail clients it is necesseary to add some registry keys in the classes root. It is tested with Windows 2000 up to Windows 7 x64 (W7 must patched to Vista WinMail).

I put the scripts there   

Torsten

Danke vielmals, Olaf! - and to Han also, of course! That's most helpful and makes me feel somewhat more comfortable about deployment.

> I mark this thread as finished although mail transmission without encryption is not very secure.

Mail transmission with encryption just between client and server does not help all that much anyway sense it's been traveling over the internet unencrypted.  ;-) To make e-mail secure the content must be encrypted.

If the settings file MERCURY.INI has been damaged it can usually be restored from the backup copies in MERCURY.BAK or MERCURY.BK2 (all in the main Mercury directory).

/Rolf 

I'm trying to write a script that adds IP addresses to the MercuryS Access Control List by appending them to the file mercurys.acl.  However, Mercury seems to keep a copy of that file in memory and flushes it out when it exits, overwriting my updates. I could shut down Mercury, update mercuryS.acl and restart Mercury but I'd rather not. Is there any way for an external program to notify a running Mercury that the mercurys.acl file has been changed?

Alternatively, since Mercury exits and restarts nightly (using loader.exe), is there any way to have loader.exe run a script before it restarts Mercury? That would allow me to update the ACL when mercury is being bounced.

I use a custom subscription account for Mercury. However, I thought the default address was maiser@ not postmaster@. To achieve this I did the following:

“Drive:\Mercury\mercury.ini” must be edited so that the [Maiser] header appears as follows:

[Maiser]
Maiser:          <Account-name>   # '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

Where the string ‘maiser’ appears in the *.mer files in the “C:\Mercury” folder, ‘maiser’ must be replaced with ‘<Account-name>’.

Edit your templates accordingly.

That's irritating for my clients - isn't it? Should be fixed! Most people are not IT-specialists. They need simple, clear answers - even by maiser!

Mercury/NLM didn't have that bug! Errormails have been FROM maiser and with informative text.

bye   Olaf

Hallo Thomas,

thanks for your answer! Depreciated or not ... would be nice if Mercury would support direct SSL with all modules. Have to test a lot if there is any mailreader especially on notebooks (and even Smartphones) of my clients, that need direct SSL. No ... you don't want a discussion with a professor about changing his mailreader or even updating the existing one. :-(

The desktops are not that problem ... they have Pegasus. But notebooks and especially private notebooks are not under my control. I know there's a wide range of mailreaders and even differnet versions of them (Thunderbird, Seamonkey, Outlook, Outlook Express, Opera ...). OK ... I'll kick the one client with Outlook Express ... isn't even capable opening WINMAIL.DAT ;-)

STunnel ... had some tests in context with other software a while ago ... and massive problems. Don't want that hack again.

bye   Olaf

 P.S. A hint in help and/or documentation, which modules are capable which encrytions, would be nice!

Hi Olaf,

Thanks for your reply. Without the astersisk wildcard in front of the "@" it works. Great

Brgds

Joerg

> Each copy of Mercury sends its own mail directly with MercuryE.
>
> This all works perfectly well and is easy to maintain.

Personally I would use MercuryC at the branch offices to deliver all mail to the main site.  Otherwise the main site becomes the gateway host sending/receiving all mail from the domain, including the branch offices.  I do not know if this will fix the problem but since one site gets all the mail and local mail never leaves the local company LANs then it may help.  

I do not normally setup branch offices like this, I normally have all users mail delivered to local mailboxes and use Domain mailboxes to collect all the mail from the users at the branch sites.  I then use MecuryD to pull the mail for the branch offices.   

One real advantage to this is that the branch offices do not have their domain registered in the DNA since they are not getting anything directly from the internet.  You have one IP address and host name seen by the outside word.

YMMV ;-)

[quote user="Thomas R. Stephenson"]

Did not like my answer???  Why do you want to get us to answer again,

[/quote]

I did not dislike your answer; simply put, as I'm a novice, I did not understand that your answer implicitly said that my solution was not advisable...

[quote user="Thomas R. Stephenson"]

your method could work but it's not something I would do nor can I test it.

[/quote]

This is an answer that - as novice - I can understand.

Thank you and sorry for having bothered.

Best regards

Filippo