"Message to big" warning needs some rounding

Feature requests Completed Features
1

I’ve piped some several thousand real mails that we’ve received in December into Zammad to test how it handles a lot of tickets. Some tickets weren’t accepted because they are too big:

  • ignore message 1/10 - because message is too big (is:10.357551574707031 MB/max:10.0 MB)
  • ignore message 2/10 - because message is too big (is:11.912149429321289 MB/max:10.0 MB)
  • ignore message 3/10 - because message is too big (is:13.995567321777344 MB/max:10.0 MB)
  • ignore message 4/10 - because message is too big (is:16.46129322052002 MB/max:10.0 MB)
  • ignore message 5/10 - because message is too big (is:11.18392276763916 MB/max:10.0 MB)
  • ignore message 6/10 - because message is too big (is:19.377135276794434 MB/max:10.0 MB)
  • ignore message 7/10 - because message is too big (is:11.498958587646484 MB/max:10.0 MB)
  • ignore message 8/10 - because message is too big (is:11.499141693115234 MB/max:10.0 MB)
  • ignore message 9/10 - because message is too big (is:10.004938125610352 MB/max:10.0 MB)
  • ignore message 10/10 - because message is too big (is:13.895692825317383 MB/max:10.0 MB)

Sounds like that error message needs some rounding :slight_smile:

2

This will be covered with the following github issue:

3

Hm, it would be very undesirable in our mail server setup when Zammad would send a bounce mail for mail that is too big :frowning:

I’ve commented the bug to explain why I prefer it the way it currently works. Thanks for the link!

4

Currently you can only get known inside the E-Mail-Account section of such problems:

image
image.png969×168 8.33 KB

Monitoring stays green, that’s not expected. Maybe we should combine this somehow
image

5

Yes, that is a problem. Additionally to the monitoring section of the administration, it might be sensible to show error indicators in some other prominent places, because an error that is only displayed in the monitoring section might be hard to notice. Some ideas:

  • The admin button could show a badge indicating that there is something in the admin area that requires attention. The “Monitoring” navbar entry could then similarly also show a badge, so that the admin can effectively follow the badge trail to the problem.
  • The dashboard could get a new widget that shows monitoring issues. Maybe so that it’ll only ever show up if something is broken, and then with a alarming red background?

Or does the monitoring section already have some kind of indicator? My instance hasn’t had any issues yet, so I can’t be certain :slight_smile:

6

Ummm yes and no.
The indication is “quiet” if not externally monitored.

You can check if healthy is not “true” then something’s wrong.

See: https://admin-docs.zammad.org/en/latest/system-monitoring.html

7

This topic was automatically closed after 416 days. New replies are no longer allowed.