Doug,
On 03/16/2017 11:23 PM, Doug Barton wrote:
Your pattern seems a little too complicated. See below.
I acquired this script from:
http://www.campworld.net/thewiki/pmwiki.php/LinuxServersCentOS/Cent6VirtMailServer
No telling where he got it from. So I greatly appreciate any and all
advi
Your pattern seems a little too complicated. See below.
On 03/16/2017 02:20 PM, Robert Moskowitz wrote:
if exists "X-Spam-Flag" {
This isn't needed. If the flag doesn't exist, the 'if header ...' line
won't match. You're doing two tests for every message where one is all
that's needed.
On 03/17/2017 01:21 AM, Nilton Jose Rizzo wrote:
Hi all,
I already searched for this error on google and nothing
I never install dovecot, this is a first time.
This error, I know, is too newbie and stupid, but I
checked more than twice.
root@server:/usr/local/etc/dovecot #
Hi
>root@server:/usr/local/etc/dovecot # sievec
>/home3/virtual/default.sieve
>doveconf: Fatal: Error in configuration file
>/usr/local/etc/dovecot/conf.d/10-ssl.conf line 7: Unknown setting: ssl
>root@server:/usr/local/etc/dovecot #
What is there at line 7 in to your /usr/local/etc/dovecot/con
Hi all,
I already searched for this error on google and nothing
I never install dovecot, this is a first time.
This error, I know, is too newbie and stupid, but I
checked more than twice.
root@server:/usr/local/etc/dovecot # sievec /home3/virtual/default.sieve
doveconf: Fat
On 03/16/2017 03:58 PM, Stephan Bosch wrote:
Op 3/16/2017 om 10:20 PM schreef Robert Moskowitz:
I am building a new mailserver on Centos7.
My sieve is created with:
mkdir /home/sieve
cat
Op 3/16/2017 om 10:20 PM schreef Robert Moskowitz:
> I am building a new mailserver on Centos7.
>
> My sieve is created with:
>
> mkdir /home/sieve
> cat require "fileinto";
> if exists "X-Spam-Flag" {
> if header :contains "X-Spam-Flag" "NO" {
>
Hello List,
i have a working dovecot imap service running with multiple clients
running fine, even iOS.
What's anying is, that only on iOS ( ) i see a huge bunch of .CONTROL
directories - marked grey.
It seems to be a copy of the existing folder structure. I don't see this
on thunderbird, ou
I am building a new mailserver on Centos7.
My sieve is created with:
mkdir /home/sieve
cat
Adi Pircalabu writes:
For us it is, we're periodically getting hammered by iOS devices that
try to open 300+ simultaneous IMAP connections for a single user from
the same IP, while the average hovers usually below 50 for the busier
mailboxes with many folders.
Oh yeah, I've seen this. I think
> On Feb 22, 2017, at 15:51, Wolfgang Hennerbichler wrote:
> Thank you, I can confirm that after the migration to sdbox I don’t see those
> errors anymore.
Turns out that message still re-appear although all my mailboxes are converted
to sdbox. The most likely case for a message to re-appear i
On Thu, 16 Mar 2017 13:48:27 +0200
Aki Tuomi wrote:
> These are always worth looking into. Please do post, also any auth debug
> logs are welcome.
Ok.
Theese the logfile lines:
Mar 14 18:06:12 master: Warning: Killed with signal 15 (by pid=7390 uid=0
code=kill)
Mar 14 18:06:20 auth: Error: net
Hello,
we have configured nginx to work as mail proxy for backend dovecot
servers. Dovecot servers behind nginx proxy are showing internal nginx
ip address for every client when running 'doveadm who' instead of
showing real client IP addresses.
Is is possible to configure this setup to show
On Thursday 16 March 2017 15:35:08 Ganael Laplanche wrote:
> Hi list,
Of course, the subject of my mail should be :
LDA locking problems - home related
not LDA*P*.
I could have LDAP locking problems but that's another story ;-)
--
Ganael Laplanche
Unix Systems Engineer @CentraleSupelec Renn
Hi list,
# dovecot --version
2.2.13
We use Dovecot LDA and I've discovered lots of messages stating that lock
files cannot be written:
Mar 16 12:02:03 mailhost dovecot: lda(someuser): Error:
file_dotlock_open(/home/sg/someuser/.dovecot.lda-dupes) failed: No such file
or directory
That user's
Hi,
It would be quite hard to enforce a limit at the proxy level since the proxies
do not share any information. Currently I do not know any way of enforcing a
limit at the proxies already.
Sami
> On 16 Mar 2017, at 7.14, Adi Pircalabu wrote:
>
> Thanks,
>
> I thought this might be the case
On 16.03.2017 12:32, Luciano Mannucci wrote:
> Hello all,
>
> I've got 3 occurences of this message in my log file:
>
> auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550)
>
> Can I ignore it, or is it a syhmptom of something wrong?
>
> I'm running dovecot 2.2.28 (bed8434). I'll p
Hello all,
I've got 3 occurences of this message in my log file:
auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550)
Can I ignore it, or is it a syhmptom of something wrong?
I'm running dovecot 2.2.28 (bed8434). I'll post my doveconf -n if it
is worth investigating further...
And the answer is, auth_username_format=%n in dovecot.conf.
On 03/16/2017 01:04 AM, Doug Barton wrote:
Looks like this is a dovecot problem after all. :)
I can get Postfix to deliver to lmtp, but it's telling it to deliver to
a fully qualified 'u...@domain.tld' address. Postfix says that it can
Looks like this is a dovecot problem after all. :)
I can get Postfix to deliver to lmtp, but it's telling it to deliver to
a fully qualified 'u...@domain.tld' address. Postfix says that it can't
find that user, and that turns out to be the case.
dovecot: auth: Debug: master in:
USER#0112#011
20 matches
Mail list logo
