similar to: Locking strategy?

Hello! In this email you can find a configuration primer for a Migration from UW IMAP with pine, Thunderbird and squirrelmail as client. For compatibility the mbox format is used. A description for pine with imap acces without entering any password is also discussed. Please use dovecot 1.0beta1 or later for correct handling with pine. Short overview of Mail folders:

Hello, I upgraded from dovecot 1.1.17 to 1.2.5. Works well so far with e.g. Thunderbird and SSL. One problem left: pine doesn't work any more with rsh: cat .pinerc (filtered): rsh-path= rsh-command=/usr/sbin/dovecot --exec-mail imap Starting pine: 1.) Opening INBOX 2.) [>SECURITY PROBLEM: insecure server advertised AUTH=PLAIN<] 3.) Afterwards I'm asked for a password: HOST:

Hello, After fixing configuration and other issues I'm still having one problem with imap executable and pine: less .pinerc # Changed config: #rsh-command=/usr/sbin/dovecot --exec-mail imap rsh-command=/usr/local/bin/imap Calling imap still fails as non root: imap /usr/bin/ld: cannot open output file /usr/local/bin/.libs/2612-lt-imap: Permission denied collect2: ld returned 1 exit statusn

Hello! Currently I'm trying to integrate dovecot's deliver program into procmail. So basically I'd write a patch for procmail to deliver not directly into the mbox file but delivering with the dovecot deliver program. Do you think this is a good concept? For testing I use the commands discussed below. Currently I'm having a problem that deliver doesn't recognize the

Hello! As discussed in the previous thread about "Dovecot deliver logging problem and procmail" I have made a small patch for procmail to deliver through dovecot's deliver program (or any other delivery program). So Procmail does not write the mailboxes directly any more. So delivery is done through pipes and an external program which can deliver the files. Since dovecot's

Hello! Noone has running a sendmail/Mailscanner/procmail/mbox environment? Ciao, Gerhard ---------- Forwarded message ---------- Date: Mon, 24 Apr 2006 20:27:56 +0200 (CEST) From: Gerhard Wiesinger <lists at wiesinger.com> To: dovecot at dovecot.org Subject: [Dovecot] Dovecot LDA with sendmail/Mailscanner Hello! I'm running dovecot in a sendmail/Mailscanner/procmail/mbox

On 15.06.2015 21:31, Christian Weisgerber wrote: > On 2015-06-15, Gerhard Wiesinger <lists at wiesinger.com> wrote: > >> I saw that OpenSSH release 6.7 removed all CBC ciphers by default. Is >> CBC therefore considered as broken and unsecure (in general or SSH >> implementation)? > CBC modes in SSH use the last encrypted block of the previous packet > as the IV

Running 1.0alpha5 (though I've been having this problem for the past couple of versions), and using mbox for the mailboxes. After I've read my mail using Apple's Mail.app (or Thunderbird) and take it offline, when I try to open the INBOX (or any mailbox) with pine, I get the following message (in pine): [Discarding bogus continuation in msg 1: $Forwarded NonJunk] Quitting

Hello, I saw that OpenSSH release 6.7 removed all CBC ciphers by default. Is CBC therefore considered as broken and unsecure (in general or SSH implementation)? I also read a lot of references (see below) but still not clear to me what's the actual "security status" of CBC and why it has been removed in general. http://www.openssh.com/txt/release-6.7 sshd(8): The default set

After the aging harddrive in my Redhat 7.2 server died, I decided it was time to upgrade. I bought a new harddrive and did a fresh install of Fedora Core 2. I've managed to get www, ssh and sendmail reconfigured, but I'm having a heck of a time with imap. I first fooled around with cyrus-imapd, and couldn't make head or tail of it, so I downloaded a fedore core 1 imapd rpm and

On 05.08.2015 13:06, Steffen Kaiser wrote: > On Tue, 4 Aug 2015, Gerhard Wiesinger wrote: > >> >> I'm running dovecot in a classical vmail.vmail setup with pigeonhole >> and LMTP. Permission worked well in the initial setup but currently >> (maybe after Fedora 22 update) I'm having the following permission >> issue: >> >> lmtp(root):

At Thu, 21 Jun 2018 20:42:50 +0200 CentOS mailing list <centos at centos.org> wrote: > > On 21.06.2018 19:28, Robert Heller wrote: > > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently > > not compatible with postfix + procmail. I need an imap daemon that will work > > with a postfix + procmail system. > > > the problem seems to

Hello! I'm running squirrelmail 1.4.8 (I know this is not the latest version) and know I'm having troubles with: 1.) Folder list view 2.) Save to sent or Drafts folder. Configuration worked well. I think it has to do with the upgrade from dovecot 1.0 to 1.1 and the LIST command. Thunderbird/alpine work well. Commands from rawlog are: A002 LIST "" "~/Mail/Drafts"

On 05 Dec 2015, at 11:32, Gerhard Wiesinger <lists at wiesinger.com> wrote: > > Is it possible to configure the secure session caching mechanism? > e.g. like in nginx: https://bjornjohansen.no/optimizing-https-nginx I remember hearing about various security vulnerabilities in that earlier.. I guess they're fixed now then, unless people find more ways to exploit it. Anyway

Hi all, I've done a bit of searching and haven't seen anybody else coming across this problem yet: I noticed that Dovecot uses the opposite flags for marking messages as deleted and draft to most other MUAs I've seen or used: With PINE, mutt and uw-imapd at least, messages are marked with X-Status 'D' for Deleted, and 'T' for drafT. Dovecot reverses this behaviour,

Dear Dovecot list, I recently switched from uw-imapd to dovecot to manage my huge mbox files (about 1 GB). I now observe a very strange behavior, difficult to reproduce reliably, which might be related to some misunderstanding on my part on how either dovecot works or imap labeling works. What I call "labeling" is the fact of marking some e-mail, in my e-mail client (currently

Not sure if this has already been covered, but any pointers or suggestions would be greatly appreciated. We just realized last night that dovecot-stable seems to be corrupting the attachments within users' inboxes. In an attempt to resolve the problem, we upgraded the mail server here to Dovecot 1.0alpha4 but it didn't help. To the best of our knowledge we didn't start experiencing

Dear list, I am planing to set up dovecot-imapd on my production-mail server which currently only runs pop3 via qpopper on debian-sarge. It would be best, if I could only use imapd and use the existing pop3- server (qpopper) as it is. Is this possible? Can the user both use pop3 (qpopper) and imapd (dovecot) in parallel then? Where does dovecot-imapd store its mails? Does it store its mail in

Hello, Is it possible to configure Dovecot as SASL client for central authentication (also remotely via TCP/TLS)? Following use case: IMAP server (host 1) <=> Windows Domain Controller and /etc/shadow authenticator via pam (host2) Should work as: IMAP server (host 1) <=> SASL Client via TLS <=> Network <=> SASL Server via TLS <=> Local SASL via pam <=>

Greetings, I have some architectural questions regarding dovecot, and though I've half answered them by looking at the source, I'm also interested in hearing whether my (our) wishes and suggestions are already being considered (or can be considered, once built) for inclusion in dovecot itself. Let me first explain why I'm doing this. I work for XS4ALL, a fairly large ISP in the