Topic: Exchange 5.5 and SME 7.3 issue

[giugiugiu72]

Hi to All


In our enterprise (around 400 users) we have an exchange 5.5 machine with all mailboxes in with an X400 connector to an external mail server in the US (so we have not SMTP installed). After a change in management we have to cut off X400 connection and install a local SMTP service with another mail address template. We have registered the new domain on an ISP and installed a SME 7.3 for fetching from the ISP on a catchall account with spam filtering (all working perfectly) and we are starting doing the job on exchange server. The question is: Is it possible to delegate SMTP service to SME with an X400 connector from Exchange 5.5 to SME or the only solution is installing SMTP on exchange 5.5 (with popcon to download messages from SME) and using SME 7.3 only for fetching form the ISP? All suggestions will be appreciated. THx a lot in advance to all.

[cactus]

Hi to All


In our enterprise (around 400 users) we have an exchange 5.5 machine with all mailboxes in with an X400 connector to an external mail server in the US (so we have not SMTP installed). After a change in management we have to cut off X400 connection and install a local SMTP service with another mail address template. We have registered the new domain on an ISP and installed a SME 7.3 for fetching from the ISP on a catchall account with spam filtering (all working perfectly) and we are starting doing the job on exchange server. The question is: Is it possible to delegate SMTP service to SME with an X400 connector from Exchange 5.5 to SME or the only solution is installing SMTP on exchange 5.5 (with popcon to download messages from SME) and using SME 7.3 only for fetching form the ISP? All suggestions will be appreciated. THx a lot in advance to all.

You can use SME Server to fetch the mail and forward it to another mail server I believe. This should be somewhere in the manual or FAQ entries in the wiki I believe.

[giugiugiu72]

and that's correct and right...but I need to made the opposite, I'm trying to find a way to receive from exchange and forward to the world outside...the target is to use SME for the dirty job of receving and sending messages leaving mailboxes on exchange 5.5..

[janet]

giugiugiu72

I don't know exchange, so my suggestion may be inappropriate, but can you tell exchange to use the sme servers smtp mail server for outgoing mail ie mail.yourdomain.com (on the sme server).


This thread may be of general interest to you (although not the answer to your question), particularly the posts by Gordon Rowell.
http://forums.contribs.org/index.php?topic=35532.0

[mmccarn]

Here's a page from 'GFI' that includes instructions on configuring Exchange 5.5 to relay all outbound email through a "smart host": http://support.gfi.com/manuals/en/msec8/msec8manual-1-21.html

[MSmith]

Isn't SMTP installed by default with Exchange 5.5?  I still have two Exchange 5.5 servers running and they *deliver* outgoing mail via their ISP's SMTP server.  They are not directly exposed on incoming port 25 but instead get their mail from a SME server via the delegate function of the appropriate server-manager panel, which routes the email from SME to Exchange via SMTP.  Works great!  Haven't tried it with fetchmail but I suspect it'd work.  Simpler, though, to just redirect your domain's MX record to the external interface of the SME server.

If your Exchange machine doesn't have "Internet Mail Service" installed, I suspect that's what you'll need to add.

Just for the record, in one of the instances above the SME server is the network's gateway, so it was easy to set up the MX record to point to the SME server's external interface.  The other SME instance is a VMWare appliance running on a Windows 2000 terminal server; this only has one IP address but accepts email just fine via portforwarding from the gateway, processes it for spam & viruses then forwards to the Exchange server.  One fewer box in the server room!

http://www.vmware.com/appliances/directory/1149

[zatnikatel]

what are you still suing something as old as exchange 5.5 i dont think even MS supports it any more as it runs on nt4 server

[MSmith]

Why Exchange 5.5?  Because not every small business feels they need to change what they're doing just because something isn't supported by Microsoft.  (Just for the record, I have *never* called Microsoft for support of *any* of their products.)  Because it still works and meets the needs of the business.  With a SME server in front, intercepting SMTP attacks and processing the incoming stream for viruses and spam, Exchange 5.5 still works just fine.  When there's a compelling reason to change, I'll advise my clients to do so.  One will be changing out this year because they like Trend Micro server-based antivirus and Trend won't be supporting NT 4 past this year; one will be changing out next year as part of an assimilation by a larger company.  Yet a third will be moving to Exchange 2007 in 2009 because we find we need to support a growing number of mobile email users and of course Exchange 5.5 isn't up to the task.  (Many workarounds exist but they want the native functionality and the budget is in place for the specified timeframe.)

"If it ain't broke, don't fix it."  Preventive maintenance, yes ... keeping an eye on the 16-gig maximum store size, yes ... replacing hard drives as needed, yes ... but change without a compelling business case ... no!