Clearing the queue is the proper thing to do in a case like this. You can check the removed files in Notepad to see if there is any real message or just looping notifictions If there is any real message just put the QDF/QCF pair back into the queue folder. Then just delete the rest.

It's impossible to say what started the loop from just seeing that notification. If you check the MercuryE log you could perhaps find out what started it there.

/Rolf 

The username and password from the session are just Base64 encoded, not encrypted, so anyone using a Base64 decoder can read it...

Good to hear it worked with msendto.exe! 

/Rolf 

A session log will show you why - my guess is that your dynamic IP is refused, and you have to use MercuryC to relay via AT&T

An autoreply generated by Mercury should have a subject starting with [Autoreply], so this is presumably something else. Furthermore autoreplies are local to each mailbox, postmaster is not involved. Check the core log for clues, and switch on session logging briefly in MercuryE/MercuryC to find out what is happening.

/Rolf 

Han is correct. This part differs Mercury from some other products, that in my view have misunderstood the negative impact a direct association with a maildrop and just one e-mail address. Defining the maildrops apart from the addresses has the following benefits out of a server standpoint:

• makes it much harder to try and harvest maildrop/password pairs as the maildrop name isn't public
• eases the teaching that a maildrop is a "box" that can be associated with more than just one address
• is syntactically correct in correlation to most e-mail clients, that state Username as the equivalent for a maildrop, and hold separate settings for name and address.

The only thing I think is missing, is, that since the association with an alias and a maildrop is possible, it would have been nice to, via a setting, allow or disallow authentication in all modules between aliases and their direct associated maildrop passwords - as well as a setting enforcing strong maildrop passwords. Hopefully that will come true some day for both NetWare, Windows integrated and stand alone operations of Mercury.

Hello all,

Has any one successfully integrated Round Cubes plug-in managesieve into Mercury mail?

Is there a stand along windows server and/or script  I can use if it is not possible ?

Thanks for your time.

I sent numerous test messages and examined the logs and the headers without finding anything. Then I fell back on that old standby and reinstalled Mercury.

It all seems to be working fine now, whatever the problem was.

 Thanks Rolf for your suggestions, at least I understand a bit more about how it is supposed to work now.

Mercury in local mode can be started at Windows Server 2008 (32 bit tested) with the following variants.

A) Mercury as its own service with approved account
B) As a "Scheduled Task" after the System start
C) With NT Wrapper (Local system for Service, Login from Wrapper configuration, Best for Server 2003)

The GUI is in Server 2008 available through the Windows message "Interactive Services" or by Login with the special account, console 0 - see other posts in this forum.

Automatic login via the Netware client works no longer with Windows 2008, unfortunately also not with NT Wrapper,
although the Netware login is possible within the Interactive Service screen when accessing appropriate files.

Anyone who operates a Netware server, can use the tool Autologon from Sysinternals with a special Mercury user account.
This only works as expected if in the Netware client options in "Advanced Login" the Novell login is disabled .
The Mercury loader can be started with a scheduled task for the account after the Autologon.

Regards, Torsten

You should complete the domains section as well. IP addresses need to be enclosed in brackets, you should enter the hostname of the server, and if you have other workstations in your LAN you should enter your local IP as well. You can call your server "localhost" but I would recommend against it as it will only confuse you. So:

mail: mail
mail: drewclardy.info
mail: [76.184.46.42]
mail: [192.168.1.100]

And you should at least turn on strict local relaying restrictions in MercuryS.

/Rolf 

 

Copy and Move actions in filters are for local users only. For external users you need to use Forward.

/Rolf

> 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