On Wed, Nov 23, 2016 at 6:05 PM, Timo Sirainen wrote:
> On 23 Nov 2016, at 0.49, Mark Moseley wrote:
> >
> > If I move messages between namespaces, it appears to ignore the quotas
> I've
> > set on them. A *copy* will trigger the quota error. But a *move* just
> > happily piles on to the overquo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 23 Nov 2016, Steve Litt wrote:
On Wed, 23 Nov 2016 16:04:22 -0600 (CST) Greg Rivers
wrote:
$ strings $(whence alpine) | grep '^/.*certs$'
/etc/ssl/certs
The directory or the certs isn't the problem. Alpine sees the
self-signed cert I ju
On 23 Nov 2016, at 0.49, Mark Moseley wrote:
>
> If I move messages between namespaces, it appears to ignore the quotas I've
> set on them. A *copy* will trigger the quota error. But a *move* just
> happily piles on to the overquota namespace. Is that normal?
Probably needs a bit more thinking,
Alpine still gives me a bad cert warning, saying I should either fix it
or disable checking. I haven't yet found a way to get Alpine to
discriminate between a valid self-signed cert and a bad one.
Well, it can't discriminate since any certificate (except those in your
trusted store) that asser
On mercredi, 23 novembre 2016 17.31:50 h CET Steve Litt wrote:
> On Wed, 23 Nov 2016 16:04:22 -0600 (CST)
>
> Greg Rivers wrote:
> > On Wed, 23 Nov 2016, Steve Litt wrote:
> > > [snip]
> > >
> > > Alpine still gives me a bad cert warning, saying I should either
> > > fix it or disable checking.
On Wed, 23 Nov 2016 16:04:22 -0600 (CST)
Greg Rivers wrote:
> On Wed, 23 Nov 2016, Steve Litt wrote:
> > [snip]
> >
> > Alpine still gives me a bad cert warning, saying I should either
> > fix it or disable checking. I haven't yet found a way to get Alpine
> > to discriminate between a valid self
On Wed, 23 Nov 2016, Steve Litt wrote:
[snip]
Alpine still gives me a bad cert warning, saying I should either fix it
or disable checking. I haven't yet found a way to get Alpine to
discriminate between a valid self-signed cert and a bad one.
Like a number of applications, alpine checks the
Hi,
I've configured the antispam plugin like in the wiki to use the sa-
learn-pipe.sh shell script.
But it's not creating the log file in /tmp.
Even if I add a "touch /tmp/x" in sa-learn-pipe.sh it's not created.
So how I can check if it works correctly?
dovecot version 2.2.26.0
/var/log/debug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Wow, that was the problem. I can't believe I overlooked that so many times.
Thank you so much. I was ready to pull my hair out.
On November 23, 2016 3:28:23 AM EST, Steffen Kaiser
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On Wed,
Hi Marti,
Marti Markov (Mi 23 Nov 2016 09:21:07 CET):
> Hi Heiko,
>
> Sorry for using your private email address. :/
… the problem is the duplicat suppression on our mailsystem, normally it
passes the 'unicasted' message and supresses the 'broadcasted' messages
(as the unicasted message comes f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 23 Nov 2016, Steven Mainor wrote:
Any help would be greatly appreciated.
~# grep sieve /var/log/syslog | nano temp.save
Nov 23 01:32:09 1 dovecot: lda(st...@degga.net): Warning: sieve: file
storage: Active Sieve script symlink
/var/mail/
Hi Heiko,
Sorry for using your private email address. :/
I managed to get this working using local_user changes by adding ldap user
verification there:
local_user:
debug_print = "R: local_user LDAP lookup for $local_part@$domain"
driver = accept
domains = +local_domains
condition = C
While setting up sieve on my email server I mistakenly setup a symlink
(~/sieve/myfilter.svbin > ~/.dovecot.sieve) but I think that that should
have been (~/sieve/myfilter.sieve > ~/.dovecot.sieve). I have fixed the
mistake but dovecot/sieve still throws an error saying that the symlink
still l
13 matches
Mail list logo
