Released Pigeonhole v0.4.23 for Dovecot v2.2.35.

Hello Dovecot users, Here is a new Pigeonhole release that goes with the new Dovecot v2.2.35 release. This release is not strictly necessary, as previous versions should be usable as well. This release only contains bug fixes. However, considering the rather nasty editheader bug that emerged in

Re: pylori error in dovecot log

Op 3/19/2018 om 8:40 PM schreef @lbutlr: > On 2018-03-19 (13:02 MDT), @lbutlr wrote: >> I am getting the following in my /var/log/dovecot: >> >> Error: sieve: Execution of script /usr/lib/dovecot/sieve/report-spam.sieve >> failed >> >> Error: plugin: failed to parse plugin

Re: Permissions on /var/log/dovecot

On 2018-03-19 (14:20 MDT), Odhiambo Washington wrote: > > I have been running FreeBSD since 1997, so I know quite a lot about it! > I know about /etc/syslog.conf, but you do realize now that you are > conflicting yourself? No, I am not, I pointed out that dovecot does not

Re: Permissions on /var/log/dovecot

On 19 March 2018 at 23:19, Roger Klorese wrote: > So is yours. > > Why not say what SHOULD be done? Since we were discussing logging, > including only the lines about logging seem to be a reasonable response to > the original open-ended question. “Please include the

Re: Permissions on /var/log/dovecot

On 19 March 2018 at 22:48, @lbutlr wrote: > On 2018-03-19 (13:19 MDT), Odhiambo Washington wrote: > > > > Plus, if dovecot is able to write to a file owned by root:wheel, then > there is a BIG problem right there!!! > > Logging is generally done by

Re: Permissions on /var/log/dovecot

So is yours. Why not say what SHOULD be done? Since we were discussing logging, including only the lines about logging seem to be a reasonable response to the original open-ended question. “Please include the complete output of ‘dovecot -n’” would get your point across instead of just letting you

Re: Permissions on /var/log/dovecot

On 19 March 2018 at 22:45, @lbutlr wrote: > On 2018-03-19 (13:19 MDT), Odhiambo Washington wrote: > > > > What does your doveconf -n have? > > imap_id_log = * > log_path = /var/log/dovecot > This is a very useless response! -- Best regards, Odhiambo

Re: Permissions on /var/log/dovecot

On 2018-03-19 (13:19 MDT), Odhiambo Washington wrote: > > Plus, if dovecot is able to write to a file owned by root:wheel, then there > is a BIG problem right there!!! Logging is generally done by syslogd, not directly by the process. So no, dovecot is not writing to a

Re: Permissions on /var/log/dovecot

On 2018-03-19 (13:19 MDT), Odhiambo Washington wrote: > > What does your doveconf -n have? imap_id_log = * log_path = /var/log/dovecot -- I have a love child who sends me hate mail

Re: pylori error in dovecot log

On 2018-03-19 (13:02 MDT), @lbutlr wrote: > > I am getting the following in my /var/log/dovecot: > > Error: sieve: Execution of script /usr/lib/dovecot/sieve/report-spam.sieve > failed > > Error: plugin: failed to parse plugin (from @INC): Can't locate >

Re: Permissions on /var/log/dovecot

On 19 March 2018 at 22:06, @lbutlr wrote: > /var/log/dovecot exists and has a lot of logging in it, but I get errors > (in mail.log) on an always_bcc action in postfix: > > mail postfix/pipe[13015]: 401cvS0R8BzbSkL: > to=, > relay=dovecot,

Permissions on /var/log/dovecot

/var/log/dovecot exists and has a lot of logging in it, but I get errors (in mail.log) on an always_bcc action in postfix: mail postfix/pipe[13015]: 401cvS0R8BzbSkL: to=, relay=dovecot, delay=398058, delays=398045/13/0/0.04, dsn=4.3.0, status=deferred

pylori error in dovecot log

