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 instea
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 2:58 PM, John Fawcett via dovecot
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 D
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 3:57 PM, Aki Tuomi wrote:
> It would be a feature request, also note that it's only available since
> version 9.5, so it really won't help anyone before that.
Would opening an issue as feature request on GitHub on the dovecot/core project
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 4:44 PM, John Fawcett via dovecot
wrote:
> I don't have PostgresSql, would you be able to verify if this syntax would
> work: INSERT INTO last_logins (last_login,username,domain) VALUES
> (1558273000,'u...@domain.tld','domain.tld') ON CO
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 7:36 PM, John Fawcett via dovecot
wrote:
> Attached is a tentative patch. I've verified no regression for mysql. There
> should be no regression for sqlite as the code path is identical.
>
> Are you able to test for pgsql? As mentioned by
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 10:45 PM, John Fawcett via dovecot
wrote:
> so basically if this works just as well:
>
> INSERT INTO last_logins (last_login,username,domain) VALUES
> (1558273000,'u...@domain.tld','domain.tld') ON CONFLICT DO UPDATE SET
> last_login=155
‐‐‐ Original Message ‐‐‐
On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot
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 be violated
Hello,
I am running Dovecot 2.3.5 package on OpenBSD 6.5 and it looks like this bug
which has been fixed in 2.3.6 is hitting me:
lib-smtp: client: Fix infinite loop in XCLIENT command interaction with server
https://github.com/dovecot/core/commit/5d03f39b345127b80d145ee90772739baa7ab810
so I wa
‐‐‐ Original Message ‐‐‐
On Friday, May 24, 2019 10:40 AM, Aki Tuomi via dovecot
wrote:
> Try setting login_trusted_networks=
Thank you Aki for your answer. Unfortunately on my Dovecot mailbox backend
servers I already have login_trusted_networks set to the IP of my Dovecot LMTP
proxy
‐‐‐ Original Message ‐‐‐
On Friday, May 24, 2019 11:23 AM, Aki Tuomi wrote:
> There is no maintainer for this package in OpenBSD?
Not really, well AFAIK packages for OpenBSD are updated every 6 months with the
new release of OpenBSD which is always around May and November. Exceptions ar
‐‐‐ Original Message ‐‐‐
On Saturday, May 25, 2019 12:18 AM, Sami Ketola via dovecot
wrote:
> just add:
>
> protocol lmtp {
> login_trusted_networks=
> }
Thank you so much Sami for the further details. I added the
login_trusted_networks specifically to the lmtp protocol and now I can s
‐‐‐ Original Message ‐‐‐
On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot
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).
>
> The attached fix should work i
‐‐‐ Original Message ‐‐‐
On Wednesday, May 29, 2019 8:01 AM, Aki Tuomi
wrote:
> We'll take this under consideration, but no promises.
Thank you very much Aki for consdering this. It would be really fair for all
the PostgreSQL users out there.
Hello,
I am running Dovecot 2.3.5.1 on OpenBSD 6.5 with RainLoop as IMAP webmail
client and just noticed the following error messages about duplicate
transaction log sequences in the index log:
Jul 01 13:15:58 Error: imap()<21324>:
Transaction log /var/vmail///dovecot.index.log:
duplicate tra
Hello,
I am using the mail_crypt plugin with Dovecot 2.3 and have issues trying to use
a mail crypt private password which contains a percent "%" character as you can
see below:
$ doveadm -o plugin/mail_crypt_private_password=SomethingWith\%Percent mailbox
cryptokey generate -u em...@domain.tl
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:21 PM, Aki Tuomi wrote:
> Hi, you need to escape % with %%. We are aware of a bug affecting when %
> comes in from some field via userdb, and we are looking into how to fix this.
Hi Aki,
Thank you very much for your very fast answer
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:39 PM, Aki Tuomi wrote:
> Are you by chance accessing mails using two different dovecot instances? This
> is not supported to be done concurrently, you need to use some sort of
> solution, such as dovecot director, to ensure user lands
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:50 PM, Aki Tuomi via dovecot
wrote:
> Please reviewhttps://wiki.dovecot.org/NFS if you have not already done so.
I actually already went through this guide once but noticed now that I had the
mail_fsync parameter set to "optimized", s
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:32 PM, Aki Tuomi via dovecot
wrote:
> I don't actually recommend using password directly from user as password for
> private keys, I recommend running them thru some hash / pkcs5 before that.
That's a great idea and makes things even
Hello,
I am testing mail_crypt plugin with per account encryption and wanted to
generate a new keypair for an account but noticed that I now end up with 2
keypairs where one is active and the other inactive as you can see below:
$ doveadm mailbox cryptokey list -u em...@domain.tld -U
Folder Ac
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:21 PM, Aki Tuomi wrote:
> Hi, you need to escape % with %%. We are aware of a bug affecting when %
> comes in from some field via userdb, and we are looking into how to fix this.
Aki, I was wondering, does this bug also affect the chan
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 11:17 AM, @lbutlr via dovecot
wrote:
> > Is it possible to delete the inactive keypair? if yes how?
>
> Wouldn’t you then be unable to *unencrypt* previous emails?
That's also what I thought but based on my understand and on the documen
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 11:18 AM, Aki Tuomi via dovecot
wrote:
> It depends. You can use either one, seehttps://wiki2.dovecot.org/Variables
>
> I think the safest option would be setup LDAP so that the private
> password would be only readable by self, and have
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 3:10 PM, Aki Tuomi wrote:
> > I am also not sure about sha512 hash because the Dovecot Variable wiki page
> > does not mention sha512 but only sha256. Is sha512 also available?
>
> Yes
Thank you Aki for confirming. I tried it out and it
24 matches
Mail list logo
