Posted by: pin on: 26 Dec, 2007
If your email is important and you can’t afford the downtime during the migration of your email service from one provider to another provider - how?
During migration, your new DNS may not respond immediately due to the DNS propagation. This problem can be solved by setting up the new DNS server to have the Zone records as the old one.
With such setup, your email could be pointing to both new or old email server during the propagation. This is fine as long as the email doesn’t get lost. You can retrieve emails from the old server later.
Once the propagation process is over, you can update the Mail Exchange (MX) to activate the new email service. MX update takes place almost immediately. Now, all email will go to the new email server.
Apart from this, you have to pre-configure the new email server to have exactly the same user account as the old one.
Zero-downtime migration for email is possible!
Posted by: pin on: 24 Dec, 2007
Outlook Express stores messages in a folder, location defined in Tools > Options > Maintenance > Store Folder. It converts every folder to respective .dbx file, for example inbox.dbx. Large dbx files turn Outlook Express to load slower.
Create New folder under Inbox. The format of the folder name should follow ‘Inbox-yyyy-mm’. Use the same format for your Sent box too. After you have created the folder, move all messages to their respective folder.
Close Outlook Express now. Go to the Store Folder, delete the file inbox.dbx and start Outlook Express again. The new inbox.dbx will be clean once again!
Posted by: pin on: 17 Dec, 2007
When you Cc’ someone when composing an email, you expect the reply from the recipient will go to you and the person in the Cc list. This will only happen if the recipient press the Reply All, instead of Reply.
So next time when you are replying an email, always hit Reply All!
Posted by: pin on: 03 Dec, 2007
Followed a new policy from TM today, all third-party SMTP servers are blocked except SMTP servers provided by Streamyx. This affects all users using TM ISP such as Streamyx Broadband or TM Dial-up on dynamic IP. Anyway, it does not affect user of Streamyx on fixed IP.
This reminds me those day when Jaring introduce the same method of blocking the use of external SMTP address. If you are on Jaring, you can’t send out email using TM SMTP, vice versa. This comman ISP SMTP-lock methods can be sometimes creating another set of problems,
1. People on the move on using different connections will have to swtch around SMTP…
2. The heavy load on the single ISP’s SMTP can cause email slow problem, and down sometimes.
Alternatively, many are switching to external SMTP on different Ports than 25. Check with your email hosting service provider if they can provide you SMTP on alternate port or even a secure SMTP will do help.