I am getting the following in my /var/log/dovecot: Error: sieve: Execution of script /usr/lib/dovecot/sieve/report-spam.sieve failed Error: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/Razor.pm in @INC (you may need to install the

Re: Fts solr and https

It's possible, yes. You can use stunnel or haproxy as workaround, maybe? Aki > On 19 March 2018 at 20:39 Alex wrote: > > > Hello, > > Excuse me, > Is dovecot really unable to work with solr through https ? > > I tried to change ssl_client_ca_dir and ssl_client_ca_file, but

Re: Fts solr and https

Hello, Excuse me, Is dovecot really unable to work with solr through https ? I tried to change ssl_client_ca_dir and ssl_client_ca_file, but nothing. Alex 2018-03-05 21:56: Hi, Dovecot 2.2.32-34 FreeBSD 10.4 Solr 7.2.1(Centos 6) When I try to use https to connect to solr, I get error

Re: Controlling dovecot caching decisions

Thanks Aki, Just a followup regarding this. I set "mail_always_cache_fields" to the following in dovecot configuration file: mail_cache_fields = flags,imap.body,imap.bodystructure mail_always_cache_fields = imap.body,imap.bodystructure I run the following command to ensure that these

v2.2.35 released

https://dovecot.org/releases/2.2/dovecot-2.2.35.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.35.tar.gz.sig     - charset_alias: compile fails with Solaris Studio, reported by       John Woods.     - Fix local name handling in v2.2.34 SNI code, bug found by cPanel.     - imapc: Don't try to

Re: Accentuated email addresses stored in LDAP

On 19/03/2018 07:23, Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 19 Mar 2018, André Rodier wrote: I had to use base64 encoding to store email addresses, because they are rejected otherwise, with an error message of illegal characters. I also you are using

Replication Slave is not auto-creating domain/user folders

Hey all, I'm experiencing a weird and annoying issue with my 2-node dovecot replication setup. The setup is based on virtual users in a pgsql database, which is replicated from the master to a slave node. For the mails I rely on the dovecot builtin replication which has been working great for me

Re: Accentuated email addresses stored in LDAP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 19 Mar 2018, André Rodier wrote: I had to use base64 encoding to store email addresses, because they are rejected otherwise, with an error message of illegal characters. I also you are using the stock "mail" attribute in LDAP as:

Re: Is possible to override Dovecot variables or Sieve env vars and extdata lookups

On 19.03.2018 09:04, MRob wrote: > On 2018-03-19 06:31, Aki Tuomi wrote: >> On 19.03.2018 06:40, MRob wrote: >>> Are the dovecot environment variables mutable? I'd like to override >>> like: >>> >>> set "${env.vnd.dovecot.username}" "someu...@example.org" >>> >>> Or better, I prefer to override

Re: Is possible to override Dovecot variables or Sieve env vars and extdata lookups

On 2018-03-19 06:31, Aki Tuomi wrote: On 19.03.2018 06:40, MRob wrote: Are the dovecot environment variables mutable? I'd like to override like: set "${env.vnd.dovecot.username}" "someu...@example.org" Or better, I prefer to override %u Dovecot variable during the userdb lookup. Is either

Re: Accentuated email addresses stored in LDAP

On 19/03/18 06:30, Aki Tuomi wrote: > > > On 19.03.2018 07:58, Alexander Dalloz wrote: >> Am 18.03.2018 um 23:25 schrieb André Rodier: >>> Every other alias works, but not those with accents. They are correctly >>> stored in the LDAP database, using base64. >> >> Why do you even think a

Re: Accentuated email addresses stored in LDAP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 18 Mar 2018, André Rodier wrote: Every other alias works, but not those with accents. They are correctly stored in the LDAP database, using base64. Despite Aki's answer, whether it works at all, I would expect the enconding in LDAP is

Re: Controlling dovecot caching decisions

On 19.03.2018 05:14, Sivathmican Sivakumaran wrote: > Hello, > > It looks like the "mail_always_cache_fields" and > "mail_never_cache_fields" can be used to control dovecot's caching > decisions. I cannot seem to find any documentation regarding how these > fields should be used. > > What are

Re: Is possible to override Dovecot variables or Sieve env vars and extdata lookups

On 19.03.2018 06:40, MRob wrote: > Are the dovecot environment variables mutable? I'd like to override like: > > set "${env.vnd.dovecot.username}" "someu...@example.org" > > Or better, I prefer to override %u Dovecot variable during the userdb > lookup. > > Is either possible? > > PS, when Sieve

Re: Accentuated email addresses stored in LDAP

On 19.03.2018 07:58, Alexander Dalloz wrote: > Am 18.03.2018 um 23:25 schrieb André Rodier: >> Every other alias works, but not those with accents. They are correctly >> stored in the LDAP database, using base64. > > Why do you even think a character like 'é' would be legal in the local > part