# My relay stopped working, how to fix? \[timeout on IMAP connection after CAPABILITY\]

**URL:** <https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369>\
**Category:** Chatmail Relays\
**Tags:** open-standards, bug, chatmail\
**Created:** [June 5, 2026, 12:53pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369 "2026-06-05T12:53:14Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![f7n5xmavu](https://forum.delta.chat/letter_avatar_proxy/v4/letter/f/85f322/32.png) [@f7n5xmavu](https://forum.delta.chat/u/f7n5xmavu)\
**Post date:** [June 5, 2026, 12:53pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/1 "2026-06-05T12:53:14Z")

</div>

Hosted a relay to avoid censorship in Russia and keep in touch with family.  
Configured domain, deployed chatmail relay on VPS in Russia, never touched.

Today (5 Jun 2026) it stopped working (either when connect from within Russia, or outside): status “connecting” in app, messages not delivered.

- `https://chat.*domain name*` page is available.
- Tried to create a new profile using android app: it stucks on “On moment… 60%”, then fails with `Configuration failed. Error: CAPABILITY command error: io: timed out: timed out`
- If i enable russian VPN, it shows “Connected” in app, but cant deliver messages

I suspect some tricky DPI.

How to collect useful debug info to find out what happened?  
What to do now?

---

<div class="post-metadata">

**Author:** ![ian](https://forum.delta.chat/user_avatar/forum.delta.chat/ian/32/3164_2.png) [@ian](https://forum.delta.chat/u/ian)\
**Post date:** [June 5, 2026, 2:04pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/2 "2026-06-05T14:04:17Z")

</div>

~~The domain name (and probably the IP as well) of your instance got burned. This happens.~~

~~Stop the VPS, clone the VM and start it under a new IP address and domain name. If you are lucky, switching subdomains might be sufficient, but there are no promises. Or the least hassle would be to reinstall it on a separate node.~~

~~Anyway, you can view server logs using `journalctl` and inspect traffic using `tcpdump` or `tshark`.~~

---

<div class="post-metadata">

**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\
**Post date:** [June 5, 2026, 2:26pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/3 "2026-06-05T14:26:50Z")

</div>

Developers are aware of the problem, there are many similar reports starting today with similar symptoms (timeout on IMAP connection after `CAPABILITY` command). At the moment there is no need for more logs from Delta Chat. It is unlikely that your specific relay is blocked and there is no quick solution like changing the address or moving to another server.

There is unfortunately no solution for users or relay operators yet, but there are people looking at the problem.

---

<div class="post-metadata">

**Author:** ![f7n5xmavu](https://forum.delta.chat/letter_avatar_proxy/v4/letter/f/85f322/32.png) [@f7n5xmavu](https://forum.delta.chat/u/f7n5xmavu)\
**Post date:** [June 5, 2026, 2:56pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/4 "2026-06-05T14:56:11Z")

</div>

could you add more details, or publish a link to topic/issue?  
what actually happened that it requires a patch from devs to fix existing instances?

---

<div class="post-metadata">

**Author:** ![darkcat09](https://forum.delta.chat/user_avatar/forum.delta.chat/darkcat09/32/3287_2.png) [@darkcat09](https://forum.delta.chat/u/darkcat09)\
**Post date:** [June 5, 2026, 3:54pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/5 "2026-06-05T15:54:08Z")

</div>

Supposedly Delta Chat clients have been blocked by their TLS fingerprints. I’m currently investigating the problem

---

<div class="post-metadata">

**Author:** ![Gluek](https://forum.delta.chat/user_avatar/forum.delta.chat/gluek/32/643_2.png) [@Gluek](https://forum.delta.chat/u/Gluek)\
**Post date:** [June 5, 2026, 3:54pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/6 "2026-06-05T15:54:11Z")

</div>

Looks like DPI are blocking specific Delta chat connection patterns, it’s happening even with non-chatmail servers. Some custom servers are working with custom build clients.

---

<div class="post-metadata">

**Author:** ![f7n5xmavu](https://forum.delta.chat/letter_avatar_proxy/v4/letter/f/85f322/32.png) [@f7n5xmavu](https://forum.delta.chat/u/f7n5xmavu)\
**Post date:** [June 5, 2026, 4:02pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/7 "2026-06-05T16:02:24Z")

</div>

thank you!  
let me know if i can assist somehow (collecting info, testing ideas - whatever)

email: [tough.foam8852@fastmail.com](mailto:tough.foam8852@fastmail.com)

pgp pub key: [tough.foam8852@fastmail.com.asc.txt](https://forum.delta.chat/uploads/short-url/7ABjQhy5SbFdrC4BB6CApPXywjb.txt) (3.1 KB)

GL!

---

<div class="post-metadata">

**Author:** ![bestman](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/96bed5/32.png) [@bestman](https://forum.delta.chat/u/bestman)\
**Post date:** [June 8, 2026, 8:25pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/8 "2026-06-08T20:25:23Z")

</div>

Yes, all the blocking is there, [I’m just thinking about it too](https://support.delta.chat/t/blocking-the-connection-on-your-server-via-protocol-or-https/5397/4). Moreover, regular mail in the application is not connected, not only chat mail. The second device also does not connect, even though all conditions are met.

---

<div class="post-metadata">

**Author:** ![Gluek](https://forum.delta.chat/user_avatar/forum.delta.chat/gluek/32/643_2.png) [@Gluek](https://forum.delta.chat/u/Gluek)\
**Post date:** [June 10, 2026, 12:16pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/9 "2026-06-10T12:16:48Z")

</div>

Update your clients to 2.52 and it should be fine (for now).

---

<div class="post-metadata">

**Author:** ![bestman](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/96bed5/32.png) [@bestman](https://forum.delta.chat/u/bestman)\
**Post date:** [June 10, 2026, 12:32pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/10 "2026-06-10T12:32:25Z")

</div>

Yes, it helped!

---

<div class="post-metadata">

**Author:** ![f7n5xmavu](https://forum.delta.chat/letter_avatar_proxy/v4/letter/f/85f322/32.png) [@f7n5xmavu](https://forum.delta.chat/u/f7n5xmavu)\
**Post date:** [June 10, 2026, 1:40pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/11 "2026-06-10T13:40:01Z")

</div>

thank you!

---

<div class="post-metadata">

**Author:** ![f7n5xmavu](https://forum.delta.chat/letter_avatar_proxy/v4/letter/f/85f322/32.png) [@f7n5xmavu](https://forum.delta.chat/u/f7n5xmavu)\
**Post date:** [June 10, 2026, 1:42pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/12 "2026-06-10T13:42:39Z")

</div>

do i get it right that as far as RKN started “hunting” deltachat, it is expected that the issue will occur again an again (with different symptoms)?

---

<div class="post-metadata">

**Author:** ![magic](https://forum.delta.chat/letter_avatar_proxy/v4/letter/m/ce73a5/32.png) [@magic](https://forum.delta.chat/u/magic)\
**Post date:** [June 10, 2026, 1:44pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/13 "2026-06-10T13:44:08Z")

</div>

do you know when this version will reach Google Play and F-Droid?

---

<div class="post-metadata">

**Author:** ![Gluek](https://forum.delta.chat/user_avatar/forum.delta.chat/gluek/32/643_2.png) [@Gluek](https://forum.delta.chat/u/Gluek)\
**Post date:** [June 10, 2026, 1:45pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/14 "2026-06-10T13:45:49Z")

</div>

will see

---

<div class="post-metadata">

**Author:** ![Gluek](https://forum.delta.chat/user_avatar/forum.delta.chat/gluek/32/643_2.png) [@Gluek](https://forum.delta.chat/u/Gluek)\
**Post date:** [June 10, 2026, 1:48pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/15 "2026-06-10T13:48:15Z")

</div>

soon?

you can download apk here, it should update on top of installed play store app:

[https://download.delta.chat/android/deltachat-gplay-release-2.52.0.apk](https://download.delta.chat/android/deltachat-gplay-release-2.52.0.apk)

---

<div class="post-metadata">

**Author:** ![Freddy](https://forum.delta.chat/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@Freddy](https://forum.delta.chat/u/Freddy)\
**Post date:** [July 16, 2026, 7:45am UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/16 "2026-07-16T07:45:31Z")

</div>

Hello, it seems blocked again.

---

<div class="post-metadata">

**Author:** ![bestman](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/96bed5/32.png) [@bestman](https://forum.delta.chat/u/bestman)\
**Post date:** [July 16, 2026, 8:44am UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/17 "2026-07-16T08:44:07Z")

</div>

Yes, today the application stopped connecting to the server

---

<div class="post-metadata">

**Author:** ![far](https://forum.delta.chat/letter_avatar_proxy/v4/letter/f/439d5e/32.png) [@far](https://forum.delta.chat/u/far)\
**Post date:** [July 16, 2026, 9:35am UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/18 "2026-07-16T09:35:36Z")

</div>

Yes, connections to chatmail servers from Russia are no longer working. However, connections to regular mail servers are working as usual. It would be a good idea to tweak the chatmail server so that it looks as much like a regular mail server as possible.

---

<div class="post-metadata">

**Author:** ![AlexUI](https://forum.delta.chat/letter_avatar_proxy/v4/letter/a/7ab992/32.png) [@AlexUI](https://forum.delta.chat/u/AlexUI)\
**Post date:** [July 16, 2026, 3:45pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/19 "2026-07-16T15:45:08Z")

</div>

I have the same problem on both mobile devices and my computer. The only thing that helps is setting the certificate verification relay to “accept invalid certificates.”

---

<div class="post-metadata">

**Author:** ![bestman](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/96bed5/32.png) [@bestman](https://forum.delta.chat/u/bestman)\
**Post date:** [July 16, 2026, 4:53pm UTC](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369/20 "2026-07-16T16:53:35Z")

</div>

I see TLS connection errors in the logs

[Next page](https://forum.delta.chat/t/my-relay-stopped-working-how-to-fix-timeout-on-imap-connection-after-capability/5369.md?page=2)
