This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

v17 MTA Mode Logging Is Severely Broken

Howdy,

The MTA Mode logging in v17 is severely broken.

In a two hour battle trying to get Authenticated Relay working and failing at every step, I managed to break inbound e-mail by removing Allow from Any in the Upstream Relay.

Looking at the e-mail logs, I could only see my outbound messages, with nothing showing for inbound connections.

Knowing this to be completely and utterly incorrect I connected via SSH, dropped to an Advanced Shell and looked at the awarrenmta.log file. Lo and behold, a whole heap of "550 Relay access denied".

Why in <deity's> name is this not presented to the Log Viewer? What is the point of the Log Viewer if it's not going to show me useful troubleshooting information to find out where a potential misconfiguration exists?

Now I'm wondering what else the Log Viewer isn't showing. It sure wasn't of any use trying to debug my Authenticated Relay problems.

Honestly Sophos, either make this stuff visible in the Log Viewer, or publish a comprehensive list of logfiles accessible via Advanced Shell so we can get on and quickly solve problems, rather than chasing our tails for hours on end with incomplete information.

Really getting to the point where I want to throw out all these XG units and replace them with something that works.



This thread was automatically locked due to age.
  • I complained about sophos trying to be extra user friendly by giving friendly error messages during the beta. Its a firewall not an iphone, we need standard errors in logs to troubleshoot. Grepping a log and presenting it in a readable format in gui should be so easy but sophos keeps on bungling it somehow.