search for: 993

Hi, I'm trying to migrate from an old courier IMAP server to Dovecot 2.3.1 (8e2f634). The old server uses self signed SSL certificate. I'm using the following configuration: imapc_host = 10.1.1.3 imapc_user = %u imapc_features = rfc822.size fetch-headers imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no mail_prefetch_count = 20 mail_shared_explicit_inbox = no Launching dsync with the command: doveadm -o mail_fsync=never -o imapc_password=PASSWORD -Dv backup -R -u USER @DOMAIN <andrzej at datatel.net> imapc: In the output logs I get messages like bel...

...tc/dovecot/ssl/pop.sonic.net.ca-bundle ssl_cert = </etc/dovecot/ssl/pop.sonic.net.crt ssl_key = </etc/dovecot/ssl/pop.sonic.net.key } STRACE: 263563 epoll_wait(14<anon_inode:[eventpoll]>, [{EPOLLIN, {u32=2772983280, u64=94500643429872}}], 8, -1) = 1 263563 accept(9<TCP:[0.0.0.0:993]>, {sa_family=AF_INET, sin_port=htons(39552), sin_addr=inet_addr("64.142.18.25")}, [16]) = 18<TCP:[64.142.111.79:993->64.142.18.25:39552]> 263563 fcntl(18<TCP:[64.142.111.79:993->64.142.18.25:39552]>, F_GETFL) = 0x2 (flags O_RDWR) 263563 fcntl(18<TCP:[64.142.111.79...

just setting a new Dovecot server to migrate from older system, but, I have a general question: 1. I've set the server with self issued cert, and both pop/imap StartTLS/110/143 SSL/993/995 (apologies if I'm using wrong naming terminology) is there a 'preferred way'? should I tell users to use 143 over 993 ? or 993 over 143? or? my current understanding is that some (MS?) clients might not support StartTLS/143 ? so best to offer both ? I think? some public WiFi blo...

...es `doveadm proxy list` repeat the header line after each entry? Too me, that just makes the output harder to read. So instead of this: root at mail1 ~ # doveadm proxy list username proto src ip dest ip port info at domain1.de imap 80.152.196.98 222.133.127.53 993 username service src-ip dest-ip dest-port info at domain1.de imap 80.152.196.98 222.133.127.53 993 username service src-ip dest-ip dest-port info at domain1.de imap 80.152.196.98 222.133.127.53 993 username service src-i...

On 21/08/17 10:37, Gedalya wrote: > On 08/21/2017 07:28 AM, voytek at sbt.net.au wrote: >> is there a 'preferred way'? should I tell users to use 143 over 993 ? or >> 993 over 143? or? > There is no concrete answer. There are various opinions and feelings about this. > The opinion againt 993/995 is that these are not standard ports, Out of curiosity, is there a source for this? It's the first time I hear that 993/995 are not standard p...

> On Jul 28, 2015, at 21:52 , Steffan Cline <steffan at hldns.com> wrote: > > Ok, I think I have come a little further. > > When dovecot stops accepting connections, I checked netstat and found this: > > [root at hosting1 ~]# netstat -an | grep 993 > tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN > tcp 0 0 65.39.x.x:993 184.101.x.x:36351 SYN_RECV > tcp 0 0 65.39.x.x:993 107.212.x.x:51487 SYN_RECV > tcp 0 0 65.3...

...08/17 13:39, Robert Wolf wrote: > > On Mon, 21 Aug 2017, Sebastian Arcus wrote: > >> >> On 21/08/17 10:37, Gedalya wrote: >>> On 08/21/2017 07:28 AM, voytek at sbt.net.au wrote: >>>> is there a 'preferred way'? should I tell users to use 143 over 993 ? or >>>> 993 over 143? or? >>> There is no concrete answer. There are various opinions and feelings about >>> this. >>> The opinion againt 993/995 is that these are not standard ports, >> >> Out of curiosity, is there a source for this? It's t...

...og]$ watch 'tail -n40 maillog >> >> does not quiver when I try to connect > > That's suspicious. > > Let's exclude it is the client which causes the problem: Connect directly to > the IMAPS server on CLI. > > openssl s_client -connect <server ip>:993 > > You hopefully see a greeting message from the IMAP server. Then issue > > a1 LOGIN username password > > If you see a success message that you logged in, then everything is fine with > your cyrus-imapd. > > Logout by entering > > a2 LOGOUT > > If you got...

Hello Mates, I am facing a really weird issue with my mail server, somehow I cannot connect using port 993. It works with 143 but not 993 nor 995. Here is a little bit of more information: # telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-I...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 28 Jul 2015, Steffan Cline wrote: > When dovecot stops accepting connections, I checked netstat and found this: > > [root at hosting1 ~]# netstat -an | grep 993 > tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN > tcp 0 0 65.39.x.x:993 184.101.x.x:36351 SYN_RECV > tcp 0 0 65.39.x.x:993 107.212.x.x:51487 SYN_RECV > tcp 0 0 65.39.x.x:993...

