yes - install MercuryD and MercuryI and MercuryC

Thanks, Thomas and Rolf, for your advice, and apologies for troubling you. I have fixed the problem.

Although my domains in mercury.ini didn't have the errors suggested, and the structure of the entries for my new domain replicated the existing (and working) ones, there was a surplus line in them - dating from the time when I first set up Mercury and knew even less than I know now.

I have learned two things which I hope may be of use to others

- if your domains are not set up correctly you can get weird things happening, such as test@domain.com being a valid address and test1@domain.com being invalid, even with a domain mailbox. Such effects may be completely random, and not symmetrical between accounts, even if the accounts are set up the same way.

- don't munge (edit) log postings to try to avoid publishing domain names or addresses (not even a little bit)

 Chris

> HI Everyone,
>
> Thanks for the great feedback. I still do not know what I am doing wrong...so what I have done is made screen captures of everything I
> think may be important (the MX record, A record, Mercury.ini, screenshots of what I am seeing, etc). These can be found at
> russvanderhorst.info . If anyone would kindly take a look at this for me and perhaps point me in the right direction, it would be greatly appreciated.
>
>  Thanks in advance,

Answer Section:
    russvanderhorst.info, MX, 0, mail.russvanderhorst.info
    russvanderhorst.info, A, 98.216.147.35
    russvanderhorst.info, NS, ns16.zoneedit.com
    russvanderhorst.info, NS, ns8.zoneedit.com

Answer Section:
    mail.russvanderhorst.info, A, 98.216.147.35

Answers as a mail server

220 mail.russvanderhorst.info ESMTP server ready.
ehlo thomas
250-mail.russvanderhorst.info Hello thomas; ESMTPs are:
250-TIME
250-SIZE 0
250 HELP

Mercury.ini I have removed lines that are not a problem.

> [General]
>
> myname:          mail.russvanderhorst.info    # Canonical name for this server

Since this is the domain for the postmaster and maiser addresses I would use just russvanderhorst.info

>
> timezone:        +0000    # Time Zone to add to date fields
> file_api:        1    # Use the file api instead of queues
> mailqueue:       C:\MERCURY\QUEUE    # Where mail should be put for delivery
> smtpqueue:       C:\MERCURY\QUEUE    # Where the SMTP client should look for mail
> newmail_path:    C:\PMAIL\MAIL\~N    # Where to find the users' WinPMail mailboxes.

Everything else looks good.

>
>
>
> [Protocols]
>
> C:\MERCURY\mercurys.dll
> C:\MERCURY\mercurye.dll
> C:\MERCURY\mercuryp.dll

Three active protocols.
 
> [Mercury]
>
> postmaster:    postmaster    # NetWare UIC of postmaster

I assume that you have created an account called postmaster.

> [MercuryC]
>
Not used.

> [MercuryE]
>
> HELO : mail.russvanderhorst.info

You can leave this blank and it will pick up the data from the system name above.

> Nameservers : ns16.zoneedit.com

Use the IP addresses of the name servers, i.e. 75.125.10.187, 207.36.5.78

ns8.zoneedit.com[75.125.10.187]
ns16.zoneedit.com[207.36.5.78]

>
> Logfile : C:\MERCURY\Logs\MercuryE\~y-~m-~d.log
> Log_Verbose : 0
> DNS_Timeout : 20
> DNS_Retries : 4
> Transcripts : 1
> MaxThreads : 10
>
> [MercuryD]
>
Not used
>
> [MercuryS]
>
> Debug : 1
> Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log
> Timeout : 30
> Relay : 0
> Strict_Relay : 0

Turn on strict since otherwise the spammers sending as your users will be able to relay.

> Allow_Illegals : 0
> SMTP_Authentication : 0
> Session_logging : C:\MERCURY\Sessions\MercuryS
> Session_logmode : 0
> Compliance_Settings : 0
> Maximum_Failed_Rcpts : 4
> Max_Relay_Attempts : 4
> SSL_Mode : 0
> ST_Blacklisting : 288
> No_VRFY : 0
> SMTP_ConnFlags : 0
>
> [MercuryP]

