Koozali.org: home of the SME Server

dmz with exchange

Karl Ponsonby

dmz with exchange
« on: December 09, 2002, 03:53:03 AM »
Hi,
This may be a silly question and a waste of time, but I will ask it anyway. Want I want to try is to use SME in a dmz situation passing through to an exchange box on the internal lan. I know that this can be done, but what I want to know/try is if there is anyway of pointing IMP to the exchange box (owa is rubbish) ?

Thanks,
Karl

Rob Wellesley

Re: dmz with exchange
« Reply #1 on: December 09, 2002, 02:45:42 PM »
just point all incoming mail to the exchange box by using the email settings in the server-manager

ryan

Re: dmz with exchange
« Reply #2 on: December 11, 2002, 07:10:24 AM »
Regarding using IMP to read Exchange 5.5 email...I do this at work.  I first set up a each user needing IMP on the SME server.  In my case domain is phx2.mydomain.com.  Then set up a new custom recipient (internet email) in exchange administrator.  The internet email address will be the user's email on the sme server....user@phx2.mydomain.com.  (Exchange=mydomain.com...SME is a subdomain).  Now open the properties of the user's standard exchange mailbox.  Under the delivery tab, change it to deliver locally plus forward to the new custom recipient user account.  Last, open the custom recipient user account (with a globe in list) and under the advanced tab, hide this account from the global address book so only a single account will show up for the user.

Your IMP users will then get the all email delivered to Exchange in their Outlook and in IMP.  They will have to clean/expunge frequently, or you will run out of disk space fast.  I suggest quotas.  

I do this in addition to all email going through a different SME prior to Exchange server to filter out the spam.  Works well for me.  

Ryan

Darrell May

Re: dmz with exchange
« Reply #3 on: December 11, 2002, 10:52:40 AM »
Karl Ponsonby wrote:
> but what I want to
> know/try is if there is anyway of pointing IMP to the
> exchange box (owa is rubbish) ?

Hi Karl,

Microsoft Exchange Server is IMAP compliant.  You 'should' be able to configure any IMAP client (IMP) to access the Exchange IMAP server directly.  Start your research here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;189326

Darrell

Karl Ponsonby

Re: dmz with exchange
« Reply #4 on: December 14, 2002, 07:48:55 AM »
hi Darrell,

Thanksyou for you response. After following your post, I went and did some indepth research and discovered the following. It came from a mail-list post, and I thought it may be of benifit to all. It allows a SME with IMP to act as a DMZ mail server and email access to the internal exchange server.
Regards, Karl

2.3.4 How can I use Microsoft Exchange as my IMAP server?
Note: The FAQ maintainer does not use Exchange, or even NT. The following comes from Alex Howansky, a contributor to the old FAQ, and is included with minor editing exactly as he wrote it then.
[IMP 2.2]: First, you must enable IMAP access in the Exchange Administrator. Expand your main container, and click Protocols. Double-click IMAP4. Check the Enable Protocol check box. Jason Haar also suggests unchecking the Enable Fast Message Retrieval check box if you experience problems with missing attachments. If you only want certain users to have IMP access, you can use the Exchange Administrator to disable IMAP for individual mailboxes.

In horde/imp/config/defaults.php3, edit these settings:

   $default->folders   = "";
   $default->sent_mail = "Sent Items";
   $default->postponed = "Drafts";
For the IMP username, use nt_domain\nt_login_id\exchange_alias. If your Exchange alias is the same as your NT login id, you may be able to use just the Exchange alias for the IMP username. Use your NT domain password for the IMP password.

Once logged in, you will have access to all your Exchange data, including calendar, tasks, contacts, etc. You can use the Imp folder management interface to subscribe and unsubscribe from these folders. Exchange serves up everything via IMAP, and IMP will happily display the contents of the non-email folders as if they were email messages. As a result, they aren't terribly useful and not at all editable, but at least you can see some detail.