[Dovecot] virtual namespace question

2010-01-10 Thread Josephus

Hi,

I'm wondering if it is possible to create a virtual namespace on a 
prefix other than virtual/. My goal is to mix IMAP folders with 
virtual folders on the same folder level (prefix = ).


mail_location = maildir:/data/mail/%d/%u/

# Virtual
namespace private {
prefix =
separator = /
location = virtual:/data/mail/%d/%u/virtual
}

# Default
namespace private {
separator = /
prefix =
inbox = yes
}

With this configuration the folders show up on the same level, but I'm 
unable to subscribe to them. When I change the prefix back to virtual/ 
it works, but folders are still gruoped under virtual. Funny thing is, 
when I use a prefix something like vfolder/, the root folder is no 
longer greyed out in my MUA (TB3), and I get a Mailbox doesn't exist: 
vfolder error msg if I click on it.


BR,
Jos


Re: [Dovecot] Dovecot-deliver sometimes fails when message set to discard via sieve

2010-01-10 Thread Steve Wagner
Sorry for the late answer, i was quiet busy the time.

I now execute the script. I report back when the error occures next time.

Steve

Am 29.12.2009 22:19, schrieb Timo Sirainen:
 On Mon, 2009-12-28 at 14:34 +0100, Steve Wagner wrote:
 The only error message i have, come from procmail.log:

 24918-Folder: /opt/dovecot/libexec/dovecot/deliver
3720
 24919-procmail: Error while writing to
 /opt/dovecot/libexec/dovecot/deliver
 24920:From keineantwortadre...@web.de  Tue Dec  8 07:19:55 2009
 
 This probably means that deliver crashed. Maybe instead of executing
 deliver directly, you could execute deliver.sh that works something
 like:
 
 #!/bin/sh
 
 cd /tmp
 ulimit -c unlimited
 /opt/dovecot/libexec/dovecot/deliver $*
 code=$?
 if [ $code != 0 ]; then
   echo 'deliver failed'  /tmp/deliver.err
 fi
 exit $code
 
 Then see if deliver wrote a core file to /tmp or to user's home dir (if
 user has one). If you do get a core file, get gdb backtrace:
 
 gdb /opt/dovecot/libexec/dovecot/deliver core
 bt full


Re: [Dovecot] leave mail on server workaround

2010-01-10 Thread Kirill Miazine
Thanks for the suggestion regarding quotas, but I'm really interested in
an approach I just described. I want to be able to disable the
possibility to leave mail on server after download.

* Stan Hoeppner [2010-01-09 20:56]:
 Kirill Miazine put forth on 1/9/2010 6:34 PM:
  Hello,
  
  POP users often keep fetched mail on server, by checking for leave mail
  on server or similar option in their client.
  
  What would be the best way to disallow them using such approach.
 
 Implement storage quotas.  I'd make the policy known to your users well
 in advance of implementing any solution to this problem though.
 Uninformed users are generally upset by unannounced changes being forced
 upon them.
 
 --
 Stan


Re: [Dovecot] leave mail on server workaround

2010-01-10 Thread Frank Elsner
On Sun, 10 Jan 2010 13:57:41 +0100 Kirill Miazine wrote:
 Thanks for the suggestion regarding quotas, but I'm really interested in
 an approach I just described. I want to be able to disable the
 possibility to leave mail on server after download.

Maybe you should disable POP in general an d offer IMAP only?

People who want their mail on their local computer can achive this
by copiyng from the (IMAP-)folder to the local folders. 


--Frank Elsner


Re: [Dovecot] leave mail on server workaround

2010-01-10 Thread Vegard Svanberg
* Kirill Miazine k...@krot.org [2010-01-10 13:57]:

 Thanks for the suggestion regarding quotas, but I'm really interested in
 an approach I just described. I want to be able to disable the
 possibility to leave mail on server after download.

Well, you'd have to hack the source then, and make it delete the message
after retrieving it.

Or you could make something that deletes read e-mails older than X days. 

-- 
Vegard Svanberg veg...@svanberg.no [*tak...@irc (EFnet)]



Re: [Dovecot] leave mail on server workaround

2010-01-10 Thread Kirill Miazine

* Vegard Svanberg [2010-01-10 14:31]:

* Kirill Miazine k...@krot.org [2010-01-10 13:57]:


Thanks for the suggestion regarding quotas, but I'm really interested in
an approach I just described. I want to be able to disable the
possibility to leave mail on server after download.


Well, you'd have to hack the source then, and make it delete the message
after retrieving it.


