WatchGuard Firebox2 blocking authenticated SMTP ?

We are running a WatchGuard Firebox2.

Authorised SMTP is being blocked...  
the following is showing up in the logs:

 removing smtp keyword: AUTH = LOGIN
 bad command: AUTH
 bad command: PRIORITY
 etc etc...

Why is this...

How can we configure the firewall so that authenticated SMTP requests pass through?

Thanks.
 
LVL 2
coopaAsked:
Who is Participating?
 
Tim HolmanConnect With a Mentor Commented:
It appears Watchguard's SMTP proxy either doesn't understand AUTH=LOGIN or considers it dangerous.
Whilst trawling through the web, it seemed that Watchguard does not fully support all ESMTP commands, so you may not be able to get AUTH working at all.
Check these links @ Watchguard:

http://wgusers.watchguard.com/archive/wg-users/2001-03/msg00045.shtml
http://wgusers.watchguard.com/archive/wg-users/2000-12/msg00160.shtml

There MAY be support in the future, but it doesn't look like there is currently.

Are you running latest version of firewall software ?

If you have a serial number etc, you can probably log this direct with Watchguard and see if there's a fix / update for this yet, but unfortunately I can't get deep enough into their support pages !
0
 
coopaAuthor Commented:
have added AUTH to list of supported proxys... but still no luck
0
 
Tim HolmanCommented:
Does your SMTP server allow these commands ?
ie - what happens without the firebox in place ?
I don't know these too well - it may just be filtering SMTP AUTH, which is sort of a standard thing SMTP filters/firewalls do
0
Managing Security Policy in a Changing Environment

The enterprise network environment is evolving rapidly as companies extend their physical data centers to embrace cloud computing and software-defined networking. This new reality means that the challenge of managing the security policy is much more dynamic and complex.

 
coopaAuthor Commented:
> Does your SMTP server allow these commands ?
I'm pretty sure it does.. yes.

> ie - what happens without the firebox in place ?
We can't just take it down unfortunately... as it protects the entire organisation... there may be a way to allow my machine to connect to the server without opening up everything.

Thanks for your help.
0
 
Tim HolmanCommented:
What mail server do you use - I'll find this out.
0
 
coopaAuthor Commented:
Microfft exchange server.

Right I have more info on this....

It is DEFINATELY the firewall that is blocking these AUTH requests.

I have opened up all ports between my machine and the mail server and the Authentication process worked fine.  
0
 
Tim HolmanCommented:
Open up TCP/UDP port 113 - I think this is the IDENT port needed for SMTP auth in this case....
Another way to solve problems like this is to look through the log files and work out what's being blocked, destined for or coming from your mail server...
0
 
coopaAuthor Commented:
That port is already open.

the log says the following:
  removing smtp keyword: AUTH = LOGIN
  bad command: AUTH
  bad command: PRIORITY

it seems to be blocking parts of the headers
0
 
coopaAuthor Commented:
Thanks tim,

> Are you running latest version of firewall software ?
Unfortunately not, our maintenance subscription has run out.

Cheers for doing the research though.
0
 
Tim HolmanCommented:
No problem.  Let me know if you need any help with renewals - we're a Watchguard reseller (UK based) - tim_holmanNOSPAM@hotmail.com
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.