Hi all 

I find the problem, there was something wrong within the scratch directory (I had over 500 files .tmp)

Once I deleted the contents of the directory the global rules began to operate even without the need to reset mercury

thanks for you support

Please send me a private message here on the forum with a working email address - the messages we send to you about this are refused.

/Rolf

Mercury wouldn't be able to do what you ask, without having really advanced deterministic behavior about what a client could be doing as next command.

 If a mail server was to store an e-mail with attachment of 5MB without consuming the server RAM, it would need an overall cache engine to query first and disk data secondly. In the background Windows does this on local files, but serverwide, meaning over network lans, and other OSs, client side caching is dangerous. This is the reason why many have large issues with file based databases, and the bad solution called opportunistic locking. 

Thanks for the quick reply.

The current config is netware 5.1 running mercury on windows platform, with pegasus client.

I had a feeling I would have to do a fresh install.  I am aware of all the manual stuff that I have to do for the full windows, I was not aware that there is AD integration which might help alot.

since I have to do a fresh install do you know how to move the mercury license

thanks for all the great info

thanks I'll give it a try

> It was sent from a php script though my website. But its not setup to keep sending out emails, but its sending though my gmail. Which
> mercury is using for outgoing. Here's whats it doing...

This bounce message doe not say why Mercury was getting the bounce message.  One of the major problem here is you are sending mail out to the internet using the domain localhost and that is not allowed.  This is especially true for the postmaster address which is taken from the domain name you entered in Configuration | Mercury core | Internet name for this system. 

Other than that we need to see exactly what you are sending out though the script.  Turn on session logging in MercuryS to see what is coming in and in MercuryC to see what is going out via the GMail relay host.

>  
> Delivery to the following recipient failed permanently:    
> Admin@localhost
> Technical details of permanent failure: The recipient
> server did not accept our requests to connect. Learn more at
> http://mail.google.com/support/bin/answer.py?answer=7720 [localhost
> (1): Connection timed out]
>
> ----- Original message -----
> Received: by 10.114.92.3 with SMTP id p3mr5560597wab.77.1283188451407;       
> Mon, 30 Aug 2010 10:14:11 -0700 (PDT)
> Return-Path: <hatchiechris@gmail.com>
> Received: from localhost (c-71-227-159-43.hsd1.wa.comcast.net [71.227.159.43])  
> by mx.google.com with ESMTPS id x9sm14552538waj.15.2010.08.30.10.14.09
> (version=TLSv1/SSLv3 cipher=RC4-MD5);        Mon, 30 Aug 2010 10:14:10 -0700 (PDT)
> Received: from Spooler by localhost (Mercury/32 v4.72) ID MO00008F;  30 Aug 2010 10:14:03 -0700
> Received: from spooler by localhost (Mercury/32 v4.72); 30 Aug 2010 10:13:52 0700
> To: Electronic Postmaster <Admin@localhost>
> From: Electronic Postmaster <hatchiechris@gmail.com>
> Date: Mon, 30 Aug 2010 10:13:41 -0700
> Subj
> User <Tatalena@opprimovox.net> not known at this site.

BTW, the message was painful to read, I had to unwrap the garbage so it was legible.  

Is this another XAMPP setup??

That's certainly unambiguous. Thank you for your help.

Regards,

Bruce

The RFC max length for a single line is 1000 characters including CR-LF, and recommended line length is max 80 characters. Check formatting of the message to see if this is the reason for your problems.

/Rolf

Thank you.

Ah, well, it was worth a try.

The reason I am trying to do this is because we use MessageLabs for two of our three domains, and as I mentioned here  we are having problems with undesirable mail (spam-bots) using the lowest MX record to deliver mail directly to our IP address.

I know I can remove the last MX record, but I wanted to avoid doing this if possible. 

This is an interesting behavior, to put it mildly. How am I supposed

to notify my users to please log off now? How about in the middle of the

night, when the server does a reboot? Many connections will be still

active, but no user will be active to close them.

Will this be fixed in the next release?

Not sure what to tell you.  These functions are only completed when the client completes the transaction by closing the connection.  If the connection is broken then the EXPUNGING mail that the person using the connection expects to be able to recover might be worse than than leaving the mail undeleted.  This is especially true when the loss of mail is usually considered a greater problem than not deleting mail.  In addition, many mail clients, including t-bird can send a manual expunge under user control after they do a delete to confirm the deletion without closing the connection.

We had similar perfomance problems with initial authentication while 802.1-Authentication was activated in the client but not supported by our Netware-Servers.

Greetings

Olaf

Mercury can serve multiple domains, you just need to point an MX record to it (by creating a new A record in that domain connected to your public IP, or by using mail.cruizers.biz). In local domains you should then simply add  "mail --> domain2.com"  and, if you created a new A record,  "mail --> mail.domain2.com".

Mailboxes in Mercury aren't domain specific, so mail for dennis@domain1.com will be delivered to the same mailbox as mail for dennis@domain2.com. It can be separated by using domain specific aliases, though.

As Mercury itself doesn't separate between domains there is no administrative interface to access users for just one domain. There is a daemon that provides a web interface for a number of administrative tasks, though (newest version: http://downloads.serieguide.se/webtools.zip). It's possible to create an administrative layer on top of Mercury to handle domains separately, but it's a rather extensive undertaking. There are plans to include other ways to handle multiple domains in the next major version of Mercury.

/Rolf 

For people that might have tried starting Mercury as a service without a license... That's not going to work. Buy a license if you want it to run Mercury as a service.

: "Licenses are required for commercial use of Mercury/32, and will modify the program's status bar to reflect the licensed status of the server when installed. You will also need a license if you wish to run Mercury as a Windows Service." 

Right, less obvious username/password combinations will probably help! ;)

/Rolf

There is more information about the licensing terms for Mercury here:  

Geez! Well that was so painfully obvious for me to hear! *face palm*... Was just on the way out the door for work and didn't have time to scout around the application looking.

Thanks for that!

So to summarize, PMail was set to delete immediately, which worked, but deleting after 1 week using Mac Mail didn't work as the "Offer only unread mail" option won't allow that. Unchecking "Offer only unread mail" will make it possible to have POP3 clients delete messages after a specified time.

/Rolf

Thanks - That took care of the relay but had to surrender the mail services back to the original server as the ip is black listed and we are getting hit by something that I can't describe here.  I am going to look deeper and start a new post

THanks to everyone -

Bob

I COULD KISS YOU!!!!

It's been days - with this struggle.  And now I see light.

thanks

Michele