Re: dovecot problem with ssl

On Fri, 17 Mar 2017 05:21:15 -0300 "Nilton Jose Rizzo" wrote: > doveconf: Fatal: Error in configuration file > /usr/local/etc/dovecot/conf.d/10-ssl.conf line 7: Unknown setting: ssl How did you install Dovecot? It sounds like it's been compiled without SSL support. Maybe

Re: Good email client to use with Dovecot?

On Thu, 17 Nov 2016 02:48:52 Steve Litt wrote: > What email clients are all of you using to look at your IMAP email? I'm currently using Sylpheed, which is lightweight and fast, but relatively basic (e.g. no HTML support). I keep meaning to try out Trojitá, which is

Re: Segfaults after upgrade to Debian Jessie

On Tue, 2015-08-18 at 08:53 +0200, Stephan Bosch wrote: Unfortunately, Jessie is stuck at a very old version of Pigeonhole which has this problem. Thanks Stephan. I've heard from the Debian packager that he's planning to package a newer version soon, so that will help. Andy

Re: Segfaults after upgrade to Debian Jessie

On Thu, 2015-08-06 at 16:10 +0200, Stephan Bosch wrote: Since the extdata plugin is not part of the normal Debian packages (not afaik anyway), you likely compiled and installed the extdata plugin manually in the past while using Dovecot 2.1. Do that again, but use this repository:

Re: Segfaults after upgrade to Debian Jessie

On Mon, 2015-08-17 at 17:37 +0200, Stephan Bosch wrote: Unfortunately my vacation rule no longer works though. I'm getting sieve: user's script dict:proxy::sieve;name=active doesn't exist (trying default script location instead) [...] I guess I'm doing something stupid. Any ideas?

Re: Segfaults after upgrade to Debian Jessie

On Mon, 2015-08-17 at 14:13 +0200, Stephan Bosch wrote: but until then you can avoid this by using the the exdata hg revision before tip (57c8d3e6b562). Great, thanks for the quick reply, that fixed the compilation problem. I'm still getting a segfault though. This time the backtrace is:

Re: Segfaults after upgrade to Debian Jessie

On Mon, 2015-08-17 at 15:23 +0200, Stephan Bosch wrote: Still looks like the executed extdata plugin was compiled against a different pigeonhole. Got it. There was an old version in /usr/lib/dovecot/modules/sieve/, whereas the new one was installed into /usr/local/lib/dovecot/sieve/. That all

Re: Segfaults after upgrade to Debian Jessie

On Thu, 2015-08-06 at 09:12 +0200, Stephan Bosch wrote: Could you provide a full backtrace using the gdb command `bt full'? Thanks for the reply. Is this everything you need? #0 0x7f8553969626 in sieve_validator_register_command () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol

Re: Segfaults after upgrade to Debian Jessie

On Thu, 2015-08-06 at 09:49 +0200, Stephan Bosch wrote: You have no debug symbols installed. Could you install dovecot-dbg package and try again? Sorry, how's this: #0 sieve_validator_find_command_registration (valdtr=0x, command=0x7fc573c4bcd8 extdata) at sieve-validator.c:309 No

Re: Segfaults after upgrade to Debian Jessie

On Thu, 2015-08-06 at 16:10 +0200, Stephan Bosch wrote: What version of the extdata plugin are you using? This looks like a version built for Dovecot v2.1/Pigeonhole 0.3.0. Keep in mind that the extdata plugin is not part of the Pigeonhole distribution, so that will not be upgraded along

Re: Segfaults after upgrade to Debian Jessie

On Sat, 2015-07-25 at 00:32 +0100, Andrew Beverley wrote: Hi, I've just upgrade from Debian Wheezy to Debian Jessie and am getting: Fatal: master: service(lmtp): child 6761 killed with signal 11 (core dumped) It seems to be something to do with sieve. When I disable that from lmtp

Segfaults after upgrade to Debian Jessie

Hi, I've just upgrade from Debian Wheezy to Debian Jessie and am getting: Fatal: master: service(lmtp): child 6761 killed with signal 11 (core dumped) It seems to be something to do with sieve. When I disable that from lmtp then everything works fine. OS: Debian Jessie Dovecot version: 2.2.13

Re: Sensible location for Sieve scripts

On Fri, 2015-06-26 at 09:40 -0600, Shawn Heisey wrote: On 6/26/2015 5:48 AM, Andrew Beverley wrote: I'm configuring some Sieve scripts for virtual users. I'd like to keep the Sieve scripts somewhere sensible. Currently, all the mail goes into /var/mail/vhosts/domain/mailbox So I

Sensible location for Sieve scripts

I'm configuring some Sieve scripts for virtual users. I'd like to keep the Sieve scripts somewhere sensible. Currently, all the mail goes into /var/mail/vhosts/domain/mailbox So I thought a good place for the sieve script might be in there as well, for example:

Re: [Dovecot] Notifications from dovecot

On Mon, 2014-05-19 at 13:07 +0200, Joakim Seeberg wrote: Hi list, im trying to build a web based system for secure communication build with standard linux software, instead of using CMS based systems. One of the requirements is to send notifications to users when receiving mail. Can a

Re: [Dovecot] Performing an action on mail receipt

On Wed, 2014-05-14 at 11:41 +0200, Jiri Bourek wrote: By user, I'd like to retrieve from a SQL database firstly which Sieve script to run (if applicable) and secondly the parameters for that particular user, in this case the external email address to notify. AFAIK PigeonHole can read

[Dovecot] Dict SQL lookups without username_field

Dear all, Is it possible to perform dict lookups with a SQL backend, without specifying the username_field in the SQL query? I am using the dict to retrieve a Sieve script. My dict configuration looks like this: map { pattern = priv/sieve/data/$id table = sieve_scripts username_field =