SMTP security server not dequeuing

[osterber]

Help! I've got a problem where my NGX R65 is not dequeuing messages.

Background -- I'm working on upgrading (by complete replacement) a NG firewall with a NGX R65 firewall. I will ultimately be on a VPN-1 UTM license. Right now, I'm on a demo license.

What happens is that all of my inbound and outbound mail is just getting stuck in the $FWDIR/spool directory (lots of files named R* in there), and are not getting sent to their destination.

What I've noticed is that the mdq process is not running. There's also no fwssd process running.

I'm not using a content checking filter. I'm just using the security server to take mail from our DMZ mail server, and route port 25 on the firewall to our inside mail server.

What am I doing wrong? This works just fine on NG!

-Rick

[osterber]

I've also tried "fw mdq" as I've seen instructed elsewhere... but that just gives me a help screen, suggesting that it's an invalid parameter to the "fw" command.

-Rick

[osterber]

I've now found this in my $FWDIR/log/mdq.elg file:

mdq_is_installed: No profile is defined
mdq_is_installed: no rule has smtp resource

Huh? I've got two SMTP resources being used in the rule set... an inbound and an outbound? Any ideas why it thinks I have none defined?

-Rick

[chillyjim]

Must be a day for e-mail problems...

I turned off SMDF this morning for some debugging then e-mail stopped coming in (Not the problem I was debugging). Turning SMDF back on e-mail came back.

I don't know if it was the problem or not, but it worked for me.

[osterber]

Resolution -- This turned out to be a problem fixed by hotfix sk33153 (a problem with disabled rules). I ended up just deleting my disabled rule, and everything is back to normal.

-Rick

[chillyjim]

BTW, I just checked and this problem is fixed with R65_HFA01 due out any day now

[JohnMH]

The quick fix for this is to place the smtp resource rule as the first rule in the rulebase... we had this months ago.

R65-HFA02/HFA01 fixes this..

John

[pabouk]

I have seen one installation where the problem was originally solved by installing a hotfix but now the problem reappeared after installing HFA_02. Have you seen something similar?