Hi,
since I had no luck finding people available on IRC, I hope someone here
can provide
me with some answers to, hopefully, 2 simple questions (and have the
solution recorded
in the archives for everyone with the same need).
A little background, as the subject says it - I want to have a single I
Hi Ben
thank you for your reply.
> The quota-status protocol is just the ordinary Postfix policy delegation
> protocol, documented in Postfix's SMTPD_POLICY_README. I would have
> thought that if you give 'service quota-status' an inet_listener you
> could have the Postfix policy check the quota
On Jun 13, 2013, at 7:55 PM, Timo Sirainen wrote:
> The \Seen flag could be made per-user, preferrably with v2.2's INDEXPVT
> setting. Otherwise you'd have to use maildir and you'd have to manually
> create a dovecot-shared file to each such maildir (every time a new one is
> created).
Is the
On 14.6.2013, at 5.38, Jonathon Price wrote:
> I'm designing a system where some but not all groups of users want to share
> a single mailbox, i.e the user will not have there own inbox. I think this
> is possible by setting up a user database that returns the same mail
> location and possible th
I'm designing a system where some but not all groups of users want to share
a single mailbox, i.e the user will not have there own inbox. I think this
is possible by setting up a user database that returns the same mail
location and possible the same home directory. This sharing would only
occur in
On Thu, 13 Jun 2013, Timo Sirainen wrote:
On 13.6.2013, at 5.33, Timo Sirainen wrote:
On Mon, 2013-06-10 at 12:30 +0200, Thomas Blomenkamp wrote:
Using dovecot on debian oldstable (squeeze) with daily builded repository,
after an upgrade this morning, dovecot always shows the following erro
On 6/13/2013 3:19 PM, Ben Johnson wrote:
> Hi, everyone,
>
> I'm surprised how little exists on the Internet regarding this
> particular subject. Given the recent headlines, that is about to change,
> I'm sure.
>
> I have a need to send an automated response to all senders who attempt
> to send
On 13.6.2013, at 5.33, Timo Sirainen wrote:
> On Mon, 2013-06-10 at 12:30 +0200, Thomas Blomenkamp wrote:
>>
>> Using dovecot on debian oldstable (squeeze) with daily builded repository,
>> after an upgrade this morning, dovecot always shows the following error:
>>
>> 2013 Jun 10 11:07:22 mail
Hi, everyone,
I'm surprised how little exists on the Internet regarding this
particular subject. Given the recent headlines, that is about to change,
I'm sure.
I have a need to send an automated response to all senders who attempt
to send unencrypted and/or unsigned email to a specific mailbox on
On 06/13/2013 04:26 AM, Yonatan Broza wrote:
Hi,
I couldn't find any decent documentation about the IMAPC feature.
Could someone please explain the purpose of this feature?
In particular, what are the differences between IMAPC and reverse
proxying?
Thanks.
imapc implements a storage engin
On 13/6/2013 05:11 , Timo Sirainen wrote:
> Looks like there was a generic problem with how crash during
> initialization was handled. This should fix all of them:
> http://hg.dovecot.org/dovecot-2.2/rev/754d244b8249
OK, thanks for the fix!
M.
Thanks everyone :) You'd think I could have found that on Google!
Simon
On 13 June 2013 16:56, InuSasha wrote:
> Hi Simon,
>
> Try to add this configuration.
> The "Port = 0" will disable the listener.
>
> Greats,
> Sascha Kuehndel
>
> service imap-login {
> inet_listener imap {
> #port =
Background: importing a mbox file containing ~700 messages (20 MB).
Our program splits MULTIAPPENDS into approx. 5MB chunks. We don't use
literal+ in order to immediately catch errors.
I can reproducibly produce the following error (2.2.2) when doing a
MULTIAPPEND where every append is us
At 12PM +0200 on 13/06/13 you (Benoit Panizzon) wrote:
>
> Or is the postfix policy daemon call to the quota-status socket documented
> somewhere (it must be, but where?) so we could implement it from within the
> Milter? (we use the sendmail Milter API from postfix to filter spam and
> viruses
Hi Simon,
Try to add this configuration.
The "Port = 0" will disable the listener.
Greats,
Sascha Kuehndel
service imap-login {
inet_listener imap {
#port = 143
}
inet_listener imaps {
port = 0
#ssl = yes
}
}
service pop3-login {
inet_listener pop3 {
#port = 110
}
At 4PM +0200 on 13/06/13 you (Simon B) wrote:
>
> I've upgraded to 2.1.7 and finally decided to turn off imaps and pop3s
> because these days everyone uses tls over 143 anyway. But it's on and
> I can't figure out why.
>
> I only have non-ssl versions specified:
> protocols = imap pop3
Dovecot
Quoting Michael M Slusarz :
It is concerning because RFC 4466 indicates that literal8's are
allowed for both APPEND and MULTIAPPEND, which is essentially an
extended APPEND. But RFC 4469 defines CATENATE TEXT as literal only:
RFC 4466:
append-data = literal / literal8 / append-data-
Quoting Timo Sirainen :
On Wed, 2013-05-22 at 09:38 -0600, Michael M Slusarz wrote:
Quoting Michael M Slusarz :
> Quoting Timo Sirainen :
>
>> Anyway .. the BINARY APPEND converts only the MIME parts that you
>> send with "Content-Transfer-Encoding: binary". Are you sending such
>> header to D
Hi
I've upgraded to 2.1.7 and finally decided to turn off imaps and pop3s
because these days everyone uses tls over 143 anyway. But it's on and
I can't figure out why.
I only have non-ssl versions specified:
protocols = imap pop3
I've stopped and started and the ports are still open and netstat
Hi,
I couldn't find any decent documentation about the IMAPC feature.
Could someone please explain the purpose of this feature?
In particular, what are the differences between IMAPC and reverse proxying?
Thanks.
Hello List
Quick overview of our set-up:
Postfix / Dovecot (2.2.2.1) / MySQL Cluster on (at the moment) three Servers
to create a HA environment where you could easily add additional servers as
the demand or load grows.
Circular dovecot replication is used so each server uses another one as
r
On Thu, 2013-06-13 at 04:59 +0300, Timo Sirainen wrote:
> On Wed, 2013-06-12 at 11:39 +0100, Simon Fraser wrote:
> > Hello folks,
> >
> > I have a problem with replication and mail_location with LAYOUT=fs set.
> >
> > If I set "mail_location = maildir:~/mail" (leaving out the :LAYOUT=fs),
> > cre
Am 2013-06-13 04:41, schrieb Timo Sirainen:
On Sun, 2013-06-02 at 10:11 +0200, Claus wrote:
Hi all,
in my settup i decided to set mail_home in 10-mail.conf,
and let dovecot do the hashing to a 2-level directory structure.
mail_location = mdbox:~/mdbox:ALT=/altstorage/%h/mdbox
mail_home = /vmail
Am 13.06.2013 03:56, schrieb Timo Sirainen:
On Wed, 2013-06-12 at 19:51 +, Bernhard Schmidt wrote:
Debian Wheezy amd64 plus Stefan's stable-auto/dovecot2.2 repository
2:2.2.2-0~auto+57 = 16495:d447dcc6b611
Crash goes away when I disable mail_attachment_dir, happens with a
fresh home as wel
24 matches
Mail list logo