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

Hi once again :)

I have been playing around with the MercuryB http server. I have successfully set it up and can access it across the Internet. I have subscribed to a test mailing list, returned the confirmation 'OK' message and have joined it without any problem.

The issue I have is that if I try to manage my subscription via the web page I get a 404 error. I enter the list name, my address, my password and click Proceed and the page fails to load.

Anyone else experienced this and/or know what might be causing it please?

Thanks

I think I have an idea what may be causing this. Mercury announces itself as apsarchaeology.co.uk, and the domain name of our IP address is mail.apsarchaeology.co.uk.

After registering my list subscription the web address displayed is mail.apsarchaeology.co.uk:59000/mlss/SubscribeTo

When I click the 'Click here' link to return to the subscription login screen, the address is apsarchaeology.co.uk:59000/mlss which of course does not load.

However, when I try to manage my subscription, the correct sub-domain.domain is used after pressing the 'Subscription' button: mail.apsarchaeology.co.uk:59000/mlss/ManageSubscription?MSubListName=external&MSubEmailAddress=greenman@gmail.com&MSubPwd=password&MSubscription=Subscription... but the page fails to load

I wonder if there is a conflict caused between the two names: apsarchaeology.co.uk and mail.apsarchaeology.co.uk

Would this problem be solved if I changed the name of the Mercury32 server to mail.apsarchaeology.co.uk?

If anyone has any thoughts on this I'll be pleased to hear them.

If you would like to check this out, the name of the test list is external

I wonder if there is a conflict caused between the two names: apsarchaeology.co.uk and mail.apsarchaeology.co.uk

Would this problem be solved if I changed the name of the Mercury32 server to mail.apsarchaeology.co.uk?

Could be, make the change and see what happens.  FWIW, I would be using the  apsarchaeology.co.uk for the address throughout since it does resolve to an IP address and MX records.

Thanks, Thomas.

We will have to add mail.apsarchaeology.co.uk to MessageLabs before proceeding with that.

However, we are thinking about setting up Mercury on another server and using it exclusively for mailing lists under a new domain name. We own several domain name variations on our company name, so could use one of those. However, is it possible to have one IP address registered with two domains? Would it work if we set up a forwarder to point the web address to our IP, and then use port forwarding on our router to direct the traffic to the Mercury32 mailer?

[quote user="Greenman"]

is it possible to have one IP address registered with two domains?

[/quote]

Yup. The domain's A record can point to ANY ip you care to enter.

[quote]

Would it work if we set up a forwarder to point the web address to our IP, and then use port forwarding on our router to direct the traffic to the Mercury32 mailer?

[/quote]

Yes, as long as it uses a different port to any other services offered on the external interface. 

Lovely. Thanks for the help :)

[quote user="Greenman"]

Thanks, Thomas.

We will have to add mail.apsarchaeology.co.uk to MessageLabs before proceeding with that.

However, we are thinking about setting up Mercury on another server and using it exclusively for mailing lists under a new domain name. We own several domain name variations on our company name, so could use one of those. However, is it possible to have one IP address registered with two domains? Would it work if we set up a forwarder to point the web address to our IP, and then use port forwarding on our router to direct the traffic to the Mercury32 mailer?

[/quote]

 Since I have three different domains pointing to my single IP address I know this can work.  I use NAT to send them all to a single Mercury/32 gateway server  that puts two of them into a domain account.  A separate Mercury/32 installation pulls from one of the domain accounts and I've got a BASIC program setup to push the mail to my Netware Mercury server. 

The only problem will be when running two domains on a single IP address is that with most routers ports 25, 110 and 143 can only be routed to a single host. If you are having MessageLabs process the mail you can setup Mercury/32 to receive mail on a different port  (587 is a good alternate) and then have them send the mail to port 587 in place of 25 for that domain.

.