- Legend Control Panel
- Legend Services
- Legend Host Migration
- Legend Mail Migration
- Frequently Asked Questions
- Why is this happening?
- Who is THUS/Demon?
- How do I migrate my Legend mail to the Demon mail service?
- I have already migrated my broadband to Demon, do I have to migrate my email too?
- I use the email service which is bundled with my Demon broadband package, can I cancel my old Legend email service?
- What if I choose not to migrate?
- What is the cost if I miss the 30 day deadline?
- Will I have to commit to a minimum contract period?
- Will I have to make any changes to my email settings once the migration has taken place?
- Will my email address change?
- Will my email forwarders be migrated?
- Will my email responders be migrated?
- Will there be any downtime as a result of this migration?
- Will there be any restrictions on the new service?
- What is a 'catch-all' email address?
- What is pops, imaps or smtps?
- What is message submission?
- When should I use message submission?
- When should I use pops, imaps, or smtps?
- Why do I need to change my username and password?
- Will I lose my old emails when I migrate?
- What is the storage quota for my mailbox?
- Will I still be able to add mailboxes?
- How long does mail stay in my mail Trash Can?
- Is my outbound mail limited?
- Can I use webmail to manage my mail when I am away from my usual base?
- How do I report spam?
- Will you be inserting adverts in webmail as consumer service providers do?
- What if I want to change the packages/services I receive?
- Why am I being asked to pay by Credit Card?
- I have a Legend hosted website, how will this be affected?
- Mail Client Settings
- Mail Client Details
- Frequently Asked Questions
What is message submission?
Legend Mail Migration
Message submission represents a refinement of the smtp protocol. While smtp (port 25) was defined as a message transfer protocol, a means to route and deliver messages, message submission (port 587) allows the submission of messages to be treated separately from their subsequent transfer. The protocol is described in RFC2476.