similar to: LDAP imaps,pop3s authentication problem

I would like to use the LLVM-C bindings to provide LLVM access with an OO-design in another language (D), e.g. map from the C API back up to a D API that closely resembles the original C++ API. Since I would like to have D (with its own exception system) to handle the IO, I need a new C API function (unless there is one and I haven't found it): LLVMBool

I''m happily running two four zone/four nic shorewall firewall configuratoins. Great software, works as expected everytime! We are conteplating a larger and more complex firewall configuration that may include as many as twelve zones with trying to cram as many as 8+ interfaces into a single machine. Are there any draw backs to this amount of zones and interfaces into a single

I asked about this ability a few weeks ago and the reply was basically that folks would be interested in seeing it happen. Well, the client insisted, so I've put together a hack that accomplishes it. The basic design requirement was that users would not see files/directories that they did not have at least read access to. This request came about because we were migrating from a Novell server,

s_client: Option unknown option -trace *** x509: Unknown parameter text On 5/25/20 11:49 AM, Aki Tuomi wrote: > Hi! > > Can you do > > openssl x509 text -noout </etc/letsencrypt/live/...../fullchain.pem > > and check these things: > > your server hostname isn included in SubjectAlternativeNames, and that the cert hasn't got MUST-STAPLE attribute? You can see

I have dovecot IMAPS + kmail working perfectly on two laptops - I'm using one now - but I just tried starting it on a third laptop, and cannot get it running; kmail on the third laptop just waits indefinitely, saying "Retrieving Folder Contents Please wait ...". All 3 laptops are running Fedora 7, with more or less the same packages, all updated. (1) I suspect the problem lies

I want Dovecot handling IMAPS. /etc/dovecot.conf: protocols = imaps imaps_listen = * ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem The problem is that Dovecot is not listening on 993 port, or there's something listening on 993, but it does not introduce itself. There's no problem if Dovecot listens on 143 (IMAP). When

Hello there, I am new to Dovecot and I am using version1.2.12. I have included the dovecot -n output: root at ubuntuSnoopBear:/home/scott# dovecot -n \# 1.2.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35-22-generic-pae i686 Ubuntu 10.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s listen: 995 ssl_key_password: nerdie1tech login_dir: /var/run/dovecot/login login_executable:

I had to restart computer yesterday and now Dovecot has strange behaviour. Dovecot is running and should serve IMAPS, but client Mozilla Thunderbird cannot connect. I tried openssl s_client -connect localhost:993 and it said only CONNECTED(00000003). A time ago when everything was OK, the listing after connection was "a bit" longer than it is now. I remember there was "OK,

OK, I did not know that this user has a new computer with Outlook 2010. This SHOULD make it easier but... I have the computer right next to me, they brought it over. It is on the same LAN as this notebook. I can access my server with: openssl s_client -connect z9m9z.htt-consult.com:995 And then log the user in with the appropriate POP3 credentials. In Outlook 2010, in Advanced settings I

Hello Aki and all, The below lines are in the dovecot config file. This seems to be the same as Aki's suggestion. correct? I have also double checked file perms, tried with several new key gens, several versions of thunderbird and created completely new thunderbird profiles. Thank you, ssl_cert = </etc/letsencrypt/live/...../fullchain.pem ssl_key =

On 11/23/2014 05:59 PM, Reindl Harald wrote: > > Am 23.11.2014 um 23:30 schrieb Robert Moskowitz: >> On 11/23/2014 04:45 PM, Robert Schetterer wrote: >>> Am 23.11.2014 um 22:33 schrieb Reindl Harald: >>>> no idea what you are talking about >>>> >>>> K9 is a android client and works fine with TLS >>>> >>>> no idea what

On Tue, 11 Aug 2015, Alexander Dalloz wrote: > Am 11.08.2015 um 22:28 schrieb Dr J Austin: >> >> Hi Alexander >> >> [root at maui:/var/log]$ 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

no idea what you are talking about K9 is a android client and works fine with TLS no idea what has "https" to do with email nor why someone needs to "disable K9 long enugh" whatever "long enough" is - don't get me wrong but most technical context on several lists of you if it comes to details is cluttered and your permanently "i am working on IETF"

Excellent, thank you again. The openssl command I have tried (that used to work with Dovecot 2.2) is: openssl s_client -connect mail.privustech.com:143 I have also tried ? ? ? ??openssl s_client -connect mail.privustech.com:143 -servername mail.privustech.com I've posted?the full output from this to?https://pastebin.com/eUSarQdx I've posted te full output?from?dovecot -n

On Tue, 11 Aug 2015, Alexander Dalloz wrote: > Am 11.08.2015 um 21:47 schrieb Dr J Austin: >>> >>> What does cyrus-imapd log? >>> >>> Alexander >>> >>> >> >> Where should I be looking ? > > /var/log/maillog is the default log file for the MAIL facility. Else check > your syslog() daemon configuration. > >

> but i try to this command > > openssl s_client -connect mail.mydomain:pop3s -starttls imap > > it says CONNECTED and hang. second command is correct? Uh, "pop3s" != "imap", and IMAP/STARTTLS is not the same as IMAP/SSL (or whatever the hell the terminology is nowadays). If you're testing IMAP, try one or the other or both depending of how many flavours

trying to login squirrelmail using dovecot-1.1.17 on a qmail-server with vpopmail setup has also running your: courier-dovecot-migrate.pl --recursive --convert --overwrite here are the output from dovecot-log: Info: imap-login: Disconnected (no auth attempts): rip=192.168.1.220, lip=192.168.1.220, TLS handshaking: SSL_accept() failed: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown

Hi, I'm trying to configure a Dovecot dsync service between two servers, using a tcp+ssl connection and a valid Let's Encrypt certificate. I followed the guide on the wiki (http://wiki.dovecot.org/Replication) using the tcps method, but when I launch the replication it fails writing on the log (/var/log/mail.err): (Server 1 - sync "client" )| Error: sync: Disconnected from

Hi, What do you think is a reasonable salary for a ROR programmer in Manchester, UK? If you''re working with ROR and in the UK i''d be interested in knowing your salary :-) Your opinions would be very valuable to me JD -- Posted via http://www.ruby-forum.com/.

Hello all; Is anyone knows if it's possible to have a dual certificate setup on dovecot like in postfix or apache ? i tried to add several crts in local name section : local_name imap.server.tdl { ssl_cert = <server_rsa_crt.pem ssl_key = <server_rsa_key.pem ssl_cert = <server_ecdsa_crt.pem ssl_key = <server_ecdsa_key.pem } but it seems that dovecot takes the last one (ecdsa)