Yes, that's probaby the easiest way to go. Or maybe a plugin for
disallowing leave mail on server to force users to use IMAP?


Or you could make something that deletes read e-mails older than X days.


--
-- Kirill Miazine k...@krot.org


Re: [Dovecot] Moving

2010-01-10 Thread Timo Sirainen
On 2.1.2010, at 23.18, Timo Sirainen wrote:

 I'm moving back to Finland tomorrow. It's probably going to take a week or so 
 until things settle down and I'm again back to coding.

And now I'm without internet at home, hopefully my mobile 3g connection opens 
in a few days.. And in any case I'll get cable modem by Saturday.

[Dovecot] how to use dsync?

2010-01-10 Thread joakim
I would like to try dsync but dont quite understand the usage
string. Can anyone offer an example?
-- 
Joakim Verona


Re: [Dovecot] how to use dsync?

2010-01-10 Thread Pascal Volk
On 01/10/2010 05:38 PM joa...@verona.se wrote:
 I would like to try dsync but dont quite understand the usage
 string. Can anyone offer an example?

New Dovecot v2.0.x things are currently partially documented and only
available in wiki_2_.
For dsync see: http://wiki2.dovecot.org/Tools/dsync


Regards,
Pascal
-- 
The trapper recommends today: beeffeed.1001...@localdomain.org


Re: [Dovecot] leave mail on server workaround

2010-01-10 Thread Frank Cusack

On January 10, 2010 1:34:25 AM +0100 Kirill Miazine k...@krot.org wrote:

What would be the best way to disallow them using such approach. That
is, what is the best way to force deletion of messages that have been
RETRieved in a POP session at the end of that POP session?

RETRieved messages will be marked as \Seen, but since users might also
use an IMAP client (e.g. webmail), it'll be dangerous to simply delete
all \Seen messages in user's mailbox.


These two statements seem to be in conflict.  If your users might also
use an IMAP client, why would you delete retrieved messages at all?


Re: [Dovecot] leave mail on server workaround

2010-01-10 Thread Kirill Miazine
* Frank Cusack [2010-01-10 12:20]:
 On January 10, 2010 1:34:25 AM +0100 Kirill Miazine k...@krot.org wrote:
  What would be the best way to disallow them using such approach. That
  is, what is the best way to force deletion of messages that have been
  RETRieved in a POP session at the end of that POP session?
 
  RETRieved messages will be marked as \Seen, but since users might also
  use an IMAP client (e.g. webmail), it'll be dangerous to simply delete
  all \Seen messages in user's mailbox.
 
 These two statements seem to be in conflict.  If your users might also
 use an IMAP client, why would you delete retrieved messages at all?

To give them an incentive to use only IMAP ;)

Actually this is a wish of one customer, so I'm trying to figure out how
much pain it will be do support such scenario.

-- Kirill


Re: [Dovecot] leave mail on server workaround

2010-01-10 Thread Stan Hoeppner
Kirill Miazine put forth on 1/10/2010 11:28 AM:

 Actually this is a wish of one customer, so I'm trying to figure out how
 much pain it will be do support such scenario.

One customer?  Why is s/he requesting this?  AFAIK, all POP clients default to
delete after download.  And even if there is one that defaults to leave a
copy on server I guarantee it has an option to delete after download.

However, regardless, these aren't motivations.  The only possible legitimate
motivation for wanting this ability is that a customer is eating too much disk
space.  The answer to that is quotas.  If you goal is that you just don't want
to support POP anymore but only IMAP, then you send an announcement to your
customer community that you will cease supporting POP on date xx/xx/ and
instructions for setting up an IMAP client can be found here:
http://www.your-domain.tld/imap-instructions.

Something is amiss here.  I fear you are not being truthful in your account of
your motivations.  There is no legitimate scenario for requesting this ability.
 Any possible motivation you could have for wanting this feature is better
properly handled by options/methods already in existence.

--
Stan


[Dovecot] dovecot bug: Next message unexpectedly corrupted in mbox file

2010-01-10 Thread Justin Piszcz

Package: dovecot-imapd
Version: 1.2.9-1
Distribution: Debian Testing x86_64

Problem: See below.

..

Looking further I found this (which is when the problem began to appear in 
the logs):


First time:
Jan  2 09:33:25 l1 dovecot: IMAP(user): Next message unexpectedly 
corrupted in mbox file /home/user/Mailbox at 10599


Due to:

2010-01-02 05:00:29 configure dovecot-common 1:1.2.9-1 1:1.2.9-1
2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1
2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1
2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1
2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1
2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1
2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1
2010-01-02 05:00:29 status half-configured dovecot-common 1:1.2.9-1
2010-01-02 05:00:31 status installed dovecot-common 1:1.2.9-1

2010-01-02 05:00:38 configure dovecot-imapd 1:1.2.9-1 1:1.2.9-1
2010-01-02 05:00:38 status unpacked dovecot-imapd 1:1.2.9-1
2010-01-02 05:00:38 status half-configured dovecot-imapd 1:1.2.9-1
2010-01-02 05:00:38 status installed dovecot-imapd 1:1.2.9-1

During an apt-get dist-upgrade..

Did dovecot 1.2.9 include this patch:
http://www.dovecot.org/list/dovecot-cvs/2009-December/015177.html

So now one sees the message, whereas before, no message was shown? 
Nothing to be concerned about?


Justin.

On Fri, 8 Jan 2010, Justin Piszcz wrote:


Hi,


t I am seeing this on one of my servers:
Jan  8 10:08:58 l1 dovecot: IMuser(user): Next message unexpectedly corrupted 
in mbox file /home/user/Mailbox at 10558


I have never seen this before, and google yields no results except when this 
warning was added to the source code here:

http://www.dovecot.org/list/dovecot-cvs/2009-December/015177.html

The user has deleted all of the mail in the Mailbox but the problem persists.

Any ideas?

Justin.



Re: [Dovecot] CLOSING THREAD (was: leave mail on server workaround)

2010-01-10 Thread Kirill Miazine

* Stan Hoeppner [2010-01-10 12:15]:

Kirill Miazine put forth on 1/10/2010 11:28 AM:


Actually this is a wish of one customer, so I'm trying to figure out how
much pain it will be do support such scenario.


One customer?  Why is s/he requesting this?  AFAIK, all POP clients default to
delete after download.  And even if there is one that defaults to leave a
copy on server I guarantee it has an option to delete after download.

However, regardless, these aren't motivations.  The only possible legitimate
motivation for wanting this ability is that a customer is eating too much disk
space.  The answer to that is quotas.  If you goal is that you just don't want
to support POP anymore but only IMAP, then you send an announcement to your
customer community that you will cease supporting POP on date xx/xx/ and
instructions for setting up an IMAP client can be found here:
http://www.your-domain.tld/imap-instructions.

Something is amiss here.  I fear you are not being truthful in your account of
your motivations.


What makes you fear that I'm not being truthful about my motivation? (So
ou mean I'm lying, huh?) I got a question about possibility to disable
leave mail on server at all. And since leave mail on server is just
a client behaviour (not deleting after retrieving), I needed to explore
options to accomplish this request.

On this list, I was asking about a way to best accomplish this. I was
not asking for opinions on whether such behaviour is optimal, desirable
etc.


There is no legitimate scenario for requesting this ability.
Any possible motivation you could have for wanting this feature is better
properly handled by options/methods already in existence.


IIRC Gmail has an option to delete a message after it is retrieved via
POP. Regardless of whether the POP client issues DELE commands or not.

I remember having come across a POP server that had a feature (disabled
by default, of course) to generate random messge ID in response to UIDL
commands. The motiviation? To discourage users leaving mail on server.

Anyway, let us close this thread now before getting too much off topic.

--
-- Kirill Miazine k...@krot.org


Re: [Dovecot] How to create UTF encoded folders?

2010-01-10 Thread Timo Sirainen
On 9.1.2010, at 13.18, Kārlis Repsons wrote:

 as I understand from post [1], system folders with UTF-8 chars in their names 
 will only be available for use with Dovecot2

No, they're not even in v2.0. I was thinking about it, but it became a bit too 
much work so I decided to leave it later.

 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...

mUTF-7 is the way to do it now, and if in future Dovecot supports UTF-8 in 
filesystem there will be a way to move to it automatically.



Re: [Dovecot] uw-imap compatability hack?

2010-01-10 Thread Timo Sirainen
On 8.1.2010, at 23.47, Simon Annetts wrote:

 if I remove the mail/ setting from 'IMAP server directory' in the client, 
 then everything works as expected and all the folders are visible.
 With this setting in however, only the inbox is visible and attempts to click 
 on another folder, say Trash result in the client error:
 Mailbox doesn't exist .mail.Trash
 I've tried various namespace configurations I found in the namespaces wiki 
 example but none seem to work.

You need to preserve the separator:

namespace private {
  prefix = 
  separator = /
}
namespace private {
  prefix = mail/
  separator = /
}