similar to: deliver+sieve: Destination address (-a) parsing changes

Sorry, couldn't find this in the archives. Under freebsd 4.x, the native mail.local that sendmail uses by default writes From_ lines that include the origin address. This is very readily parsable and handy for quick greps in mboxes. But deliver defaults it to MAILER-DAEMON. I see you can specify the envelope From_ with "-f", but I'm not sure how that's useful. Also

http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz.sig - deliver: v1.0.2's bounce fix caused message to be always saved to INBOX even if Sieve script had discard, reject or redirect commands. - LDAP: auth_bind=yes and empty auth_bind_userdn leaked memory - ACL plugin: If user was given i (insert) right for a mailbox, but not all

http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz.sig - deliver: v1.0.2's bounce fix caused message to be always saved to INBOX even if Sieve script had discard, reject or redirect commands. - LDAP: auth_bind=yes and empty auth_bind_userdn leaked memory - ACL plugin: If user was given i (insert) right for a mailbox, but not all

I want to discuss some problems/enhancements for dovecot in a webmail/otp setup. For access to an IMAP server like dovecot I see different client types: a) a "normal" MUA installed in a more or less trusted environment b) remote access via "webmail" from untrusted environments For a) I see with dovecot and other IMAP servers no problems, tricky is the setup for b). If you use

Good Afternoon I?m really new at this and i don?t know if i?m posting at the right place. My problem is that our Dovecot IMAP is stopping from time to time with no info in the log, i just realize about this when our support person call me saying that the whatsup monitor is showing the IMAP4 process down. I can figure about this too by trying to get in our webmail Horde and i cannot login.

The sieve plugin compares the modification dates of sieve source and compiled script and compiles the script only if necessary. When the managesieve extension is used, it creates a symbolic link for the script. In order to switch between scripts managesieve changes the link only. Therefore the sieve plugin should include the modification date of an symlink in its decision about compilation.

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

Hi Is there known advices on how to favor PFS with dovecot? In Apache, I use the following directives, with cause all modern browsers to adopt 256 bit PFS ciphers, while keeping backward compatibility with older browsers and avoiding BEAST attack: SSLProtocol all -SSLv2 SSLHonorCipherOrder On SSLCipherSuite ECDHE at STRENGTH:ECDH at STRENGTH:DH at STRENGTH:HIGH:-SSLv3-SHA1:-TLSv10

Hello! With many MTAs it is possible to use a special form of adressing: subaddresses or "plussed addresses". For sendmail you can read some information on http://www.sendmail.org/m4/misc_features.html http://www.unix.org.ua/orelly/networking/sendmail/ch24_04.htm#SML2-CH-24-SECT-4-3 In a sieve filter you can analyse these special detail values, the syntax is described in RFC3598

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"

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

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.

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 ? >>

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.

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

Hi list I searched the net, but could not find something related. Is it possible to export the client socket to sendmail for smtp auth? What would be the sendmail.mc configuration for this? #client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. #path =

From: Wang Shilong <wangsl.fnst@cn.fujitsu.com> Scrubing supers is not in a transaction context, when trying to write supers to disk, we should check if we are trying to scrub supers.Fix it. Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com> --- fs/btrfs/disk-io.c | 2 ++ fs/btrfs/transaction.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/fs/btrfs/disk-io.c

Hi, 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 ? thank you. P.S. I want to use virtual users