Nothing special here.

>
> [Domains]
>
> server: server
>
> server: server

Need a lot more here.

Server :     Server
Server :     russvanderhorst.info
Server :    mail.russvanderhorst.info
Server :    [98.216.147.35]

>>I would have though the router configuration would have shown the external interface and not the internal.

You asked for the external interface. But i have no idea how to get hold of that information. All i can access on the router is the page i just posted, with all options clicked on.

If you are only getting an IP address via DCHP then this is a dynamic address and you cannot use MercuryE with a dynamically assigned IP address.  You need to switch to using MercuryC and enter the host name of your ISP's SMTP host as the relay host name.

Here is a copy of the session log

Thanks for the help I am new to all of this.

 15:12:59.000: Connection from 192.168.0.40, Fri Jul 10 15:12:59 2009<lf>

My email client has a Secure Password Authentication setting, and I was simply wanting to test the setting out using Mercury. 

DLN - I am now clear about how SpamCop works.  Thank you for the explanation.

No, the connection using MercuryS is for a potential special application that I haven't set up yet.  Normally, I just download mail from several of my ISP accounts using the Distributing POP3 client and read it with IMAP4.

I haven't done anything specific with regard to MX.  My DNS record shows the name of my mail exchanger to be my normal domain name, i.e. not mail.domain_name or something like that.  Given that I have a rather simple arrangement for home use, I didn't think that anything else would be necessary.  I used the DNS check tool at and the answers that came back were what I expected.

PaulW - Thank you for the comment.  Yes, I can see that looking up the more servers is likely to result in more false positives.

Thank you

Gordon

(deleted)

Please help us solve the problem. We have installed Novell 6.5, Mercuri 1.48.  NDS mode.

And we have a problem. We cannot make postmaster receive messages about

errors. For example, if mail comes to a user who is not registered in

Novell, Mercury  sends an answer to the author of the message about the error, but postmaster doesn’t get a message about it.

First of all a warning, I do not do NDS, only binary.  If mail is rejected by MercuryS then postmaster will only know about it by viewing the MercuryS logs.  If the mail gets to core then the way you are setup postmaster is also supposed to be notified but I would have to verify that mail to the postmaster@ukrnew.gov.ua is actually received.  I tried send to the postmaster@ukrnew.gov.ua address but the DNS said the domain was invalid.  Are you providing real data?

From what version did you upgrade?

This is base64 encoded except the password is encoded in MD5.  You can easily get the username though.

11:42:45.438: >> AUTH CRAM-MD5<cr><lf>
11:42:45.438: << 334 PC0yNzE0Mzg1OC4zNDZAZGF2aWRoYXRoYXdheS5jby51az4=<cr><lf>

<-27143858.346@davidhathaway.co.uk>

11:42:46.938: >> amFtZXNoQGRodGwuY28udWsgYmUxMWQ1ZjViZTM3ZjE0Yzk2NGFhYTk4YjU1ZjY0YzU=<cr><lf>

jamesh@dhtl.co.uk be11d5f5be37f14c964aaa98b55f64c5

You might try using a simple username rather than the full SMTP address here.  That said, this may be one of those servers that advertise CRAM-MD5 but then do not implement it.  Upgrade to PB1 and you can tell PMail not to use this protocol. From v4.5x help.

 Do not use CRAM-MD5 authentication even if it is advertised  This one's a bit technical, so please bear with us... The process of logging into the SMTP server to authenticate your identity can take a variety of forms: the server "advertises" the forms it understands, and Pegasus Mail looks through that list, choosing the most secure form it recognizes. Some forms are very "weak", in that they either transmit your credentials as clear text or in a form that can be easily broken, while other forms are "strong", in the sense that it is very difficult to work out your credentials simply by observing the exchange of data between the two programs. Unfortunately, one of the strongest forms of authentication, called CRAM-MD5, is commonly misconfigured on SMTP servers, even at quite reputable ISPs - the server will advertise that it supports it, but will actually fail any attempt to use it. Getting the ISP to realize that they are at fault is a lost cause in most cases - it's almost always easier simply to check this control, which tells Pegasus Mail never to use CRAM-MD5 for this server. You should be aware that you reduce the security of your connection by checking this control: CRAM-MD5 is the only commonly-used authentication form that offers reasonable security, and by disabling it, you force Pegasus Mail to use less secure methods... But sometimes you may decide that being able to send mail is more important than being able to do it securely. The choice is yours.

