Hello
I want to set readonly over IMAP for users mailboxes at Archive
namespace, (and have single user who can move mails there on automated
way)
This don't work but found that if I add file to
/srv/mail.archives/user/dovecot-acl
containing only
owner lr
then login to imap (with telnet) and do
Hello,
there is a way with a sieve rule to add a Date: header when it is
missing? Adding one with the time of reception of the message or using
the date from the the first Received: header would be good options.
Unfortunately I'm receiving some useful automated messages that lack a
Date header
Latest config
http://pastebin.com/XKNn6W24
Ricardo Branco wrote, On 16/07/2014 14:56:
Shows that auth is not honouring the %n i have.
Does the username_format need to be only in the userdb section or also the
passdb part?
http://pastie.org/9396504
Ricardo Branco wrote, On 15/07/2014 18:23:
Am 17.07.2014 16:13, schrieb Daniele Nicolodi:
there is a way with a sieve rule to add a Date: header when it is
missing? Adding one with the time of reception of the message or using
the date from the the first Received: header would be good options.
Unfortunately I'm receiving some
On -10.01.-28163 20:59, Daniele Nicolodi wrote:
Unfortunately I'm receiving some useful automated messages that lack a
Date header and this screws up the sorting in my imap clients. I have a
script to fix those acting on the Maildir storage, but I would prefer to
have the thing solved more
Hello Harald,
On 17/07/2014 16:30, Reindl Harald wrote:
Am 17.07.2014 16:13, schrieb Daniele Nicolodi:
there is a way with a sieve rule to add a Date: header when it is
missing? Adding one with the time of reception of the message or using
the date from the the first Received: header would
Am 17.07.2014 16:46, schrieb Daniele Nicolodi:
Hello Harald,
On 17/07/2014 16:30, Reindl Harald wrote:
Am 17.07.2014 16:13, schrieb Daniele Nicolodi:
there is a way with a sieve rule to add a Date: header when it is
missing? Adding one with the time of reception of the message or using
Am 17.07.2014 16:13, schrieb Daniele Nicolodi:
Hello,
there is a way with a sieve rule to add a Date: header when it is
missing? Adding one with the time of reception of the message or using
the date from the the first Received: header would be good options.
Unfortunately I'm receiving some
Hello list,
Is there a way to call a spam filter in dovecot-lda like maildrop uses
the xfilter command within the .mailfilter file to do the same?
Eric
On 17.7.2014 16:40, Jochen Bern wrote:
On -10.01.-28163 20:59, Daniele Nicolodi wrote:
Unfortunately I'm receiving some useful automated messages that lack a
Date header and this screws up the sorting in my imap clients. I have a
script to fix those acting on the Maildir storage, but I would
Am 17.07.2014 17:32, schrieb Eric Broch:
Is there a way to call a spam filter in dovecot-lda like maildrop uses
the xfilter command within the .mailfilter file to do the same?
are you aware that dspam is dead and the webinterface pratically
not maintained and so very likely full of security
Greetings,
I'm working on building a redundant Dovecot server which will be
replicated with my original. I would like to know if there's any
potential problems I could run into in running this for the first time.
For example, during an initial sync is it possible for the new server to
sync
On 17/07/2014 17:34, Jiri Bourek wrote:
On 17.7.2014 16:40, Jochen Bern wrote:
On -10.01.-28163 20:59, Daniele Nicolodi wrote:
Unfortunately I'm receiving some useful automated messages that lack a
Date header and this screws up the sorting in my imap clients. I have a
script to fix those
On 17/07/2014 16:51, Alex JOST wrote:
Am 17.07.2014 16:13, schrieb Daniele Nicolodi:
Hello,
there is a way with a sieve rule to add a Date: header when it is
missing? Adding one with the time of reception of the message or using
the date from the the first Received: header would be good
On 17/07/2014 16:50, Reindl Harald wrote:
as said:
fix the application or try to solve that at MTA level
If it were so simple to convince people to fix their applications (I
especially hate applications refusing the + character in email address
local part), the world would definitely be a
Am 17.07.2014 18:24, schrieb Daniele Nicolodi:
On 17/07/2014 16:50, Reindl Harald wrote:
as said:
fix the application or try to solve that at MTA level
If it were so simple to convince people to fix their applications (I
especially hate applications refusing the + character in email
On Thu, Jul 17, 2014 at 04:50:20PM +0200, Reindl Harald wrote:
as said:
fix the application or try to solve that at MTA level
The correct place would be the MSA.
If all mail genrated by Web appliocations woul pass through a working
MSA fixing them up, a lot of problems would go away.
if at
Am 17.07.2014 21:19, schrieb Jost Krieger:
On Thu, Jul 17, 2014 at 04:50:20PM +0200, Reindl Harald wrote:
as said:
fix the application or try to solve that at MTA level
The correct place would be the MSA.
pfff MSA / MTA - 999 out of 1000 MSA setups are just postfix
or exim on localhost
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ricardo Branco wrote:
Latest config
http://pastebin.com/XKNn6W24
Ricardo Branco wrote, On 16/07/2014 14:56:
Shows that auth is not honouring the %n i have. Does the
username_format need to be only in the userdb section or also the
passdb
We have been using LDA in the past with our old Sendmail system, on our
new mail server we were proposing to use LMTP with Postfix.
LMTP does not work at all, it just keeps saying that the user is not
recognised, LDA on the otherhand does work.
I am unable to login via IMAP/POP using the full
Also just to note that Postfix is not the problem here, that has now
been ruled out
Ive been trying the LMTP protocol directly and still confirm the problem..
220 localhost I am ready.
LHLO wenn.com
250-localhost
250-8BITMIME
250-ENHANCEDSTATUSCODES
250 PIPELINING
mail from:i...@wenn.com
250
Am 2014-07-15 14:08, schrieb David Gessel:
Good catch, thank you. (I used LAYOUT=fs at first, but found behavior a
little anomalous. I forgot to disable the workarounds).
This may have stopped the problem of redownloading the entire mailbox
(on restart I got downloading 1 of 8 instead of 1 of
When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error:
Warning: fd limit (ulimit -n) is lower than required under max. load (1024
4096), because of default_client_limit
# doveconf default_internal_user
default_internal_user = dovecot
Should dovecot print this warning based on
Am 18.07.2014 00:58, schrieb Will Yardley:
When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error:
Warning: fd limit (ulimit -n) is lower than required under max. load (1024
4096), because of default_client_limit
# doveconf default_internal_user
default_internal_user =
24 matches
Mail list logo
