Stuck in Draft (didn't send)

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).

You should at least fix your smtpd_banner
Perhaps this is what’s causing

what else have you done to postfix config?

But it doesn’t. Just as I indicated above (with the normal theme) It adds the “draft” as an attachment - revealed by those . . .. Then I could probably add an additional message (perhaps) and send it. But the user’s message should have gone out without me tampering with it.


No spinning button just

so that points the finger at the Authentic theme (I guess) at least for being stuck with the spinning button of doom.

Still think the “Edit as new” is not doing what it claims to be. It is not allowing full editing of draft or even what is actually needed “sending of draft”

@Ilia did something change in the mail editing UI in the most recent release that would have impacted how editing a message works? I don’t think we need that separate reply section for example…

I would do a test using a VM server with Usermin version 1.861 which has been unchanged for months. If the problem disappears then later versions introduced it. Looking over the changes, there are not many

https://github.com/webmin/usermin/compare/1,861...2,000

How to downgrade to an older version of Usermin (is it even safe to do so) this is a live box with other VS that are not reporting problems. It is only this domain+user (as far as I’m currently aware). I have other boxes all running usermin 2.001 (apparently happily)

I would not do a downgrade in production. you can search for information on the Internet downgrade linux package depending on the operating system.

If you say that you have no problems on two other systems with the same Usermin version, then you should not look for the solution through a downgrade, but rather in the configuration files.

Virtualmin/Webmin/Usermin/Cloudmin were designed to be configured through the UI interface. If files are edited outside the interface, it is possible that these programs do not know about them, or worse, problems occur. Most likely this is also happening in your case.

I recommend everyone to use the etckeeper program that keeps track of the changes in the configuration files, which behaves similar to git.

1 Like

Interesting. I’ve never heard of this but it seems installed by default on my Debian 11 upgraded from 10. Not so on my home 12 that I had to install from scratch when the upgrade path failed.

More learning for ‘old dog’. Seems like a very good addition to backups. Thanks.

Indeed, etckeeper is installed together with the other packages, and appears in the log file of Virtualmin installation. This extremely powerful tool can show you what happens behind the scenes when you save settings in the interfaces *min.

I notice that your operating system is Ubuntu, in order to downgrade you have to find out which package we want to use

apt list -a usermin

Let’s say from the list we want to downgrade to version 1.860

apt install -s usermin=1.860

The -s option simulates the installation but does not do it. If the output is fine, you can run the command without this option.

Yeah, I broke it when adding a new replies functionality. Here is the patch:

Sadly, there is no easy way to combine new reply formatting and draft messages…

I would agree - so a downgrade is not a real option here - even if it really is a Usermin problem.

But deleting the user and starting new still has potential?

But I am pretty certain no configuration has changed on this (or on any other VS on this box) certainly not outside the Virtualmin/Webmin/Usermin GUI - which I trust not to corrupt the configuration files.

So is that the reason it is stuck in “Draft”
or
is that the reason why “Edit as New” includes the message under the . . . and acts like a completely new message" still leaving the message stuck in “Draft”

It’s the reason why Edit as New was edited as a reply.

If it is in production, you can create another email account for testing and see what happens.

If you don’t use etckeeper then I recommend you to use the find command in the /etc directory and look for which files have changed in the last period (1 day, a week, a month) you set the period. Either since you did the last update, you noticed the error…

All *min products are intended to work as delivered. When everyone gets down to business and makes changes to files, it’s natural that issues arise. This forum is full of such situations every day. the bottom line is that some don’t even have a clue about what they are going to get through those changes. For example, Virtualmin is not designed to work with a proxy in front of the webserver and here I have to make custom changes that are obviously not recognized in Virtualmin. If a Re-Check is done on the configuration, it will not find a proper Apache configuration.

Tx @Ilia for fast response. So if I implement the code change in that link. the “Edit as New” will be back to “Editing the Draft” and the “Send button” back to “Send” and in theory it should go out as normal - just like my test messages did?

or should I wait for an update.

I just provided a fix for the draft not being editable.

If there is another bug, you should open a new thread, I think.

OK, that is a solution to question raised by @Jamie above not my OP, which is about the message that never got out of Daft and is still stuck there.

There was a suggestion to “Edit as New” that was indicated might resolve it - but as I said above an inappropriate title on the button when all that is wanted is “Send the draft”

There are separate issues with this user and I have raised them as new topics. Doing so doesn’t seem to really help as they are probably all connected.

I really cannot understand that there is no simple button / method to move a message in “Draft” out and into “Send”. Or why it got stuck here in the first place.