(Update. 2009-10-13 6:13 pm. Stage 1 is now in effect. Please make the changes described below.)
In the classic linux environment, after Stage 1 of our mail system migration comes into effect, our new servers will no longer use pop-before-smtp to identify you as a customer when you send outgoing mail. You will therefore need to configure your POP or IMAP client to send mail using authenticated SMTP on port 587.
(Please don't make this change before Stage 1 comes into effect, as authenticated SMTP won't work until then.)
All the available ports and protocols are given below.
For reading mail after Stage 1 comes into effect:
For sending mail after Stage 1 comes into effect:
Note: If you have a DSL, cable, or other high-speed connection, you can
send outgoing mail via your connectivity provider's SMTP server following
their instructions. It's not necessary for you to connect to
to send outgoing mail.
Note: For authenticated SMTP, please use your login name and password as you would use it to log in via ssh into the Linux shell, i.e., of the form “joeuser” (and not of the form firstname.lastname@example.org).
Our old servers
mauve.rahul.net will continue to
operate for a limited time. If using authenticated SMTP proves to be a hardship for you,
you can simply repoint your POP or IMAP client to these older machines, and keep
using the old ports and protocols so long as the old servers are available.
If you wish to do this, then instead of connecting to
green.rahul.net. Each machine will do both POP and IMAP.
All other information will then remain unchanged, and you will connect to
SMTP port 2525 on these machines to send outgoing mail.
Note that if either of the two machines is not available, you will need to manually repoint your mail client to the other.