docker-mailserver: bug report: setup script alway fail with "setup email list" related on the user name

πŸ“ Preliminary Checks

  • I tried searching for an existing issue and followed the debugging docs advice, but still need assistance.

πŸ‘€ What Happened?

I don’t make sure this is really related on the username but:

j5 is ok

setup email add j5@example.com x
setup email list
* j5@example.com ( 0 / ~ ) [0%]

but j5v is not ok

setup email add j5v@example.com x
setup email list
[  ERROR  ]  Supplied non-number argument '' to '_bytes_to_human_readable_size()'
[  ERROR  ]  Aborting
[  ERROR  ]  Supplied non-number argument '' to '_bytes_to_human_readable_size()'
[  ERROR  ]  Aborting
* j5v@example.com (  /  ) [%]

πŸ‘Ÿ Reproduction Steps

No response

πŸ‹ DMS Version

v13.3.1

πŸ’» Operating System and Architecture

Linux docker-mailserver-7b4bd5cdf9-n5vk9 5.15.0-205.149.5.1.el8uek.x86_64 #2 SMP Fri Apr 5 12:44:45 PDT 2024 x86_64 GNU/Linux

βš™οΈ Container configuration files

I guess this is not a bug related on configuration file but if you want, I'll put my configuretion file here.

πŸ“œ Relevant log output

This is not an error of e-mail server.

Improvements to this form?

No response

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 22 (10 by maintainers)

Most upvoted comments

I will have a look at this later today, just FYI.

FYI: This is now a blocker for v14.0.0 - I thought it’d be good to resolve this before we release v14.0.0.

Be more specific:

You are doing something differently than reported if you still experience this issue. We need more context to know where that problem is though.

So the email address must be strongly secret.

For this then, keep in mind that you’ll have only lowercase letters (due to planned normalization with DMS) and numbers, 36 values (aka base 36).

To avoid malicious abuse from guessing this by sending mail to many addresses, you would want this suffix to have plenty of entropy. The same advice for the passphrase would work here (eg: wordpress.detailed-snail-summons-slim-lab-coat@example.com, but obviously don’t use the same value as a password).

The equivalent with base 36 is roughly 47-bit (log2(36^9) = 46.53) and would look like wordpress.zqy2cs5c5. If my math is right, that would require sending over 250k email addresses every second 24/7 to reach halfway of the possible email addresses (((36^9 / 250e3) / (60*60*24*365)) / 2_) within the same 6 years target (this assumes they already know the wordpress. part). There’s over 100 trillion possible values in 36^9.

log2(52^8) (upper + lowercase letters) as shown in the image example from WP is 45.6 bits of entropy, so this is roughly equivalent of what they’re suggesting. For another point of context log2(36^7) = 36, just dropping down to 7 characters from 9 is now 36-bit, and if the attacker could only send at a much slower rate of 5k mails per second constantly, that 50% point (average rate of guessing successfully) is now 90 days (((36^7 / 5e3) / (60*60*24)) / 2).

Hope that helps translate the WP advice to adjust for security equivalence in DMS πŸ‘

The write of the article write and submit the text of the article to a specific (veriy secret) e-mail address. Apart from that, WordPress checks for new emails triggered by cron and publishes the body text as an article. So DMS is used for just e-mail spooler.