search for: 143

Am 26.08.2018 um 20:48 schrieb TE Dukes: >> You see a basic error message "Could not connect to localhost:143". So >> test that without using additional software. Foremost consult the >> maillog, in this case the log content produced by dovecot. And test >> connectivity on the lowest level. >> >> echo QUIT | openssl s_client -connect localhost:143 -starttls imap > I...

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...

Hi Everyone, Just trying to work out how totally disable SSL/TLS support on port 143 while enabling SSL support on port 993 In the config file when I comment out the setting "ssl_disable = yes", I have Webmail client that will no longer be able to auth against port 143, Now I can get the Webmail client to sort of work via using the setting the port to "143/notls&quo...

...08.2018 um 18:12 schrieb TE Dukes: > Thanks. I did open the port but made no difference. > > I found this in the roundcube mail error file: > > [26-Aug-2018 11:48:41 -0400]: <a763f95e> IMAP Error: Login failed for tdukes > from 192.168.1.102. Could not connect to localhost:143: > php_network_getaddresses: getaddrinfo failed: System error in > /usr/share/roundcubemail/program/lib/Roundcube/rcube_imap.php on line 197 > (POST /?_task=login?_task=login&_action=login) > > There is also a warning about the time zone. It's set as America/New_York in >...

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, b...

...ation from one server to 2 new servers". Hi, I have tried the same way as per your suggestion. But it's throwing an error. ------------- [root at production2 log]# doveadm backup -a All -R -u kishore at test.ba.com imapc: dsync(kishore at test.ba.com): Info: imapc(production1.baplc.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) dsync(kishore at test.ba.com): Warning: imapc(production1.baplc.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - reconnecting (delay 0 ms) dsync(kishore at test.ba.com): Info: imapc(production1.baplc.com:143): Conn...

...From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of >> Alexander Dalloz >> Sent: Sunday, August 26, 2018 3:46 PM >> >> Am 26.08.2018 um 20:48 schrieb TE Dukes: >> >> You see a basic error message "Could not connect to >> >> localhost:143". So test that without using additional software. >> >> Foremost consult the maillog, in this case the log content >> >> produced by dovecot. And test connectivity on the lowest level. >> >> >> >> echo QUIT | openssl s_client -connect localhost:...

Hi all, I'm trying to figure out a weird bug I'm seeing. I'm hoping it's something simple in my IR but I can't see anything wrong so I'm hoping someone here can see something. I'm using LLVM to compile Java bytecode into native functions. My code keeps track of the Java local variables in an array of llvm::Value pointers which get phi'd up at various points. The

Hi there. How can I configure dovecot not to listen for imaps connections on port 143. Thanks Lars

On Sat, 13 Jun 2015 14:16:30 +0200, you wrote: >Am Samstag, den 13.06.2015, 08:00 -0400 schrieb Steve Matzura: >> >> All of the above specified settings are correct. Yet, when I telnet >> localhost 143, I get: >> >> Trying ::1... # this is certainly suspect >> Escape character is '^['. >> Connection closed by foreign host. > >What does 'netstat -l46np' say? It doesn't look good. Active Internet connections (only servers) Proto Recv-Q Send-Q Loca...

...Behalf Of >> >> Alexander Dalloz >> >> Sent: Sunday, August 26, 2018 3:46 PM >> >> >> >> Am 26.08.2018 um 20:48 schrieb TE Dukes: >> >> >> You see a basic error message "Could not connect to >> >> >> localhost:143". So test that without using additional >> >> >> software. Foremost consult the maillog, in this case the log >> >> >> content produced by dovecot. And test connectivity on the >> >> >> lowest level. >> >> >> >> &gt...

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, and there is no need to allocate new ports for the secure version of each protocol since we can use STARTTLS. The p...

I'm encountering connection issues to Dovecot when reuse_port is activated. Some of the connections work fine, but about every 3rd of them does not receive the banner after the TCP connection has established: # nc -v 10.6.7.133 143 Connection to 10.6.7.133 143 port [tcp/imap2] succeeded! * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Hello. ^C # nc -v 10.6.7.133 143 Connection to 10.6.7.133 143 port [tcp/imap2] succeeded! * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR...

...stion. But it's throwing an error. > > ------------- > [root at production2 log]# doveadm backup -a All -R -u kishore at test.ba.com <mailto:kishore at test.ba.com> imapc: > dsync(kishore at test.ba.com <mailto:kishore at test.ba.com>): Info: imapc(production1.baplc.com:143 <http://production1.baplc.com:143/>): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) > dsync(kishore at test.ba.com <mailto:kishore at test.ba.com>): Warning: imapc(production1.baplc.com:143 <http://production1.baplc.com:143/>): connect(xxx.xxx.xxx.xxx, 143) tim...

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 s...

...nning openssh-2.9p2 on Linux. If server is run with 'sshd -6' (to enable ipv6 easily on server end), ie all IPv4 are represented as mapped addresses, port forwarding will not work; just running plain ol' IPv4 fixes this of course. The server error, when forwarding from the client '143:localhost:143' and connecting to localhost 143 is: debug1: server_input_channel_open: ctype direct-tcpip rchan 1 win 20480 max 2048 debug1: server_request_direct_tcpip: originator 127.0.0.1 port 1340, target 127.0.0.1 port 143 connect_to 127.0.0.1: unknown host (Address family for hostname not...

...having some problems and I really don't know what is happening. So if you guys could help me with a path to solve this, I will be glad. I'm using Dovecot 2.1.7 in a Debian Wheezy machine. The command I'm using is: dsync -Dv -o imapc_features=rfc822.size -o imapc_host=IP -o imapc_port=143 -o imapc_username='breno.moreira at mav.com.br' -o imapc_password='pass' -u breno.moreira at mav.com.br mirror imapc:/tmp/dsync-imapc and what I got with the logs is: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded...

...ntos.org] On Behalf Of Alexander > Dalloz > Sent: Sunday, August 26, 2018 3:46 PM > To: centos at centos.org > Subject: Re: [CentOS] Mail has quit working > > Am 26.08.2018 um 20:48 schrieb TE Dukes: > >> You see a basic error message "Could not connect to localhost:143". So > >> test that without using additional software. Foremost consult the > >> maillog, in this case the log content produced by dovecot. And test > >> connectivity on the lowest level. > >> > >> echo QUIT | openssl s_client -connect localhost:143...

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, On 25/05/2020 23:04, Voytek wrote: > jumping here with a question, if I use 143 with STARTTLS, and, force > TLS/SSL in configuration, that's equivalent from security POV, isn't > it? and, same for 110 STARTTLS? Or am I missing something? Interesting point, after some googling, I think you are right, and as long as we have set "disable_plaintext_auth = yes&q...