These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Notification of emails in Postfix queue on the new forum.
Web Hosting and Cloud Computing Control Panels
I found this under Postix General Options:
"Time in hours before sending a warning for no delivery"
I set this to 4 hours and the saved it. When I returned to the menu the option setting was blank. As if it didn't accept the change.
Ok, I see that it relates to the delay_warning_time directive which as I mentioned doesn't seem to stick. What other options must be changed as well to inform the sender?
If making a change in the Postfix module doesn't "stick", as you say, then it's a bug. File a ticket, and it'll get fixed.
--
Check out the forum guidelines!
What if I added it manually to the main.cf file? What is the exact syntax then.
delay_warning_time = 4h (this is just a guess)
Are there any directives that need modification?
Yes. That's correct. I don't think there are any other changes needed.
In the main.cf the comment for this option is:
# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h
So, I'd say that'll do it. (Restart postfix after, of course.)
--
Check out the forum guidelines!
Well this is interesting. When I add the line "delay_warning_time = 4h" to main.cf and return to the General Options GUI it is disabled. If I re-enable then the directive is deleted from main.cf.
Perhaps there are other directives that need modification for this to work. main.cf is the default from from the original install.
<div class='quote'>When I add the line "delay_warning_time = 4h" to main.cf and return to the General Options GUI it is disabled. If I re-enable then the directive is deleted from main.cf.</div>
Bug. File a ticket.
<div class='quote'>Perhaps there are other directives that need modification for this to work.</div>
I don't understand what you mean? The GUI is wholly separate from the functioning of the mail server. You've found a bug in the GUI. The workaround is to edit the file directly (and file a bug in the tracker, so the GUI can be fixed).
--
Check out the forum guidelines!
The issue came down to simply labeling I believe. If "Disabled" is on and a value is in the field it really doesn't mean that the directive is not enabled. It is in fact enabled with the said value.
Finally read Jamie's email on this ticket. He points out that is should read "Default".
Yep, and he's applied a patch for the next Webmin release, so this mislabeling will be fixed soon.
--
Check out the forum guidelines!