Issue with MailEnable MAPI and Untangle

[bruce2400]

I am having a problem with MailEnable MAPI and Untangle. MailEnable support has helped me as far as pointing a finger at Untangle saying that is the issue but can’t assist me any further. MailEnable MAPI is a feature in the Enterprise Premium Service to enable Calendar, Contact and Task Sharing here is a link to their site mailenable.com/premium-edition.asp

I did setup syslog and when set to informational I can see the log of the computer trying to contact our Mail Server however Untangle doesn’t seem to be blocking anything. Here is the log.

06-15-2010 15:19:54 Local6.Info 192.168.68.2 Jun 15 15:19:51 untangle.globaljet.gjs uvm[0]: PipelineStats # endpoints: create-date=Tue Jun 15 15:19:51 EDT 2010, session-id=1984645095, protocol=TCP, policy=Default Rack, client-iface=inside, client-addr=192.168.50.72, client-port=2246, server-addr= xxx.xxx.xxx.xxx, server-port=143, server-iface=inside, client-addr=192.168.50.2, client-port=37567, server-addr= xxx.xxx.xxx.xxx, server-port=143 # stats: raze-date=Tue Jun 15 15:19:51 EDT 2010, c2pBytes=1347, p2sBytes=1347, s2pBytes=14177, p2cBytes=4161, c2pChunks=9, p2sChunks=9, s2pChunks=21, p2cChunks=12, uid= #

Also tried it on a different computer on a different network here is that log.

06-15-2010 15:52:45 Local6.Info 192.168.68.2 Jun 15 15:52:42 untangle.globaljet.gjs uvm[0]: PipelineStats # endpoints: create-date=Tue Jun 15 15:52:41 EDT 2010, session-id=1984647356, protocol=TCP, policy=Default Rack, client-iface=inside, client-addr=192.168.68.57, client-port=59768, server-addr= xxx.xxx.xxx.xxx, server-port=143, server-iface=outside, client-addr=192.168.68.57, client-port=59768, server-addr=xxx.xxx.xxx.xxx, server-port=143 # stats: raze-date=Tue Jun 15 15:52:42 EDT 2010, c2pBytes=1347, p2sBytes=1347, s2pBytes=13892, p2cBytes=4160, c2pChunks=9, p2sChunks=9, s2pChunks=22, p2cChunks=12, uid= #

Since MAPI uses IMAP protocol is there some setting inside Untangle that I am missing or does a port forward rule need to be setup?

[sky-knight]

It probably has something to do with the anti-spam filter.

How do I get around this issue?

I have a rack called "mail" that all inbound requests for pop3 and imap are routed to. Because the mail server is protected on the SMTP side on the way in, I see no point in scanning the messages a second time on the way out to the client.

In short, you why are you even passing the pop3/imap traffic into the spam module? Assuming untangle is protecting your SMTP server on the SMTP side... the filtering is already done.

[bruce2400]

The only thing is I am not using the Anti-spam in Untangle, I actually don't even have it loaded in the rack. Our email/web server is hosted by Liquid Web and has it's own Spam filters loaded in MailEnable. I have gone as far as setting up on my internal network a laptop with Outlook and this MAPI and connected it directly to the router bypassing Untangle completely and I get no errors when using the MAPI portion of Outlook.

Is there anyway to tell Untangle to bypass all IMAP traffic?

[bruce2400]

Well after posting the last message I decided to stop all the services running in the Rack and Untangle Box crashed. I unplugged it and plugged it back in and logged in, everything in the rack was stopped. I checked the MAPI and it was working great. I slowly turned each service in the rack on, one by one testing the MAPI the entire time and sure enough all the services are running in the rack and the MAPI is still working great so not sure if something went wrong and after the crash it got reset but everything is working now.