Displaying 20 results from an estimated 1000 matches similar to: "Auth-worker, unknown scheme ARGON2ID"
2023 Feb 22
1
Auth-worker, unknown scheme ARGON2ID
> On 22/02/2023 07:00 EET James Brown <jlbrown at bordo.com.au> wrote:
>
>
> On 21 Feb 2023, at 10:12 pm, James Brown <jlbrown at bordo.com.au> wrote:
>
> >
> >
> > The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate:
> >
> > Feb 21 21:51:03 master: Info: Dovecot v2.3.20
2023 Feb 21
0
Auth-worker, unknown scheme ARGON2ID
On my current mail server I was able to upgrade everyone?s password scheme to ARGON2ID with no issues, I just had to have:
service auth {
vsz_limit = 0
}
This was an older version of macOS than the new server I?m trying to migrate to.
The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate:
Feb 21 21:51:03 master: Info: Dovecot v2.3.20
2023 Feb 22
1
Auth-worker, unknown scheme ARGON2ID
> On 22/02/2023 09:10 EET James Brown <jlbrown at bordo.com.au> wrote:
>
>
> On 22 Feb 2023, at 5:53 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>
> >
> >
> > > > >
> > > > > % locate libsodium
> > > > > /opt/homebrew/Cellar/libsodium
> > > > > /opt/homebrew/Cellar/libsodium/1.0.18_1
2023 Feb 22
1
Auth-worker, unknown scheme ARGON2ID
> On 22/02/2023 07:48 EET James Brown <jlbrown at bordo.com.au> wrote:
>
>
> > On 22 Feb 2023, at 4:14 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
> >
> >
> > > I?ve spent ages on this and am getting really desperate! :-(
> > >
> > > CPPFLAGS=-I/opt/homebrew/Cellar/openssl at 3/3.0.8/include
2006 Jul 28
1
Problems reading mbox
I'm having problems getting dovecot to read my mbox file. I have
turned on mail_debug. Log says:
Jul 28 11:03:20 Bordo-Mail-Server dovecot: Dovecot v1.0.rc2 starting up
Jul 28 11:03:36 Bordo-Mail-Server dovecot: pop3-login: Login:
user=<jlbrown>, method=PLAIN, rip=192.168.1.10, lip=192.168.1.9
Jul 28 11:03:36 Bordo-Mail-Server dovecot: POP3(jlbrown): Effective
uid=501, gid=501
Jul
2019 Jan 30
3
"unknown user - trying the next userdb" Info in log
On 30 Jan 2019, at 10:57 am, Stephan Bosch <stephan at rename-it.nl <mailto:stephan at rename-it.nl>> wrote:
>
> Op 30/01/2019 om 00:06 schreef James Brown via dovecot:
>>
>>> On 30 Jan 2019, at 9:24 am, Stephan Bosch <stephan at rename-it.nl <mailto:stephan at rename-it.nl>> wrote:
>>>
>>>
>>>
>>> Op 29/01/2019
2018 Dec 06
3
argonid and dovecote
on a FreeBSD 11.2 amd64 machine, I am trying to get Dovecot 2.3.4 to play
nice with "argonid" encryption.
In the "10-auth.conf" file, I tried:
auth_mechanisms = plain argon2id
Upon restarting dovecot, I received an error message when attempting to
actually it:
auth: FATAL: Unknown authentication mechanism "ARGON2ID"
Output from doveadm pw -l
doveadm pw -l
SHA1
2018 Dec 04
2
Lda fatal: setgid (102 from userdb lookup) failed
Sorry if this is a nubbie question, but I?m getting:
lda(jlbrown at bordo.com.au)<4444><QFg5KRHVBBxcEQAAYBwt+A>: Fatal: setgid(102 from userdb lookup) failed with euid=501(jlbrown), gid=20(staff), egid=20(staff): Operation not permitted (This binary should probably be called with process group set to 102 instead of 20(staff))
How can I fix this?
(macOS Mojave, Dovecot 2.3.4)
2019 Jan 30
2
"unknown user - trying the next userdb" Info in log
On 30 Jan 2019, at 4:35 pm, Aki Tuomi <aki.tuomi at open-xchange.com <mailto:aki.tuomi at open-xchange.com>> wrote:
>
>>
>> On 30 January 2019 at 07:12 James Brown < jlbrown at bordo.com.au <mailto:jlbrown at bordo.com.au>> wrote:
>>
>>
>> >> My settings:
>> ...
>> >> userdb {
>> >> driver = passwd
2023 Feb 22
1
Auth-worker, unknown scheme ARGON2ID
> On 22 Feb 2023, at 5:33 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>>
>> Thanks Aki, that was helpful. When I add that I get:
>>
>> checking for LIBSODIUM... no
>> configure: error: Can't build with libsodium: not found
>>
>> So I have to tell it where libsodium is.
>>
>> Tried:
>>
>>
2023 Feb 22
1
Auth-worker, unknown scheme ARGON2ID
> On 22/02/2023 08:41 EET James Brown <jlbrown at bordo.com.au> wrote:
>
>
> > On 22 Feb 2023, at 5:33 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
> > >
> > > Thanks Aki, that was helpful. When I add that I get:
> > >
> > > checking for LIBSODIUM... no
> > > configure: error: Can't build with libsodium: not
2018 Sep 26
2
Can't authenticate using ARGON2ID crypt scheme from doveadm pw w/rounds != default
I'm using dovecot version 2.3.2.1 (0719df592) and trying to use the
ARGON2ID crypt scheme for authentication using the passdb passwd-file
driver. My passdb config is very simple:
??? passdb {
????? driver = passwd-file
????? args = username_format=%u <path-to-file-here>
??? }
If I generate a password this way:
??? doveadm pw -s ARGON2ID -p 'This is a test'
I get a crypt
2018 Mar 01
2
Make fails with 2.3.0.1 & 2.2.34 on Mac OS X 10.7.5
On 1 Mar 2018, at 4:09 pm, Aki Tuomi <aki.tuomi at dovecot.fi <mailto:aki.tuomi at dovecot.fi>> wrote:
>
>
>> On 01 March 2018 at 06:21 James Brown < jlbrown at bordo.com.au <mailto:jlbrown at bordo.com.au>> wrote:
>>
>>
>> Have tried 2.3.0, 2.3.0.1 & 2.2.34.
>>
>> Compile is failing for me.
>>
>> ./configure
2019 Jan 29
2
"unknown user - trying the next userdb" Info in log
> On 30 Jan 2019, at 9:24 am, Stephan Bosch <stephan at rename-it.nl> wrote:
>
>
>
> Op 29/01/2019 om 01:51 schreef James Brown via dovecot:
>> I?ve set up a new mail server. Auth-worker is giving me this error all the time:
>>
>> auth-worker(11160): Info: passwd(sales at bordo.com.au <mailto:sales at
2009 Jun 03
3
Lost sub-mailboxes - not showing after upgrading to Dovecot from Courier-IMAP
Last night we migrated from Courier-IMAP to Dovecot 1.2RC5 and all
seems to work fairly well, but I seem to have lost all my mailboxes
apart from INBOX. The maildirs are all on the HD in the correct place
(/usr/local/virtual/bordo.com.au/jlbrown):
mail:jlbrown root# ls -l
total 21400
drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:11 .4D
drwxrwxr-x 14 _vmail _postfix 476 Jun
2018 Dec 06
2
argonid and dovecote
On Thu, 6 Dec 2018 18:16:05 +0000, Larry Rosenman stated:
>Update to the latest port in the HEAD ports tree
>
>?On 12/6/18, 11:44 AM, "dovecot on behalf of Jerry"
><dovecot-bounces at dovecot.org on behalf of jerry at seibercom.net> wrote:
>
> on a FreeBSD 11.2 amd64 machine, I am trying to get Dovecot 2.3.4 to play
> nice with "argonid"
2023 Feb 20
1
service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 268435456): Invalid argument macOS
I fixed the issue with Dovecot not starting on macOS Ventura by adding this to 10-master.conf:
service log {
vsz_limit = 0
}
But now when I try to login via Imap on port 143 I get the same error for imap-login:
Feb 20 15:55:41 imap-login: Error: Feb 20 15:55:41 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 268435456): Invalid argument
Feb 20 15:55:41 imap-login: Fatal: master:
2018 Sep 04
3
Best way to move mail from one server to another
Thanks Sam
Users not using new mail server yet.
Both old and new using maildir.
Sounds like rsync is the way to go.
Thanks for your help.
James.
Sent from my iPhone XI
> On 4 Sep 2018, at 5:41 pm, Sami Ketola <sami.ketola at dovecot.fi> wrote:
>
>
>
>> On 4 Sep 2018, at 10.20, James Brown <jlbrown at bordo.com.au> wrote:
>>
>> I?d like to
2023 Feb 28
1
"sh: doveadm: command not found" with doveadm -Dv backup -R
I?m moving from an old mail server to a new one.
On the new one, trying to transfer mailboxes from the old machine using doveadm. It fails saying it can?f find doveadm:
% sudo doveadm -Dv backup -R -u myuser at bordo.com.au remote:mail.bordo.com.au
Password:
Debug: Loading modules from directory: /usr/local/lib/dovecot/doveadm
Debug: Skipping module doveadm_acl_plugin, because dlopen() failed:
2020 Aug 16
2
generating secure ARGON2ID passwords
Hello,
I'm using dovecot 2.3.4.1 on a Debian buster system.
with Argon2ID password scheme, it's only possible to configure the
parameters used for it via the generic -r option to "doveadm pw".
A higher -r will increase time and memory comsumption.
But on my dual core VM it always uses p=1.
So it seems the needed threads can only be changed on compile time?
Will there be in