Scheduled reports failed to generate

Hi Ian,

Please open a support case so that we can resolve this matter for you.  

Hi Rob,

I am a home user, so support is not available to other than through the various forums.

Ian

Failed again this morning. I will try restarting the XG to see if that fixes the issue.

Ian

Well, that was a total failure. XG failed to restart correctly, locked up the external interface and would not handout DHCP addresses.

Restarted by pressing the reset button, again locked up the external interface and did not hand out IP addresses.

Removed power for a short while and the XG is back online, but still no reports.

Ian

Tried sending a manual backup this morning and received the following error message - unable to send due to incorrect server setup. Which server?

This was working before I upgraded to the GA.

Ian

further testing and nothing about smtp/s shows in the logs or reports.

more testing - I can send test emails from XG, but not backups or reports.

Tried sending a manual backup this morning and received the following error message - unable to send due to incorrect server setup. Which server?

This was working before I upgraded to the GA.

Ian

further testing and nothing about smtp/s shows in the logs or reports.

more testing - I can send test emails from XG, but not backups or reports.

Hi,

Thank you for the feedback. The issue is not reproducible in our lab. I would request appliance access on PM.

Regards,

Deepti

Hi Deepti,

PM sent with details.
Ian

Hi,

this morning the two daily reports were delivered, but no backup.

Ian

All automatic reports and backups are working again.

Ian

What changed Ian?

I changed the configuration of the server which worked previously, so there was some tightening of the function in the GA release. The change did not work for the automatic generated reports, just the test reports. The error report when trying to create a manual mail backup cleared again after something besides my change was run.

The Development team logged into my XG and changed the access method to SSH, so what additional changed they made i have no idea about?

Ian

I removed the ssh access yesterday and it is back today, so I assume and hope the Dev team is looking around inside my XG?

Ian

Hello Ian,

We have probed the appliance and interestingly we found the system generated notifications dated from 1st December to 4th December were rejected by the mail server classifying them as spam. We see mail send works right after then.

Dec 0X 0XX:XX:26 MAIL_SEND: Values-->

 Mail Server: --> smtp.t*l*r*.com

 Mail From: --> *more*se@*bigp*com

 Mail To: --> i*more*se@bigp*.com

 Subject: --> Backup for SFV*57

 Hostname: --> S*p*o*

MailBodyPath: -->

 Username: -->

 MailAction:--> 0

 SMTPSecurityMode:--> 2

 SMTPCertificate:-->App*nceC*cate

 Appliance IP(LAN):-->

Dec 04 09:37:27 Mail could not be sent to i*more*@big*.com

Dec 04 09:37:27 Unable to send Mail : Server error:Expecting code :'250' but server responds with:'550 5.7.1 *C30*70* Message content rejected due to suspected spam. OB703^M

There could be many reasons why did the mail server might have rejected the mails by classifying them as spam. 

1) the public IP of your network might trapped in to any RBLs (Blacklisting service) during that time

2) the PTR/SPF record might not mapped correctly... 

you may check health of your public IP using https://mxtoolbox.com/blacklists.aspx. 

Hi UTMGeek,

thank you for the detailed investigation. The issue was only with the XG, not the users. User mail went trough without errors, while the XG daily reports were failing to send.

Ian