> On 28/01/2021 20:22 Malte Schmidt wrote:
>
>
> Setting "auth_cache_verify_password_with_worker = yes" in order to leverage
> multiple cores for the Dovecot authentication-process causes Dovecot not to
> proxy anymore. With debug-logging I figured:
>
>
Did you try with `doveadm pw -t 'hash-goes-here'`?
Sometimes you need to use
passdb {
driver = passwd-file
args = scheme=your-pw-scheme /path/to/file
}
Note that the path must be placed last.
Aki
> On 28/01/2021 20:53 Gregory Sloop wrote:
>
>
> Anyone?
>
>
>
>
>
>Trying
Thanks for the patch, we'll take a look at it.
Aki
> On 29/01/2021 04:49 Duc Anh Do wrote:
>
>
> Hi all,
>
> Because I think this is a race condition so instead of using only one
> current_ioloop:
> * I create ioloop for each Backend in the list of Director
> * I think connections from
Hi,
We are looking for a tool for bulk SMTP testing / Email validation using
telnet or similar protocol ( which doesn't send the mails )
It generally involves steps like NSlookup to check MX of destination server,
opening port25, telnet to communicate with client server, then finally
Google is responding to me as Unauthorized.
So I need to send my credentials such as access token in the request
parameter for authentication in google’s Get User API request.
But I don’t know how to configure dovecot to achieve that.
Could you please help me with this?
Best regards,
tify in the callback function. Might this
> be a race condition?
> I understand there's a workaround to do my work:
>
>- Run *doveadm user '*'* to get all users
>- Loop through all users and run *doveadm quota get -u xxx*
>
>
> Thanks,
> Anh Do
>
--
Thanks,
Duc Anh
Email: doducanh2...@gmail.com
Skype: ducanh.do88
Mobile: +84975730526
fix-doveadm-quota-director-20210128-2055.patch
Description: Binary data
On Thu, 28 Jan 2021, Michael Peddemors wrote:
Given the reputation of the Azure IP space, be hesitant to start operating an
email server there, UNLESS you can get MS to give you SWIP or 'rwhois' for
your IP space.
As long as it's only dovecot (IMAP) and not anything doing SMTP, there should
Anyone?
Trying to get master users working.
I'm not sure what info would be best, but here's the detail I have now, in
trying to get it working.
Setup the master user file, and enabled master users in the conf files.
Created the master user file and user/password hash.
Turned on
On 1/28/2021 11:14 AM, Maciej Milaszewski wrote:
Hi
For test I crete a new director with 2.3.13 and node 2.3.13 I mount
storage via nfs with this same options:
rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120
I create a simple MTA and
Your clue is in the log:
1611654464.207331 "message": "Request is missing required authentication
credential. Expected OAuth 2 access token, login cookie or other valid
authentication credential. See
https://developers.google.com/identity/sign-in/web/devconsole-project.;,
1611654464.207331
Setting "auth_cache_verify_password_with_worker = yes" in order to leverage
multiple cores for the Dovecot authentication-process causes Dovecot not to
proxy anymore. With debug-logging I figured:
auth_cache_verify_password_with_worker = no
passdb out: OK 1 user=username host=bla port=10993
Hi
For test I crete a new director with 2.3.13 and node 2.3.13 I mount
storage via nfs with this same options:
rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120
I create a simple MTA and change MX to thi same like director1
In kernel
Given the reputation of the Azure IP space, be hesitant to start
operating an email server there, UNLESS you can get MS to give you SWIP
or 'rwhois' for your IP space.
Just an FYI..
High levels' of AUTH attacks originating from that space as well. To
the point we even have a reputation list
> On 28/01/2021 16:55 Tobias Stein wrote:
>
>
> Hi Aki,
>
> Thanks for your prompt reply! :-)
> And because i classically forgot to attach
> the dovecot-sysreport, i'll deliver it now. :-)
>
>
> Yes, you're right. Setting :LAYOUT=fs would be a workaround.
> I'd also have to migrate every
Hi Aki,
Thanks for your prompt reply! :-)
And because i classically forgot to attach
the dovecot-sysreport, i'll deliver it now. :-)
Yes, you're right. Setting :LAYOUT=fs would be a workaround.
I'd also have to migrate every
single mailbox to the new hierarchical layout.
The hierarchical
On 2021/01/28 14:51, Aki Tuomi wrote:
> Hi!
>
> Would it be possible for you to provide the mail through obfuscation.
>
> You can use https://dovecot.org/tools/maildir-obfuscate.pl for this purpose.
>
> If you are using maildir format, you can decompress the mail with lz4
> decompression tool.
> On 28/01/2021 15:15 Tobias Stein wrote:
>
>
> Hi,
>
> i'm running Dovecot 2.3.14.alpha0 with shared namespaces
> and stumbled across some errors messages logged,
> when the list of subscribed mailboxes is queried by a client.
> For every distinct account of in the list of subscriptions
>
Hi,
i'm running Dovecot 2.3.14.alpha0 with shared namespaces
and stumbled across some errors messages logged,
when the list of subscribed mailboxes is queried by a client.
For every distinct account of in the list of subscriptions
two corresponding lines are logged:
Jan 28 11:42:34 mx1 dovecot:
Hi!
Would it be possible for you to provide the mail through obfuscation.
You can use https://dovecot.org/tools/maildir-obfuscate.pl for this purpose.
If you are using maildir format, you can decompress the mail with lz4
decompression tool. If you are using dbox format, it's slightly trickier
On 2021-01-24, Stuart Henderson wrote:
> I'm seeing this on some mailboxes with 2.13 on OpenBSD amd64 (recent
> snapshot):
>
> dovecot: imap(sthen)<47220>: Panic: file istream.c: line
> 332 (i_stream_read_memarea): assertion failed: (!stream->blocking)
>
> Using sieve, imapsieve, replicator,
20 matches
Mail list logo
