You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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!
The text was updated successfully, but these errors were encountered:
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:
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!
The text was updated successfully, but these errors were encountered: