You really should get a static IP.  If you can't, then that's another good reason for using an SMTP relay service.

 

Mercury/32 v4.51 is now publicly available.

Although on

the surface v4.5 will not appear markedly different from v4.01, "under

the hood" it's quite a different story. The code has been heavily

reworked in almost every area, focusing heavily on robustness,

reliability and performance.

A download link and list of new features in v4.5 is available at

    http://www.pmail.com/m32_451.htm

Starting

with this release of Mercury, the licensing model for the program has

changed. Mercury remains completely free for non-commercial use, but

commercial users will need to purchase a license if they wish to

continue using it after a 60-day evaluation period. We have attempted

to produce a licensing program that is both very inexpensive, and

completely non-intrusive. Details and pricing can be found here:

   http://community.pmail.com/pmail/MercuryPricing.aspx

Please

note that if you have a current support subscription at any level under

the old Pegasus Mail Support Consortium arrangement, you are

automatically entitled to a Mercury site license at no charge - please

contact me directly to arrange this.

A personal note: I'm

acutely conscious that it has taken an abnormally long time to get this

release done. One of the lessons I have learned from the problems in

getting v4.5 complete is that I need to open up the beta testing

process so that more people have greater access to betas and patches

more often. I will be developing a strategy for this over the next

couple of weeks.

Any problems or issues arising from this

release can be raised either on the public mailing list at bama.ua.edu,

or in the Community forums at our community web site,

http://community.pmail.com.

Cheers!

-- David --
 

Hi i'm trying to set up squirrel and Mercury, the SMTP seams to receive mail okay but the mails stay trapped in mercury smtp queues they never get deposited/deleivered to individual mail boxes - so when a user logs onto the Squirrel system they do not see any mails - any ideas what this might be it's beeen driving me nuts !!

You really have not provided enough info. 

Does the MercuryS log show the mail has been received?

Does the mercury core screen show the mail being processed?

 

[quote user="Graham"]Is there a way to leave mail on the ISP pop server after checking  with Mercury.[/quote]

It's on my to-do list, but it hasn't made it into the v4.5 release.

Cheers!

-- David --

Besides our normal SMTP server we get mails from a POP3 account and I wanted to install a content filtering rule which reacts on wrong HELO/ELHO when the mail arrives at the POP3 account.

I tried following rule:

if Header "Received" matches "*helo=*by server*"
ANDNOT Header "Received" matches "*helo=*.*by server*" weight 51 tag "wrong HELO"

but it is no working. If HELO is OK it produces "X-CC-Diagnostic: Header Received contains "helo=" (0)", but if HELO is wrong it does nothing.

As a workaround I am now using:
if Header "Received" matches "*helo=*by server*" weight 51 tag "received by server"
if Header "Received" matches "*helo=*.*by server*" weight -51 tag "HELO OK"

My question is, what is wrong with the first rule?

There is unfortunately just one address for all mails going out, the ones that return do return for reasons I need to address individually.

Hopefully this is better handled in CS2007.

If its failover you want how about using VMWARE,  that would let you run Mercury in a virtual machine and set up another virtual machine, hosted on a different physical server, to take over if the first one stopped working for some reason.   Both servers could obviously use the same queue hosted on a NAS device somewhere.

 As soon as I can get my lot to part with £1200 for two sets of bundled virtual OS and utilities thats where all or servers hosting databases, email etc are going.   Licensing is per CPU not per core so we can have two systems running virtual server for that price plus most of the monitoring and failover utilities we could need.   This seems much cheaper than other automatic failover systems I have looked at in the past.

Starting Mercury on a new system is a fairly trivial task for us at least all we need do is copy of move the disk with our mail on, change to the correct IP address and start the server.   We have done this a few times now when hardware fails, it takes about 2 minutes to be running with our more critical accounts already accessible, doing it manually.
 

[quote user="Markus"]

I think I remember David talking about dropping cryptlib and transferring to openssl, but couldn't give a definite estimate if and when this would happen.

[/quote]

This is planned for Mercury v. 5.

/Rolf  

Thanks! Looks a good idea. I presume that a welcome message isn't sent if there's a welcome file specified.

Looks like I picked too soon to do the update. [:$]

not 100%, but it is in this forum that I found the last answer

Check the clamwall log?

It gives 'sender' & 'recipient' & 'found virus', thats enough for me to spot a FP (if I ever get any) 

[quote user="KeithW"] 

Thanx for the reply !!

I am being beat up trying to get SPF implemented and cannot get email to the MSN / HotMAIL domains working.  I was working thru the MicroSoft SenderID Wizard and it asked if those RFC's were fully supported,  I could not find any references on the web site so I posed the question.

[/quote]

 

There is something else going on here that has nothing to do with SPF.  I'm sending to both MSN & Hotmail (same place) and i have no SPF record at all.  What error are you getting when sending to these addresses?  What are you using for sending?  MercuryE?  MercuryC  If you do not have a fixed IP address or if you do not have a PTR record at all then you can be rejected by these MS systems.  In any case a session log is in order to see why you can't send.

 

 

> For some reason I can't send from tbird to a client setup on mercury.
>
>
> I have domains on mercury as follows
>
> gibberish    mydomain.local
>
> moregibberish    192.168.1.100
>

Check the domains setting in Mercury.ini.  The domains sections should look something like this.

[Domains]
;Server : Domain
Server : Server
Server : mydomain.local
Server : [192.168.1.100

This mail mail sent to user@mydomain.local and user@[192.168.1.100] will be treated as local mail.  If you want to use the user@mydomain.local from other systems on the local LAN you'll need to setup some sort of local DNS.


>  
>
> No aliass or any thing else set except usernames.
>
> user names are
>
> fred and wilma
>
> I can send an email from mercury to fred and tbird will get it.
>
> When I send to fred from tbird I get an unable to relay for fred@[192.168.1.100]

This means that you do not have [192.168.1.100] in the domains section.

>
>  Any ideas?
>
>  
>
> Thanks for your help.
>
> Chris
>

Clever! I have to say that I probably wouldn't have thought of that solution, even though it's a good one.

Just goes to show - the fact that I wrote the program doesn't necessarily mean that I know the best ways of using it. It's nice to have a creative user community. [:)]

Cheers!

-- David --

I can appreciate the effort you've put in to maintaining the legacy of code while supporting the breadth of email technologies in Mercury.  I'll keep an eye out for the support of various IMAP extensions in the future.  Thanks again for putting forth the effort to maintain this type of technology.  It's not too common these days to have the primary developer of a product dedicate the time to respond to queries like this.

John

Okay, I don't have a fantastic solution, but maybe you could run your pop3 server on a different port from the default port, so attackers that are just guessing you have pop3 because you SEND / ACCEPT mail will be thrown off the trail.  Of course it will mean informing all of your users ... which might be a major headache!

*that's what I did when I was just starting and people were trying to connect to my pop3 and I didn't even have any users yet ! ! !,  I changed port and now get no unwanted attention* 

YEP, Works great when you know where to go and set it up !!

Thanx for the assistance, much appreciated !!

 

Regards,

Keith

[quote user="GLM"]

Anyone knows how bare LF messages received by the SMTP module are processed by Mercury/32?

                              -messages are accepted and LF converted to CR/LF pair

[/quote]

I would expect this to be the case almost everywhere in Mercury. The problem is that a message file can be processed so many times in the course of passing through the queue that there may be some places where it's not so - but as a general rule, this is what I would expect to happen. I code pretty defensively against bad line endings.

Cheers!

-- David --

Mercury NLM 1.48, Netware 4.20, Pegasus Mail 4.41 NDS Mode, NPEG 2.06, GETMAIL 0.41

2 domains, SpamAssassin 3.1.7 on a smart host (internet provider), less than 1000 Emails every day,

original Pentium 150 MHz, 208 MB RAM,

System on IBM 8 GB SCSI HD (at Compaq EISA SE-Wide-SCSI Controller), Mailboxes RAID5-Array,

System setup 06-05-1996, works also as File- and FTP-Server  (workday, working hours CET+1), never touch a running system... ;-)