I'm trying to ask in the "Tor Stack Exchange Q&A Site" about Signaled readiness to systemd... but always count my question as spam while it is not...

my question body : https://pastebin.com/tTEh3Szs

  • 3
    Spammers often leave email, so likely the email triggers the alert. Unless vital to the question, remove it. May 13, 2023 at 18:24
  • @Joachim no offense to Adam but that is a pretty useless duplicate target.
    – rene
    May 13, 2023 at 18:51
  • @rene Yeah, but among all the similar questions this one at least makes an attempt to give an answer applicable to all situations. I don't think we need a question like this for every specific scenario and site. There is this Q which is also used to link closed questions to, but it's even less useful (no offence to Shog9). And the proposed Q's answer also explains why the spam filter can't be more specific.
    – Joachim
    May 13, 2023 at 18:57
  • @Joachim well, we need a FAQ then where you can compile all answers I've written for these type of questions. I need the rep.
    – rene
    May 13, 2023 at 19:01
  • @rene I never intended to deny you that rep. The first thing I noticed was that you need the rep.
    – Joachim
    May 13, 2023 at 19:02

1 Answer 1


Your body starts like this:

Hello everybody,
Tor isn't fully starting nor bootstrapping! due to **Signaled readiness to systemd...**
and connections keeps on throwing time-out errors...
**journalctl -xeu [email protected]**:
May 13 20:34:56 ZDei systemd[29470]: [email protected]: Executing: /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/

Here are the things to try:

  • We don't need opening statements. Remove Hello everybody,
  • Don't do **Signaled readiness to systemd** inline. Instead make it a proper quote by having it on a new line (empty line before it) that starts with a > followed by a space and then a new blank line following it.
  • Don't end a paragraph with multiple periods ...
  • Headers are created with the hash character. Instead of **journalctl -xeu [email protected]**: do ### journalctl -xeu [email protected] followed by a blank line.
  • Code blocks should always start with a blank line before the code fence and end with a blank line after the last code fence.
  • Spammers often leave email, so likely the email triggers the alert. Unless vital to the question, remove it.1

Generally: you have a lot of "code" / logfile with little other substance. Are you sure everyone needs all of that to diagnose your issue? Reducing the overall length of the post is advised when you run into the specific error you face.

If that doesn't solve the issue, copy everything out and add it back piece by piece, checking each time if you fulfill the quality requirements.

1. thanks to Shadow The Spring Wizard for providing that tip


Not the answer you're looking for? Browse other questions tagged .