similar to: Expire plugin with PostgreSQL

The wiki entry at http://wiki.dovecot.org/Plugins/Expire needs an update for Dovecot 1.2 and PostgreSQL: -- v1.2+: CREATE OR REPLACE FUNCTION merge_expires() RETURNS TRIGGER AS $$ BEGIN IF exists(SELECT 1 FROM expires WHERE username = NEW.username AND mailbox = NEW.mailbox) THEN UPDATE expires SET expire_stamp = NEW.expire_stamp WHERE username = NEW.username AND mailbox = NEW.mailbox;

Anyone out there using expire? At this point, I'm not sure that it's even running. It was touching the plugin libraries yesterday, but doesn't appear to be doing so today. The plugin directory wasn't explictly set, so I've done so now, but it's still not touching these. Anyone have a cf file I could take a look at, or any ideas as to what might be happening? Thanks!

On 21/05/2019 15:45, mabi via dovecot wrote: > ??????? Original Message ??????? > On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot > <dovecot at dovecot.org> wrote: > >> So looking into this with a postgresql databse to work with: the >> above query does not work. You have to specify either the column name >> or the constraint name that you expect to

Dear all, I'm trying to get last_login plugin working with PostgreSQL, but seems Dovecot doesn't handle duplicate key while updating last login time (note: same setting works fine with MariaDB). I wonder whether it's a bug of Dovecot or i should handle this with PostgreSQL trigger. OS: OpenBSD 6.4 (amd64) Dovecot: 2.2.36 PostgreSQL: 10.5 Error log: ################### Mar 31

Hello, I am trying to setup the last_login plugin on Dovecot 2.3 in order to log a user's last IMAP login into a separate PostgreSQL table called last_login. I am actually following that guide: https://docs.iredmail.org/track.user.last.login.html with the exception that I use PostgreSQL instead of MySQL. So far it works at least for the very first login of a user but it looks like Dict

??????? Original Message ??????? On Sunday, May 19, 2019 2:58 PM, John Fawcett via dovecot <dovecot at dovecot.org> wrote: > I guess it is not supported for PostgreSQL or Sqlite, since they don't > have "ON DUPLICATE KEY UPDATE" statement which is what is being used in > MySQL. That's it, PostgreSQL does not have "ON DUPLICATE KEY" but instead uses

On 19/05/2019 22:45, John Fawcett via dovecot wrote: > On 19/05/2019 22:37, John Fawcett via dovecot wrote: >> On 19/05/2019 20:31, mabi via dovecot wrote: >>> >>> ??????? Original Message ??????? >>> On Sunday, May 19, 2019 7:36 PM, John Fawcett via dovecot >>> <dovecot at dovecot.org> wrote: >>>> >>>> Attached is a

Running dovecot 1.2.12 on ubuntu 10.10. Here is the problem: I have mysql backend for expire. I am using the dovecot-postfix package which creates /etc/dovecot/conf.d/01-mail-stack-delivery.conf which looks like this: # Some general options protocols = imap imaps managesieve disable_plaintext_auth = no ssl = yes ssl_cert_file = /etc/ssl/certs/ssl-mail.pem ssl_key_file =

Hi, I've changed my running qmail/vpopmail/procmail/courier-imap/sqwebmail installation to qmail/vpopmail/siege/dovecot/horde imp. So far, I've got everything running. Authentification with vpopmail as passdb is working, Mail delivery with siege into different Mail folders is working as well. One of the reasons why I switched to dovecot was the expire plugin and right now I'm trying

Hi all, Maybe someone here can help me with this problem, not sure if this is a configuration issue or an actual bug. my daily cron job says: #!/bin/sh doveadm expunge -A mailbox Junk savedbefore 14d doveadm expunge -A mailbox Trash savedbefore 30d doveadm expunge -A mailbox "Trash.*" savedbefore 30d But it hasn't been deleting any messages in a long time, I'm not sure when

Hi all, I'm experimenting with the expire plugin and seem have run into a small problem. I am using Dovecot 1.2.4 on a test server. The config is taken mostly verbatim from the expire plugin wiki page [1], using MySQL as a database. See below for detailed output. Namespace "private" has "/" configured as mailbox separator: namespace private { separator = /

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 22 May 2019, John Fawcett via dovecot wrote: > an update when insert fails seems to be a MySQL specific extension to > standard Sql. So I think that it's clear that support for PostgreSql and > Sqlite? needs to be implemented. The same issue likely exist in other > plugins too, for example expire. > > My doubts are

Hello, Dovecot does not fill expires table when moving messages to Trash or Junk folder. I looked all over mailing list and googled around and cannot find what could be wrong - pleas help :) Dict works for quota, so I presume connection to mysql is not a problem - mailuser has Select,Insert,Update,Delete privileges over quota and expires table (log below for deleting message) dovecot

Hello, I followed the instructions on http://wiki2.dovecot.org/Plugins/Expire to configure the expire plugin, but when I move a message to the Trash folder, I get the following error messages in my logfile: dovecot: dict: Error: sqlite: exec(INSERT INTO expires (expire_stamp,username,mailbox) VALUES ('1292525469','christoph','Trash')) failed: unable to open database

On 28.5.2019 22.34, mabi via dovecot wrote: > ??????? Original Message ??????? > On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot > <dovecot at dovecot.org> wrote: > >> there's no field name that is obviously the primary key. I've >> reworked the patch to use the postgres default primary key constraint >> name (tablename_pkey). >>

Hi, I'm testing out the dovecot expire plugin, and not seeing anything go into the database I've got set up. It's a mysql db. I've gone in and verified that the db is set up correctly. The socket is set up so that deliver should be able to talk to the db, but I'm not seeing anything in the expires table when I look. Is there anywhere that expire can log to so I can see

Hello, I've configured dovecot to use expire plugin: heres my dovecot -n: --------------------- # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4 auth_mechanisms = plain login dict { expire = mysql:/etc/dovecot/dovecot-dict-expire-sql.conf.ext } mail_location = maildir:/home/mail/vhosts/%d/%n mail_plugins = expire mail_privileged_group = vmail

Hi, testing expire plugin I get an error message "User lookup failed": /usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool -test Error: userdb(lukas at manual.at) didn't return uid Info: User lookup failed: lukas at manual.at Info: gkaefer2 at manual.at/INBOX.Sent: stop, expire time in future: Wed Mar 31 14:38:33 2010 Reviewing the expires database I see simmilar

I was struggling for a while to get the expire plugin to expunge mail. I was using (and still would like to use) PAM as passdb and passwd as userdb but with this I could not get the expire-tool to delete any mails. For debugging purpose I switch to passwd-file as userdb/passdb and enabled mail_debug=yes. 1. passwd-file contains home directory and userdb_mail (->working!)

All of the mailboxes on this system are in MailDIR format. None of the users delete mail off of the server after POPing their accounts. This is the present setting: expire = Trash 7 Spam 30 expire_dict = proxy::expire Is that correct for MailDIR style mailboxes? It doesn't appear correct; however, I have not been able to find any specific documentation on expire with MailDIR style