Hi,
Am 01.11.21 um 18:00 schrieb infoomatic:
> please inform the mailing list if problems persist, thank you!
>
> I am about to migrate to FreeBSD ...
it does. Fresh install with a config, that used to work:
# doveadm sync -u x...@zzz.de tcps:mail.bruecko.de
doveadm(x...@zzz.de): Panic: file ar
please inform the mailing list if problems persist, thank you!
I am about to migrate to FreeBSD ...
On 01.11.21 13:53, Hanns Mattes wrote:
Hi,
Am 01.11.21 um 00:51 schrieb Hanns Mattes:
Hi,
Am 01.11.21 um 00:27 schrieb infoomatic:
does 2.3.17_1 from ports fix the problem?
I'm building own
Hi,
Am 01.11.21 um 00:51 schrieb Hanns Mattes:
> Hi,
>
> Am 01.11.21 um 00:27 schrieb infoomatic:
>> does 2.3.17_1 from ports fix the problem?
>
> I'm building own packages with poudriere and "pkg info dovecot" says
> it's 2.3.17_1
>
> Given the fact that this version is dated 2021-10-28 I'm no
Hi,
Am 01.11.21 um 00:27 schrieb infoomatic:
> does 2.3.17_1 from ports fix the problem?
I'm building own packages with poudriere and "pkg info dovecot" says
it's 2.3.17_1
Given the fact that this version is dated 2021-10-28 I'm not sure, if
its part of the problem or the solution.
Regards Hann
does 2.3.17_1 from ports fix the problem?
On 01.11.21 00:01, Hanns Mattes wrote:
Hi,
Am 31.10.21 um 18:30 schrieb Hanns Mattes:
Hi, me again,
Hanns Mattes schrieb:
I stand corrected and forgot to remove
things are working, except replication.
no, they don't.
okay, imap logins are working
Hi,
Am 31.10.21 um 18:30 schrieb Hanns Mattes:
> Hi, me again,
> Hanns Mattes schrieb:
> I stand corrected and forgot to remove
>> things are working, except replication.
> no, they don't.
okay, imap logins are working again.
Replication still failing. My guess is, that my master-user
configura
Hi, me again,
Hanns Mattes schrieb:
I stand corrected and forgot to remove
>things are working, except replication.
no, they don't.
Regards Hanns
Hi,
I've installed Dovecot on a freshly installed machine running Freebsd
13.4.
Configuration was copied from an earlier installation, which worked
perfectly, until I screwed an update.
AFAICS things are working, except replication. I see tons of Errors on
the remote and the local machine
Oct 3
On Jun 8, 2012, at 10:25 AM, Timo Sirainen wrote:
> I think the answer to this is simply that Dovecot v1.0 didn't tell PAM the
> rhost. Upgrade.
Will do. What you say fits with what I see in the logs and
is a lot simpler than many other suggestions. And you do
have some credibility in this ar
On 6.6.2012, at 2.08, Glenn English wrote:
>> And these brute force attempts would be logged, each one.
>
> They are, with no rhost. And there are other brute force attempts
> that *do* have IPs.
I think the answer to this is simply that Dovecot v1.0 didn't tell PAM the
rhost. Upgrade.
On Jun 5, 2012, at 3:53 PM, /dev/rob0 wrote:
> What suspicions were confirmed?
At first I thought that somebody was TCP'ing in and somehow
turning off the remote IP in the log so I couldn't block it.
Then an answer from another mailing list, and a little thinking,
made it occur to me that may
Glenn English wrote:
Maybe someone is brute forcing your server's Postfix authenticated
SMTP service since Postfix can be configured to use Dovecot's SASL
authentication framework.
and for the suggestion -- I do have Postfix using Dovecot-Auth checking
for SASL.
I think I'm going to re-insta
On Tue, Jun 05, 2012 at 09:38:49AM -0600, Glenn English wrote:
> On Jun 4, 2012, at 8:45 PM, Joseph Tam wrote:
> > If dovecot-auth is getting input from a local socket, then rhost
> > information is irrelevant since the host doing the asking is the
> > server itself (maybe from another daemon con
On Jun 4, 2012, at 8:45 PM, Joseph Tam wrote:
> If dovecot-auth is getting input from a local socket, then rhost
> information is irrelevant since the host doing the asking is the server
> itself (maybe from another daemon connected to a remote host).
Thanks for the confirmation of my suspicions
Glenn English writes:
I'm getting a lot of what I think is a local socket asking
dovecot:auth to verify username/passwords:
May 31 09:00:54 server dovecot-auth: pam_unix(dovecot:auth): authentication
failure; logname= uid=0 euid=0 tty=dovecot ruser=admin rhost=
If dovecot-auth is getting in
I forgot to include this config info:
> # 1.0.15: /etc/dovecot/dovecot.conf
> log_timestamp: %Y-%m-%d %H:%M:%S
> protocols: imap pop3
> ssl_listen: *
> ssl_disable: yes
> disable_plaintext_auth: no
> login_dir: /var/run/dovecot/login
> login_executable(default): /usr/lib/dovecot/imap-login
> logi
Debian Lenny, Dovecot v 1.0.15.
I'm getting a lot of what I think is a local socket asking
dovecot:auth to verify username/passwords:
> May 31 09:00:54 server dovecot-auth: pam_unix(dovecot:auth): authentication
> failure; logname= uid=0 euid=0 tty=dovecot ruser=admin rhost=
Note the empty 'r
17 matches
Mail list logo
