coopa
asked on
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.
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.
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
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
ASKER
> 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.
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.
What mail server do you use - I'll find this out.
ASKER
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.
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.
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...
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...
ASKER
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks tim,
> Are you running latest version of firewall software ?
Unfortunately not, our maintenance subscription has run out.
Cheers for doing the research though.
> Are you running latest version of firewall software ?
Unfortunately not, our maintenance subscription has run out.
Cheers for doing the research though.
No problem. Let me know if you need any help with renewals - we're a Watchguard reseller (UK based) - tim_holmanNOSPAM@hotmail.c
ASKER