Hi yes we are using SMTP authentication in the AUTH Password file

[quote user="Ellie Kennard"]Is It istevenkennard.com or just stevenkellard.com ?"[/quote]

My typo.

[quote]Note the spelling of the second email where in reality you had actually written stevenkennard.com - so how could THAT have happened? Pegasus? Transmission? Mercury?[/quote]

Corrected within 20 seconds, but not before the email was sent.  :(

I assume that you are getting all mail via MercuryS.

The first thing that comes to mind is that the RCPT TO: address is not the same as the From: address. 

The second is that you deleted the user with Mercury/32 running and did not use the CTRL+Manage local users and/or restart Mercury so that the address was not deleted from memory.

Changing of the IP address should have no affect on this.

Thanks,

 1- But, in my mail client I can configure if I want that mails remind x days in my ISP server, for me this option is essential because my boss sometimes works via webmail of the ISP server. I could create a clone account in the ISP server, but I would like if i can configure this via mercury mail.

2- Ok, that's ok, I will do it through my mail client. 

thanks

Can one get a temporary license to allow for testing Mercury/32 running as a service? 

If domain.de is an external domain then you should not have it listed in "Local Domains".

You can set a local user for each MercD pop account to deliver to, or set an alias for the you@domain.de address (or get your own domain name [:)])

David has reported having fixed the MercuryX problem, and we the testers will most likely receive 4.73 RC within a week with additional issues addressed.

Rolf's HttpServer now also works with Mercury running as a native service.

Watch this space for more news.

Have a nice weekend.

Must have missed something as I now have the vbscript firing as expected.  Sorry for the false alarm.

E 20090915 121135 a94 Error connecting to RBQITEXCHVS01.XCTC.CTC.NHS.UK.

This can be caused by a number of reasons.

1.  Port 25 is being blocked by your ISP and this is not your ISPs SMTP relay host.

2.  Port 25 is being blocked by your firewall.

3.  Mercury/32 is being blocked by your firewall.

As a test try using Start | Run telnet tstephenson.com 25 to verify that you get the answer 220 tstephenson.com ESMTP server ready.  If you do not then port 25 is being blocked.  BTW I cannot connect to RBQITEXCHVS01.XCTC.CTC.NHS.UK either.

Well, the "JFNOFILTER" flag seem to be set by Mercury on DF's for a reason.

It may have other effects when used in Netware or Pmail integrated scenario's, neither of which I am very familiar with.

It may indeed be a feature rather than a bug as it seems to be intentional behaviour.

Maybe some of the Beta testers with a better overview could comment?

First off - thanks to both of you for really helpful replies. Let me see if I can clarify some things...

ASSP is basically a proxy server that filters incoming mail for spam and receives all outgoing so it can whitelist all addresses mails are being sent to. This has the big advantage that addresses users send mails to are automatically whitelisted for a year. As for the configuration - I'm aware that it is somewhat complicated, but this is the official configuration recommended by the ASSP documentation when ASSP and Exchange are running on the same machine, which they do in my case.

@dilberts_left_nut: I'm currently only worried about Mercury as a possible cause for an open relay. Yet I see your point that Mercury itself cannot actually be the problem.

@Thomas R. Stephenson: Thanks for the advice - I'll add the refuse entry. From your recommendation I take it that entries that are higher up supersede ones below, right?

Taken together, I take your two posts to say that Mercury probably is not the cause of my problem. That means I'll turn to the Exchange server and recheck that one...

Thank you so much!

Cheers,
Stefan.

Good point!  I hadn't thought of that :-)  I wondered why the reports had stopped!  So, I will have to reduce the reporting period, if I do a daily restart.  I have now set it to 23 hours, which will lose some of the count.  I wonder if it will handle reporting periods that include fractional hours.

Gordon

For maintenance of aliases I need to run sometimes the Mercury Nsynonym.exe tool.

This works fine on the Win2000-client, but is not working on the WinXP-client.

Any suggestions ?

Upgrade the client to v4.91??

To make this work you need to have MercuryE running in the domain1.com instance of Mercury to perform the delivery to the anotherdomain.com instance. If you are using MercuryC to send via an external server the local 192.168.1.100 address will not be found.

You should perhaps have a look at the WSMTPEx.exe program instead? See this thread:

/Rolf 

[quote user="Alar.Pandis@mtk.ut.ee"]

Forgot. ASSP is working together with Mercury/32.
Alar.

[/quote]

And against you, it would seem.

Mercury will not change the headers, only add a Recieved: line.

ASSP is my prime suspect, you should turn off ASSP and see if that solves the problem (of growing Ref header).

A valid message body must not have any single line greater than 1000 characters, so once the line exceeds this, it is no longer a valid message, which would explain why Merc can not process it correctly.

Sorry,

As Chris Bolton said, my  "myinternaldomain.com" is an internal domain that I had made up myself, not  a real "from" adress. So I use my external domain with the parameters of my ISP .

[quote user="GordonM"]A message was recently generated/received that had 80 characters in the local part, which is longer than the RFC seems to suggest.[/quote]

Well that's fine.  Although it says the local part should not exceed 64 characters, it also says  [quote]Every implementation MUST be able to receive objects of at least these sizes.[/quote]

It seems to me that Mercury is adhering to the standards.

Hello,

I have a user that wants to forward his incoming mail to multiple addresses.

Since this is not possible in Pegasus, I have created a mailing list in Mercury allowing posts from non members, created the subscribers, and in Pegasus set both local and Internet mail forwarding to this mailing list.

However, I can see in Mercury (version 4.52) that although the mail is forwarded to the mailing list, it is never sent to the subscribers.

If mail is sent directly to the mailing list, the mail is sent to the subscribers.

Am I missing something here, or is my set-up not possible?

I think I have found the option.  Checking "Suppress validation of "From" field when processing mail" in Mercury Core/General seems to allow any (invalid) "From:" address.

Gordon

If you're using popfile, either delete the user at the incoming server (which isn't Mercury) or continue to pop the incoming server, but direct the particular users e-mail to an account with filtering rule, that deletes any inbound messages.