Re: [Dovecot] dovecot 2.x via xinetd
Le dimanche 22 juillet 2012, Timo Sirainen a écrit : > On 22.7.2012, at 14.46, Mathieu Roy wrote: > > > Hello, > > > > I was using dovecot 1.2.x via xinetd with a setup like > > http://wiki.dovecot.org/InetdInstall > > Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer > > works. At best, I end up with stuff like > > > > Error: net_connect_unix(anvil) failed: No such file or directory > > Fatal: Couldn't connect to anvil > > > > Any clues? > > Regards, > > > > (add me in Cc in replies, I'm not suscribed to the list) > > Doesn't work anymore. No plans to make it work anymore. Way too much trouble. Is there any way to make dovecot aware of hosts.deny and hosts.allow? Thanks for your reply, Regards, -- Mathieu Roy
Re: [Dovecot] ot: execute a script via email?
On Fri, July 13, 2012 9:28 pm, Ken Anderson wrote: > If you don't have root, you are probably going to be restricted from thanks for all the suggestions, for now I've settled on 'ostiary'; I'll look at the other suggestions later, thanks again -- Voytek
Re: [Dovecot] Upgrade Problem from 2.0.18 to 2.1.7
Am 22.07.2012 17:23, schrieb Daniel Parthey: > Michael Domann wrote: >> Can i prevent dovecot from making new dirs? >> Because i have one draft and one entwürfe dir, also one trash and >> one papierkorb. one german, one english. the dirs are always created >> new, after i delete them. > > Most probably, your mail clients are responsible for creating > the folders via IMAP. Dovecot only performs the commands from > your IMAP client, so this is rather a client issue. > > You will need to tell *all* your mail user agents and your > mobile phone to use the same folders for the same purpose. > > Regards > Daniel you may "advice" mailclients if they support it i.e http://dovecot.org/list/dovecot/2011-December/062327.html feature called IMAP SPECIAL-USE > -- Best Regards MfG Robert Schetterer
Re: [Dovecot] Performance based choices
Am 22.07.2012 15:39, schrieb Hans J. Albertsson: > I've stopped trying to find a HowTo that suits me right away, and > instead I am happily trudging thru the Dovecot wiki, article by article. > > I have right up front thought of one question, a general one, and some > detailed versions of that same question: > > Generally, is there much general performance and reliability background > data available for making the basic choices? > > Say: 1st. > delivery: > maildrop or LDA or LMTP? lmtp should be fine > I tend to think LMTP should be the ideal choice for me, from what I've > gleaned so far. > Above all it means that there's only one conceptual thing that needs to > know, and postfix and other stuff can safely let dovecot deal with > accessing and finding mailboxes. > And it won't start and stop thousands of processes. > > 2nd. > mailbox format: Maildir and mbox are the older forms. Are there any > advantages to using dovecot's dbox instead? mdbox strikes me as having > the potential for being a fast and reliable format. Is that an accurate > impression? And, is mdbox mature enough for me to forget maildir and mbox? mdbox maybe the best choice > > 3rd. > I'm aiming for a poor man's High Availability system: > I'm using zfs, and I'm hoping to place all config data for dovecot and > postfix and everything else in one zfs file system, and all the user > owned data (what should normally go in a home directory) in another (or > two or three other) zfs file systems. > Then I'm planning to copy over all data at regular intervals, to a > second, normally passive, mail server. If the main server breaks, we'll > manually (or using scripts and autodetection) fail over to the passive > one, making it active, and turning power off to the failed guy using IPMI. > The data transfer is to be zfs send/zfs recv over a separate highly > redundant network connection. for poor man i would recommend master/master drbd and some cluster filesystem i.e ocfs2 etc, for backup you may use dsync with loadbalancing i.e keepalived etc anyway you need a "quick" storage for imap a standby soltution maybe good too, but why not simply use loadbalancing > Is this a reasonable idea, or is there some advantage to letting dsync > do some of the copying??? Or is there some totally different > alternative? iscsi? > > 4th. > With about a thousand users/accounts: does MySQL pay off? Or is LDAP the > way to go? Or will a dovecot-specific passwd-file do the job well enough? > Those are the three I'm used to since before. > I'd like to stay with the flat file, but not the system password file: > we're not going to let users in except into dovecot. with modern hardware/kernel cpu and mem thousends of user accounts are no problem with mysql, but i guess same is in ldap anyway this is only my meaning, wait till you heard more ones before act Perhaps you should give more additional info like planned standard quota of mailboxes awaited average user cons etc for better advice -- Best Regards MfG Robert Schetterer
[Dovecot] Corrupted dbox file - purging found mismatched offsets
Hi,
we are running a cluster using mdbox on NFS with director+mailbox on each node.
After running our daily doveadm purge loop over all users,
we got dbox corruption...
doveadm user "*" |\
while read username
do
doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -u "$username"
done
For one user (which deleted a lot of messages from his mailboxes today),
we got the following error in the dovecot.log:
Jul 22 20:10:36 10.129.3.213 dovecot: doveadm(u...@example.org): Error:
Corrupted dbox file /mail/dovecot/example.org/user/mail/storage/m.24 (around
offset=1380859): purging found mismatched offsets (1380829 vs 920527, 3/61)
Jul 22 20:10:36 10.129.3.213 dovecot: doveadm(u...@example.org): Warning: mdbox
/mail/dovecot/example.org/user/mail/storage: rebuilding indexes
What does this message exactly tell me and
how to prevent this in the future?
Now the indexes are broken and flags are lost.
The "storage" directory content of the affected user looks as follows:
drwx-- 2 vmail vmail 4096 2012-07-22 20:10 .
drwx-- 4 vmail vmail 4096 2012-05-06 12:16 ..
-rw--- 1 vmail vmail99008 2012-07-22 20:10 dovecot.map.index
-rw--- 1 vmail vmail33016 2012-07-22 20:10 dovecot.map.index.log
-rw--- 1 vmail vmail34664 2012-07-22 20:10 dovecot.map.index.log.2
-rw--- 1 vmail vmail 8134 2012-05-16 11:36 m.22
-rw--- 1 vmail vmail 10572466 2012-06-02 23:09 m.24
-rw--- 1 vmail vmail 1380205 2012-05-27 10:59 m.24.broken
-rw--- 1 vmail vmail 6506837 2012-06-09 15:42 m.25
-rw--- 1 vmail vmail 18201641 2012-06-17 22:50 m.26
-rw--- 1 vmail vmail 11345293 2012-07-01 14:37 m.28
-rw--- 1 vmail vmail 36707787 2012-07-08 23:05 m.29
-rw--- 1 vmail vmail 6062419 2012-07-15 23:34 m.30
-rw--- 1 vmail vmail 52396198 2012-07-22 20:10 m.31
-rw--- 1 vmail vmail 3067862 2012-07-20 14:31 m.32
-rw--- 1 vmail vmail 44520965 2012-07-20 14:31 m.33
-rw--- 1 vmail vmail 52426605 2012-07-22 20:10 m.34
-rw--- 1 vmail vmail 28984844 2012-07-22 20:10 m.35
-rw--- 1 vmail vmail 14465248 2012-07-22 20:10 m.36
-rw--- 1 vmail vmail 37451127 2012-07-22 20:10 m.37
-rw--- 1 vmail vmail 41494033 2012-07-22 20:10 m.38
-rw--- 1 vmail vmail 52066924 2012-07-22 20:10 m.39
-rw--- 1 vmail vmail 49785529 2012-07-22 20:10 m.40
-rw--- 1 vmail vmail 23509886 2012-07-22 20:10 m.41
-rw--- 1 vmail vmail 29339462 2012-07-22 20:10 m.42
-rw--- 1 vmail vmail 29510420 2012-07-22 20:10 m.43
-rw--- 1 vmail vmail 50896380 2012-07-22 20:10 m.44
-rw--- 1 vmail vmail 8331046 2012-07-22 20:10 m.45
-rw--- 1 vmail vmail 5903744 2012-07-22 20:10 m.46
-rw--- 1 vmail vmail70281 2012-07-22 20:10 m.47
-rw--- 1 vmail vmail 27397909 2012-07-22 20:10 m.48
-rw--- 1 vmail vmail 3893509 2012-07-22 20:10 m.49
-rw--- 1 vmail vmail 1410097 2012-07-22 20:10 m.50
-rw--- 1 vmail vmail 1905759 2012-07-22 20:10 m.51
-rw--- 1 vmail vmail 51783968 2012-05-06 12:12 m.9
Any hints on how to prevent dbox corruption in this case?
And what should I do with the "m.24.broken" file now?
Regards
Daniel
--
https://plus.google.com/103021802792276734820
# 2.1.8: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-40-server x86_64 Ubuntu 10.04.4 LTS
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_cache_ttl = 1 mins
auth_verbose = yes
auth_verbose_passwords = sha1
deliver_log_format = mailbox: deliver: msgid=%m from=%f: %$
dict {
quota = mysql:/etc/dovecot/conf.d/dovecot-dict-sql.conf.ext
}
disable_plaintext_auth = no
doveadm_password = xxx
imapc_features = rfc822.size
imapc_host = local-mailbox
imapc_port = 18143
instance_name = dovecot-mailbox
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
login_greeting = Mailbox
login_log_format = mailbox: login: %$: %s
login_trusted_networks = 10.129.3.0/24
mail_debug = yes
mail_fsync = always
mail_gid = vmail
mail_home = /mail/dovecot/%d/%n
mail_location = mdbox:~/mail
mail_log_prefix = "mailbox: mail: %s(%u): "
mail_plugins = quota stats
mail_privileged_group = vmail
mail_uid = vmail
managesieve_implementation_string = Sieve
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date ihave
mdbox_rotate_interval = 1 weeks
mdbox_rotate_size = 50 M
mmap_disable = yes
passdb {
args = /etc/dovecot/conf.d/dovecot-sql.conf.ext
driver = sql
}
plugin {
quota = dict:User quota::proxy::quota
quota_rule = *:storage=10G
quota_rule2 = Trash:storage=+100M
quota_warning = storage=95%% quota-warning 95 %u
quota_warning2 = storage=80%% quota-warning 80 %u
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
stats_refresh = 30 secs
stats_track_cmds = yes
}
protocols = imap pop3 lmtp sieve
service auth {
unix_listener auth-userdb {
group = dovecot
mode = 0660
user = dovecot
}
}
se
Re: [Dovecot] dovecot 2.x via xinetd
On 22.7.2012, at 14.46, Mathieu Roy wrote: > Hello, > > I was using dovecot 1.2.x via xinetd with a setup like > http://wiki.dovecot.org/InetdInstall > Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. > At best, I end up with stuff like > > Error: net_connect_unix(anvil) failed: No such file or directory > Fatal: Couldn't connect to anvil > > Any clues? > Regards, > > (add me in Cc in replies, I'm not suscribed to the list) Doesn't work anymore. No plans to make it work anymore. Way too much trouble.
[Dovecot] maildir_copy_with_hardlinks on v.2.0.19
Hi,
I'm trying to get the so-called "single instance store" (I think cyrus
has got the name for the first time) with dovecot --version = 2.0.19
binary package installed from ubuntu 12.04 lts official repo.
I have checked that "maildir_copy_with_hardlinks" is enabled ("dovecot
-a|grep hard" shows "yes") then I have installed and enabled the lmtp
component of dovecot. The configuration "dovecot -n" is pasted here:
http://paste.lug.ro/131180
Also in the same paste is a strace against dovecot and childrent
showing evidence of the MTA delivering a single copy of the message
via LMTP with multiple RCPT TO: headers.
However when looking in the Maildir, I see the mail break down into
three separate files instead of expected hardlinked files ("stat" and
"ls" shows one single link count, inodes are different)
Given the above data, what (am I | dovecot is) doing wrong?
Please cc me if you need additional input when replying as I'm not
subscribed to the list (I'll watch the thread online only)
Many thanks in advance.
[Dovecot] dovecot 2.x via xinetd
Hello,
I was using dovecot 1.2.x via xinetd with a setup like
http://wiki.dovecot.org/InetdInstall
Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. At
best, I end up with stuff like
Error: net_connect_unix(anvil) failed: No such file or directory
Fatal: Couldn't connect to anvil
Any clues?
Regards,
(add me in Cc in replies, I'm not suscribed to the list)
# doveconf -n
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-3-amd64 x86_64 Debian wheezy/sid ext4
mail_location = maildir:/home/%n/.Maildir:LAYOUT=fs
mail_privileged_group = mail
namespace inbox {
inbox = yes
location =
prefix =
}
passdb {
driver = pam
}
protocols = " imap"
ssl_cert =
Re: [Dovecot] Upgrade Problem from 2.0.18 to 2.1.7
Michael Domann wrote: > Can i prevent dovecot from making new dirs? > Because i have one draft and one entwürfe dir, also one trash and > one papierkorb. one german, one english. the dirs are always created > new, after i delete them. Most probably, your mail clients are responsible for creating the folders via IMAP. Dovecot only performs the commands from your IMAP client, so this is rather a client issue. You will need to tell *all* your mail user agents and your mobile phone to use the same folders for the same purpose. Regards Daniel -- https://plus.google.com/103021802792276734820
Re: [Dovecot] Upgrade Problem from 2.0.18 to 2.1.7
Thanks for pointing the right direction. I have set default_vsz_limit = 16M and it works. And a short question, possible i should make a new thread, but i think it's a little config issue from me. Can i prevent dovecot from making new dirs? Because i have one draft and one entwürfe dir, also one trash and one papierkorb. one german, one english. the dirs are always created new, after i delete them. thanks and regards Michael Am 21.07.2012 23:04, schrieb Daniel Parthey: Michael Domann wrote: Jul 20 20:17:15 imap: Error: dovecot/imap: error while loading shared libraries: libpthread.so.0: failed to map segment from shared object: Cannot allocate memory Jul 20 20:17:15 imap: Fatal: master: service(imap): child 22594 returned error 127 Looks like a "out of memory" problem. default_vsz_limit = 6 M Maybe increase this value. On my Linux box it is set to 256M. Possibly 6M is not enough? root@fritz:/var/mod/root# free -m total used free shared buffers Mem: 5951252260 72520 2452 -/+ buffers: 49808 9704 Swap: 538608 8116 530492 You're almost running out of memory, used 50MB out of 60MB. Try to temporarily disable other services on the box and see the IMAP service runs smoothly? Regards, Daniel
[Dovecot] Performance based choices
I've stopped trying to find a HowTo that suits me right away, and instead I am happily trudging thru the Dovecot wiki, article by article. I have right up front thought of one question, a general one, and some detailed versions of that same question: Generally, is there much general performance and reliability background data available for making the basic choices? Say: 1st. delivery: maildrop or LDA or LMTP? I tend to think LMTP should be the ideal choice for me, from what I've gleaned so far. Above all it means that there's only one conceptual thing that needs to know, and postfix and other stuff can safely let dovecot deal with accessing and finding mailboxes. And it won't start and stop thousands of processes. 2nd. mailbox format: Maildir and mbox are the older forms. Are there any advantages to using dovecot's dbox instead? mdbox strikes me as having the potential for being a fast and reliable format. Is that an accurate impression? And, is mdbox mature enough for me to forget maildir and mbox? 3rd. I'm aiming for a poor man's High Availability system: I'm using zfs, and I'm hoping to place all config data for dovecot and postfix and everything else in one zfs file system, and all the user owned data (what should normally go in a home directory) in another (or two or three other) zfs file systems. Then I'm planning to copy over all data at regular intervals, to a second, normally passive, mail server. If the main server breaks, we'll manually (or using scripts and autodetection) fail over to the passive one, making it active, and turning power off to the failed guy using IPMI. The data transfer is to be zfs send/zfs recv over a separate highly redundant network connection. Is this a reasonable idea, or is there some advantage to letting dsync do some of the copying??? Or is there some totally different alternative? iscsi? 4th. With about a thousand users/accounts: does MySQL pay off? Or is LDAP the way to go? Or will a dovecot-specific passwd-file do the job well enough? Those are the three I'm used to since before. I'd like to stay with the flat file, but not the system password file: we're not going to let users in except into dovecot.
Re: [Dovecot] Confusion when trying to set up a first postfix+dovecot mailserver
Sorry, you're right: I was stressed out when writing this. I meant mkdir .lkml and mkdir .bugtraq and touch dovecot-shared. Of course. It is not the best example, I agree. Still it should say something like "create the file dovecot-shared if you want a shared mailbox named dovecot-shared" (can probably be whittled down). And, yes, if I can get thru setting up dovecot properly ( I know I can, it will just take longer ) I will of course do a writeup in the style I want to see myself. When it comes to dovecot, I am a user (that IS a terribly derogative term, isn't it?), but I have been actively supporting large farms of servers running other forms of mail delivery agents in Sun's various OSes since 1986 up to 2008, so I do think I ought to be able to get my head around dovecot, too. I will just have to read the wiki thru, all of it... :-) On 2012-07-22 12:41, Charles Marcus wrote: On 2012-07-22 5:53 AM, Hans J. Albertsson > As an example, to wit, in the http://wiki2.dovecot.org/SharedMailboxes/Public doc, there's a line "In the above example, you would then create Maildir mailboxes under the /var/mail/public/ directory." and a colour plate plate showing a directory listing. # ls -la /var/mail/public/ drwxr-s--- 1 root mail 0 2007-03-19 03:12 . drwxrws--- 1 root mail 0 2007-03-19 03:12 .lkml drwxrws--- 1 root mail 0 2007-03-19 03:12 .bugtraq -rw-rw 1 root mail 0 2007-03-19 03:12 dovecot-shared I am guessing that this means I'm supposed to do mkdir dovecot-shared inside /var/mail/public. Since it isn't listed as a directory, I'm confused as to why would you guess that? dovecot-shared is a FILE, not a directory. The 3rd line below that example on that page specifically says: "The dovecot-shared FILE..." It seems to me that you aren't even bothering to read these docs, andit is more like all you want to do is complain that there is nothing already written holding your hand through every possible config that you want to accomplish. Dovecot is primarily written by one guy (Timo), and he does a remarkable job of both coding and documenting dovecot on the wiki, as well as answering support questions here on the list, and while sometimes there are a few days before he answers many questions, serious bug reports generally get prompt attention, and I don't think I've ever seen him not respond to a question in time. There is no doubt that dovecot could really use some good, experienced technical writers that could help Timo with documenting dovecot to make it easier to learn by someone new to it, and I'm sure he would welcome that help - are you volunteering? Sorry if I'm being horridly difficult, but I think (from experiencing it as a user) dovecot is too good not to have proper tutorials and howtos. Well, dovecot's intended audience isn't a 'user', it is experienced system/mail admins, but if you are volunteering to help Timo (and the dovecot community) out by improving the wiki documentation and/or creating some of these HowTos from the perspective of someone totally new to dovecot (and maybe even IMAP servers in general), then I am quite certain that Timo will welcome such help. And as for documentation in the form of books, you cannot compare dovecot to postfix in this regard. Postfix is one of the most mature, stable projects out there - it's core functionality basically never changes (only the rare bug fixes), and major new features are pretty rare too, so even books written 8 years ago are still fairly relevant (and generally are only missing the new features). With dovecot, things are very different. It is still very young and changing rapidly, and probably will continue to do so as Timo adds new features on his ToDo list. A book written even a year ago would not have much use to someone using the current version today. As it matures and features stabilize, this will change, and I'm hopeful that in a year or two, dovecot will stabilize to the point that some of the talented book writers out there will take on such a huge project - but none of them want to do that right now because dovecot is such a fast moving target.
Re: [Dovecot] Confusion when trying to set up a first postfix+dovecot mailserver
On 2012-07-22 5:53 AM, Hans J. Albertsson > As an example, to wit, in the http://wiki2.dovecot.org/SharedMailboxes/Public doc, there's a line "In the above example, you would then create Maildir mailboxes under the /var/mail/public/ directory." and a colour plate plate showing a directory listing. # ls -la /var/mail/public/ drwxr-s--- 1 root mail 0 2007-03-19 03:12 . drwxrws--- 1 root mail 0 2007-03-19 03:12 .lkml drwxrws--- 1 root mail 0 2007-03-19 03:12 .bugtraq -rw-rw 1 root mail 0 2007-03-19 03:12 dovecot-shared I am guessing that this means I'm supposed to do mkdir dovecot-shared inside /var/mail/public. Since it isn't listed as a directory, I'm confused as to why would you guess that? dovecot-shared is a FILE, not a directory. The 3rd line below that example on that page specifically says: "The dovecot-shared FILE..." It seems to me that you aren't even bothering to read these docs, andit is more like all you want to do is complain that there is nothing already written holding your hand through every possible config that you want to accomplish. Dovecot is primarily written by one guy (Timo), and he does a remarkable job of both coding and documenting dovecot on the wiki, as well as answering support questions here on the list, and while sometimes there are a few days before he answers many questions, serious bug reports generally get prompt attention, and I don't think I've ever seen him not respond to a question in time. There is no doubt that dovecot could really use some good, experienced technical writers that could help Timo with documenting dovecot to make it easier to learn by someone new to it, and I'm sure he would welcome that help - are you volunteering? Sorry if I'm being horridly difficult, but I think (from experiencing it as a user) dovecot is too good not to have proper tutorials and howtos. Well, dovecot's intended audience isn't a 'user', it is experienced system/mail admins, but if you are volunteering to help Timo (and the dovecot community) out by improving the wiki documentation and/or creating some of these HowTos from the perspective of someone totally new to dovecot (and maybe even IMAP servers in general), then I am quite certain that Timo will welcome such help. And as for documentation in the form of books, you cannot compare dovecot to postfix in this regard. Postfix is one of the most mature, stable projects out there - it's core functionality basically never changes (only the rare bug fixes), and major new features are pretty rare too, so even books written 8 years ago are still fairly relevant (and generally are only missing the new features). With dovecot, things are very different. It is still very young and changing rapidly, and probably will continue to do so as Timo adds new features on his ToDo list. A book written even a year ago would not have much use to someone using the current version today. As it matures and features stabilize, this will change, and I'm hopeful that in a year or two, dovecot will stabilize to the point that some of the talented book writers out there will take on such a huge project - but none of them want to do that right now because dovecot is such a fast moving target. -- Best regards, Charles
Re: [Dovecot] Confusion when trying to set up a first postfix+dovecot mailserver
On 2012-07-22 11:39, Hans J. Albertsson wrote: To the point: Explain what you are going to demonstrate, and explain to what extent it can or cannot serve as a boiler-plate for more advanced configs. Complete ( in the appropriate manner ): For every single thing you display, explain what the reader is supposed to do about it, and make sure you explain what is going to appear automagically and what the reader must do to achieve what won't appear as a result of dovecot's own actions. Do not point the reader to other docs unless those docs agree with the current one in both form and perspective. If they don't, copy in and adjust to fit the current doc. And also, make sure that if you write in english, the meaning of your words in absolutely unequivocal, there must not appear in any reader's mind the slightest doubt as to how (s)he's supposed to use the info given. As an example, to wit, in the http://wiki2.dovecot.org/SharedMailboxes/Public doc, there's a line "In the above example, you would then create Maildir mailboxes under the /var/mail/public/ directory." and a colour plate plate showing a directory listing. # ls -la /var/mail/public/ drwxr-s--- 1 root mail 0 2007-03-19 03:12 . drwxrws--- 1 root mail 0 2007-03-19 03:12 .lkml drwxrws--- 1 root mail 0 2007-03-19 03:12 .bugtraq -rw-rw 1 root mail 0 2007-03-19 03:12 dovecot-shared I am guessing that this means I'm supposed to do mkdir dovecot-shared inside /var/mail/public. But "creating Maildir mailboxes" might mean more than just mkdir, and not explaining that bit at this point in the doc slows the reader down, especially if (s)he's not already well versed in the mysteries of dovecot wizardry. And if (s)he is that, why should (s)he read the doc at all? Sorry if I'm being horridly difficult, but I think (from experiencing it as a user) dovecot is too good not to have proper tutorials and howtos.
Re: [Dovecot] Confusion when trying to set up a first postfix+dovecot mailserver
I find your answer a bit confusing:
I was showing these problems off as sources of confusion, not as
examples of what I want to achieve!
My view of what a HowTo or a Tutorial is supposed to be is:
To the point: Explain what you are going to demonstrate, and explain to
what extent it can or cannot serve as a boiler-plate for more advanced
configs.
Complete ( in the appropriate manner ): For every single thing you
display, explain what the reader is supposed to do about it, and make
sure you explain what is going to appear automagically and what the
reader must do to achieve what won't appear as a result of dovecot's own
actions.
Do not point the reader to other docs unless those docs agree with the
current one in both form and perspective. If they don't, copy in and
adjust to fit the current doc.
Many of the "other docs" pointed to by the HowTos (and there appears to
be no tutorials at all ) leave the uninitiated confused, because they
appear to make slightly different assumptions from the referring doc.
Many docs say "you must first configure THIS,"
LMTP refers you back to the LDA config, and that may be absolutely
correct, but me not being an initiate, I get lost. Because it seems that
the perspective and the assumptions are slightly skewed or totally
different, how can I tell at the first attempt?
I started out doing postfix config: that was easy, very easy, and I have
set up several different ones now, none of which took more than an hour.
The first one was Chap 3 in Book Of Postfix by the German fellows, and
that is just about the best tutorial I have ever seen. I did that w/o
understanding the first thing about postfix vs sendmail,and it taught me
a lot, and I could then read the rest of the book much faster.
On 2012-07-21 21:00, Thomas Leuxner wrote:
Am 21.07.2012 um 16:49 schrieb Hans J. Albertsson:
location = maildir:/var/vmail/public:LAYOUT=fs:INDEX=~/public
This namespace is defined for "public/shared" mailboxes<> private mailboxes:
See: http://wiki2.dovecot.org/SharedMailboxes/Public
Basically something different from the setting you appear to be looking for.
User Home directory structure:/var/vmail///
This is indeed the structure used in this example. The mail location is set to:
mail_location = maildir:~/Maildir
In this configuration this translates to the actual location being read from
the userdb (dynamically):
[…]
args = username_format=%u /var/vmail/auth.d/%d/passwd
[ file: /var/vmail/auth.d//passwd ]
@:{SSHA}:5000:5000::/var/vmail///...
[…]
While this may not be the easiest configuration example to start with, it is a
quite scalable and flexible approach though. You may find more background on
this here:
http://wiki2.dovecot.org/MailLocation
http://wiki2.dovecot.org/UserDatabase
Regards
Thomas
