similar to: Dovecot and remote SASL Client via TLS

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

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

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):

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"

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

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

Hi Gerhard, This is not exactly true. CTR modes have the length field encrypted. etm MAC modes and AES-GCM have the length field in cleartext. CBC is dangerous because the length field is encrypted with CBC. aes128-ctr + hmac-sha256 doesn't have any known vulnerability and encrypts the packet length, but uses the bad practice of e&m. chacha20-poly1305 encrypts both payload and packet

Hello, 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): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary open: failed to open: open(/etc/dovecot/sieve_after.svbin) failed: Permission denied (euid=9999(vmail)

Hello! Is it possible with sieve to do the following: When a new message is added to a folder (e.g. dovecot folder and not INBOX) then an action like forwarding it per E-Mail should be triggered. Is this possible? If yes, how does the sieve script look like? If possible, can a shell script also be triggered as action? Thanx. Ciao, Gerhard -- http://www.wiesinger.com/

Hello! I'm using rsync to generate a backup. DATE=`date +%Y.%m.%d.%H.%M.%S` cat files.txt | rsync -avz -e ssh --include-from=- / root@myserver:/backup/$DATE files.txt contains e.g.: - /home/user1 + etc/ + etc/* + etc/.* + etc/*/ + etc/*/* + etc/*/.* + etc/**/ + etc/**/* + etc/**/.* + boot/ + boot/* + boot/.* + boot/*/ + boot/*/* + boot/*/.* + boot/**/ + boot/**/* + boot/**/.* + dev/ + dev/*

On Tuesday 08 of December 2015, Gerhard Wiesinger wrote: > On 07.12.2015 20:13, Timo Sirainen wrote: > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig > > > > This could be (one of) the last v2.2.x release. We're starting v2.3 > > development soon. > > Great! > > What's on

Hello Timo, I think the following commit makes problems: http://hg.dovecot.org/dovecot-2.2/rev/68a8b650578e # Doesn't work A01 LIST "" ~/Mail/Gesendet # OK with quoted mailbox A02 LIST "" "~/Mail/Gesendet" Details: imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS

Hello, I'm trying to move from procmail to dovecot sieve. I found the translation script at http://www.dovecot.org/tools/procmail2sieve.pl It works well except the following use cases: * ^From:.*myemail at mydomain.com.* | formail -I"X-Priority: 2 (high)" -I"X-mydomain-com-seen: yes" | $SENDMAIL -oi \ myemail at mydomain2.com \ myemail at mydomain3.com :0c *

Hello! Yesterday I upgraded from 1.0beta3 to 1.0beta4. I've major problems now with my inbox (quite large, 900MB) and another large folder. Thunderbird 1.5 connects and disconnects. I tried to delete the indexes of dovecot and thunderbird without any sucess. Finally I downgraded to 1.0beta3 and it works well again (Beta3 was running for a timeframe from when it came out and now without

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! I've some folders where I deleted some messages. They are not really deleted, but have the X-Status: D header field set. How can I force a real delete in dovecot? Thank you for the answer. Ciao, Gerhard

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as