I configured my xg firewall vm with version 18.0.4 MR4 as smtp mail gateway, it worked fine for about 1 month, and now its not showing any log in Email > Mail Log section but the email are going and entering normally. this is what i got from the smtpd_main.log:
I Also have another question when the mail log was working i was only able to see incoming emails why couldn't i see outgoing ones ?
THANKS COMMUNITY !!!!!!!!!
Hi Youcef Rahmouni,
Thanks for reaching out to the Community!
Try adding "-f" with the tail command:
Community Support Engineer | Sophos Technical SupportSupport Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts If a post solves your question use the 'Verify Answer' button.
It shows the same thing :
Hi Youcef Rahmouni,
Thanks for the update.
Did you configure SMTP deployment mode in MTA? If yes, did you configure the SMTP route & scan policy under Policies & exceptions? To see the logs, you'd have to configure the email protection policies for your domain.
Also, check out the following document for Log file details.
yes i configured SMTP deployment mode in MTA and yes i configured route & scan policy under Policies & exceptions and it worked perfectly for about one month.
Could you please double-check the email protection license at Administration > Licensing > Module subscription details?
Additionally to what my co-worker Harsh has mentioned, double-check that you didn't create a DNAT rule with service set as ANY as this will bypass the MTA, right now the SMTPD is basically for an email to arrive at it, however, if you have DNAT the email can potentially still be delivered but the SMTPD log won't show any entry.
for the email protection license its active, and for the DNAT i don't have any DNAT set to service any and still no mail logs are showing.
Thank you, we have sent you a PM, please take a look.
This issue got solved by removing an incorrectly configured DNAT rule, (DNAT rules with email-related services such as SMTP and SMTPS bypass the MTA mode) and re-creating the default MTA rule by changing from MTA to Legacy and back to MTA, so the system could rebuild the MTA default Firewall rule.