similar to: deliver command line options "visible" in sieve script

Do you think it wold be worthwhile to add command line options to "deliver" and "imap" to make them ignore "system wide" configuration file and use ~/.dovecotrc instead? I would like to use "imap via fetchmail ssh plugin" and "deliver via ~/.forward (to get sieve support)". Such options would allow "cleaner" configuration. --

What is the best way to keeps rsynced copy of rotate log files ? x.log -> x.log.1 -> x.log.2.gz -> ... Can rsync "notice" changes of file name and avoid needless synchronization ? -- Andrzej [en:Andrew] Adam Filip anfi@priv.onet.pl anfi@xl.wp.pl http://anfi.webhop.net http://slashdot.org/~anfi

Which email clients support SMTP/IMAP via STDIN&STDOUT of proxy command? I would like to be able to use local and remove dovecot to access maildir *without* running dovecot daemons. -- [pl>en: Andrew] Andrzej Adam Filip : anfi at onet.eu If the future navigation system [for interactive networked services on the NII] looks like something from Microsoft, it will never work. -- Chairman

Is there any chance for rdiff ? I need to frequently synchronize big text file (60MB+) undertaking small changes and I am interested in differences between the subsequent versions [DNS RBL data in dnsbl format, 1E6+ lines of text, new version every 20m, on average 50 new entries (lines) in every synchronization] I would like to get (small) diff file as result of rsync session and apply it to

Would it be sensible/"cost effective" to make dovecot-deliver generated X-Delivered-To header(s) based on command line parameter(s)? [after striping such existing headers, before consulting sieve] I need it to: a) *clearly* mark POP/IMAP account fetched by fetchmail [with fetchmail using directly dovecot-deliver in --mda option] b) cleanly implement "shared mailboxes" with

Would it be possible to make rsync capable to sync gziped source (at server) with non gziped detination file? PROBLEM: The rsyncd server provides a few *frequently* accessed, slow changing, *big* text files (DNS RBL zones). It seems that the source files are too big to stay in memory caches and rsync sessions cause to many hard disk I/O operations. Making rsynd capable to "ungzip"

How to call deliver program to be sure it will *NEVER* generate bounce messages? [all signalling via deliver exit code ] -- [pl>en: Andrew] Andrzej Adam Filip : anfi at onet.eu : anfi at xl.wp.pl You k'n hide de fier, but w'at you gwine do wid de smoke? -- Joel Chandler Harris, proverbs of Uncle Remus

Hi, so sendmail can use only cyrus-sasl ? ok, thank you >Mario Pavlov wrote: >> I was wondering if I can make sendmail use dovecot's SASL >> implementation...maybe I should somehow compile it against dovecot's >> SASL ? My idea is to make sendmail and dovecot authenticate against >> one central user/password repository. Is this possible ? >>

Could you offer some suggestion how to fetch mailbox content over high RTT link (with negligible packet loss)? Currently I use IMAP+IDLE *but* it fails to use full available bandwidth due to high RTT and "send command wait for response" nature of POP3 and IMAP4 protocols. -- [pl>en: Andrew] Andrzej Adam Filip : anfi at onet.eu Learning without thought is labor lost; thought

When I upgraded my old, long running dovecot 1.1 to newer dovecot-1.2.4 + doevecot-sieve- 0.1.12 I observed a change in destination address (-a) parsing. Old behaviour: When Timo introduced this feature (http://www.dovecot.org/list/dovecot/2007-September/025813.html) it was possible to hand over only the detail part. In my sendmail configuration I used "-a +$h", where $h contains the

Hello everybody, I am using dovecot 2.0.13 and have a special case here in which I want a mail that is delivered locally with dovecot-lda to be marked as "seen". In dovecot 1.1.7 I succeeded to achive this, by modifing deliver.c so that upon adding a -S switch to the command arguments, the flag MAIL_SEEN was added to the call of mailbox_copy(). This seemed to work pretty good.

Hi, does anybody know, how a bash shell script looks, which automatically enters the ssh password? the rsync call should be: rsync -avz -e ssh /home/johndoe/data/repository billythegate@192.168.10.102:/home/johndoe/junk the call causes a password question. Is ist possible to automate that by a cron? If yes how should the script look to automatically enter the password? ThanX for an answer.

dear all, quickie - is possible(if yes - how, params, directives, etc) to use any alternative to sendmail_path = /usr/lib/sendmail is is configurable at all? like having postfix or anything else? regards

Need help with setup/config. Current situation: (dovecot version : 1.1.7) we have system users and virtual users. (with different domains) Virtual users have procmail as LDA Now we want "deliver" to become the LDA I'm confused reading http://wiki.dovecot.org/LDA/Sendmail sendmail.mc: divert(-1) divert(0)dnl include(`/usr/share/sendmail-cf/m4/cf.m4')dnl

Hi, I have a Centos 5 system with sendmail running as my MTA. Normally I note from sendmail logs that mails get delivered using the 'local' mailer. I have therefore entered the following into my sendmail.mc file, from an earlier post on this list: define(`LOCAL_MAILER_PATH',`/usr/libexec/dovecot/deliver') define(`LOCAL_MAILER_FLAGS',`DFMPhfnu9')

Is any posibility to pass parameters/environment variables to deliver with sieve plugin? I have some procmail rules to decide where mail should go, which can't be migrated to sieve (uses external programs). So far I write it to maildirs, but I wonder to migrate to mdbox, and procmail can't handle it. Any ideas? KJ --

I have been trying to set up procmail but I am running into some issues with using deliver. I am running Debian Etch with Dovecot 1.1.8 compiled from the Debian Experimental source package. ##### Start .procmailrc ##### # System-wide settings for procmail SHELL="/bin/bash" SENDMAIL="/usr/sbin/sendmail -oi -t" LOGFILE="/var/log/procmail.log"

Dear RSYNCians, I'm trying to rsync my labtop pc (let's assume A-computer) with my desktop pc (let's assume C-computer) through our firewall. In between there is one computer (let's assume B-computer) that has an open port, so I theoretically could connect via a tunnel. I checked the SSH- website and internet and so on but did not find an answer that works. I tried the

Op 11-1-2019 om 10:53 schreef Marc Weustink: > Hi all, > > Andrzej A. Filip wrote: >> Timo Sirainen <tss at iki.fi> wrote: >>> On 9 Jul 2018, at 16.49, Andrzej A. Filip <andrzej.filip at gmail.com> >>> wrote: >>>> >>>> Is it intended behavior? >>> >>> No. >>> >>>> It seems to be caused by

Timo Sirainen <tss at iki.fi> wrote: > On 9 Jul 2018, at 16.49, Andrzej A. Filip <andrzej.filip at gmail.com> wrote: >> >> Is it intended behavior? > > No. > >> It seems to be caused by upgrade to 1:2.3.2-2 on Debian/Testing. > > What was the old version? What's your doveconf -n? How are you testing > that it's not working? It seems that