Thanks Rolf... everything is up and running :)

Since my router has a quirk and won't send logs the way it should (please don't ask me to explain it, it would take a few pages) a few years ago I had Mercury setup to do this chore for me. The router would send the logs as an email to the appropriate 192 address where Mercury was located and Mercury would then forward it along. Worked like a charm. Unfortunately, now I can't remember how I had the setup done. I don't remember what modules I used. I've tried using just the SMTP modules but it keeps rejecting claiming the user is not known. I can't for the life of me remember what I did to get around that issue. Any ideas or wisdom where to start searching? Mercury was used strictly to relay the email to the appropriate destinations as defined in the email the router would send to it.

Thanks in advance :)

Glenn

You will need the SMTP server module (MercuryS) and either MercuryE (end-to-end SMTP delivery) or MercuryC (SMTP relay using your ISP's server). To get the forwarding to work you can either create a local user with that name and use automatic mail forwarding, or you can create an alias pointing to the real recipient. To use the first option the checkbox "Allow file-based forwarding specification using FORWARD files" in Mercury Core module configuration/Advanced must be checked.

/Rolf 

Thanks Rolf, I made the appropriate changes and it's accepting the email, however, it doesn't go out afterward. I haven't located the setting to get Mercury to send it though and I'm using the first option you suggested.

Regards,

Glenn

Check the logs for MercuryE or MercuryC (whichever you are using) to see if there is some indication of the problem. It could be several things: firewall problem, DNS problem, port 25 being blocked, some detail in the settings that's incorrect, so that's the best place to start.

/Rolf