Watchguard Stopping mail to certain domains.

OK, just so you know, the HTTP service has a content filter. This was some how affecting mail leaving site because as soon as I turned it off

I have now allowed all content types through as there is no way of telling what the particularly relates to?

Thank you

Brian simps> I have used a Watchguard Firebox III for two years and just recently i

I came across something interesting, and wanted to ask people who probably know more than I do...

We have a number of websites hosted on one IIS server, running via Hostheaders (as in, more than one website on the same server, therefore, the same IP address). For testing purposes, I have a PC running EZ-Firwall

The FIRST site accessed running on a given server works fine.

The second site running on that same server, if 3rd party cookies are being blocked, will have it's cookies blocked. I know that because the Site List on the Privacy tab shows the sitename of the first site only. (This also happens across sessions).

In other words, somewhere in Zonealarm, it's remembering the domain name of the first site, associating it with the IP, and assuming any other site coming along won't have the same IP... Except in the case of multiple sites on one server (therefore one IP) won't work, except for the very first one accessed. (ZoneAlarm Pro v5, session and persistent cookies allowed, 3rd party, web bugs, and private header info blocked).

Any opinions on this theory, from people more versed in ZA? And is there a way around it?

Thanks for the reply.

I have checked the ports and they are correct as per their protocol.

I am viewing the email using Outlook 2003.

This has only happened since a new Watchguard went in and replaced the old one. The email server hasn't been touched for months and worked fine with the old watchguard.

The Watchguard support hasn't been able to find out why this happening. They have checked settings and believe everything is set up correctly.

Thanks

Brian. Leythos wrote:

I'm still confused:

I use the HTTP Proxy service to filter content out of outbound HTTP Sessions and don't see this problem.

What version of WSF are you running?

What specific firewall appliance do you have?