100% CPU usage if wrong port is specified in email settings #3527

New Issue

MrUnknownDE · 2026-04-06T04:57:40+02:00

MrUnknownDE commented

2026-04-06 04:57:40 +02:00

Originally created by @rcdailey on 2/23/2019

In the /admin page, I set up SMTP Email Settings to use smtp.gmail.com with port 465. With this port, sending invitation emails resulted in the app being hung at this step:

[lettre::smtp::client][DEBUG] connecting to 173.194.200.108:465

(IP address above was different, but the log was the same)

Apparently the TLS port must be used in this case: 587. I also noticed 100% CPU usage by bitwarden_rs on Linux (Docker) when an invitation email was sent while using port 465. I had to kill the service and restart to stop the issue.

I expect the CPU usage to not be so high in this scenario, and for there to be some timeout or error to handle the bad port case, if possible.

*Originally created by @rcdailey on 2/23/2019* In the `/admin` page, I set up SMTP Email Settings to use `smtp.gmail.com` with port `465`. With this port, sending invitation emails resulted in the app being hung at this step: [lettre::smtp::client][DEBUG] connecting to 173.194.200.108:465 (IP address above was different, but the log was the same) Apparently the TLS port must be used in this case: `587`. I also noticed 100% CPU usage by `bitwarden_rs` on Linux (Docker) when an invitation email was sent while using port 465. I had to kill the service and restart to stop the issue. I expect the CPU usage to not be so high in this scenario, and for there to be some timeout or error to handle the bad port case, if possible.

MrUnknownDE closed this issue

2026-04-06 04:57:40 +02:00

Sign in to join this conversation.

No Label troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting troubleshooting

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#3527