# Sidekiq TCP-fout opgelost door poort 587 te gebruiken (niet 25)

**URL:** <https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275>\
**Category:** Self-hosting\
**Created:** [11 november 2022 om 04:38 UTC](https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275 "2022-11-11T04:38:32Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [13 november 2022 om 06:59 UTC](https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275/11 "2022-11-13T06:59:10Z")

</div>

So with iptables / ufw you tend to block incoming traffic, but the error is about outgoing traffic from your server to [mailersend.net](http://mailersend.net).

But that is not your issue.

Port 25 is not being used for _relaying_ emails (as opposed to delivering them) nowadays. Instead, most email services use port 587, and when I google for the mailersend documentation it indeed tells you to use port 587, not port 25.

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275)._
