similar to: Order of keys

Alex, et al., I spoke too soon. Upon close examination of /var/log/maillog, the errors previously reported via the maillog extracts only happen when I attempt to test the imap connection. Everything appears correctly set up, defined, etc. It's now down to the certificates themselves I think. I have the following files: . A file containing the certificate as issued by the certifying uthority

On advice/recommendation received on this list, I removed version 1.0.15 with: rm -rf /usr/local/dovecot However, now that I have version 2 properly installed, configured, and ready to start testing with Postfix, it appears the old version is still in /usr/local/sbin, /usr/local/include, /usr/local/libexec, /usr/local/lib and /usr/local/shared/doc. Thinking that anything in /usr/local is

My /var/log/maillog was getting pretty big because of lots of testing and re-configuring I've been doing lately with both Dovecot and Postfix. I figured just remove /var/log/maillog and it would be re-created. It wasn't--not by Dovecot, not by Postfix. I had to manually create a new one, put one character in it, save it, properly secure it with chmod, and then Dovecot (and postfix)

I mean, in the source directory. On 12 June 2015 at 15:13, Muzaffer Tolga Ozses <tolga at ozses.net> wrote: > Have you done *make distclean* in prior? That should remove all things > dovecot. > > On 12 June 2015 at 15:10, Steve Matzura <number6 at noisynotes.com> wrote: > >> On advice/recommendation received on this list, I removed version >> 1.0.15 with:

Am 14.06.2015 um 14:03 schrieb Steve Matzura: > Alex, et al., > > I spoke too soon. Upon close examination of /var/log/maillog, the > errors previously reported via the maillog extracts only happen when I > attempt to test the imap connection. Everything appears correctly set > up, defined, etc. It's now down to the certificates themselves I > think. I have the following

After applying some changes to 10-master.conf as detailed at http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP I receive the following when trying to start: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-master.conf line 49: Expecting '{' I'm trying to enable LMTP. The instructions say: Socket configuration The actual socket is configured in

Sorry for having lost the original chain of this problem. It's been a very long day. New output from 'dovecot -n output', including the contents of dovecot.conf, conf.d/10-master.conf, conf.d/10-mail.conf and conf.d/10-ssl.conf: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS ext4

On Thu, 21 May 2015 19:21:41 -0500, you wrote: > >On May 21, 2015, at 9:25 AM, Steve Matzura wrote: > >> I needed to receive a message to admin at mydomain.com. I waited and >> waited for it, but it never showed up in the admin mailbox on the >> mydomain.com machine. So I looked for the admin account in >> /etc/dovecot.passwd, and there it was, plain-text password

2.2.4? I didn't think SSL was implemented until version 2.4.3. What would be helpful, not to mention useful, is to explain specifically and exactly what goes into the key file. The choices are: your server's private key, your server's public key, your server's certifying authority (CA) key, maybe even the curl CA. I've also seen this in examples of the SSL stanza from

On Tue, 16 Jun 2015 22:02:29 +0200, you wrote: >Am Dienstag, den 16.06.2015, 11:44 -0400 schrieb Steve Matzura: >> The next phase of my testing procedure involves the simple act of >> delivering mail to my test box. When I send a message to either a >> valid or relayed user at my remote machine's address, it never gets >> there. I know this virtually for sure

hi jost thx for the reply, by access I mean to read the variable require ["fileinto", "variables", "?destfolder?" ]; if anyof ( destfolder :matches "*") { fileinto "${1}/subfolder"; }else{ fileinto "INBOX/subfolder"; } On 08/07/2015 12:26 PM, Jost Krieger wrote: > On Fri Aug 7 12:19:22 2015, matthias lay wrote:

Hi all, anybody knows, if there is a way to acces the folder from a call like this deovecot-lda -m destfolder from within a sieve script? thx in advance matze

Since I've decided to go to version 2, which is a lot more difficult to set up because I have to look in a lot more places than I did with version 1.0.15, what do I do with the old dovecot/passwd or its contents? I see no references to it in any of the stuff in conf.d or doc/dovecot/wiki. As always, thanks in advance.

My system has a great big four users. The Dovecot wiki says LMTP is more efficient, and someone on IRC told me I'd need it if I were ever to use sieve, which at this time I have no intention of doing. Should I stick with LDA, or just implement LMTP so I'm ready if ever I need it in the future? The bottom line is, it's unclear from the wiki how to explicitly specify use of one or the

Look at /etc/hosts ::1 is the ipv6 version of localhost.? Sent from Samsung tablet -------- Original message -------- From Steve Matzura <number6 at noisynotes.com> Date: 06/13/2015 6:00 AM (GMT-06:00) To dovecot <dovecot at dovecot.org> Subject Testin new installation The first place I went to for test advice and planning recommendations was

On Tue, 16 Jun 2015 11:27:58 -0500, you wrote: >No attempt to deliver almost always means either: >- a DNS problem; the sender can't find the destination, or finds the >"wrong" destination. That would be interesting, since I tried both the actual IP address and the DNS name for the test node. Neither message got through. >- a connectivity problem; the sender can't

On Mon, 15 Jun 2015 17:22:13 +0200, you wrote: >> Now, when I telnet 127.0.0.1 143 and attempt to log in with the >> string: >> >> a login <any username> <any password> >> >> whether it's one in my users file or not, I get: >> >> a NO [AUTHENTICATIONFAILED] Authentication failed. >> > >Logs might give you a clue what

Hello all, I have dovecot running under daemontools and I can't see dovecot-lda in action when I read the logs. I've set the logs to /dev/stderr because daemontools redirects /dev/stderr to /var/log/dovecot/current. The dovecot server works fine and I know that dovecot-lda is actually doing the delivery, because the sieve facility is working as well. I can get lda log working -but

I use sieve-filter for postprocessing misclassified mail. For false positives I use the following script: require [ "variables", "include", "fileinto" ]; global [ "FORCENOSPAM", "ext", "ext1" ]; set "FORCENOSPAM" "YES"; fileinto "JUNK-PRENOUCE"; if header :matches "Delivered-To"

Am 06.09.2017 um 12:17 schrieb ????? ?????: > Thank you for your answers. > I fixed config to: > > plugin { > sieve_default = /mnt/rw_disc/dovecot/sieve/default.sieve > sieve_global = /mnt/rw_disc/dovecot/sieve/ > > quota = maildir:User > quota_rule = *:storage=10M > # quota_rule2 = INBOX.Trash:storage=+10%% > quota_max_mail_size = 3M >