> Hi there,
>
>  I have mercury running on my local webserver. Now I want to configure
> mercury that it sends all the emails received to another smtp server
> in my network (e.g. smtp.mydomain.org). Mercury should not make any mx
> lookups itself, only forward it.

Mercury/32 currently does not provide MX services.  David's looking into this for a future enhancement but until that happens here's a work around.   

1.    Create a domain account for the domain you want forwarded. For example I forward the domain novell-tstephenson.com so I have a domains list setting of

DM=novell: novelltstephenson.com

2.    Create a program to get the CNM files in the user NOVELL directory and convert them to 101 "glue" header queue files that change the address to the IP address of the receiving SMTP host.  I did this in BASIC but you could use anything you happen to have and are familiar with to do the same thing.


REM This program was developed to send mail from a "domain" account to a different
REM server via SMTP.  It takes the CNM RFC 2822 message body, extracts the SMTP addresses
REM and then saves it as a 101 file.  The CNM import file is a directory listing
REM of the CNM files in the "domain" user account.

CLS
REM Set the path to the domain mailbox and the new domain name.
PATHSPEC$ = "c:\pmail\mail\novell\"
Domain$ = "@[192.168.1.3]"

REM Read in the CNM files
OPEN PATHSPEC$ + "files.txt" FOR INPUT AS #1
       
WHILE NOT EOF(1)
        REM Read the CNM directory listing
        LINE INPUT #1, Line$
        REM Check to see if this is a CNM file else skip it.  The CNM file is always 8.3.
        IF RIGHT$(Line$, 3) = "CNM" THEN File$ = RIGHT$(Line$, 12) ELSE GOTO SKIP
    
        REM Read the CNM file
        OPEN PATHSPEC$ + File$ FOR INPUT AS #2
       
        REM Get the MAIL FROM: and RCPT TO: addresses for the glue headers.
        REM I'm using the Sender: for the MAIL FROM: address. It may be blank
        REM for locally delivered mail but a blank MAIL FROM: works for me.
        WHILE NOT EOF(2)
            LINE INPUT #2, Line$
            IF LEFT$(Line$, 14) = "X-Envelope-To:" THEN RCPTTO$ = MID$(Line$, 16, LEN(Line$))
            IF LEFT$(Line$, 7) = "Sender:" THEN MAILFROM$ = MID$(Line$, 9, LEN(Line$))
        WEND
        REM Close the CNM file.
        CLOSE #2

        REM Change the domain name to the new domain in the RCPT TO: address.
        FOR I = 1 TO 100
            IF MID$(RCPTTO$, I, 1) = "@" THEN RCPT2$ = MID$(RCPTTO$, 1, I - 1) + Domain$
        NEXT I

        REM If the SMTP address was in brackets add the trailing bracket.
    IF LEFT$(RCPT2$, 1) = "<" THEN RCPT2$ = RCPT2$ + ">"

        REM Write the 101 file in Glue header format.
        OPEN PATHSPEC$ + File$ FOR INPUT AS #2
        OPEN PATHSPEC$ + LEFT$(File$, 8) + ".101" FOR OUTPUT AS #3
        REM Write the MAIL FROM:, RCPT TO: and blank line.
        PRINT #3, "$$ " + MAILFROM$
        PRINT #3, RCPT2$
        PRINT #3, ""
        REM Write the rest of the RFC 2822 body to the 101 file.
        WHILE NOT EOF(2)
            LINE INPUT #2, Line$
            PRINT #3, Line$
        WEND
        REM Close the CNM and 101 Files.      
        CLOSE 2
        CLOSE 3
        REM Delete the CNM file
        KILL PATHSPEC$ + File$
SKIP:
WEND
CLOSE
SYSTEM
END

4.    Create a BATCH file to process the CNM files.  I got the program wait.com off the web someplace.  Works fine.

ECHO OFF
:LOOP
CD c:\pmail\mail\novell
dir c:\pmail\mail\novell\*.cnm > c:\pmail\mail\novell\files.txt
REM CALL c:\qb45\qb /RUN c:\pmail\mail\novell\MX.BAS
call c:\pmail\mail\novell\mx.exe
move *.101 c:\mercury\queue
DEL c:\pmail\mail\novell\files.txt
call c:\pmail\mail\novell\wait -m 5
GOTO LOOP

5.    Load the batch file at startup.  I use NT Wrapper Pro to run it as a service  at startup.

Now mail for domain novell-tstephenson.com is received by tstephenson.com and moved to the Novell user new mail directory.  The bat file runs the program very 5 minutes and makes a list of all the CNM to files.txt.  The BAS file is run and reads the files.txt file to get all of the CNM files and adds the "glue" headers to the original CNM file and saves it as a 101 file.  The bat file moves the 101 files to the queue and loops.

This works for me to forward all mail from the outside world with the domain novell-tstephenson.com to the Mercury NLM server running on my Novell system. 

So, this PTR,reversed record can also be at my ISP and not needed at

my domain name hoster (budgetwebhosting.nl) because the spreading is

better than stuck in one place. Am i right or totally wrong?

Not totally wrong, not totally right.

1.    The PTR record is not required by the SMTP/ESMTP RFCs at all. There is no MUST requirement that the rDNS show anything.

2.    Many SMTP hosts though will not accept a connection that does not have a PTR record since a valid SMTP server SHOULD have one and it should point to a vaild host name. 

3.    A very limited number of SMTP hosts wil  not accept the mail from hosts where this PTR does not match the connecting EHLO/HELO srting.  I've never run into one of these but some have reported this as a problem.

