> On 30 June 2018 at 05:54 Stuart Henderson wrote:
>
>
> On 2018-06-07, Ricardo Branco wrote:
> > Solr 7 returns JSON by default but fts_solr requires XML.
> >
> > Would be good to have wt=xml added to the query to force it to xml all the
> > time, this would prevent errors if solr has
> >
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 Red Hat Enterprise Linux Server
release 6.9 (Santiago)
disable_plaintext_auth = no
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mbox_write_locks = fcntl
passdb {
driver = pam
}
protocols = imap
service imap-login
will you be updating extdata plugin please?
Quoting Stephan Bosch :
Hello Dovecot users,
Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will
need this release for Dovecot v2.3.2, because the previous v0.5.1
release will not work. No changes were performed since the release c
Hello,
The metadata support in dovecot is now quite stable ( at least i didn't
encountered problems on my servers )
But the metadata is only about marking the folders ( you can mark a
folder as "calendar" or "contact").
caldav/carddav are based on webdav protocol, so normally you need an web
ser
On 2018-06-07, Ricardo Branco wrote:
> Solr 7 returns JSON by default but fts_solr requires XML.
>
> Would be good to have wt=xml added to the query to force it to xml all the
> time, this would prevent errors if solr has
> not had xml set as default for index.
This is already done in Dovecot 2
We have an existing Dovecot/Postfix/Roundcube email solution, which I
was hoping to add Caldav (and carddav?) support to, with the goal of 3rd
party email clients being able to keep contacts and calendars in sync
(as well as having the same information in roundcube)
In doing research, I came a
> On 29 June 2018 at 23:39 Jean-Daniel wrote:
>
>
>
>
> > Le 29 juin 2018 à 14:51, Timo Sirainen a écrit :
> >
> > https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz
> > https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig
> >
> > v2.3.2 is mainly a bugfix release. It contains all
> Le 29 juin 2018 à 14:51, Timo Sirainen a écrit :
>
> https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz
> https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig
>
> v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as
> well as a bunch of other fixes (mainly f
Hello Dovecot users,
Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will
need this release for Dovecot v2.3.2, because the previous v0.5.1
release will not work. No changes were performed since the release
candidate.
Much like version 0.4.24 for Dovecot v2.2, this release con
On 2018-06-29 16:00, Timo Sirainen wrote:
On 29 Jun 2018, at 15.28, Tom Sommer wrote:
On 2018-06-29 15:20, Timo Sirainen wrote:
On 29 Jun 2018, at 15.05, Tom Sommer wrote:
On 2018-06-29 14:51, Timo Sirainen wrote:
v2.3.2 is mainly a bugfix release. It contains all the changes in
v2.2.36, a
On 29 Jun 2018, at 15.28, Tom Sommer wrote:
>
> On 2018-06-29 15:20, Timo Sirainen wrote:
>> On 29 Jun 2018, at 15.05, Tom Sommer wrote:
>>> On 2018-06-29 14:51, Timo Sirainen wrote:
v2.3.2 is mainly a bugfix release. It contains all the changes in
v2.2.36, as well as a bunch of other
On 2018-06-29 15:20, Timo Sirainen wrote:
On 29 Jun 2018, at 15.05, Tom Sommer wrote:
On 2018-06-29 14:51, Timo Sirainen wrote:
v2.3.2 is mainly a bugfix release. It contains all the changes in
v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only
bugs). Binary packages are alread
On 29 Jun 2018, at 15.05, Tom Sommer wrote:
>
> On 2018-06-29 14:51, Timo Sirainen wrote:
>
>> v2.3.2 is mainly a bugfix release. It contains all the changes in
>> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only
>> bugs). Binary packages are already in https://repo.dovecot.org/
On 2018-06-29 14:51, Timo Sirainen wrote:
v2.3.2 is mainly a bugfix release. It contains all the changes in
v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only
bugs). Binary packages are already in https://repo.dovecot.org/
A simple "yum update" will result in a ton of these error
https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig
v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as
well as a bunch of other fixes (mainly for v2.3-only bugs). Binary packages are
already in https://repo.do
Yes
On Fri, Jun 29, 2018, 11:22 Luca Bertoncello wrote:
> Zitat von Sec Adm :
>
> > In all cases you need an account
>
> I mean: if I just want to have info@ on the Server and all users
> accessing it via IMAP, I just need __ONE__ account.
> If I want to use a shared mailbox, __ALL USERS__ need
Sharing IMAP accounts poses no technical problems, we do that all the time.
It might pose GDPR / confidentiality problems however, depending on the
type of mails in the account and on the legal situation.
JC
Am 29.06.2018 um 09:53 schrieb Luca Bertoncello:
Zitat von Remko Lodder :
Hi Remko,
Zitat von Sec Adm :
In all cases you need an account
I mean: if I just want to have info@ on the Server and all users
accessing it via IMAP, I just need __ONE__ account.
If I want to use a shared mailbox, __ALL USERS__ need an account on
the server.
Is it correct?
Thanks
Luca Bertoncell
Zitat von Sec Adm :
You will face additional problems with this approach, the first user who
reads a message will mark it as read for consecutive users.
That is NOT a problem, but in this case the wanted behaviour...
Regards
Luca Bertoncello
(lucab...@lucabert.de)
In all cases you need an account
On Fri, Jun 29, 2018, 11:15 Luca Bertoncello wrote:
> Zitat von Aki Tuomi :
>
> Hello Aki,
>
> > Or you can use shared mailboxes...
> > https://wiki.dovecot.org/SharedMailboxes/Shared
>
> Understand I right, that in this case, I __NEED__ all users to have an
> a
Zitat von Jeff Abrahamson :
Hello Jeff,
I think the question is "is it a problem for multiple clients to access
the same account"? (Ignore the part about people.) If so, then, no,
this is the same as having my phone, my tablet, my work computer, my
home computer, ... all having access to my m
Zitat von Aki Tuomi :
Hello Aki,
Or you can use shared mailboxes...
https://wiki.dovecot.org/SharedMailboxes/Shared
Understand I right, that in this case, I __NEED__ all users to have an
account on the server?
Thanks
Luca Bertoncello
(lucab...@lucabert.de)
You will face additional problems with this approach, the first user who
reads a message will mark it as read for consecutive users.
It's better to make a public mailbox for that but that involves more
complex setup
And dovecot is not so admin friendly on this matter from my experience so
far.
Ge
On 29/06/18 09:53, Luca Bertoncello wrote:
> Zitat von Remko Lodder :
>
> Hi Remko,
>
>> Emails can only be read if they are authenticated / authorized in
>> someway to access the store. That means you might need to share the
>> info@ credentials with the other
>> people so that they can read it ov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 29 Jun 2018, Remko Lodder wrote:
On 29 Jun 2018, at 09:42, Luca Bertoncello wrote:
Hi list!
I have an account (let's say i...@mydomain.com) that should be read from more
people.
These people does NOT have an account on the server.
Current
On 29.06.2018 10:53, Luca Bertoncello wrote:
> Zitat von Remko Lodder :
>
> Hi Remko,
>
>> Emails can only be read if they are authenticated / authorized in
>> someway to access the store. That means you might need to share the
>> info@ credentials with the other
>> people so that they can read
Zitat von Remko Lodder :
Hi Remko,
Emails can only be read if they are authenticated / authorized in
someway to access the store. That means you might need to share the
info@ credentials with the other
people so that they can read it over imap or webmail etc.
That is self-evident and it i
> On 29 Jun 2018, at 09:42, Luca Bertoncello wrote:
>
> Hi list!
>
> I have an account (let's say i...@mydomain.com) that should be read from more
> people.
> These people does NOT have an account on the server.
> Currently i...@mydomain.com is a forward to their addresses, but of course
> t
Hi list!
I have an account (let's say i...@mydomain.com) that should be read
from more people.
These people does NOT have an account on the server.
Currently i...@mydomain.com is a forward to their addresses, but of
course this solution has a huge problem: if info@ receives spam that
the s
29 matches
Mail list logo
