similar to: what is the correct password file format?

(sorry if you received it already, I had a server crash and never received this from the list, so I thought I'd resend it) ----- Forwarded message from "M. Fioretti" <mfioretti at mclink.it> ----- Subject: Re: [Dovecot] put procmail between postfix and dovecot From: "M. Fioretti" <mfioretti at mclink.it> Date: Sat, 16 Sep 2006 13:48:49 +0200 To: dovecot at

Greetings, I have seen via google that this very problem was already discussed on several lists some months ago, but the archives report no solution. I have a remote server with dovecot 1.0-0_12.beta8 on Centos 4.3. IMAP works just fine: I can read email from both Squirrelmail via web and Kmail. Now I have created an ssl certificate on the server, and I'm trying to retrieve email via pop3s

Hello, I have not clear, due to the new syntax, how to configure dovecot 1.0 to listen only for the following combinations of ports and services: no pop3, from whatever host accept imap connections only if coming from localhost (since I understand this is secure _and_ the only way to make squirrelmail talk to dovecot) listen on the internet only for imaps and pop3s connections, accept them

I have a remote server running centos 4.3 and a home desktop running suse 10.1. I have generated an SSL certificate on the server, copied it on the desktop and run on the desktop: >openssl x509 -in mynewcertCert.pem -fingerprint -subject -issuer -serial -hash -noout >c_rehash . getting this warning: > > Doing . > WARNING: mynewcertPrivateKey.pem does not contain a certificate or

Hello, I have seen via google that this very problem was already discussed on this and other lists some months ago, but the archives report no solution. I have dovecot 1.0-0_12.beta8 on Centos 4.3. IMAP works just fine: I can read email from both Squirrelmail via web and Kmail. Now I have created an ssl certificate and I'm trying to use it via pop3. When I launch fetchmail I get the error

I have noticed on a Centos 4.3 server where I had set some >8 characters passwords for some accounts, that only the first 8 characters are needed (if I forget or mistype the others I login all the same). Can I "move" the live, running system to longer passwords, and how? or is a reinstall necessary? TIA, Marco -- Marco Fioretti mfioretti, at the server

Greetings, I have just been given a VPS with a fresh, minimal Centos 4.2 installation. When I ran "yum update" it went on updating some tenths of packages and signalled this error: Updating : perl ####################### [24/88] Updating : rpm-python ####################### [25/88] Updating : MAKEDEV

Greetings, I just ran "yum update" on a remote 4.2 Centos install. Then I typed "yum search some package" and got this error message repeating continuously: sem_post: Invalid argument A search for this message revealed only these links: http://www.linode.com/forums/archive/o_t/t_1898/centos4_installations_rpm_database_corruption.html http://bugs.centos.org/view.php?id=1202

...on Centos 4.3? Or a stand alone RPM, if no yum install is available? TIA, Marco -- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/ Non si puo' campare con le idee che fanno la coda nel cervello, senza riuscire a uscirne, altrimenti sono talmente strette che si prendono a gomitate facendoti venire il mal

Hello, I'm running dovecot 1.0-0_12.beta8. Since I have only a very small number of user on that server, I have their names and password in text files, no databases. imap works both via webmail and via Kmail Is it possible to have, for the same user, a plain unencrypted password when connecting via imap on the local interface (needed, as I understand it, to be squirrelmail compatible) and a

Hello, I have just ran nmap on a remote server with a minimal (or so I believed) Centos 4.3 installation. Besides what I expected (ssh, httpd, smtp) it found as open for listening these ports: Starting Nmap 3.95 ( http://www.insecure.org/nmap/ ) at 2006-06-14 17:57 CEST Interesting ports on <my.remote.server> (The 1667 ports scanned but not shown below are in state: closed) PORT STATE

Hello, I've read on several howtos that one way to make ssh more secure, or at least reduce the damage if somebody breaks in, is to NOT allow direct ssh login from root, but allow logins from another user. So you have to know two passwords in order to do any real damage. Does this make sense? IF yes, what is the right way to create an user only for this purpose, that is one that can only

Hi! You have misconfigured service imap-login, remove the 993 listener config (it's there by default) or add ssl = yes to it. Aki On 11.12.2018 11.58, Marco Fioretti wrote: > hello, and some update > short version: the error is still there, but I have some more data to > share, thanks in advance for further advice > > first, I am using Mutt 1.10.1 (2018-07-13) as mail client,

Hello, a couple of months ago, also thanks to help from this list, I set up postfix and dovecot for virtual domains on a Centos 4 remote server. I have postfix set up to deliver all email for marco at domain1.net to /var/mail/vhosts/marco_domain1.net/ Everything is fine, as far as postfix is concerned: all email to marco at domain1.net goes in that mailbox, dovecot sees it, etc... Now I need

Hello Aki, maybe I misunderstood you, but both adding an "ssl = yes" line to this section of dovecot.conf, and commenting out the whole "four lines starting at "inet_listener imaps" do not have any effect : service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } this is the error I still get after

-----Original Message----- From: "centos-request at centos.org" <centos-request at centos.org> To: "centos at centos.org" <centos at centos.org> Sent: 12/30/06 12:01 PM Subject: CentOS Digest, Vol 23, Issue 30 Send CentOS mailing list submissions to centos at centos.org To subscribe or unsubscribe via the World Wide Web, visit

My approach to configuring Samba was that I refused to duplicate the effort required to manage user accounts under NT. My resource domain already had the accounts. I did everything I could to stay away from manual (or even programmatic) manipulation of the smbpasswd file. The smbpasswd file is not used or required in the following scenario. There have been some very important Samba

Greetings, I have had to reinstall my email server on another Linux (centos 7.6) VPS, with a newer version of dovecot, other software and a brand new letsencrypt certificate just for email withpostfix and dovecot (that certificate works fine with postfix). Output of dovecot --version and dovecot -n on the new server is below. Now, messages ARE delivered in the right IMAP mailboxes, but when I try

The configuration I'm trying to use is a SAMBA PDC with a SAMBA Member Server, using tdbsam. Binaries for SuSE 9.3 from the samba web page, version 3.0.14a-4.1.i586.rpm. This is SuSE 9.3 Pro with patches and kernel up-to-date thru 20050708. I need to use Samba 3.0.14a because in production the Samba PDC will have to work with several Samba member servers and 3 Windows 2003 member servers.

hello, and some update short version: the error is still there, but I have some more data to share, thanks in advance for further advice first, I am using Mutt 1.10.1 (2018-07-13) as mail client, so it is not an obsolete version. second... at the moment I can send email through postfix on the same server, with the same certificates (almost: I still have to fix some stuff, but is NOT related to