Hi,
I am experiencing similar error messages when setting passdb to
mechanisms = plain login.
More details can be found at
https://github.com/orgs/docker-mailserver/discussions/3836.
I hope this information helps.
Regards,
James
On 5/07/2024 02:32, Oliver Krone via dovecot wrote:
Hi the
Hello,
After adding `mechanisms = plain login` to passdb (passwd-file),
`doveadm -D sync -u e...@example.com -d -N -l 30 -U` failed with
```
Jan 26 06:49:22 doveadm(e...@example.com): Error:
remote(server2.example.com:61526): doveadm(1.1.1.1,e...@example.com):
auth-master: passdb lookup(e...@
On 25/10/2019 00:00, Daniel Miller via dovecot wrote:
So, given that the complete address is used as the username I now use:
iterate_query = SELECT username FROM mailbox
https://doc.dovecot.org/configuration_manual/authentication/sql/#user-iteration
...says that iterate_query has two variants
On 07/08/2019 11:19, James via dovecot wrote:
My more simplistic policy does not need both. I perform whitelist,
blacklist, geo and greylist
...and DNSBL which where I started with the policyserver, "Can dovecot
do DNSBL?", only indirectly via a policyserver. This is better as
On 07/08/2019 11:02, Aki Tuomi via dovecot wrote:
before and after auth? roundcube webmail reports an error with only
auth_policy_check_before_auth. I cannot see why. The simple and lazy
solution is to use double auth_policy_check_!
...
The double-check is for places which want to implemen
On 06/08/2019 06:46, Aki Tuomi via dovecot wrote:
On 2.8.2019 13.45, James via dovecot wrote:
My auth process is dumping core. This happens several times per day
...
There is an easy fix for this, attached.
Patch applied; no core dump in 24 hours.
This appears to have fixed the problem
On 02/08/2019 11:45, James via dovecot wrote:
My auth process is dumping core. This happens several times per day but
dovecot can operate normally for hours between errors.
The crash occurs in src/auth/auth-policy.c, line 356:
t@1 (l@1) program terminated by signal SEGV (no mapping at the
My auth process is dumping core. This happens several times per day but
dovecot can operate normally for hours between errors.
The crash occurs in src/auth/auth-policy.c, line 356:
t@1 (l@1) program terminated by signal SEGV (no mapping at the fault
address)
Current function is auth_policy_p
On 09/07/2019 06:35, Aki Tuomi via dovecot wrote:
As for 1st, isn't gcc 3 rather old?
As is Solaris 10. Solaris 10 predates gcc4 and comes/came with gcc3. No
one says we have keep using the system gcc3 exclusively. 9.1.0 works too.
Solaris 10 03/05 = March 2005, release January 31, 2005 [
On 09/07/2019 01:02, Joseph Tam via dovecot wrote:
Issue 2) Cannot build with --enable-hardening
Using gcc 9.1.0, "configure" step fails because fd passing was
broken, but the real problem was a compilation failure when
"--enable-hardening" is used. Demonstration:
See:
https://do
On 10/06/2019 14:40, Roderick Johnstone via dovecot wrote:
Compiling dovecot 2.2.36.1 with the native compiler on Solaris 10 is
giving the error below.
...
-m64 -c -o sha3.lo sha3.c
libtool: compile: cc -DHAVE_CONFIG_H -I. -I../..
-I/export/home/exim_build_20190605/build_local/include -m64 -
On 30/04/2019 14:21, Aki Tuomi via dovecot wrote:
https://dovecot.org/releases/2.3/dovecot-2.3.6.tar.gz
Trivial but...
"mail-index-transaction-update.c", line 198: void function cannot return
value
Thanks.
--- ../original/src/lib-index/mail-index-transaction-update.c 2019-04-30
13:25:0
On 12/04/2019 08:42, Aki Tuomi via dovecot wrote:
On 12.4.2019 10.34, James via dovecot wrote:
On 12/04/2019 08:24, Aki Tuomi via dovecot wrote:
Weakforced uses Lua so you can easily integrate DNSBL support into it.
How does this help Dovecot block?
A link to some documentation or example
On 12/04/2019 08:24, Aki Tuomi via dovecot wrote:
Weakforced uses Lua so you can easily integrate DNSBL support into it.
How does this help Dovecot block?
A link to some documentation or example perhaps?
We will not add DNSBL support to dovecot at this time.
Is there a reason why you will
On 11/04/2019 14:33, Anton Dollmaier via dovecot wrote:
Which is why a dnsbl for dovecot is a good idea. I do not believe the
agents behind these login attempts are only targeting me, hence the
addresses should be shared via a dnsbl.
Probably there's an existing solution for both problems (su
On 11/04/2019 12:49, Marc Roos via dovecot wrote:
Yes indeed, we have already own dnsbl's for smtp and ssh/ftp access. How
do you have one setup for dovecot connections?
Two answers:
1. I wrote my own very simple implementation but it does not share other
people's data. Sharing the key to vi
On 11/04/2019 11:43, Marc Roos via dovecot wrote:
A. With the fail2ban solution
- you 'solve' that the current ip is not able to access you
It is only a solution if there are subsequent attempts from the same
address. I currently have several thousand addresses blocked due to
dovecot log
On 02/04/2019 05:42, Richard Hector via dovecot wrote:
I'm using PostgreSQL for my auth db. I used the example CREATE TABLE
statement in the config file, but now I find the fields are too short. I
assume dovecot will be fine with 'text' type columns replacing the
varchars? Or failing that, I can
https://wiki.dovecot.org/SSL/DovecotConfiguration#Different_certificates_per_IP_and_protocol
says:
local 192.0.2.10 { # instead of IP you can also use hostname, which will
be resolved
However if the name resolves to multiple values only one is used.
Test.
Choose any name with multiple values,
I have an imap and pop3 for the same account.
When I delete a message from imap and then fetch the mail from the pop3
account, it retrieves the deleted message.
I am using thunderbird for the MTA.
Does anyone know why it happens?
It could be a timing issue.
20 matches
Mail list logo