Hi,
At present we are using MercuryS SMTP server, to deal with incoming email direct to our server, MercuryP POP3 server, I'm not sure quite why I have that turned on. MercuryO POP3 client to fetch email from an exchange server at our head office using MailDav, MercuryI IMAP server to enable offsite access to mailboxes and toe allow some users access to their old email if they are using other clients, and Finally MercuryC SMTP relay client to relay via a smarthost which will soon be biting the dust.
I would like to change over to MercuryE SMTP end to end delivery client but if I enable MercuryE on restarting Mercury I get an error register_listdu failed. Once Mecury finishes starting only MercuryS and MercuryP are actually running.
Is there something else I need to set up to make MercuryE start. I am running Mercury on Windows Server 2003.
<p>Hi,</p><p>&nbsp;</p><p>At present we are using MercuryS SMTP server, to deal with incoming email direct to our server, MercuryP POP3 server, I'm not sure quite why I have that turned on. MercuryO POP3 client to fetch email from an exchange server at our head office using MailDav, MercuryI IMAP server to enable offsite access to mailboxes and toe allow some users access to their old email if they are using other clients, and Finally MercuryC SMTP relay client to relay via a smarthost which will soon be biting the dust.</p><p>&nbsp;</p><p>I would like to change over to MercuryE SMTP end to end delivery client but if I enable MercuryE on restarting Mercury I get an error register_listdu failed. &nbsp;Once Mecury finishes starting only MercuryS and MercuryP are actually running.</p><p>&nbsp;Is there something else I need to set up to make MercuryE start. &nbsp;I am running Mercury &nbsp;on Windows Server 2003.</p>