similar to: Missing return-path on vacation messages

Hi, I know I've brought this up before (see http://www.mail-archive.com/dovecot at dovecot.org/msg20974.html), and I've since upgraded to 1.2.6, but our vacation messages are still being rejected because of Bad_MIME. We are using Dovecot Sieve 0.1.12, the auto reply message contains ^M characters at the end of a few lines, they are only visable through vi, example: Received: from

It's long over due, but now I finally plan on upgrading from v1.0.15 to v1.2.16 on our servers. Would appreciate any comments! We have 7 servers, all running of the same GPFS filesystem. Both maildirs and indexes are stored here. We use dovecot for POP/IMAP and deliver. Currently we're using mysql as authentication source, but want to move to using ldap instead. Can we upgrade one server

Hello list, I'm using dovecot 1.1.11 and I'm going to prohibit users to remove their INBOX and some other directories in the mailbox root. I used Access Control Lists (http://wiki.dovecot.org/ACL) to do this: protocol imap { mail_plugins = acl } plugin { # With global ACLs in /etc/dovecot/acls/ directory: acl = vfile:/etc/dovecot/acls } /etc/dovecot/acls/.DEFAULT: owner

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Dovecot v1.0.0 if there is no Return-Path in the message and Deliver cannot deliver the message, no DSN is sent _and_ the MTA is returned 0 (aka success) return code, which leads to mail loss. This is not the case, when the message actually finds a Return-Path, but fails to invoke the MTA. - --- src/deliver/mail-send.c (revision 47) +++

Hello Dovecot developers, Apple has made and tested significant changes to Dovecot v1.1 and now is ready to contribute them back to your open source project. The changes include: Scalability and performance: allow pop/imap mail processes to handle multiple clients larger listen queues Stability and maintenance: fix to allow cross-compilation workarounds for Mac OS X bugs a couple general

Hello, the vacation module of Sieve works fine for me, but the sender name (From Header) is always the e-mail address. I'm unable to add a name here. I'd love to have my realname in the From: field. Did I miss something? :-) Thanks, Jakob

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

Hi all, is it possible to install/activate a "out of office" messages for each user in dovecot? I've read about the Sieve scripts, but can't find a howto to install it on your dovecot 1.0.7 installation. http://wiki.dovecot.org/LDA/Sieve ... With v1.1 it's possible to include other Sieve scripts in your script ... I know, its an old release, so don't treat me like a

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

HI All, We have the latest Dovecot 1.1.6 running and I need to migrate some POP3 users over from Courier to Dovecot and would need to convert the courierpop3dsizelist to maintain the UIDs. I just need to confirm that the script (http://www.dovecot.org/tools/courier-dovecot-migrate.pl) only works for Dovecot v1.0 and not for v1.1? As the dovecout-uidlist file that is created (by the script) is not

Hi! I'm quite new to Dovecot. helping my friend to migrate from Courier-IMAP to something more efficient, we are evaluating Dovecot at the moment. I had to prepare 2 small patches for Dovecot to suit our needs, and I've decided to post it here. I'm not fully familiar with Dovecot architecture yet, I'd appreciate if someone could look if these changes make sense (i.e.

http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz.sig v2.2.26 had a couple of nasty bugs left in it, so here's a fixup release. The version number is also a little bit weird, but had to be done this way (although 2.2.26.0.1 could have been another possibility). - Fixed some compiling issues. - auth: Fixed

http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz.sig v2.2.26 had a couple of nasty bugs left in it, so here's a fixup release. The version number is also a little bit weird, but had to be done this way (although 2.2.26.0.1 could have been another possibility). - Fixed some compiling issues. - auth: Fixed

> On Sep 14, 2016, at 10:44 AM, Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > > Am 14.09.2016 um 05:53 schrieb Michael A Weber via samba: >> Experts— >> >> I’m attempting to export a keytab for a created SPN on the AD DC machine but I’m receiving an error: >> >> ERROR(runtime): uncaught exception - Key table entry not

So we have two different Samba servers we are trying to connect to what was originally a Windows 2003 AD and was raised to 2008R2 (both Forest and Domain). (We really only need to connect one of them - the one hosting Samba 4.7.6). Any ideas or suggestions are helpful! We've scoured the lists (Rowland - you are amazing), but still not found what is wrong (we think it is probably a config

On 25 Feb 2017, at 21.54, Timo Sirainen <tss at iki.fi> wrote: > > Oh, I forgot to remove the #if OPENSSL_VERSION_NUMBER checks from lib-dcrypt. Will be removed in v2.2.29. Attached the planned patch that should do it. Well that didn't work with <v1.1. Maybe this one. -------------- next part -------------- A non-text attachment was scrubbed... Name: openssl.diff Type:

I have read that so many times. I started out with the simple, prompted 'samba-tool domain join' and built up from there. Version is: Samba 4.7.6 from Ubuntu (18.04.2) Interesting what happens when I take out --site directive (see below). root at DC2:~# samba-tool domain join DOMAIN1.DOMAIN DC --username='DOMAIN1\EnterpriseAdminUser' --realm='DOMAIN1.DOMAIN'