What was the error message(s)?   Did they just get sent with no errors?  In any case, turn on session logging in MercuryC and then send a mail message to these addresses.  At least this will verify that it got to the relay host without problems.

Maybe the relay host is being blocked by some blacklists. You have a fixed IP address.  Is the ISP blocking port 25 outbound?  If not then try sending via MercuryE direct to the receiving hosts. maybe the relay host is being blocked by some blacklists.

Thanks, Thomas. I must have misunderstood the Help info on how to use a normal delivery in a filter - I thought I had to use MOVE or COPY to obtain delivery?

However, I can now scrap this attempt - the vendor of Profimail, the mail client I wanted to use but was having SSL issues with, has now published a beta update which uses TLS and works with Mercury. I am not sure whether or not this was written in response to me reporting my problems to them via their forum, but it's either impressive service or impressive co-incidence.

Thank you for all your help with this

 Chris

I am using the same IP for my http server and Mercury 32 mail server.

However, I am using comcast's smtp to relay the mail (smtp.comcast.net,

port 587) if that even matters for the MX.

It does not matter how you are sending.  A MX record is not really required, the RFC says to send to the A record if there is no MX record.  That said, there are some strange mail servers out there and so I would recommend that you enter the GoDaddy domain as the MX record domain so those that require a MX record will be happy.  Now if you do have an off-site MX host for your domain then you should also enter this MX host as a higher numbers secondary MX host.

FWIW, it would have been very helpful if you had not munged up the real data so we could provide real answers.  This is not a security issue, these data go out with every message you send.

Thanks again Nico, for clearing this up.

I will keep the config as it is now (never fix it if it aint broken ;-).

I have another (performance) issue with your CamAV implementation, but this does not have anything to do with Mercury32 (I think), so I will contact you directly through your web site.

Regards,

Ed

it's true :( anyway both (1 and 2)  don't leave a copy on the server and directly forward the message to the destination server... it not good enough :(

i'm working now with the 3......

What I want to do is to be able

to use/see my emails where ever I am in the world be it on multiple

machines within my network, connected to the internet remotely (where I

would like to be able to download new emails and manage emails) and

also when not connected to the internet read a local copy on my laptop

and when reconnected to the internet or internal to my network update

the central database with my changes I made to the local copy whilst

offline.

 Mercury/32 can provide access to your mail stored on the Mercury/32 server either via IMAP4 or POP3.  Outlook can cache the IMAP4 mail folder for processing offline.  Mercury/32 will not automatically change anything that you have done offline but that might be a function of Outlook, I really do not use Outlook all that much.

FWIW, I have both PMail & Mercury/32 IMAP4 and Squirrelmail access to my system when on travel and I copy my current mailbox to my laptop when  going on the road. when using a slow or costly connection I generally get the mail via POP3 (MercuryD) and send via the SMTP client (MercuryC).  This means I am only on-line for a few minutes for mail processing.

I have also installed Mercury/32 on the laptop so I can send/receive my mail from my home system bypassing all port blocks.  Work I have done on the laptop is sent to a transfer folder and moved back to the main system when connected to the lan. 

[quote user="Vincent Fatica"]

When Mercury processes an email with "CC: mailing_list" the persons on "mailing_list" receive an email with "mailing_list" in the "To:" header and containing no "CC:" header.  Is there any way to keep Mercury from doing this so CC recipients can readily see to whom the email was send and that they were cc'd?  A test shows "header stripping" does not affect this.  Thanks.[/quote]

Does version 4.7 do that also?

Sorry I should have replied earlier.

Rebooting the server fixed it !!

Thanks

Thanks everyone for your help it is working now :-)

Especially Mr Stephenson you are a legend - Thanks.