search for: tulpen

...ditional 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 That must be successful first. You can too test "lsof -i :143" or "ss -tulpen | grep 143". And tail your maillog. Alexander

...43 -starttls imap > I'm getting what appears to be help file with various options when trying to > run the above commad Can we guess that you don't offer TLS for IMAP connections? >> That must be successful first. You can too test "lsof -i :143" or "ss >> -tulpen | grep 143". And tail your maillog. >> > Running lsof -i :143, I get: > > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap (LISTEN) > dovecot 1576 root 38u IPv6 32015 0t0 TCP *:imap (LISTEN) >...

...l have no impact on dovecot), are -- as the RH documentation indicates -- to turn off weak protocols, they don't turn anything on, other directives are used for that. > >> >> That must be successful first. You can too test "lsof -i :143" >> >> or "ss -tulpen | grep 143". And tail your maillog. >> >> >> > Running lsof -i :143, I get: >> > >> > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> > dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap >> > (LISTEN) dovecot 1576 roo...

...e lowest level. > > echo QUIT | openssl s_client -connect localhost:143 -starttls imap I'm getting what appears to be help file with various options when trying to run the above commad > > That must be successful first. You can too test "lsof -i :143" or "ss > -tulpen | grep 143". And tail your maillog. > Running lsof -i :143, I get: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap (LISTEN) dovecot 1576 root 38u IPv6 32015 0t0 TCP *:imap (LISTEN) Running ss -tulpen | grep 143 :...

...solutions/120383 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_protocols = !SSLv2, !SSLv3 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = !SSLv2, !SSLv3 > >> That must be successful first. You can too test "lsof -i :143" or "ss > >> -tulpen | grep 143". And tail your maillog. > >> > > Running lsof -i :143, I get: > > > > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > > dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap (LISTEN) > > dovecot 1576 root 38u IPv6 32015...

...are -- as the RH documentation indicates -- to > turn off weak protocols, they don't turn anything on, other > directives are used for that. > > > > >> >> That must be successful first. You can too test "lsof -i :143" > >> >> or "ss -tulpen | grep 143". And tail your maillog. > >> >> > >> > Running lsof -i :143, I get: > >> > > >> > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > >> > dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap > >> &g...

...tation indicates -- >> to turn off weak protocols, they don't turn anything on, other >> directives are used for that. >> >> > >> >> >> That must be successful first. You can too test "lsof -i >> >> >> :143" or "ss -tulpen | grep 143". And tail your maillog. >> >> >> >> >> > Running lsof -i :143, I get: >> >> > >> >> > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> >> > dovecot 1576 root 37u IPv4 32014 0t0 TCP *...

...;> to turn off weak protocols, they don't turn anything on, other > >> directives are used for that. > >> > >> > > >> >> >> That must be successful first. You can too test "lsof -i > >> >> >> :143" or "ss -tulpen | grep 143". And tail your maillog. > >> >> >> > >> >> > Running lsof -i :143, I get: > >> >> > > >> >> > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > >> >> > dovecot 1576 root 37u IPv4...

On Sun, 2 Apr 2017 19:02:35 +0200 Karl Heinz Wichmann via samba <samba at lists.samba.org> wrote: > Hallo Marc > > I change the loglevel to 10 > > > database > "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_9.so -d 10"; > > and i get following errors: > > 02-Apr-2017 18:47:44.389 samba_dlz: ldb: ldb_asprintf/set_errstring: > No

maybe this is a simple fix but i really don't know how to fix it... it seems that i cannot run any net rpc commands... i wanted to see the members of Domain Users group so i did the following: root# net rpc group members "Domain Users" -Uroot%not24get and i got this error: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_CONNECTION_REFUSED i can ping localhost

...al dns? Ok. I changed the parameter. The same problem. The test with the internal dns. It looks good. service sernet-samba-ad stop service bind9 stop change server services = -dns to # server services = -dns samba_upgradedns --dns-backend=SAMBA_INTERNAL service sernet-samba-ad start netstat -tulpen | grep 53 (dns in running) I think i found the error. bind9 at debian 8.7 was default not compiled with "--with-dlopen=yes" only with '--with-gssapi=/usr' named -V -------- BIND 9.9.5-9+deb8u10-Debian (Extended Support Version) <id:f9b8a50e> built by make with '-...

Am 26.08.2018 um 15:25 schrieb TE Dukes: > Checked maillog: > > Aug 26 09:12:31 ts130 postfix/qmgr[2194]: E5B948331053: from=<fail2ban at palmettodomains.com>, size=469, nrcpt=1 (queue active) > Aug 26 09:12:31 ts130 postfix/smtp[2307]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused > Aug 26 09:12:32 ts130 postfix/smtp[2307]: E5B948331053: to=<root at

...---------- 8< ------------------------------- (Please note that "a.b.c" is a real ip address, just "anonymised" for this posting.) After starting Samba, the following ports are used: ----------------------------------- 8< ------------------------------- tux:~# netstat -tulpen | grep mbd tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 0 8671 2362/smbd tcp 0 0 a.b.c.233:139 0.0.0.0:* LISTEN 0 8669 2362/smbd tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 0 86...