# Delta chat tor protocols socks5 tcp udp? **URL:** \ **Category:** Mutual Help\ **Created:** [May 25, 2023, 4:19pm UTC](https://forum.delta.chat/t/delta-chat-tor-protocols-socks5-tcp-udp/2586 "2023-05-25T16:19:07Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![gggvv](https://forum.delta.chat/letter_avatar_proxy/v4/letter/g/3d9bf3/32.png) [@gggvv](https://forum.delta.chat/u/gggvv)\ **Post date:** [May 25, 2023, 4:19pm UTC](https://forum.delta.chat/t/delta-chat-tor-protocols-socks5-tcp-udp/2586/1 "2023-05-25T16:19:07Z")
> **[Bittorrent over Tor isn't a good idea | Tor Project](https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea/)** > > An increasing number of people are asking us about the recent paper coming out of Inria in... The article suggests that if an application goes on the internet by another protocol than tcp, then tor cannot catch the data traffic. Does delta chat transfer internet data by other protocols than tcp? Wrongfully I thought proxychains would force any application to transfer data over tor. Or deny the data transfer. That is not the case. Cf jami. If you select the socks5 option in delta chat it says if you type in an address in the email field there will be dns lookup that wont get tunneled through socks5. proxychains support proxy dns. Whether proxychains will catch dns requests made by delta chat I cannot say. ---
**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:** [May 25, 2023, 4:50pm UTC](https://forum.delta.chat/t/delta-chat-tor-protocols-socks5-tcp-udp/2586/2 "2023-05-25T16:50:50Z")
Most of the times Delta Chat connects to the email server using IMAP and submits messages using SMTP. These protocols work over TCP. These protocols should be caught with `torsocks`, and they are also proxied when you configure the SOCKS 5 option inside the application itself. During the initial configuration Delta Chat also does HTTPS requests to the email server to check for the [autoconfiguration XML](https://web.archive.org/web/20210624004729/https://developer.mozilla.org/en-US/docs/Mozilla/Thunderbird/Autoconfiguration). These requests also use TCP and are proxied over SOCKS 5. What is not proxied is the DNS query for the MX record: > This is the DNS lookup that you are talking about. It is skipped if you enable the SOCKS5 setting, but the problem is that SOCKS5 setting is actually enabled only once you click “configure”. A solution could be to have a screen where you can enable SOCKS5 before the screen where you enter the email address, but this is not the current state of the UI. This DNS lookup uses external library [`trust_dns_resolver`](https://docs.rs/trust-dns-resolver/latest/trust_dns_resolver/type.TokioAsyncResolver.html) and I cannot for sure say whether it uses TCP or UDP for DNS requests, the library even contains multiple resolver implementation for multiple operating systems. One thing that uses UDP is an “Add as second device” option, it is based on [`iroh`](https://github.com/n0-computer/iroh) library which uses QUIC interally. This is not proxied and the QR code contains local IP address so one device can discover the other on the local network. This should not be a concern though, because it does not make any requests to any servers, even relays. This may change if `iroh` introduces UDP holepunching to deal with cases where your devices are on different networks, but you don’t have to use this feature and indeed better avoid using it in a torified setup. ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [October 6, 2026, 3:11pm UTC](https://forum.delta.chat/t/delta-chat-tor-protocols-socks5-tcp-udp/2586/3 "2026-10-06T15:11:31Z")