similar to: Dovecot LDA with sendmail/Mailscanner (fwd)

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 all, After looking at the LDA/Sendmail page in the dovecot wiki, I wanted to contribute another method to easily configure Sendmail to use deliver. Instead of adding a new mailer definition, as already suggested, one can simply use the following line in their sendmail.mc file instead: FEATURE(`local_procmail', `/usr/libexec/dovecot/deliver', `deliver -d $u',

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'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 *

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'm running dovecot in a sendmail/Mailscanner/procmail/mbox environment. I want to use dovecot lda because index files aren't updated when using sendmail as lda. Has someone this combination running and some configuration hints so that sendmail, Mailscanner and procmail ist working well. Does procmail work with lda, too? Thank you for the answer. Ciao, Gerhard

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

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, 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 <=>

Hi all... How can deliver messages to a subfolder using the LDA? For example, I want a message to joe+spam at abc.com to be placed inside the 'spam' subfolder. Any hint is appreciated. Thanks ;)

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)

Hi, I have site w. around 7000 users, most of which have some procmail rules (theres even .procmailrc in /etc/skel with rule to put spam into spam folder). Afaik dovecot's deliver doesnt understand procmail rules, so i'd like to ask if its possible to configure procmail so it saves mail using deliver, without modifying users .procmailrc Thanks for any pointers, Vaclav Hula

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/*

Hello! I run the following environment: UW imapd pine sendmail procmail mbox format I migrated from UW imapd to dovecot. It is pretty faster than UW imapd. To ensure a compatible environment I did the following configuration changes in /etc/dovecot.conf: protocols = imaps default_mail_env = mbox:~:INBOX=/var/mail/%u mail_full_filesystem_access = yes mbox_read_locks = fcntl mbox_write_locks

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

(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