Hi, I've noticed that nmap crashes my imap-login (also pop3-login) and narrowed it down to `nmap -sV -p 993 $host`. I've noticed that if I remove "ssl_protocols = !SSLv2 !SSLv3" from my config or enable SSLv3 rather than disabling it the segfault disappears. I'm running on Arch Linux with dovecot 2.2.16-1 and openssl 1.0.2.a-1. I've also attached a network capture, but since it'...

I am trying to backup a gmail account (not the one I am writing from) to dovecot, using doveadm-backup and imapc, but am having ssl connection problems. ted at expectation:~# doveadm backup -D -R -u ted imapc: dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.108:993 (local 10.7.1.179:53852) dsync(ted): Warning: imapc(imap.gmail.com:993): Server disconnected unexpectedly: SSL_connect() failed: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40 - reconnecting (delay 0 ms) dsync(ted): In...

...ot quiver when I try to connect >>> >>> That's suspicious. >>> >>> Let's exclude it is the client which causes the problem: Connect >>> directly to the IMAPS server on CLI. >>> >>> openssl s_client -connect <server ip>:993 >>> >>> You hopefully see a greeting message from the IMAP server. Then >>> issue >>> >>> a1 LOGIN username password >>> >>> If you see a success message that you logged in, then everything >>> is fine with your cyrus-imapd...

...ng to migrate from an old courier IMAP server to Dovecot 2.3.1 > (8e2f634). The old server uses self signed SSL certificate. > > I'm using the following configuration: > > imapc_host = 10.1.1.3 > imapc_user = %u > imapc_features = rfc822.size fetch-headers > imapc_port = 993 > imapc_ssl = imaps > imapc_ssl_verify = no > mail_prefetch_count = 20 > mail_shared_explicit_inbox = no > Launching dsync with the command: > > doveadm -o mail_fsync=never -o imapc_password=PASSWORD-Dv backup -R -u > USER at DOMAIN <mailto:andrzej at datatel.net>imapc...

Permissions to the logs are fine. In /var/log/maillog I do see dovecot logging in there but nothing that indicates why there?s a failure. The one thing I thought of is if there?s too many connections but I am using a firewall that blocks excessive attempts but that?s fine. Netstat shows a bunch of CLOSE_WAIT though. I?ll try the debug level and see what I find. Thanks, Steffan Cline steffan at

I'm testing my new dovecot server with Thundirbird I can have it working on port 143 with STARTTLS, or on port 993 with SSL/TLS my uderstanding is that on 993 I get encrypted 'password and mail transfer' (yes ?) so what happens if I use 143 with STARTTLS, is that equivalent to port 993 if STARTTLS is used ? thanks for any insights.. -- Voytek

Hi, I am trying to find a nice way to identify dovecot clients that are still configured to use port 143 to connect to our mailserver, from the dovecot logs. I would then ask them to move over to 993, and finally disable port 143 altogether. When looking at the dovecot logs, it seems this is not logged in any obvious way. Of course I could use netflow etc, but that would not give us usernames, but IP's, etc. So, is there a nice way to somehow indicate in the dovecot logs, if a client...

...gt; On Mon, 21 Aug 2017, Sebastian Arcus wrote: >>> >>>> >>>> On 21/08/17 10:37, Gedalya wrote: >>>>> On 08/21/2017 07:28 AM, voytek at sbt.net.au wrote: >>>>>> is there a 'preferred way'? should I tell users to use 143 over 993 ? >>>>>> or >>>>>> 993 over 143? or? >>>>> There is no concrete answer. There are various opinions and feelings >>>>> about >>>>> this. >>>>> The opinion againt 993/995 is that these are not standard por...

...untouched before I tried to run the following command. Running this command: sudo doveadm -vvv -o imapc_host=s04.srv-net.de -o imapc_user=username -o imapc_password=password -o mail_fsync=never -o mail_prefetch_count=20 -o imapc_features=rfc822.size -o imapc_features=fetch-headers -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_ca_dir=/etc/ssl -o imapc_ssl_verify=no -o imapc_features=rfc822.size -o mailbox_list_index=no -D backup -R -u michael at domain.com imapc: I get the following output (I took out some lines obviously not relevant): doveadm(root): Debug: Loading modules from direc...

...> > On Mon, 21 Aug 2017, Sebastian Arcus wrote: > > > > > > > > On 21/08/17 10:37, Gedalya wrote: > > > > On 08/21/2017 07:28 AM, voytek at sbt.net.au wrote: > > > > > is there a 'preferred way'? should I tell users to use 143 over 993 ? > > > > > or > > > > > 993 over 143? or? > > > > There is no concrete answer. There are various opinions and feelings > > > > about > > > > this. > > > > The opinion againt 993/995 is that these are not standard ports,...