> On 21/01/2021 00:02 Ron Garret wrote:
>
>
> Pigeonhole/sieve has a “vacation” feature that keeps track of which addresses
> it has sent messages to already so it doesn’t send too many. The state for
> this feature seems to survive a dovecot restart, so it must be persistent
> somewhere
> On 20/01/2021 22:37 Ron Garret wrote:
>
>
> On Jan 20, 2021, at 12:32 PM, Piotr Auksztulewicz wrote:
>
> > On Wed, Jan 20, 2021 at 12:12:40PM -0800, Ron Garret wrote:
> >> 1. Is there any documentation about what “requires” are needed
> >> to access various features? The only source
Hello Dovecot developers,
I'm using a mail-crypt plugin to perform encryption at rest using per user
keys encrypted with their password. Great plugin and I really appreciate
it's continuous development and improvement.
I have a question regarding mail-crypt keys being stored in HSM. Is it
Pigeonhole/sieve has a “vacation” feature that keeps track of which addresses
it has sent messages to already so it doesn’t send too many. The state for
this feature seems to survive a dovecot restart, so it must be persistent
somewhere and not just stored in RAM. But I don’t recall
On Jan 20, 2021, at 12:32 PM, Piotr Auksztulewicz wrote:
> On Wed, Jan 20, 2021 at 12:12:40PM -0800, Ron Garret wrote:
>> 1. Is there any documentation about what “requires” are needed
>> to access various features? The only source I’ve found for this is
>> reverse-engineering examples.
>
>
On Wed, Jan 20, 2021 at 12:12:40PM -0800, Ron Garret wrote:
> 1. Is there any documentation about what “requires” are needed
> to access various features? The only source I’ve found for this is
> reverse-engineering examples.
Sieve RFCs. At least this is what I have used to learn sieve. Each
I think I figured out what happened. I think I edited the .sieve file but
forgot to save it, so I was actually running an old version that did not have
“mailbox” in the require statement.
On which note, two more questions:
1. Is there any documentation about what “requires” are needed to
On 20 Jan 2021, at 07:20, Erwan David wrote:
> On Wed, Jan 20, 2021 at 01:58:38PM CET, "@lbutlr" said:
>> On 20 Jan 2021, at 04:33, Piotr Auksztulewicz wrote:
>>> On Wed, Jan 20, 2021 at 04:27:11AM -0700, @lbutlr wrote:
set imap_pass = "lasH-hds[er$asd" # Not a real password
>>>
>>> Use
On Wed, Jan 20, 2021 at 01:58:38PM CET, "@lbutlr" said:
> On 20 Jan 2021, at 04:33, Piotr Auksztulewicz wrote:
> > On Wed, Jan 20, 2021 at 04:27:11AM -0700, @lbutlr wrote:
> >> set imap_pass = "lasH-hds[er$asd" # Not a real password
> >
> > Use single quotes around the password. Double quotes
On Wed, Jan 20, 2021 at 05:58:38AM -0700, @lbutlr wrote:
> Also… gr. Who though expansion inside a password string was a
> clever idea and can I introduce them to a clue bat? :p
Well, this is just the result of a generic config file parser, every
statement gets processed the same way. I guess
On Wed, 20 Jan 2021 at 15:59, @lbutlr wrote:
> On 20 Jan 2021, at 04:33, Piotr Auksztulewicz wrote:
> > On Wed, Jan 20, 2021 at 04:27:11AM -0700, @lbutlr wrote:
> >> set imap_pass = "lasH-hds[er$asd" # Not a real password
> >
> > Use single quotes around the password. Double quotes make $asd
On 20 Jan 2021, at 04:33, Piotr Auksztulewicz wrote:
> On Wed, Jan 20, 2021 at 04:27:11AM -0700, @lbutlr wrote:
>> set imap_pass = "lasH-hds[er$asd" # Not a real password
>
> Use single quotes around the password. Double quotes make $asd to be
> interpreted as shell variable and replaced with
On Wed, Jan 20, 2021 at 04:27:11AM -0700, @lbutlr wrote:
> set imap_pass = "lasH-hds[er$asd" # Not a real password
Use single quotes around the password. Double quotes make $asd to be
interpreted as shell variable and replaced with (most likely) empty
string, so you get a shortened passwort in
> On 20/01/2021 13:27 @lbutlr wrote:
>
>
> I have a user who is unable to use mutt to login. I tested and sent a muttrc
> that worked for me and all he needed to do was put in his username and
> password.
>
> Which failed.
>
> After some back and forth, I figured out that his password
I have a user who is unable to use mutt to login. I tested and sent a muttrc
that worked for me and all he needed to do was put in his username and password.
Which failed.
After some back and forth, I figured out that his password contains a '$' and a
'[' in it, and it seems like one of, or
Version 2.3.13 (89f716dc2). I have never seen them before.
Lefteris
On 20 Jan 2021, at 8:33 AM, Aki Tuomi wrote:
What version is this?
But this was probably caused by aborted authentication attempts when you
restarted dovecot.
Aki
> On 19/01/2021 20:45 Lefteris Tsintjelis wrote:
>
>
>
16 matches
Mail list logo