So, I believe you are are properly setup and should have no problems delivering the mail.

 

I believe this message is hardcoded in the program. If you want a message in the system log window at program start you could write a small resident daemon with a startup function that has a logstring command. See daemon.txt in the Mercury\Resource directory for more information.

/Rolf 

hmm.. I double check to make sure

Thanks :) 

Thanks, it looks pretty simple when viewed like this. Unfortunately my head is averse to logic [:P] and trying to concoct this stuff leaves me in a gibbering heap.

What does the E stand for in FRE? Should it be FRS?

 

Edit 2:

It's OK, just discovered what it is.

Thanks again for the help *thumbs-up*

Ahh - thanks. Problem is, without going through the entire help system, users will not know this, nor other details which appear in the Help, but not in the manual.

Again, thankyou - looks like this is the perfect solution for me now. [H]

Hi Peter,

Thanks for your reply, and sorry for my late response.

I agree that these issues are not impairing the real functionality of Mercury/32 in any way, but it would be nice when the change of development environment would cure them.

If I can help in any way by testing something, just let me know.

Regards, Ed

[quote user="tomt"]

It turns out the filter was fine !
The user was still CC'ing the other 2 users..

[/quote]
That was exactly what the filter I've suggested was meant to avoid :)

Best regards,

Nico

problem solved thanks. just checking back, we had changed the username & Password many times and was sure it was right, when we turned on logging we found the local pasword set as the POP3 Password, this was definatly not the case when i looked at it friday but it may have been the case in the begining the person who set up the email may have entered it first time around.

 is there any chance of it getting locked up with the wrong password - either way the logging allowed me to view and check that it has been fixed.

thankyou for all your time

Mattr88

hard to help unless to can tell us exactly what you are trying to do and what is failing.  Mercury/32 is not all that difficult to setup and sending mail via MercuryE or MercuryC only requires a couple of configuration entries.

 

> I sent a msg from my hotmail account to my mercury account. They
> arrived ok, but a reply back doesnt work. After my initial post I tried
> some other accounts ( like my work) and noticed they all are resolving
> to 205.178.187.13. this mean I have some kind of DNS issue I assume.

Not necessarily, but in this case it looks like it's not resolving correctly

hotmail.com, MX, 5, mx4.hotmail.com
hotmail.com, MX, 5, mx1.hotmail.com
hotmail.com, MX, 5, mx2.hotmail.com
hotmail.com, MX, 5, mx3.hotmail.com

    mx1.hotmail.com, A, 65.54.244.136
    mx1.hotmail.com, A, 65.54.245.8
    mx1.hotmail.com, A, 65.54.244.8
    mx2.hotmail.com, A, 65.54.244.40
    mx2.hotmail.com, A, 65.54.244.168
    mx2.hotmail.com, A, 65.54.245.40
    mx3.hotmail.com, A, 65.54.244.72
    mx3.hotmail.com, A, 65.54.244.200
    mx3.hotmail.com, A, 65.54.245.72
    mx4.hotmail.com, A, 65.54.244.232
    mx4.hotmail.com, A, 65.54.245.104
    mx4.hotmail.com, A, 65.54.244.104

Are you sure you are pointing to the DNS hosts in MercuryE?


>
> 18:53:08: processing job MO000017
> Resolved CN for 'hotmail.com' to 205.178.187.13

This IP address give a rDNS of www.networksolutions.com


> Connecting to 205.178.187.13
> Connection error.
>
> 19:11:48: processing job MO00001D
> Resolved CN for '<deleted domain>.com' to 205.178.187.13
> Connecting to 205.178.187.13
> Connection error.
>

Thanks a lot, Thomas, that's useful advice.

All I get is "message not successfully sent."

Is there a way of finding out why? Without this, it becomes rather impossible to debugg & fix.

If you turn on session logging in Configuration | MercuryS then each TCP/IP transaction will be logged in a TCP[4 hex digits].MS  Point the session logging to drive:\mercury\logs\mercuryS and then make sure the directory exists.

Am I supposed to do some set-up work first?

1.    Verify that mercury/32 is properly setup to receive the mail via MercuryS. 

2.    Read up a bit on SMTP transfers to ensure you can tell a good TCP/IP session from a bad one.  

3.    Read the Mercury manual to figure out how it's supposed to be configured. 

I sorted it out. I was using MS-Excel to edit the file (removing duplicates, double @@'s, spaces etc from the addresses), and when saving as a text file it was saving it as unicode. After I opened the txt file and saved it as an ANSI text file, Mercury could import the addresses. Phew!

Only via a daemon since only daemons get access to the the QCF control files containing RCPT TO: addresses.  If you are sending via the Mercury/32 queue you might be able to write something to process the "glue" headers of the 101 file to catch these.

Thanks a lot, Thomas. Now I know what to do in future.

Use Configuration | MercuryS | Connection control and select the first two options to turn off relaying and to turn on strict local relaying.  You can then check the third option to allow and setup the auth password file that contains the username and passwords to be used to allow specific users to relay.

 

Yes.

I have created a shortcut which links to:

I copied it to c:\documents and settings\all users\desktop

It then appears on everyone's desktop when they logon. When they click it, they are prompted for a user name - it's just the same as a local installation and the end user does not notice any difference.

And Mercury will manage all mail as you say, so long as it is configured correctly.

Very many thanks.   

I didn't know that but it has worked and I can now continue my 15 years use of Pegasus.

J Booth