I’m gonna be honest here, I have no clue how to word this thread, or what I need to provide to receive help. All I know is that Discourse sent 18K+ emails and failed to send 7K+ emails (after my Amazon SES was frozen for having such a high bounce rate ~%20). It also looks like its still trying to se…

You can see what’s got it open. You didn’t install a name server, so that’s probably the culprit. You need to spin up a new server and move there. You cannot know what is on the server. Everything is suspect.

My guess is that email or redis was broken for a long time and today it got fixed and sent out a bunch of queued up mail. You can look at admin, email, to see what it sent.

There’s only been 23 emails sent ever when I go there. EDIT: The day of this happening was the April 10th (just now figured out it was discourse that sent the emails), and there’s not a single email on there from the 10th.

Then something else sent the emails. That’s the best explanation.

What would’ve, I don’t run anything else on the server but discourse, could I have been attacked or something?

Also just found this, under the retries tab on the Sidekiq dashboard, the arguments are all something like this: {"type"=>"digest", "user_id"=>11, "current_site_id"=>"default"}

Perhaps someone got your smtp password and sent from somewhere else? Perhaps they hacked your server (is it protected by a password and you don’t have fail2ban?). Something like that. There’s pretty much zero chance that Discourse has anything to do with it. You should probably set up a new server…

[imagen] pfaffman: Perhaps they hacked your server That’s what I thought, so I went and checked the last login into it, and it was from me in March.

It may be surprising, but it’s not hard to edit logs. Or install a root kit that does it. The addresses you’re sending to don’t exist in discourse, right? So it didn’t send the messages. It’s almost certain that you’ve been hacked. Do you log in with a password? Do you have fail2ban? Google for h…

The only other port than 22, 80, and 443 that’re open is 53. And I don’t know what fail2ban is, but I’ll look into it and try to increase security. I assume I should go ahead and close port 53?

What about the backup files, are they okay to import there?

¿Discourse envió 18K+ correos? O, mi servidor fue hackeado

Soporte

BobHill74 (200Tigersbloxed) 18 Abril, 2020 00:43 5

¿Qué podría haber pasado? No ejecuto nada más en el servidor aparte de Discourse. ¿Podría haber sido atacado o algo así?

Tema		Respuestas	Vistas
Discourse not sending Emails Support unsupported-install	11	1145	24 Junio 2022
Email failed jobs Support	7	188	4 Marzo 2025
Severe Email Issue since last update a couple days ago - 3.4.0.beta4-dev Support	25	472	16 Febrero 2025
SMTP failure not reported and too many login attempts on backlog clearing Support	23	9938	22 Diciembre 2022
Extreme memory usage due to bad mail credentials Self-hosting server-resources	16	1125	16 Noviembre 2022

¿Discourse envió 18K+ correos? O, mi servidor fue hackeado

Temas relacionados