-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 23 Feb 2014, Francesco wrote:
i was reading the dovecot-lda documentation as i'm using LDA as a
delivery agent on my current mailserver configuration.
I was curious to know if there are some options for having a message to
be delivered to a
Hi,
after more than 20 days uptime, Dovecot stopped with the following logged in
/var/log/messages:
- master: Fatal: kevent(): Invalid argument
dovecot -n:
# 2.2.10: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 9.2-RELEASE-p3 amd64
auth_default_realm = xxx.com.ua
auth_mechanisms = plain l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Feb 2014, Steffen Kaiser wrote:
On Sun, 23 Feb 2014, Francesco wrote:
i was reading the dovecot-lda documentation as i'm using LDA as a
delivery agent on my current mailserver configuration.
I was curious to know if there are some optio
On 2/24/2014 3:58 AM, Steffen Kaiser wrote:
I would add a BCC recipient in the MTA. It's more save in such
situation. See the thread about qmail and multiple recipients for one
mail address.
The only downside to this is all of the original headers are *not*
preserved in the BCC copy.
I to
On 2/23/2014 9:07 AM, Francesco wrote:
i was also planning to use shared folders + ACLS to have backup_alice
accessible as a read only mailbox directly from the alice imap account.
Hi Francesco,
I would be *very* interested in seeing what you come up with, as I have
been wanting to do the ex
Hello,
I am using Dovecot version 2.2.10. I am quite familiar with ssh replication
and I managed to set it up correctly. The only problem I see is that when i
run the command:
doveadm replicator status I get a wrong "Total number of known users" which
is
a) is different between the two (2) replica
On 2/24/2014 6:58 AM, Charles Marcus wrote:
> On 2/24/2014 3:58 AM, Steffen Kaiser wrote:
>> I would add a BCC recipient in the MTA. It's more save in such
>> situation. See the thread about qmail and multiple recipients for one
>> mail address.
>
> The only downside to this is all of the origin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Feb 2014, Charles Marcus wrote:
On 2/24/2014 3:58 AM, Steffen Kaiser wrote:
I would add a BCC recipient in the MTA. It's more save in such situation.
See the thread about qmail and multiple recipients for one mail address.
The only d
On 2/24/2014 8:39 AM, Stan Hoeppner wrote:
On 2/24/2014 6:58 AM, Charles Marcus wrote:
On 2/24/2014 3:58 AM, Steffen Kaiser wrote:
I would add a BCC recipient in the MTA. It's more save in such
situation. See the thread about qmail and multiple recipients for one
mail address.
The only dow
On 2/24/2014 9:25 AM, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Feb 2014, Charles Marcus wrote:
On 2/24/2014 3:58 AM, Steffen Kaiser
wrote:
I would add a BCC recipient in the MTA. It's more save in such
situation. See the thread about qmail and multiple
Hi,
we still run dovecot 1.2.17 and upgrading is not planed for some time.
But I'm asked to install a sieve system to be used with SOGo soon.
What do I have to install / configure?
Is installing/configuring the dovecot-sieve-0.1.19 and
dovecot-managesieve-0.11.13 enough?
We still use mostly th
Il giorno lun, 24/02/2014 alle 07.59 -0500, Charles Marcus ha scritto:
> On 2/23/2014 9:07 AM, Francesco wrote:
> > i was also planning to use shared folders + ACLS to have backup_alice
> > accessible as a read only mailbox directly from the alice imap account.
>
> Hi Francesco,
>
> I would be *
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Feb 2014, Charles Marcus wrote:
Date: Mon, 24 Feb 2014 09:44:15 -0500
From: Charles Marcus
Reply-To: Dovecot Mailing List
To: dovecot@dovecot.org
Subject: Re: [Dovecot] realtime backup with LDA?
On 2/24/2014 9:25 AM, Steffen Kaiser wr
On Mon, Feb 24, 2014 at 12:54:51AM +0100, Reindl Harald wrote:
>
> you described nothing relevant
You're quite ignorant and obviously don't understand the background.
> you only talk why 127.0.0.1 is treated as "secured"
> well because it is by definition, if you don't trust
> 127.0.0.1 you
Am 24.02.2014 16:19, schrieb Hadmut Danisch:
> On Mon, Feb 24, 2014 at 12:54:51AM +0100, Reindl Harald wrote:
>>
>> you described nothing relevant
>
> You're quite ignorant and obviously don't understand the background.
no
>> you only talk why 127.0.0.1 is treated as "secured"
>> well because
On 24/02/2014 15:19, Hadmut Danisch wrote:
As far as I can see dovecot does not consider 127.0.0.1 as "secured"
for any good reason, just to make debugging in plaintext easier. This
is a severe security gap. Hadmut
You could choose not to use localhost IP, but bind to the actual local
IP of th
On 2/24/2014 10:13 AM, Steffen Kaiser wrote:
What changes are made by default, that are not implemented by the MTA
admin?
Sorry, I don't understand the question (language thing I'm sure).
I'm talking about the 'always_bcc' feature in postfix, which obviously
must be enabled by the MTA sysa
So schrieb Fabiano Sidler:
> Hi folks!
>
> I have set up dsync replication with SSH according to
> http://wiki2.dovecot.org/Replication with the exception of having system users
> and calling doveadm dsync-server directly from authorized_keys, because the
> wrapper script posted on the above site
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Feb 2014, Giles Coochey wrote:
You could choose not to use localhost IP, but bind to the actual local IP of
the host, even though it is on the local machine?
Is it only attaching to the 127.0.0.1 because you're binding to it by
hostnam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Feb 2014, Charles Marcus wrote:
On 2/24/2014 10:13 AM, Steffen Kaiser wrote:
What changes are made by default, that are not implemented by the MTA
admin?
Sorry, I don't understand the question (language thing I'm sure).
Doesn't ma
On 2/24/2014 11:14 AM, Steffen Kaiser wrote:
On Mon, 24 Feb 2014, Charles Marcus wrote:
I'm talking about the 'always_bcc' feature in postfix, which
obviously must be enabled by the MTA sysadmin.
Ah, OK. But this is not what I meant, because it would sent all
messages to one and a single mai
On 2/24/2014 8:42 AM, Charles Marcus wrote:
> On 2/24/2014 8:39 AM, Stan Hoeppner wrote:
>> On 2/24/2014 6:58 AM, Charles Marcus wrote:
>>> On 2/24/2014 3:58 AM, Steffen Kaiser
>>> wrote:
I would add a BCC recipient in the MTA. It's more save in such
situation. See the thread about qmai
Am 24.02.2014 18:06, schrieb Charles Marcus:
> On 2/24/2014 11:14 AM, Steffen Kaiser
> wrote:
>> On Mon, 24 Feb 2014, Charles Marcus wrote:
>>> I'm talking about the 'always_bcc' feature in postfix, which
>>> obviously must be enabled by the MTA sysadmin.
>
>> Ah, OK. But this is not what I meant
On 2/24/2014 12:12 PM, Stan Hoeppner wrote:
On 2/24/2014 8:42 AM, Charles Marcus wrote:
On 2/24/2014 8:39 AM, Stan Hoeppner wrote:
On 2/24/2014 6:58 AM, Charles Marcus wrote:
On 2/24/2014 3:58 AM, Steffen Kaiser
wrote:
I would add a BCC recipient in the MTA. It's more save in such
situatio
Hello people,
I am absolute newbie in the world of Dovecot. Before I start learning
configuration and plugin writing I want to ensure that what I am trying to
do can be done using Dovecot. I want to have a IMAP proxy setup with a
module (written by me) that scans email data for some specific conten
Am 24.02.2014 05:15, schrieb rhklinux:
> Hello people,
> I am absolute newbie in the world of Dovecot. Before I start learning
> configuration and plugin writing I want to ensure that what I am trying to
> do can be done using Dovecot. I want to have a IMAP proxy setup with a
> module (written by m
On 2/24/2014 10:14 AM, Steffen Kaiser wrote:
...
> I mean to add a
> BCC per user to "user"_backup, like a per user alias or forward.
>
> A message to user A is "split" into a message to user A and A_backup,
> where the new message to user A is not split again.
If using Postfix, this can be accom
On 24 Feb 2014, at 08:07 , Götz Reinicke - IT Koordinator
wrote:
> we still run dovecot 1.2.17 and upgrading is not planed for some time.
>
> But I'm asked to install a sieve system to be used with SOGo soon.
>
> What do I have to install / configure?
I was under the impression that dovecot 1
On 24 Feb 2014, at 05:58 , Charles Marcus wrote:
> I too would very much like to see a way to 'split' the mail delivery
> transaction so that an *identical* copy of the message is delivered to two
> different places simultaneously.
I have two methods of doing this.
1) /etc/postfix/virtual
2) /
On 24 Feb 2014, at 09:14 , Steffen Kaiser wrote:
> Ah, OK. But this is not what I meant, because it would sent all messages to
> one and a single mail address, for all users, right? I mean to add a BCC per
> user to "user"_backup, like a per user alias or forward.
>
> A message to user A is "
Hadmut Danisch:
I did not say that I did not trust 127.0.0.1. I said that I do not
trust the Web-IMAP-Gateway (such as squirrelmail) if the client uses
an untrusted computer.
the question to me is: why could Hadmut Danisch not configure
dovecot use an non default trust state for localhost for
On Feb 20, 2014, at 5:12 PM, Cyberonic Turbo wrote:
> Following this guide:
> http://sys4.de/en/blog/2013/04/08/postfix-dovecot-mailbox-quota/ I can't
> seem to get it to work, as soon as I add the smtpd_recipient_restrictions
> setting to postfix I can no longer send mail at all. I get the messag
On Friday 21 February 2014 08:54:34 Steffen Kaiser wrote:
> On Thu, 20 Feb 2014, Boris wrote:
> > On Thursday 20 February 2014 20:45:32 Boris wrote:
> >> Dovecot 2.2.9-1 accepts SETACL commands that share mailboxes to
> >> non-existent mailboxes. There is no error message. Is this intended
> >> beh
Quoting Boris :
On Friday 21 February 2014 08:54:34 Steffen Kaiser wrote:
On Thu, 20 Feb 2014, Boris wrote:
> On Thursday 20 February 2014 20:45:32 Boris wrote:
>> Dovecot 2.2.9-1 accepts SETACL commands that share mailboxes to
>> non-existent mailboxes. There is no error message. Is this inten
On Monday 24 February 2014 18:04:40 Michael M Slusarz wrote:
> SETACL only returns NO if you "can't set acl". But "can't set acl" !=
> "mailbox has to exist". Example: a server can allow pre-setting ACLs
> for mailboxes that MAY be created in the future. Perfectly legal
> according to the spec.
Thanks ! I will check it out.
--
View this message in context:
http://dovecot.2317879.n4.nabble.com/Dovecot-hooks-tp46887p46922.html
Sent from the Dovecot mailing list archive at Nabble.com.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 24 Feb 2014, LuKreme wrote:
On 24 Feb 2014, at 09:14 , Steffen Kaiser wrote:
Ah, OK. But this is not what I meant, because it would sent all messages to one and a
single mail address, for all users, right? I mean to add a BCC per user to
37 matches
Mail list logo
