Thanks.. Working now !!

I use SMTP  blacklists to tag emails, Content control and SpamHalter.
I think it was logging emails caught be Content Control in the syslog !!

For all the frustration that these delays bring both you as the program and us as the end users... You software has always been well worth the wait!!!  I think I can hold out a little longer ;-)

 Thanks for GREAT products in Pegasus and Mercury.

Well, try nil, and if that doesn't work either in your programming environment check if there is an alignment problem in the daemon (I believe Mercury expects byte aligned data).

/Rolf
 

Maybe a basic filter rule for 'failure' in the subject and MOVE to admin or a temp user for review?

Keeps them out of the users boxes.

You just have to ride it out, it will stop eventually. 

PS

"..and no relaying at all."

If you have outgoing mail you are relaying. Any mail accepted by your server addressed to a non-local domain must be relayed to the server that handles that domain. [:)]

I assume you mean that you do not relay mail from non-local sources. [:)]

We don't use synonyms in our installation so I have no experience of this. This is what the manual says about it, though:

If you have created synonyms on your system using the Pegasus Mail PMGRANT utility, you will
need to use the CH_SYN.EXE utility supplied with Mercury to build a synonym database for
Mercury, and enter the name and location of that file here. (note that if running in NDS mode,
you will use the NDS-aware synonym builder NSYNONYM.EXE instead).

/Rolf

To send mail through your ISP's mailserver:

1. Open the Configuration / Protocol modules dialog in Mercury. 

2. Uncheck MercuryE

3. Check MercuryC

4. Click OK and restart Mercury.

5. Open the Configuration / MercuryC SMTP client dialog and fill in the name of your ISP's SMTP server as well as username and password (according to the information you have received from your ISP). It might be a good idea to enter a name for a general log file as well. Increase the value for TCP/IP timeout to at least 300. Leave the rest as it is for the time being.

6. Click OK and test it.

/Rolf 

Yes, SpamHalter processes the message before it gets to the rules, so you can create rules to handle messages tagged by SpamHalter the way you prefer. The recommended procedure is to move them to a special mailbox that you can review to make sure there are no false positives.

/Rolf 

What have you put for the policy command line?

I have a couple of excluded addresses in an email list (status = X) (*). When I do a review of the list (via email), the excluded addresses appear as normal active subscribed addresses. (Whereas disabled addresses, and those not receiving mail, are described as such.) Bit of a shock to see apparently signed up!

Is there something wrong with my installation or is it always like this?

(*) yes, I know, probably not overly useful seeing as they could sign up with new addresses

My ISP has made it tough to send e-mails if the sender's e-mail address isn't the one registered with them.  I run a mailing list and would like to continue doing so, the problem of course is that I can't register all the senders' e-mail addresses at my ISP.  When an e-mail arrives from the list the FROM is: Mail Server @ me.com on behalf of   but the internal From address is just sender@otherISP.com.  I would like to change it so that the FROM address is mailserver@me.com and the reply-to is sender@otherISP.com

Is that something that's doable? 

Thanks, Eric 

PS: I've written daemons for Mercury in the past and wouldn't mind doing it that way...

The calls are made directly to the dll you provide, there are no other files involved. So either there is a problem with the dll that makes the call fail altogether, or there could maybe be a second instance of Mercury running on the computer.

/Rolf 

Hi Sabahattin

Your mail came through without any problems, thanks for the check.

The postmaster problem remains though.

And, yes, it would be good to send plain text mail, but HTML is so useful and conveys meaning in a much better and intuitive style.

We are there although I still do not understand why this problem just surfaced after several years.

Mercury had the path to the Mailbox folder via a share in the form of \\ComputerName\MAILBOX\~8

 I changed this to J:\MAILBOX\~8 and all was well.

Thanks

Ken
 

Well, we probably wrote past each other.

Btw I moved your original post to the proper forum [;)]

Ok fellows, I think we finally have this all racked up in a pile. It looks like it's working now.

I can't find any info on how to restart Mercury. Is this closing the interface? I wasn't sure so I've been closing the interface and restarting Apache.

Regardless, I was restarting it somehow in there because the new setting took and I can sent myself mail. Here is the Session log: 

[quote]

13:21:42.046: Connection from 127.0.0.1, Fri Apr 25 13:21:42 2008<lf>
13:21:42.062: << 220 localhost ESMTP server ready.<cr><lf>
13:21:42.062: >> HELO Compaq1<cr><lf>
13:21:42.062: << 250 localhost Hello, Compaq1.<cr><lf>
13:21:42.062: >> MAIL FROM:<Admin@localhost><cr><lf>
13:21:42.078: << 250 Sender OK - send RCPTs.<cr><lf>
13:21:42.078: >> RCPT TO:<test@localhost><cr><lf>
13:21:42.078: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
13:21:42.093: >> DATA<cr><lf>
13:21:42.093: << 354 OK, send data, end with CRLF.CRLF<cr><lf>
13:21:42.109: >> Date: Fri, 25 Apr 2008 13:21:42 -0400<cr><lf>
13:21:42.109: >> Subject: test11<cr><lf>
13:21:42.109: >> To: test@localhost<cr><lf>
13:21:42.109: >> From: test <this@that.com><cr><lf>
13:21:42.109: >> <cr><lf>
13:21:42.109: >> Message sent: 04.25.2008 at 13:21:41:<lf>
13:21:42.109: >> <lf>
13:21:42.109: >> From: test<lf>
13:21:42.109: >> Email: this@that.com<lf>
13:21:42.109: >> About: test11<lf>
13:21:42.109: >> <lf>
13:21:42.109: >> --------------------------- COMMENTS ---------------------------<lf>
13:21:42.109: >> <lf>
13:21:42.109: >> test test test11<lf>
13:21:42.109: >> <lf>
13:21:42.109: >> --------------------------------------------------------------------------<lf>
13:21:42.125: >> <lf>
13:21:42.125: >> <cr><lf>
13:21:42.125: >> .<cr><lf>
13:21:42.125: << 250 Data received OK.<cr><lf>
13:21:42.140: >> QUIT<cr><lf>
13:21:42.140: << 221 localhost Service closing channel.<cr><lf>
13:21:42.140: --- Connection closed normally at Fri Apr 25 13:21:42 2008. ---
13:21:42.140:
[/quote]

Thanks everyone - thank you thank you. dilberts_left_nut, I  but you're better than the right_nut.

I'm only able to send mail to users@localhost though. Is there some way to allow Mercury to send emails outside of localhost? For my purposes of testing php systems, such an email (lacking a .com and so on) gets caught.

Global rules does this.

General rules are connected to the users via the alias function.

thanx alot ................ using username instead of username@localhost works ...

i was stuck with this prob a while ...

thanx alot 

Sabahattin, that is a very useful post, thanks a lot.

I will setup a list using Mercury and see how it goes.

That 'Job OK' message will be in the 'Core' window.

That means that the message was successfully received and processed by the core process.

It then needs to be sent on to the destination address by an SMTP client module, either mercuryC (via an SMTP smarthost such as your ISP's) or mercuryE (direct end-to-end delivery). Which are you using?

You will need to check the log for mercC or mercE to see what is happening with your outbound message. 

That was it.  That set of rules has been in place for years

Thank you

Gus