the make config options for dovecot on FreeBSD list list
[x] ICU Use libicu for FTS unicode normalization
but https://wiki2.dovecot.org/Plugins/FTS makes no mention of libicu (nor of
icu at all).
is linicu simply in addition to the four options of Solar, Lucene, fts-xapian
On Mon, 2013-03-18 at 23:15 -0500, Stan Hoeppner wrote:
> Do you have a way to simply dump all the current conf file parameter
> names from 2.x into a single column text file?
With "doveconf -d" you get all the settings and also the defaults. The
docs probably should mention the defaults also.
>
On 19 March 2013 15:20, Jerry wrote:
> On Tue, 19 Mar 2013 13:36:53 +0100
> Joseba Torre articulated:
>
> {snip}
>
>> Definitely, something like man 5 postconf would be really useful. I
>> would like to collaborate with that, but I think that my English
>> writing skill are not good enough.
>
> I
On Tue, 19 Mar 2013 13:36:53 +0100
Joseba Torre articulated:
{snip}
> Definitely, something like man 5 postconf would be really useful. I
> would like to collaborate with that, but I think that my English
> writing skill are not good enough.
I would be willing to assist in a project like that.
El 19/03/13 05:15, Stan Hoeppner escribió:
On 3/18/2013 11:37 AM, Timo Sirainen wrote:
So basically you're saying that the major documentation improvement = an
index listing/describing all settings. Sure, would be useful, but I
don't see having time to write that anytime soon.
The time issue
On 3/18/2013 11:37 AM, Timo Sirainen wrote:
> So basically you're saying that the major documentation improvement = an
> index listing/describing all settings. Sure, would be useful, but I
> don't see having time to write that anytime soon.
The time issue is perfectly understandable Timo.
My sug
On 18.03.2013, at 17:37, Timo Sirainen wrote:
> Because it significantly increases development times, and when you're
> basically doing everything yourself there's nobody else reading those
> anyway.
From my point of view: do continue the very same way every since writing
your first code regard
On 2013-03-18 12:38 PM, Ajax wrote:
FWIW I've found the exemplary postconf(1) almost indispensable both
for exploring the Postfix configuration and for applying impromptu
changes.
I think most everyone would agree that postfix is in a class by itself
when it comes to code quality and docume
I was going to just bite my tongue, but couldn't let this go...
On 2013-03-18 11:33 AM, Stan Hoeppner wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be improved in any
major way. They say that the software developer himself is th
On Mon, 2013-03-18 at 18:37 +0200, Timo Sirainen wrote:
>
> > I don't know who "they" is. Wietse writes all the Postfix documentation
> > himself. It comes naturally when one performs formal software
> > development, not ad hoc, because documentation precedes coding. I would
> > assume you do a
On Mon, Mar 18, 2013 at 11:33 AM, Stan Hoeppner
wrote:
> A few things could improve the current docs in a major way.
FWIW I've found the exemplary postconf(1) almost indispensable both
for exploring the Postfix configuration and for applying impromptu
changes.
On Mon, 2013-03-18 at 10:33 -0500, Stan Hoeppner wrote:
> On 3/17/2013 3:50 PM, Timo Sirainen wrote:
>
> > It's the best I can do myself. I have no idea how they could be improved in
> > any major way. They say that the software developer himself is the worst
> > possible person to write its doc
On Mon, 18 Mar 2013, Stan Hoeppner wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be
improved in any major way. They say that the software developer himself
is the worst possible person to write its documentation, because he
can
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
> It's the best I can do myself. I have no idea how they could be improved in
> any major way. They say that the software developer himself is the worst
> possible person to write its documentation, because he can't understand what
> others find diffic
Le 12 mars 2013 à 14:28, andr...@cymail.eu a écrit :
> Can somebody please clarify the following in the documentation?
>
> I am actually looging at the 2.x docs:
> In the http://wiki2.dovecot.org/Authentication file there is
> a good effort to clarify between authentication mechanisms and passwor
Can somebody please clarify the following in the documentation?
I am actually looging at the 2.x docs:
In the http://wiki2.dovecot.org/Authentication file there is
a good effort to clarify between authentication mechanisms and password
schemes.
The authentication mechanisms are described in
htt
On Thu, 2012-12-06 at 14:46 +0100, Urban Loesch wrote:
> Hi,
>
> in the release notes of 2.1.9 I read that dovecot supports memcache and redis
> backends for
> userdb/passdb authentication. This is very interesting for me and should
> reduce queries and database load of
> our mysql servers.
>
>
Hi,
in the release notes of 2.1.9 I read that dovecot supports memcache and redis
backends for
userdb/passdb authentication. This is very interesting for me and should reduce
queries and database load of
our mysql servers.
My idea is to use memcache or redis in our IMAP/POP3 proxies in front o
On 12.12.2011, at 13.57, Marcio Merlone wrote:
> On http://wiki.dovecot.org/MainConfig I read:
>
> "mmap_disable = no
> Don't use mmap() at all. This is required if you store indexes to
> shared filesystems (NFS or clustered filesystem). "
The wording is a bit too strong, but..:
> Does that
Greetings,
On http://wiki.dovecot.org/MainConfig I read:
"mmap_disable = no
Don't use mmap() at all. This is required if you store indexes to
shared filesystems (NFS or clustered filesystem). "
Does that mean:
1. mmap is required when using NFS or
2. it is required to don't use mmap at a
On 2010-09-22 12:26 PM, Timo Sirainen wrote:
> On Tue, 2010-09-21 at 20:53 +0100, William Blunn wrote:
>> Though for me, the version numbers are too small to be useful.
> I know they're small, but I didn't want them to make the bar any
> higher. Also having something like "Documentation v1.x v2.0
On Tue, 2010-09-21 at 20:53 +0100, William Blunn wrote:
> On 21/09/2010 19:17, Timo Sirainen wrote:
> > Wonder if http://dovecot.org/index2.html looks ok.
>
> Interesting. Though for me, the version numbers are too small to be
> useful.
I know they're small, but I didn't want them to make the ba
On 2010-09-21 3:53 PM, William Blunn wrote:
> On 21/09/2010 19:17, Timo Sirainen wrote:
>> Wonder if http://dovecot.org/index2.html looks ok.
>
> Interesting. Though for me, the version numbers are too small to be
> useful. I tried it through Firefox 3.6.8 and Microsoft's version 8
> offering wit
On 21/09/2010 19:17, Timo Sirainen wrote:
Wonder if http://dovecot.org/index2.html looks ok.
Interesting. Though for me, the version numbers are too small to be
useful. I tried it through Firefox 3.6.8 and Microsoft's version 8
offering with the same result.
Also I've been wondering about w
On 2010-09-21 2:38 PM, Timo Sirainen wrote:
> Wonder how much trouble b) would be to implement. Still, this behavior
> has the downside of getting lots of links to wiki1, wiki2, etc. all
> around the internet which could be pointing to obsolete information by
> the time they're being read by peopl
On Tue, 2010-09-21 at 14:32 -0400, Charles Marcus wrote:
> Just have wiki.dovecot.org be a landing page with very prominent links
> to each version.
To avoid breaking existing links, wiki.dovecot.org/Foo would either have
to:
a) automatically redirect to one of wiki1/Foo, wiki2/Foo
b) Show the
On 2010-09-21 2:17 PM, Timo Sirainen wrote:
> Another possibility could be to just make wiki.dovecot.org redirect to
> wiki2.dovecot.org and wiki.dovecot.org/blah/ to wiki1.dovecot.org/blah/.
> Existing links would work and then wiki2 links would start showing up
> more and maybe some day in futur
On Tue, 2010-09-21 at 16:51 +0100, William Blunn wrote:
> Perhaps the "Documentation" link on the home page could be re-worked to
> something like
>
> Documentation v2.x v1.x
>
> where "v2.x" and "v1.x" are links to the two wikis.
Wonder if http://dovecot.org/index2.html looks ok.
Also I've b
On the Dovecot home page http://www.dovecot.org/ we have a link
"Documentation" which links to the Dovecot 1.x wiki (
http://wiki.dovecot.org/ ).
There is a question mark in my mind as to whether that is a good idea
considering as how the current stable version of Dovecot appears to be
2.0.x.
On 03/09/2010 11:13, William Blunn wrote:
I was thinking about documentation for alternate storage.
I have added a new section
http://wiki2.dovecot.org/MailboxFormat/dbox#Alternate_storage
and made various changes elsewhere
http://wiki2.dovecot.org/MailLocation/dbox#Alternate_storage
http://
On Fri, 2010-09-03 at 17:09 +0100, William Blunn wrote:
> I think the only thing I had further questions on was how alternate
> storage works with mdbox.
>
> In http://wiki2.dovecot.org/MailboxFormat/dbox it says we have
>
> * dovecot.map.index* files contain the "map index"
> * m.* files c
On 03/09/2010 15:01, Timo Sirainen wrote:
With multi-dbox the moving is more complex, but still it only copies
the data in m.* files.
Dovecot always tries to look for the u.123 or m.123 file from primary
storage and if it's not found there, it looks it up from alternate
storage. The state isn
On Fri, 2010-09-03 at 11:13 +0100, William Blunn wrote:
> We might want to have a name for the wiki page. Perhaps
> "AlternateStorage"? Of course if it only applies to dbox, then another
> idea is to make it a section on the page "MailboxFormat/dbox". All
> suggestions gratefully received.
I t
I was thinking about documentation for alternate storage.
We have a few mentions at:
http://wiki2.dovecot.org/MailboxFormat/dbox
http://wiki2.dovecot.org/Tools/Doveadm
http://wiki2.dovecot.org/Tools/Doveadm/Altmove
But I was thinking it would be helpful if there could be a page about
alternate
http://wiki.dovecot.org/Debugging/Authentication
There appears to be an error in this line:
The PLAIN mechanism's authentication format is: NUL
NUL . Authentication ID is the username
who you want to log in as, and authentication ID is the username whose
password you're giving.
I suppose it sh
hi!
Is there any documentation to guide me how to create a dovecot plugin?
I'm trying to read the code, but I'm not a good C programmer.
I have been able to copy the mail-log plugin into copy-log, edited about
4 lines of code, then I edited Makefiles and configure, now I'm able to
compile, in
Boris Lorbeer wrote:
Hi there,
I have two questions:
- Is there a dovecot documentation for developers (apart from the source
itself
- In the site I am concerned with, it happens very often that one mail is
delivered to hundreds of recipients. Since almost all of the mailboxes are
situated on the same filesystem, the mail is delivered by just saving it
once and establishing hardlinks from the mail director
Hi there,
I have two questions:
- Is there a dovecot documentation for developers (apart from the source
itself
39 matches
Mail list logo
