similar to: New Gmail Android App and Dovecot

Here is the first crash I've seen with the current CVS... Feb 19 00:45:52 mail35a dovecot: IMAP(mnash at stest1.com): Corrupted transaction log file /var/index//data1/mail/st/stest1.com/mn/mnash//.Trash/dovecot.index.log: Append with UID 5736, but next_uid = 5744 Feb 19 00:45:55 mail35a dovecot: IMAP(mnash at stest1.com): Corrupted transaction log file

Hi there, Just wondering what is considered current best practice for managing dovecot? The options I see are: Doveadm binary Doveadm protocol via socket Doveadm http protocol I?m currently on v2.2.10 and it appears the doveadm protocol command set is limited to just the ?mailbox? commands and the http protocol hasn?t been implemented. Is the doveadm http protocol still experimental in v2.3.2?

I run dovecot --version 2.3.10.1 (a3d0e1171) postconf mail_version mail_version = 3.5.7 with three valid accounts on the server, user1 at example1.net user2 at example2.net admin at mx.example.com I can send/receive from each -- both to/from external addresses, as well as between one another. E.g., on mail sent to user2 at example2.net -> admin at mx.example.com logs of the

I disabled postscreen and enabled logging, I have all ports working except 993, in log when I try to connect on port 993 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=10.244.0.24, lip=10.244.0.108, TLS handshaking: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number, session=<rEH6ocGoOtUK9AAY> I found that I could

I'm running postfix + dovecot + dovecot-pigeonhole on my CentOS-7 home server. I would like spam to finish up in ~/Maildir/.Spam/ . Spam is being marked, but is not separated - it ends up with all the other email in ~/Maildir/cur/ . Evidently there is some step I have omitted to take. I give the output of "sudo doveconf -n" below. The file ~/.dovecot.sieve reads:

Hi, Thanks for the reply. I guess RHEL choose v2.2.10 <http://dovecot.org/list/dovecot-news/2013-December/000268.html> as it is a good release with all the things working. My source of confusion are from 1) http://dovecot.org/oldnews.html I have gone through each release update news. Lots of work and bug fix after v2.2.10

i've been able to consistently reproduced the issue. no luck ID'ing the specific cause, yet. fyi, i've asked as well @ http://postfix.1071664.n5.nabble.com/local-postfix-re-delivery-of-dovecot-sieve-redirected-mail-fails-normal-direct-deliveries-are-OK-td107691.html with slightly simple config and cleaner log detail.

adding a second, non-redirect action to the sieve rule in order to test, + require ["copy","fileinto"]; # rule:[SIEVETEST] if header :contains "subject" "SIEVETEST" { + fileinto :copy "testing"; redirect "user2 at example2.com"; } on send exec, the 'fileinto' action does work as expected. the 'redirect' fails

I was hoping that someone has seen a similar problem to the one I am facing. I have a samba 3 server connected to an windows domain. All connections appear correct most of the users can connect via windows xp with no issue. However there are a unlucky few whose work stations cannot connect. All xp work stations are the same (at least as well as a large company can get). The user in question

Hello all, I am going for a dovecot director based setup (2 director+ 2 imap), more imap servers will be added later depending on demand/load. Presently I have 12000+ dovecot users with Maildir quota varying from 1 GB to 20GB. (peak hour IOPS 50000+) I am having 2 options in choosing dovecot version. 1) Old stable release. I.e RHEL, with prebuilt binary. This will be having less trouble in

Hi, I can successfully run Samba (v2.2.10 or v 3.0.10) in the smbpasswd mode. However, I cannot get it to connect to the IBM LDAP server (IDS v5.2). Can someone point me to a doc or web site for this? Thanks, Andy

I've been trying for a few days to get pigeonhole/sieve working in order to filter email with spamassassin. Unfortunately I have had no success; and I have found no document which simply tells me what changes I need to make to which files, and what other action I have to take. I'm running CentOS-7 on my home-server, and have postfix + dovecot working perfectly; moreover spam is marked

Op 06/01/2019 om 17:02 schreef Steven Craig: > Thanks, its a weird one. > > On 1/6/2019 8:00 AM, Stephan Bosch wrote: >> >> Op 06/01/2019 om 11:50 schreef Stephan Bosch: >>> >>> Op 31/12/2018 om 23:59 schreef Steven Craig: >>>> Hello there, >>>> >>>> Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but

Hi, I'm creating a scrambler plugin, that adds an istream and an ostream to the stream-chain for the mail input/output. It works well until the zlib plugin is added to the configuration. The scrambler should run before the zlib and encrypt the mail before it's compressed. Since, the plugin is named lib18_scrambler_... (and the other lib20_zlib....), that works well when a mail is

I have a new Dovecot v2.2.9 installation and am having trouble getting virtual users recognized. Also, the example configuration listed on the Wiki generates config errors. Note that I haven't tried running dovecot yet, I wanted to verify that the config looked good first. First, my configuration. I'm trying to use /etc/dovecot/users as my combined userdb and passdb file, with all

Op 06/01/2019 om 11:50 schreef Stephan Bosch: > > Op 31/12/2018 om 23:59 schreef Steven Craig: >> Hello there, >> >> Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but >> after updating to version 2.2.36, our director servers are not able >> to proxy LMTP. >> >> We are sending mail from exim to the local Dovecot LMTP socket, which

Hi, I want to say hello and here is my big problem ;D Iam trying to archive a Postfix/Dovecot 2.2.10 CentOS7 Multidomain Setup with multiple (valid StartSSL Certs), but iam only able to run a single Domain Cert server only. ps: I need a multiple domainssetup for every customer and it is not an option for me redirecting any email to a single domain server. I really need this setup working.

Hi, first of all, many thanks for a great piece of software. Today I updated one of our 2 IMAP/POP3 proxies from version 2.2.15.17-1 to 2.2.23.1-1 (both are enterprise editions). After the update I now see randomly the following errors in the log file on my first proxy: ... Apr 15 10:28:54 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz.sig I tried to keep the configuration and APIs compatible with v2.0.beta1, but unfortunately there were a few things that really had to be changed: 1. passdbs and userdbs have now a separate "driver" setting inside them. So for example if you had: userdb passwd {

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz.sig I tried to keep the configuration and APIs compatible with v2.0.beta1, but unfortunately there were a few things that really had to be changed: 1. passdbs and userdbs have now a separate "driver" setting inside them. So for example if you had: userdb passwd {