Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛: Many SMTP RCPT TO commands from IP fails to ban #1134

Open
1 task done
tonyhardcode opened this issue Jan 28, 2025 · 1 comment
Open
1 task done

🐛: Many SMTP RCPT TO commands from IP fails to ban #1134

tonyhardcode opened this issue Jan 28, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@tonyhardcode
Copy link

What happened?

I adjusted my Automatic Banning settings to:

Auth failures 10/1 day
Abuse attempts 10/1 day
Loitering 150/1 day

In my Stalwart logs I have 100 lines of variations of this one after another with the same timestamp and IP:

2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"
2025-01-28T07:05:11Z INFO SMTP RCPT TO command (smtp.rcpt-to) listenerId = "smtp", localPort = 25, remoteIp = 180.7.189.51, remotePort = 51465, to = "[email protected]"

But in my Security > Blocked IPs does not list 180.7.189.51

I think the Abuse attempts banning system should catch this correct? I am guessing Stalwart might have an issue with the timestamp all being the exact same time?

How can we reproduce the problem?

I can reproduce the problem by doing the following steps:

Send a lot of SMTP RCPT TO commands

Version

v0.11.x

What database are you using?

RocksDB

What blob storage are you using?

RocksDB

Where is your directory located?

Internal

What operating system are you using?

Docker

Relevant log output

Code of Conduct

  • I agree to follow this project's Code of Conduct
@tonyhardcode tonyhardcode added the bug Something isn't working label Jan 28, 2025
@mdecimus
Copy link
Member

Try setting the log level to trace and please share the full log with the error message that Stalwart is returning to the client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants