Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make "MaxMessageBytes" configurable #1249

Open
AASluke opened this issue Jan 4, 2025 · 0 comments
Open

Make "MaxMessageBytes" configurable #1249

AASluke opened this issue Jan 4, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@AASluke
Copy link

AASluke commented Jan 4, 2025

Hi, new user here
I am self hosting using docker. For me the SMTP listener feature is exceptionally useful. But the message size seems to have a hard limit of 1048576 bytes, which I bumped into during first tests with my openmediavault instance:

2025-01-03T22:52:40+0100 omv1 postfix/pickup[158966]: 7343780570: uid=0 from=<root>
2025-01-03T22:52:40+0100 omv1 postfix/cleanup[169905]: 7343780570: message-id=<20250103215240.7343780570@omv1.local>
2025-01-03T22:52:40+0100 omv1 sudo[25336]: pam_unix(sudo:session): session closed for user root
2025-01-03T22:52:40+0100 omv1 postfix/qmgr[2428]: 7343780570: from=<omv1@ntfy.local>, size=2448907, nrcpt=2 (queue active)
2025-01-03T22:52:40+0100 omv1 postfix/smtp[169916]: 7343780570: to=<omv1@ntfy.local>, relay=192.168.10.10[192.168.10.10]:8283, delay=0.05, delays=0.04/0.01/0/0, dsn=5.3.4, status=bounced (message size 2448907 exceeds size limit 1048576 of server 192.168.10.10[192.168.10.10])
2025-01-03T22:52:40+0100 omv1 postfix/pipe[169915]: 7343780570: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.07, delays=0.04/0.01/0/0.03, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)
2025-01-03T22:52:40+0100 omv1 postfix/cleanup[169905]: 808818059A: message-id=<20250103215240.808818059A@omv1.local>
2025-01-03T22:52:40+0100 omv1 postfix/bounce[169920]: 7343780570: sender non-delivery notification: 808818059A
2025-01-03T22:52:40+0100 omv1 postfix/qmgr[2428]: 808818059A: from=<omv1@ntfy.local>, size=2326, nrcpt=1 (queue active)
2025-01-03T22:52:40+0100 omv1 postfix/qmgr[2428]: 7343780570: removed
2025-01-03T22:52:41+0100 omv1 postfix/smtp[169916]: 808818059A: replace: header Subject: Undelivered Mail Returned to Sender: Subject: [omv1.local] Undelivered Mail Returned to Sender
2025-01-03T22:52:41+0100 omv1 postfix/smtp[169916]: 808818059A: to=<omv1@ntfy.local>, relay=192.168.10.10[192.168.10.10]:8283, delay=1, delays=0/1/0.01/0, dsn=2.0.0, status=sent (250 2.0.0 OK: queued)
2025-01-03T22:52:41+0100 omv1 postfix/qmgr[2428]: 808818059A: removed

The message size 2448907 exceeds size limit 1048576 of server 192.168.10.10 (which is the server my ntfy instance is running on). Therefore the ntfy server does not accept it and the message is bounced.
I not a software engineer and spent some time to figure this out - I think here is where this comes from.

So my

💡 Idea/Proposal

is, to add SMTPServerMaxMessageBytes as a configurable value to the config file with the default value, it is currently fixed at.
This way, we could configure it just as other parameters to accept SMTP messages with more than 1MB.

💻 Target components

ntfy server

Looking forward to hearing what you think!

@AASluke AASluke added the enhancement New feature or request label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant