our query
frankly "I see around 5-6 times per day the following warning" as reason
for writing a mail and continue insist the problem is on your side shows
missing network understanding
Am 04.02.2015 um 17:48 schrieb ML mail:
> Thanks for your comments. I understand as DNS us
the way.
I am not running a local DNS cache on the server. As suggested using a local
DNS cache would simply fix this issue but I am more interested to know what is
generating these slow DNS queries...
On Wednesday, February 4, 2015 2:59 PM, LuKreme wrote:
On 04 Feb 2015, at 03:38 , ML mail
Hello,
I am running a dovecot and proxy server on two different virtual machines and
on the dovecot proxy server I see around 5-6 times per day the following
warning:
Feb 03 16:15:12 auth: Warning:
proxy(em...@domain.com,xxx.xxx.xxx.xxx,): DNS lookup for
mailboxserver.domain.com took 1.550 s
Thanks for your tip regarding the busy network.
I am using a one year old Cisco Catalyst 2960S (WS-C2960S-48TD-L) with cat6e
cables and my network should not be overloaded as far as I know. My mailbox and
mail proxy servers are on two different virtual machines on two different
servers. It coul
ction reset by peer
maybe around 20-30 per day.
On Friday, January 30, 2015 9:28 AM, ML mail wrote:
Hello,
I was checking the errors on my mailbox server using "doveadm log errors" and
found that around 2-3 times a day I get the following error:
Jan 29 22:14:43 auth: Error: auth
BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 30 Jan 2015, ML mail wrote:
> I was checking the errors on my mailbox server using "doveadm log errors" and
> found that around 2-3 times a day I get the following error:
>
> Jan 29 22:14:43 auth: Error: auth worker: Aborte
Hello,
I was checking the errors on my mailbox server using "doveadm log errors" and
found that around 2-3 times a day I get the following error:
Jan 29 22:14:43 auth: Error: auth worker: Aborted request: Lookup timed out
Any ideas if this is a bad sign? For example some timeout on my side wh
Hello
I am using the quota warnings e-mail feature of dovecot to warn users at 80%
and 95%. The issue here is that I have one use who his mailbox is now back down
to 20% but he still receives the 95% mailbox full warning mail. Any ideas what
could be wrong or what to do?
My dovecot config of t
spammer who abuses this limit by attaching a big image...
Regards
ML
On Thursday, January 15, 2015 12:23 PM, ML mail wrote:
Thank you for your helpful hints on debugging this issue. I wanted first to get
the mail which generates this error but unfortunately the user already deleted
it as
generated this error due
to the size of the mail?
Regards
ML
On Thursday, January 15, 2015 8:29 AM, Steffen Kaiser
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Jan 2015, ML mail wrote:
It would be better to have the original question & discussion at the top,
so one c
tener {
port = 12345
}
}
service imap {
process_limit = 4096
}
service lmtp {
inet_listener lmtp {
port = 24
}
}
service quota-warning {
executable = script /usr/local/bin/quota-warning.sh
unix_listener quota-warning {
user = vmail
}
user = vmail
}
ssl_cert = wrote:
On 01/14/2015 03:05 PM, ML
Hello,
I am using the antispam plugin of Dovecot with SpamAssassin and in some cases
when users move back mails from the Spam folder to their INBOX (false positive)
they get the following error message:
[SERVERBUG] failed to send mail
Does anyone have an idea what could be the issue here? It i
Hello,
I am wondering which variant is more secure for user authentication and
password scheme. Basically I am looking at both variants:
1) MD5-CRYPT password scheme storage with CRAM-MD5 auth mechanism
2) SHA512-CRYPT password scheme storage with PLAIN auth mechanism
In my opinion the option 2
Hello,
It looks like my iteration SQL query (iterate_query) does not work as when I
try to run "doveadm quota recalc -A" I get the following error:
$ sudo -u vmail doveadm quota recalc -A
doveadm(nobody): Error: user nobody: Mail access for users with UID 65534 not
permitted (see first_valid_u
Hi Trent,
Thanks for your exhaustive explanation now it is clear. What was unclear to me
was the fact that the IMAP proxy server has to take care of the
authentication in this case of using a master user and therefore it
needs access to the passwords (in my case stored in the mailbox table in
Hello,
I would like to know if it possible to have a dovecot IMAP proxy frontend where
CRAM-MD5 can be used as auth mechanism (assuming I would be using a master
user/password on the dovecot IMAP backend/mailbox)? I have read a few times the
following http://wiki2.dovecot.org/PasswordDatabase/E
16 matches
Mail list logo
