fig/guides/quick.html
passdb passwd-file {
passwd_file_path = /path/to/passwd
}
Still not working.
Anyway, this is quite long now, so thanks for any suggestions.
Jackie
> On Jan 31, 2025, at 07:09, Aki Tuomi via dovecot wrote:
>
>
>> On 30/01/2025 20:05 EET John Muccigr
After last week's struggle with the new version and my conf file, I got
everything working. Now however dovecot crashes on me every few hours.
The logs show a bunch of this kind of warning, which I find mention of on the
internets:
> Feb 07 15:13:47 imap(58317): Warning: Time moved forward 48.8
Further info: this whole "time moved forward" thing had a long discussion and
eventual fix in 2.3:
https://forums.freebsd.org/threads/dovecot-time-moved-forwards.82886/page-2
For the record, how my clock compares with a standard:
> > sntp time.euro.apple.com
> +0.109836 +/- 0.031550 time.euro.a
Done. Thanks.
J
> On Feb 1, 2025, at 11:51, Aki Tuomi wrote:
>
> Unless there is such setting somewhere in your base config, I would strongly
> suggest
>
> auth_username_format = %{user|lower}
>
> Aki
>> On 01/02/2025 12:18 EET John Muccigrosso via dovecot
I got bitten by the upgrade from 2.3 to 2.4 on my MacOS laptop. I know enough
to be dangerous here and had a set-up that was working fine, but now I can't
quite figure out how to modify my conf file to work correctly.
The current error I'm getting is that there is no group "dovecot" even though
(Looks like I forgot to reply to the list last time.)
With `sudo dovecot -F`, I'm now getting:
Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument
The old(?) solution doesn't work for me:
default_vsz_limit = 0
It reports: doveconf: Fatal: Error in configuration file
/opt/homebrew/etc
{
passwd_file_path = /Users/%{user}/passwd
}
---
Thanks to Timo and Aki for the help.
> On Feb 1, 2025, at 10:16, Timo Sirainen via dovecot
> wrote:
>
> On 1. Feb 2025, at 10.27, John Muccigrosso via dovecot
> wrote:
>>
>> Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid
As this continues to happen and the list seems uninterested, how exactly should
I report this bug?
Thanks.
J
> On Feb 11, 2025, at 12:18, J wrote:
>
> Further info: this whole "time moved forward" thing had a long discussion and
> eventual fix in 2.3:
>
> https://forums.freebsd.org/threads/d
This is of course the same issue I’ve been raising for weeks now. I’ve been
waiting for the home brew upgrade.
J
> On Apr 7, 2025, at 10:19, Emmanuel Bardet via dovecot
> wrote:
>
> Hello Aki,
>
> 2.4.0 is the latest available via homebrew. I'm not too sure I can upgrade
> manually.
>
>
Wondering if there's anyone who can help with this, which is still happening.
Yesterday's crash in the logs:
> Feb 26 15:55:07 imap(82011): Panic: file ./time-util.h: line 40
(timeval_add_usecs): assertion failed: (usecs >= 0)
Thanks.
J
On Feb 15, 2025, at 11:18, John Muccigrosso
wro
aybe the build-in RTC doesn't keep the time
> as it should caused i.e. by a depleted CMOS battery (note: No CMOS battery in
> portables though).
>
> I would do a SMC reset on that laptop. If this doesn't help consider a NVRAM
> (or PRAM) reset.
>
> Tamsy
>
>
&
OK, first here's a series of warnings while the laptop was closed, 18:43-19:04:
Mar 02 18:44:02 imap(1392): Warning: Time moved forward 24.925040 seconds
Mar 02 18:44:02 imap(1397): Warning: Time moved forward 24.925062 seconds
Mar 02 19:01:24 imap(1397): Warning: Time moved forward 993.009103 sec
OK, still crashed overnight while the laptop was closed.
Here's the log. I had shut the laptop a bit before this first entry:
Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds -
adjusting timeouts.
Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_u
Thanks.
It happens in various scenarios, including when I'm actively working on the
computer (or it's at least not sleeping). It also happens overnight when the
computer should be sleeping. It doesn't seem to happen on resuming.
For example, here's this morning's (or late last night's) when the
14 matches
Mail list logo
