Good evening

Thank you very much for your fast answer & your description of steps I can do! I'll go an test it…

Kind regards,
Thomas

[quote user="Rolf Lindby"]

If you block all incoming messages with <> as sender you may block more than you intend to. Delivery failure messages from SMTP servers can have that as well.

/Rolf 

[/quote]

Thanx for that heads-up.
At present I am moving the messages to a black-hole mailbox that I monitor.
I'll keep an eye open for that sort of message before I institute "killfile" :)

Yes, I did. The issue has been resolved. Thanks

Terry

Go to your mercury installation directory and delete the file 'm32pass.dat'.  (Probably best with Mercury not running.)

DNS MX records should contain a host name - that is a name you have set up with an 'A' record pointing to an IP address.

[quote user="madbuffalo"]Yes they are correct.  I have used up to three actions on the same line before. i.e. (BSL)[/quote]

I've just done some tests, and I'm not seeing that.  You get a log entry anyway if Mercury blocks and send a response - you don't get an extra one with an 'L' in the final position.  I get exactly the same entries with 'R', 'RL', 'R-L' or 'RSL'

[quote]As for the 'N', I have never used it--so I am not sure if the functionality is there or not.[/quote]

It is still working - it must be an omission in the help.

Hi,

I'm using Pegasus on Netware (NDS mode) with Public Folders. Configured Merc/32 4.51 to deliver directly to the Public Folder via an alias.  Works like a charm.

Is there any way to notify users of new mail arriving in the Public Folders (the same way as new mail arriving in their personal folders) without running 3rd party tools?

Thanks

Ron

If it's not in your CC filters could it be coming FROM another mercury server's CC.

Check Received headers for another merc system?

Don't know if these are supposed to go on outgoing mail though. 

Is this the way to do it for all of us with support subscription, I mailed the support account before summer regarding this but not reveived an answer yet. It is a bit annoying running with crippled interface.

Best regards and thanks for the superb software

/Nils 

I see you have also had to avoid it.
I was hoping to set up this response :-

With reference to your message with the subject:
   "~S"
   that you attempted to send to : ~OR

This is what the help text says:

Local user  If you enter the name of a local user on your system (one to which Mercury can deliver directly) then all the mail downloaded from the remote account will be sent to that local user, irrespective of the address fields in the message. If you leave this field blank, MercuryD will examine the To, CC and BCC fields of each message looking for addresses it recognizes as local. When it finds a local address, it will send a copy of the message to that local user.

As far as I can tell no address headers in the message should be checked if a local user has been defined. 

 /Rolf
 

I emailed the author of the clamav version I'm running.
He suggested trying the SVN version.

I've tried that and now it launches in a couple of seconds with NO event log errors.

Thanks :)

Thanks David.  I am going to do the upgrade right now.

 Eric

Unless there is support in M/32 or the new daemon interface for recalculating the queue counters a webadmin interface won't help much in this case, though. If there is support for it I'd be happy to add the function to my web interface.

/Rolf 

Interesting, I'll play with this in a test environment later on and let you know what I find - I say interesting because it is something I can elaborate on in the webadmin for a domain since many have asked about how to divide and distribute info between departments.

Thanks.

Installed and seems to be working very well.

Okay, well thanks a lot for the help, I'm pretty sure I got it working properly now!  What happened was, I logged into my DNS center and after searching around for a while, I finally found out that, by default, the mail was being redirected to my hotmail account.  I just wish that it wasn't set as default like that without me even knowing, and it would have saved a lot of stress.

Oh and I can send and receieve e-mails properly now, so thanks a lot guys, I really really appreciate it!!   

Most any unused port is valid for receiving mail from your e-mail clients, port 587 is normally used for mail user agents.  Mail sent from other servers to MercuryS though must be received on port 25.  You can configure MercuryS to use port 587 as well as port 25 and you can also use TLS secure links and authorization.  Mail servers sending through MercuryS may or may not be able to use the secure connection so you must not disable the unsecured connections.

It's possible that your IP is on a blackhole list.