Stuck in Draft (didn't send)

SYSTEM INFORMATION
OS type and version Ubuntu Linux 22.04.3
Webmin version 2.101
Usermin version 2.001
Virtualmin version 7.7
Theme version 21.04
Package updates All installed packages are up to date

An email composed using Usermin yesterday.
was scheduled too be sent (so went into “Draft” ?)

mail was not delivered to external recipient who is in address book (has received other emails in the past ok)

mail is still sitting in “Draft”
I can’t see option (don’t know how) to flush it out to be sent late.


also don’t know why it did not get sent on schedule.

PS. just gone in as user and tried sending a test email to myself. Everything ok up to clicking on “send” (no attempt to schedule) it has also gone to draft (very quickly) and then remained stuck on page with the “Send” button “not allowed”

Did you edit as new?

No. Is that what it means?
Ill try and see if that sends it out.

Not what I expected! That shows the original mail as a included/attached message with the space open for a new message (as if it is a forward) not only that it gets stuck in swirling circle of doom mode when I try to send.

did you click the arrowed button ?
image
to see what the schedule shows I guess.
TBF I don’t get this problem sending scheduled mail, when I send one a green box appears at the bottom of the screen confirming that the message has been scheduled

Check Webmin error log and server mail logs to get more details.

Also, check browser’s console for specific errors.

I didn’t. But I believe that is what was checked by the usermin user for the first message that got stuck in draft (and still is)

However. That “please ignore this is a test” message that I did without scheduling did eventually get out of draft and that stuck spinning “send” button did eventually go - or at least give up. It has not appeared in the Sent folders. But it has probably disappeared due to logging in to usermin afresh today and browser refresh.

Lots in /var/log/mail.err
All the same (just different dates) Aug 12 10:43:44 tor postfix/smtpd[1528778]: fatal: bad string length 0 < 1: smtpd_banner =

Nothing in /var/log/mail.warn

lots today in /var/log/mail.log but only since logging in today -
a sample:
Aug 12 11:01:40 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 11:02:03 tor postfix/smtpd[1532036]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 11:02:04 tor postfix/smtpd[1532038]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 11:02:04 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1532036 exit status 1 Aug 12 11:02:04 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 11:02:05 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1532038 exit status 1 Aug 12 11:02:05 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling

As I’m newly logged in I’ll leave that to look at with another test message. I didn’t think of that at the time.

I wonder, if you switch to Gray Theme in Usermin and try to send the mail, do you get any additional error messages?

How? Don’t see that option. I assume that will only affect me signed in as that particular user on that VS and not cause suprises to othe VS and users on this box?

You need to go to Webmin ⇾ Usermin Configuration: Available Modules first to enable Change Theme module and later change the theme from within Usermin using Usermin ⇾ Change Theme page.

Is Dovecot running without errors? Check your logs for Dovecot errors as well.

You may want to restart dovecot to see if it will spit anything out related to your warning messages.
It could be the issue, or even resolve it.

Thanks @Ilia not been there before. Done and restarted Usermin.
Logged in as the user, and

but only options are:

  • Global usermin default
  • Authentic Theme
  • Framed Theme

No Gray Theme

Yes it is running.
but /var/log/dovecot.log
is empty

should be in mail.log or even syslog just type dovecot in search

Do a restart on dovecot and check those logs after for any errors when starting up.

edit: sorry I meant syslog

Try Framed Theme instead.

OK everything looks different - no surprise there
That first message is still in “Draft”


Still can’t see how to send it.

Edit as new just creates a new email and adds the draft as an attachment - that is not any use. I simply want to make the draft “Sent”

I would go with edit as new message, this is the way you would do it in thunderbird, as a side note I sent a test message on a schedule it worked perfectly and at the exact time maybe you have other issues

Done → no obvious problem.

/var/log/syslog
Aug 12 16:14:47 tor systemd[1]: dovecot.service: Consumed 29.680s CPU time. Aug 12 16:14:49 tor systemd[1]: /lib/systemd/system/clamav-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Aug 12 16:14:50 tor systemd[1]: Starting Dovecot IMAP/POP3 email server... Aug 12 16:14:50 tor dovecot: master: Dovecot v2.3.16 (7e2e900c1a) starting up for imap, pop3 (core dumps disabled) Aug 12 16:14:50 tor systemd[1]: Started Dovecot IMAP/POP3 email server. Aug 12 16:14:52 tor systemd[1]: /lib/systemd/system/clamav-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Aug 12 16:14:54 tor postfix/smtpd[1565417]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:14:55 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1565417 exit status 1 Aug 12 16:14:55 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:15:01 tor CRON[1565564]: (root) CMD (/etc/webmin/status/monitor.pl) Aug 12 16:15:17 tor systemd[1]: /lib/systemd/system/clamav-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Aug 12 16:15:23 tor postfix/smtpd[1565847]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:15:23 tor postfix/smtpd[1565846]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:15:24 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1565847 exit status 1 Aug 12 16:15:24 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:15:24 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1565846 exit status 1 Aug 12 16:15:24 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:15:55 tor postfix/smtpd[1566022]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:15:56 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566022 exit status 1 Aug 12 16:15:56 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:16:10 tor dovecot: pop3-login: Disconnected: Connection closed: SSL_accept() failed: error:0A000076:SSL routines::no suitable signature algorithm (no auth attempts in 2 secs): user=<>, rip=45.33.94.72, lip=138.197.146.82, TLS handshaking: SSL_accept() failed: error:0A000076:SSL routines::no suitable signature algorithm, session=<aLnAJbwCSO4tIV5I> Aug 12 16:16:24 tor postfix/smtpd[1566180]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:16:24 tor postfix/smtpd[1566179]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:16:25 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566180 exit status 1 Aug 12 16:16:25 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:16:25 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566179 exit status 1 Aug 12 16:16:25 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:16:56 tor postfix/smtpd[1566181]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:16:57 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566181 exit status 1 Aug 12 16:16:57 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:17:01 tor CRON[1566183]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 12 16:17:25 tor postfix/smtpd[1566189]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:17:25 tor postfix/smtpd[1566188]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:17:26 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566189 exit status 1 Aug 12 16:17:26 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:17:26 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566188 exit status 1 Aug 12 16:17:26 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:17:57 tor postfix/smtpd[1566360]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:17:58 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566360 exit status 1 Aug 12 16:17:58 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:18:04 tor systemd[1]: /lib/systemd/system/clamav-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Aug 12 16:18:26 tor postfix/smtpd[1566625]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:18:26 tor postfix/smtpd[1566624]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:18:27 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566625 exit status 1 Aug 12 16:18:27 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:18:27 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566624 exit status 1 Aug 12 16:18:27 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling Aug 12 16:18:59 tor postfix/smtpd[1566826]: fatal: bad string length 0 < 1: smtpd_banner = Aug 12 16:19:00 tor postfix/master[1460844]: warning: process /usr/lib/postfix/sbin/smtpd pid 1566826 exit status 1 Aug 12 16:19:00 tor postfix/master[1460844]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling

That looks like a bug! Editing draft as new shouldn’t create a reply, right @Jamie?

But what happens when you compose and then send the new message?

No, edit as new should allow full editing of the draft (not replying to it).