[Dovecot] dovecot security with IPv6
Hi Timo, hi all others! In fact, I've only read one person claiming that IPv6 support opens up "too many backdoors" [1], but anyway, as I intend to run just particular services, please give me your opinion if it's insecure to have a dovecot server, which is accessed through a public IPv6 address... (or note just shortly what else could give a firm ground to such claims...) [1] http://forums.gentoo.org/viewtopic-t-882557.html
Re: [Dovecot] comprehensive info on search capabilities?
On Sunday 14 February 2010 19:36:20 Timo Sirainen wrote: > Squat: Supposed to be completely transparent, but I don't like its > performance. The indexing speed is too slow. And it seems like the > incremental indexing rebuilds the index too often. (I used to use it, > but every time I wanted to do a search, it spent a few minutes on > indexing, even when there hadn't been all that many new messages.) Needs > a redesign some day. Well, but how can its capabilities be accessed, for example, to a) search only for full words, b) search also for word parts? signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] revision control on maildir possible?
On Sunday 14 February 2010 11:26:17 Markus Beyer wrote: > Hi, > > I was wondering if it is possible to put a dovecot managed maildir under a > vcs like system, for example git or bzr. I'd like to have a seamless > history of all mail going in and out of my mailboxes, so a vcs like system > seams a good choice for me. I'm not quite sure however if that would cause > any problems to dovecot and what the best way of handling commits would > be. > > If anyone on the list got any pointers regarding this, it would be much > apprechiated. If thats not a secret, what is the reason why you can't be sure of things with just attaching a trusted timestamp header for each mail? Someone could edit or delete those mails? Well, if you'd be using a LDA like maildrop, you could easily just call some bash script or direct command to make a new commit as your VCS provide... After each newly arrived message. (I don't know about moved / deleted messages hooks!) But... That is quite a heavyweight solution. Can there be any other reason to use it than because someone could delete or change a mail without your knowledge? signature.asc Description: This is a digitally signed message part.
[Dovecot] comprehensive info on search capabilities?
People, where to read about how to make the most of the current Dovecot search capabilities, including squat and possibly also the related future plans? There are many aspects like IMAP protocol itself, extensions, current support into Dovecot, support among MUAs... Could you post some good links, please? signature.asc Description: This is a digitally signed message part.
[Dovecot] Execute mailfilter after message move
Hi, came here to ask, if there are any ideas about a possible Dovecot feature, which would allow execution of a specific mailfilter or other program after new message is *moved* in specified mail location? The practical benefit on my side would be, that there wouldn't be any need to do getmail cronjobs, which unnecessarily fill up logfiles... (primarily for easy spam learning and reporting) signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Conditionally use a sieve script with deliver?
On Thursday 21 January 2010 15:18:28 Steffen Kaiser wrote: > One thing, that Sieve is not able to do, is to > deliver to multiple users without re-sending the mail. Just what did you mean by "multiple users"? signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Conditionally use a sieve script with deliver?
On Thursday 21 January 2010 11:13:22 Marcus Rueckert wrote: > On 2010-01-20 21:11:59 +0000, Kārlis Repsons wrote: > > I found a post in this list [0], which says sieve scripts can be used to > > deliver mail as read. However, can it be done somehow conditionally, I > > mean, with a direct or indirect switch for deliver? > > For a nonexistent example, it would be simply > > < | deliver -m path/to/maildir -r > or maybe an environment variable > > could be exported to deliver sieve and checked there? > > > > (Still not sure if sieve can replace maildrop in my case, however, using > > it with dovecot creates various problems with interoperability; but > > perhaps I can just add those imap4flags like "\\seen" myself to the > > message with maildrop and avoid mess with sieve at all?) > > > > [0] http://www.dovecot.org/list/dovecot/2008-July/032294.html > > just curious: what stops you from migrating your maildrop rules to > sieve? > > darix [not about dovecot here] My silly and honest answer is: the fact, that I found maildrop first some weeks ago and it seemed very flexible (a feeling of security in a sense, that I won't have "any" impossible thing), but then I came across the mentioned problem and still I haven't learned much about sieve. So, if I have some 50KB of mailfilter rules, which I want to divide across a tree of filter files, each of which can inherit variables from their includers, handle mailinglists, sometimes deliver copies to multiple maildirs, is there a reasonable chance I can do with sieve? signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] MUA notifications on new mail in a new folder?
On Wednesday 20 January 2010 21:29:37 Timo Sirainen wrote: > On 20.1.2010, at 23.17, Kārlis Repsons wrote: > > What exactly? Does a MUA gets notified about both the new folder and > > mail? > > > >> But this is more of a client and/or IMAP protocol problem. Nothing > >> Dovecot can do about it. > > > > Could you, please, explain why can it be a protocol problem? > > In IMAP a single connection can select a single folder. When it has > selected the folder, it gets notifications about changes to that one > specific folder. When it issues IDLE command, it gets those notifications > immediately. > > There are no automatic notifications about changes to non-selected folders. > There are two ways clients can get these: > > a) They'll create n connections to select n folders and issue IDLE command > for them. This won't work if there are a lot of folders. For example > Dovecot limits the number of connections/ip to 10. > > b) They'll issue STATUS commands to ask for folder state every n minutes. > > Typically it seems to be a combination of a) and b). There is a NOTIFY > extension that supports notifying changes to non-selected folders, but > there are very close to zero servers and clients supporting it. Dovecot > will, some day.. Thanks! signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] MUA notifications on new mail in a new folder?
On Wednesday 20 January 2010 20:59:58 Timo Sirainen wrote: > On 20.1.2010, at 22.53, Kārlis Repsons wrote: > > I wonder, is a connected IMAP MUA > > automatically notified, that the new message has arrived in the new > > folder? As I see from some experiments with Thunderbird, it has no > > problems with immediate notifications of new mail in previously existing > > folders, however, it has problems with the case of new folder. > > Correct. What exactly? Does a MUA gets notified about both the new folder and mail? > But this is more of a client and/or IMAP protocol problem. Nothing > Dovecot can do about it. Could you, please, explain why can it be a protocol problem? signature.asc Description: This is a digitally signed message part.
[Dovecot] Conditionally use a sieve script with deliver?
I found a post in this list [0], which says sieve scripts can be used to deliver mail as read. However, can it be done somehow conditionally, I mean, with a direct or indirect switch for deliver? For a nonexistent example, it would be simply < | deliver -m path/to/maildir -r > or maybe an environment variable could be exported to deliver sieve and checked there? (Still not sure if sieve can replace maildrop in my case, however, using it with dovecot creates various problems with interoperability; but perhaps I can just add those imap4flags like "\\seen" myself to the message with maildrop and avoid mess with sieve at all?) [0] http://www.dovecot.org/list/dovecot/2008-July/032294.html signature.asc Description: This is a digitally signed message part.
[Dovecot] MUA notifications on new mail in a new folder?
If deliver gets run with a non-root userid like this: < | deliver -m path/to/NEWmaildir >, I wonder, is a connected IMAP MUA automatically notified, that the new message has arrived in the new folder? As I see from some experiments with Thunderbird, it has no problems with immediate notifications of new mail in previously existing folders, however, it has problems with the case of new folder. signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Update Dovecot index files on maildrop delivery?
On Friday 15 January 2010 14:44:07 Eduardo M KALINOWSKI wrote: > On Sex, 15 Jan 2010, Kārlis Repsons wrote: > > On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote: > >> On Sex, 15 Jan 2010, Kārlis Repsons wrote: > >> > is there some easy way to inform Dovecot about a new delivery, which > >> > has happened after postfix invoked maildrop, so the index files would > >> > be updated? > >> > >> That's exactly the task for which dovecot deliver was made. > > > > But maybe you could also post a short info on how should deliver be > > called? > > > > I read that "The Dovecot LDA, called deliver, is a local delivery agent > > which takes mail from an MTA and delivers it to a user's mailbox, while > > keeping Dovecot index files up to date." > > However in my case maildrop seems to be in the place of deliver. > > Would it work > > if maildrop had deliver called by xfilter with the options appended, then > > followed by "to /dev/null"? > > I don't know maildrop, so I can't tell if this would work. But the > idea is to use deliver instead of maildrop, unless you need something > that only maildrop can do. > > In this case, I'd leave things as they are and not worry about > indexes. When the mail folder is opened next time dovecot will notice > the new messages and update the indexes. But I think, client MUA will not be timely notified of the new mail, which might happen for one together with index updating (wouldn't it?)... signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Update Dovecot index files on maildrop delivery?
On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote: > On Sex, 15 Jan 2010, Kārlis Repsons wrote: > > is there some easy way to inform Dovecot about a new delivery, which has > > happened after postfix invoked maildrop, so the index files would be > > updated? > > That's exactly the task for which dovecot deliver was made. But maybe you could also post a short info on how should deliver be called? I read that "The Dovecot LDA, called deliver, is a local delivery agent which takes mail from an MTA and delivers it to a user's mailbox, while keeping Dovecot index files up to date." However in my case maildrop seems to be in the place of deliver. Would it work if maildrop had deliver called by xfilter with the options appended, then followed by "to /dev/null"? signature.asc Description: This is a digitally signed message part.
[Dovecot] Update Dovecot index files on maildrop delivery?
Hi all, is there some easy way to inform Dovecot about a new delivery, which has happened after postfix invoked maildrop, so the index files would be updated? signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] IMAP client dependence on dovecot mail storage fromat?
It might be useful to add this conversation here: On Friday 08 January 2010 22:43:27 Ingo Klöcker wrote: > On Friday 08 January 2010, Kārlis Repsons wrote: > > On top of that, its impossible > > to create and access a new folder with KMail on my dovecot: it > > doesn't happen, that a new folder would be created with name > > "newfolder" into "parrentfolder", but along with the latter > > "parrentfolder.newfolder" is created! > > Hmm. "parentfolder.newfolder" sounds like maildir++. All KMail (and also > Thunderbird) does is tell the IMAP server to create a folder "newfolder" > below the folder "parentfolder". It's up to dovecot to actually create > the folder in its storage as needed. I cannot imagine why a folder > created by Thunderbird results in parentfolder/newfolder while a folder > created by KMail results in parentfolder.newfolder unless you switched > dovecot's storage format. Well, that is weird to me as I didn't! No joke, I did again: Thunderbird 3.0; KMail 1.12.1 Using KDE 4.3.1 (KDE 4.3.1); dovecot-1.2.6; So: 1) create folder TOP with KMail, then create a subfolder sub, which results in: "TOP" and "TOP.sub" (both prepared as maildirs with cur,new,tmp and maildirfolder file); 2) create folder "TOP2" on the same fs level with Thunderbird, then create a subfolder "sub2" into it, which results in: "TOP2" prepared and containing "sub2" also prepared (prepared just like with KMail). So... Its reality! signature.asc Description: This is a digitally signed message part.
[Dovecot] How to create UTF encoded folders?
Hey, as I understand from post [1], system folders with UTF-8 chars in their names will only be available for use with Dovecot2 and I certainly look forward to that, but somehow I was short of info about the current use of UTF characters like ā, Ž etc. Should I just omit thinking about modified-UTF-7, avoid those characters for the time being and then with Dovecot2 create UTF-8 encoded folders with MUA and also on fs? Or there is something to know anyway? Please suggest as it would be a pity not to create folders with utf symbols... [1] http://www.mail-archive.com/dovecot@dovecot.org/msg23576.html signature.asc Description: This is a digitally signed message part.
[Dovecot] IMAP client dependence on dovecot mail storage fromat?
Hi, After setting up a maildir tree with :LAYOUT=fs and accessing it with KMail and Thunderbird, various mail client-specific problems appeared, but, as I didn't try with maildir++, I would like to confirm here: does that matter for an IMAP client much if I store mail on server as ":LAYOUT=fs" or maildir++? Can it see differences? I would like to think, that IMAP protocol should provide for all transactions in a standard way and its dovecot's/server's sole business how it stores mail locally. However... These results seem not very good: KMail: try creating a folder "sub" in "parrent" and you'll get "parrent.sub" along with "parrent" on server side. There, however, are no problems with Latvian unicode chars. Thunderbird: it can create a new folder in "parrent" as desired, but it can't display Latvian unicode chars (being such at server side) on client, while, if I try creating a new folder with Thunderbird with these chars, on server it will look somewhat like base64! So I'm really confused. All together these things are pretty frustrating, sure, but I'd like to understand whats the real problem here! signature.asc Description: This is a digitally signed message part.
[Dovecot] IMAP server to move sent mail according to maildroprc?
Hi, Sorry if subj. is far from anything possible, but I try solving this problem: On Saturday 12 December 2009 16:57:40 /dev/rob0 wrote: > On Sat, Dec 12, 2009 at 03:37:17PM +0000, Kārlis Repsons wrote: > > Could anyone help me sorting this out: its very convenient to store > > mails on mailserver and relay sent mail through it, so it gets sent > > immediately, but there is a problem: how can relayed sent mail be > > also saved on mailserver, using the same LDA program as for > > incoming mail (to place it into the right folder where also > > incoming mail is)? Is that possible? > > This is generally best handled at the MUA/IMAP level, where a MUA > uses a "sent" IMAP folder to store mail. .. > I think the bottom line is that you're trying to make a MTA do > things it was not meant to do. The whole problem lies in a desire to use these two things in the same time: 1. maildrop filters file for all users messages (to place sent mail right); 2. store / access mails from mailserver, which is also a relayhost. Maybe there are some suggestions in this list on how should I solve the problem? signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] id/permissions question
On Friday 11 December 2009 17:22:52 you wrote: > On Fri, 2009-12-11 at 17:17 +0000, Kārlis Repsons wrote: > > dovecot.conf contains this line: mail_privileged_group = mail > > This is needed only with mbox format. You should probably just comment > it out. > chgrp user1 /path/user1 > chmod 0700 /path/user1 Thanks Timo, yes, was my own silly mistake... signature.asc Description: This is a digitally signed message part.
[Dovecot] id/permissions question
People, There is an imap client, which runs with user1 uid, but when its accessed to watch a maildir, whose (and its contents) ownership is user1:user1, this error occurs: dovecot: IMAP(user1): fchown(/path/user1/dovecot-uidlist.tmp, -1, 12(mail)) failed: Operation not permitted (egid=1000(user1), group based on /path/user1) dovecot.conf contains this line: mail_privileged_group = mail authentication happens through passwd-file, where for user1 its uid and gid are specified as in /etc/passwd and /etc/group. So how should dovecot be told to use user1 group instead of mail group? (or it needs some other solution?) signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Manual files moving and index files
On Friday 04 December 2009 07:51:12 Joseba Torre wrote: > El Jueves 03 Diciembre 2009 a las 21:52, Kārlis Repsons escribió: > > And there is no need to refresh any index files for IMAP users to > > see / not to see moved mails? > > Yes, but dovecot does that by itself. In my case, procmail is moving > files into mail folders all day ;-) Thanks all! signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Manual files moving and index files
On Thursday 03 December 2009 19:57:31 Eduardo M KALINOWSKI wrote: > Kārlis Repsons wrote: > > Hello all! > > > > My first question about dovecot turns out to be: what if I have something > > outside of dovecot, which sometimes moves messages out of a mail folder > > and other times into it? Does that make any problem for dovecot or > > indexing? > > No. And there is no need to refresh any index files for IMAP users to see / not to see moved mails? signature.asc Description: This is a digitally signed message part.
[Dovecot] Manual files moving and index files
Hello all! My first question about dovecot turns out to be: what if I have something outside of dovecot, which sometimes moves messages out of a mail folder and other times into it? Does that make any problem for dovecot or indexing? signature.asc Description: This is a digitally signed message part.