Question : HMail Server on dedicated web server with in-house Exchange 2003

We have our own in house Exchange 2003 box, currently configured to SMTP smarthost connect through a UK Messaglabs provider.

We have custom MX records set up in our WWW shared hosting domain control panel DNS for this (A records point to the web host's server where our site lives, and MX records point to the Messaglabs provider).

We have recently bought our own dedicated Windows web server with a well-known UK provider and we are looking to make a staged move from our current arrangement, but I am not sure which way is best going forward.

Ideally I want email to be moved across to our new web server and HMail makes sense as a first choice option since it is already installed and available on the new dedicated server.

The main poin here is that while mail is to move to go through our new dedicated server, the website must remain where it is for now. The current site uses an unsupported version of PHP and is due to be replaced with a new site shortly, so I have no choice but to leave the existing A records pointing to the current web files.

I am guessing that the best way forward for this is to create a domain on our new dedicated server and then create custom DNS records pointing back to the shared host's server for WWW and FTP, or should I simply leave everything (DNS and files) where it is currently and re-point the existing MX record to the new dedicated server ?

In particular, what are the difficulties in setting up accounts which, in the first instance, will only be used for piping email traffic ?

In addition, what is the standard setup procedure for HMail on an external dedicated server combined with Exchange 2003 standard installed on an in-house box ?

I can find a lot of documentation and examples involving running HMail on the Exchange server (or vice versa) but I have no intention of installing Exchange on the dedicated web server, or of installing HMail on the in-house Exchange box.

So, in summary, I currently have:

Exchange 2003 Standard (in-house) >> External shared hosting for WWW/FTP >> Custom MX record >> Messagelabs

And what I want to end up with is:

Exchange 2003 Standard (in-house) >> Dedicated Windows web server HMail >> DNS to external shared hosting for WWW/FTP, to be switched to the dedicated server later.

I hope that is clear enough, but any additional information can be supplied.

As always, thanks in advance for any and all input, and I am away for much of this week and will only be able to check in on this every other day or so, so please take that into account.

Answer : HMail Server on dedicated web server with in-house Exchange 2003

Greetings,

You can use DateField's labelFunction to show custom text formatting:

Below is the working code snippet:

Hope this will help.

                       
         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:

           
           
             <?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
	<mx:Script>
		<![CDATA[
			private var dayNames:Array = ["A", "B", "C", "D", "E", "F", "G"];
			private var monthNames:Array = ["JAN", "FEB", "MAR", "APR", "MAY", "JUN", "JUL", "AUG", "SEP", "OCT", "NOV", "DEC"];
			
			private function formatDate(date:Date):String 
			{
				if (!date)
				{
					return "";
				}
				var monthDay:String = String(date.getDate());
				var monthName:String = monthNames[date.getMonth()];
				var year:String = String(date.getFullYear());
				
				return monthDay + " " + monthName + " " + year;
            }
            
            private function initDate():void
            {
            	df.dayNames = dayNames;
            	df.monthNames = monthNames; 
            }
		]]>
	</mx:Script>
    <mx:DateField id="df" creationComplete="initDate()" labelFunction="formatDate" parseFunction="null"/>
</mx:Application>

           
         