oh, that was easy, Thanks!

 

 

Reasonable questions all, but I don't have old Mercury logs - I only turned on that particular logging when it became an issue. I've checked Received headers in a current message and one received six months ago, and Mercury is declaring v4.74 in both.

It's possible that it's the level of problem that has changed. I've had the odd message before come to me, but I'm postmaster, so I just assumed an unknown problem and forwarded it. Now it's probably running at 20% or more of my wife's messages (haven't counted properly).

Another (possibly related) problem we have is spurious suppression of duplicate messages by Mercury. Since, in reality, we're both using the same mailbox on a given ISP, and the Envelope-to: headers are distinguishing which of us should get the mail, then if, say, we're both on the same mailing list, Mercury will suppress one copy of the message, which is infuriating, because you cannot easily work out what you've missed, or even which user missed it. At least if there were an option to turn duplicate suppression off, or even redirect duplicates for the postmaster's attention, there would be some control. I'm aware that the "Look only in these headers" setting should prevent this, but it does not appear to do so. I haven't even found a log where I can check what duplicates were suppressed. In at least one case, I'm having to use a rule in Pegasus Mail to autoforward the messages to the other account(s) and thus work around the issue, but I can only do that for mailing lists that I know are affected. I've also tried arranging for us to use different ISPs when registering on such lists, but not necessarily with great success. I'm not clear that I wouldn't even get spurious suppression sometimes if a friend included both of us in the addressees for the same message.

I'll try removing X-Envelope-to from the rules, because it seems to be irrelevant. As you say, it shouldn't make any difference, but who knows?

Happy to pass on logs and headers - should I PM you?

To state the obvious, I also have logs for messages that were delivered, including one where "duplicate" messages (from a Yahoo Group to which we both belong) were delivered properly to each of us, which is the result required. No real idea why it worked in that case and not in others.

Regards

OK Thanks

[quote user="Steen"]

Set up:
Novell 6.5sp8 server (not going to move to a later version if I can avoid it, nor going to setup a windows server instead).
Mercury 1.48nlm running all module but MercuryC (as I can't use smtp-relay any more... unless somebody knows of a free reliable one)

Usually I use a laptop win 8.1 as working machine but I do have more laptops than this. Bascially if any other runs, my win8.1 is also running. Pegasus running from all my laptops in server mode when I am at home, in local when I am out.

Now for my idea: Run Mercury/32 the E module alone in order to be able to send mails with out any relay from my win 8.1. Can this be done? What is needed? Any downsides that will backfire?[/quote]

This does work and I use it occasionally.  You need to load both MercuryE and MercuryS in your Mercury/32 version to enable it to relay from Pegasus.

[quote]I have no idea if this is possible, but I guess I should be able to use Pegasus to send to the MercuryE/32 and then that should be able to handle my mails (it is really sad that there was never an E-module to the nlm because then I would never have had to consider all of this - anybody knows a free mailer for Novell 6.5sp8 with Apache, please let me know... I am in contact with the dutch guy that did one for Novell 5.1 running the netscape webserver, to see if that can be brought to work)[/quote]

I can't help with Netware these days as my last Novell installation went about 5 years ago  :(

Ok think i am getting the hang of this. Thanks for your help Olaf

Thanks! That is what I had expected -> put everything under c:

directly as applications are still allowed to write into such folders.

For me this would mean that I have to copy my existing Mercury

installation from c:\programme\mercury to c:\mercury and therefor I

guess that I need to modify some configuration files due to the path

changes. I hope that this is possible at all!

With "virtualization" I meant the file virtualization technology from UAC like it is described here:

https://decibel.ni.com/content/groups/windows-7/blog/2009/10/02/uac-virtualization-and-how-it-affects-your-installers

 

Konrad

Does username and/or password have some special characters (non 7bit)?

bye   Olaf

 

Hi,

since I'm mainly using the POP3 client to poll my mailboxes: I noticed some strange behaviour when editing the MercuryD config.

It sometimes happens whenever the MercuryD configuration is edited during a poll cycle -

Either, the list of mailboxes is incomplete (i.e. some are missing in the config window), and when the incomplete list is saved, the MercuryD.dat file is crashed/crippled/incomplete, or

While editing the list during a poll cycle, the polling process stops just at any random mailbox, and then halts until the config editor window is closed again.

This means: One can either cripple the mailbox configuration (i.e. loose configured POP3 mailboxes), or block the POP3 polling entirely until the config editor windows are all closed.

Anybody else seen tha same behaviour ? If so, it's perhaps worth a bug report ?

Kind Regards,
Andy

 

Hi,

could it be possible that there is a length restriction of the username field in the "Edit POP3 Mailbox definition" popup ?

Whenever I enter a string (username) longer than 47 characters, it gets cut off after the 47th char !
This invalidates my username string, and the mail provider just doesn't like it anymore ... :-(

You might say: "Why's this dude using usernames with such a insane length?"
Quite easy: I am using POPFILE as mail proxy to pull mail from for POP3 mailboxes, so I need to redirect the Mercury POP3 client logins to popfile running on localhost, and pass all required stuff in the username field, like so:

POP3 Host: 127.0.0.1
Username: pop3.provider.com:Mailbox.Name;maildomain.com:ssl

As you can easily see, this adds up to a pretty long string. It works for almost all of my mailboxes, but some are longer than 47 chars, so I am lost. In the very old versions of Mercury, the MercuryD.dat config file was plaintext ASCII, so I could modify it. Nowadays, this file is encrypted (which is good to keep passwords secret), and cannot be edited anymore, so I don't see any way of working around that issue.

Is the restriction only in the GUI window when editing the mailbox definition, or a overall restriction in MercuryD ?

Thanks !

Kind Regards,
Andy

 

Thx, I will work through the provided links.

The new TCP/IP module could explain the network problems and therefor the crashes and it fits to my observation that this network issues did not happen before the installing the new beta.

Can you provide the "special version of mercury.exe" so that I can send the logs after the next crash?

 

Konrad

Okay, I will unload MercuryC... and using Mercury/32... well, that means I will have to run an extra machine which I really have no idea to do. Maybe I can be forced to, but I will do a lot not to do it. One of the things I need to check is if there was a SMTP-server in the old Border Manager 3.0 (I can't find the licence to 3.5 although we had it) and that it can run on Netware 6.5 - a co advantage will be that I may run my own VPN which is handy when it comes to going to China etc. The downside is that I think I have to change my NAT and so on...

Other alternatives is to have all my stuff hosted outside or change to a Novell Linux server... but I am really not in any mood to look into a another system.

 

But still if somebody knows a way to move port and to ad user and password to a MercuryC.nlm let me know... 

Rolf

 

This sounds just the ticket. I'll look forward to buying the new release. Thanks for the response.

 

Duncan

Does anyone know how "secret" the password used to encrypt the private key that Mercury uses in it's cryptlib interface is?  I wrote a C# program to import an OpenSSL certificate/private key into the PKCS #15 file that cryptlib uses that I think others might find of use.  But, since it's un-obfuscated C#, and such a small program, it's much easier to discover the private key used from it than by looking at Mercury, a much larger C/C++ program.

I had previously been using stunnel which worked well for many years; but, an increasing amount of mail was incorrectly being marked as possible spam by SpamAssassin.  Something easily resolved by having clients connect directly to Mercury and whitelisting certain IP addresses.  I use a self-signed certificate created in OpenSSL and didn't want to distribute a new one, thus the reason for creating the import program.

You know you have to start the GUI in addition to the service? Mercury installed as service won't start the GUI.

bye    Olaf

 

Hi,

Since I have arranged an additional content filter (content control) in Mercury (v4.74), which is forwarding particular incoming e-mails to special mobile devices, some temp files ($$$) remain in the Mercury mail outbox queue. These files have to be removed manually from time to time.

Why Mercury does not remove them by itself?

Cheers

Joerg

[quote user="Rolf Lindby"]To allow for local users connecting from the Internet and authenticating use operation D instead of H in the rule.[/quote]

*Facepalm* I could not see for looking. Thanks!

[quote user="Rolf Lindby"]Mercury 4.74 does not use OpenSSL, so it's not at risk. In the upcoming v. 4.80 there will be a corrected version of OpenSSL.[/quote]I know but i must use SSL. Without SSL get i no connection to my mail-provider and with SSL have I annoying crashes of Mercury32.

 

[quote user="Konrad Hammerer"]If so, make sure to use the latest stunnel v5.01 as the prior versions are affected as well![/quote]Jep. Installed, old keys revoked and new keys created.

 

[quote user="bfluet"]

Following up to report my experience with adding Sanesecurity signatures including the Foxhole signatures.  They dramatically increase the number of quarantined message but a significant percentage of them have already been tagged as Spam by my domain host so would have been detected by existing spam filters.  I am still receiving messages containing a .scr file inside of an attached .zip so my original problem remains.  Some of these messages appear to come from a financial institution and are genuine looking enough that I hesitate to tell POPFile they are spam for fear of increasing the possibility of false positives.  I have considered creating a ZIP user and diverting all messages containing .zip attachments to it so I could review them messages before forwarding to the intended user but this does not seem very practical and would certainly cause delays. 

I remain open to new suggestions.

[/quote]

If you have executables inside zip files which are being missed by foxhole_all then please report them as errors to the relevant address found in Sanesecurity.

Thanks for you help, much appreciated.

Ahha, scratch the above I think I have found it, the new firewall has a slightly odd setting method....