Re: Subject tag [Dovecot] is gone
On Tue, Jun 10, 2014 at 11:04:28AM -0400, Chris Young wrote: Gmail doesn't let me filter on message headers so I've updated my filter as follows Yes it does. I use this: (list:dovecot OR to:dovecot) It matches both mail received from the mailing-list and those I send to the mailing-list. +1 for te subject tag removal :) -- Nicolas
Re: [Dovecot] Initial status notification not received
On Fri, Nov 23, 2012 at 08:18:32AM +0200, Timo Sirainen wrote: On 16.11.2012, at 16.12, Nicolas KOWALSKI wrote: We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs startup, dovecot almost always shows these errors: Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps disabled) Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591 killed with signal 9 As the last line tells, dovecot stops logging information. We have to restart the dovecot processes to get back normal behaviour. I also tried to set idle_kill values to services definitions, without success. You mean this happens when the VM starts up, but if you manually restart it later they don't happen? Yes. Is there a way to prevent these errors? I wonder if it's because of SLES or something else. We narrowed the problem to another process, started before dovecot, which takes a lot of CPU and disk resources; since we delayed its launch, dovecot starts up happily. However, I am still confused about why dovecot kills itself. Maybe the master process could restart its runaway processes, or the initial status notification delay could be customized? -- Nicolas
Re: [Dovecot] Initial status notification not received
Hello,
Has anybody some suggestions about the problem below?
I see in the archives
(http://thread.gmane.org/gmane.mail.imap.dovecot/67077) that someone
also has (had?) this problem; a cronjob workaround was used, but no
dovecot solution was given.
Thanks,
Nicolas
On Fri, Nov 16, 2012 at 03:12:59PM +0100, Nicolas KOWALSKI wrote:
Hello,
We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs
startup, dovecot almost always shows these errors:
Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core
dumps disabled)
Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status
notification not received in 30 seconds, killing the process
Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status
notification not received in 30 seconds, killing the process
Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial
status notification not received in 30 seconds, killing the process
Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591
killed with signal 9
As the last line tells, dovecot stops logging information. We have to
restart the dovecot processes to get back normal behaviour. I also tried
to set idle_kill values to services definitions, without success.
Is there a way to prevent these errors?
Here is the dovecot -n output:
# 2.1.10: /etc/dovecot/dovecot.conf
# OS: Linux 3.0.42-0.7-xen x86_64 SUSE Linux Enterprise Server 11
(x86_64)
default_client_limit = 4096
default_idle_kill = 5 mins
default_process_limit = 16384
listen = 10.254.251.18
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
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap sieve
service anvil {
client_limit = 65536
idle_kill = 0
}
service auth {
client_limit = 32768
}
service imap-login {
inet_listener imap {
port = 0
}
}
service imap {
process_limit = 0
}
service log {
idle_kill = 0
}
service managesieve {
process_limit = 0
}
service ssl-params {
idle_kill = 0
}
ssl_ca = /etc/dovecot/ssl/ca.pem
ssl_cert = /etc/dovecot/ssl/server-crt.pem
ssl_key = /etc/dovecot/ssl/server-key.pem
userdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
protocol sieve {
passdb {
args = /etc/dovecot/dovecot-ldap-sieve.conf.ext
driver = ldap
}
}
Thanks,
--
Nicolas
--
Nicolas
[Dovecot] Initial status notification not received
Hello,
We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs
startup, dovecot almost always shows these errors:
Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps
disabled)
Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status
notification not received in 30 seconds, killing the process
Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status
notification not received in 30 seconds, killing the process
Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial
status notification not received in 30 seconds, killing the process
Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591 killed
with signal 9
As the last line tells, dovecot stops logging information. We have to
restart the dovecot processes to get back normal behaviour. I also tried
to set idle_kill values to services definitions, without success.
Is there a way to prevent these errors?
Here is the dovecot -n output:
# 2.1.10: /etc/dovecot/dovecot.conf
# OS: Linux 3.0.42-0.7-xen x86_64 SUSE Linux Enterprise Server 11
(x86_64)
default_client_limit = 4096
default_idle_kill = 5 mins
default_process_limit = 16384
listen = 10.254.251.18
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
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap sieve
service anvil {
client_limit = 65536
idle_kill = 0
}
service auth {
client_limit = 32768
}
service imap-login {
inet_listener imap {
port = 0
}
}
service imap {
process_limit = 0
}
service log {
idle_kill = 0
}
service managesieve {
process_limit = 0
}
service ssl-params {
idle_kill = 0
}
ssl_ca = /etc/dovecot/ssl/ca.pem
ssl_cert = /etc/dovecot/ssl/server-crt.pem
ssl_key = /etc/dovecot/ssl/server-key.pem
userdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
protocol sieve {
passdb {
args = /etc/dovecot/dovecot-ldap-sieve.conf.ext
driver = ldap
}
}
Thanks,
--
Nicolas
Re: [Dovecot] ssl_cert_username_field and subjectAltName?
On Tue, Mar 20, 2012 at 02:55:12PM +0100, Nicolas KOWALSKI wrote: Does dovecot support the subject Alternative Name email value [1] as ssl_cert_username_field? If so, how should it be specified in the configuration? Well, I just found the wiki states no: The text is looked up from subject DN's specified field (http://wiki2.dovecot.org/SSL/DovecotConfiguration) Sorry for the noise, -- Nicolas
[Dovecot] ssl_cert_username_field and subjectAltName?
Hello, Does dovecot support the subject Alternative Name email value [1] as ssl_cert_username_field? If so, how should it be specified in the configuration? Thanks. [1] http://www.openssl.org/docs/apps/x509v3_config.html#Subject_Alternative_Name_ -- Nicolas
Re: [Dovecot] proxy, managesieve and ssl?
On Wed, Jan 11, 2012 at 10:34:33PM +0200, Timo Sirainen wrote:
On 11.1.2012, at 21.01, Nicolas KOWALSKI wrote:
I would like to use IMAPs, instead of IMAP+STARTTLS, from proxy to
backend, and have Managesieve still working. Is this supported?
You'll need to kludge it a little bit. I guess you're using LDAP, since you
mentioned pass_attrs?
Yes, I am using LDAP.
protocol sieve {
passdb {
args = ldap-with-starttls.conf
}
}
When just adding the above, it works perfectly, Thanks!
protocol !sieve {
passdb {
args = ldap-with-ssl.conf
}
}
Is this really needed? It looks like it works without it. When using it,
I get this error:
Jan 12 09:40:59 imap1 dovecot: auth: Fatal: No passdbs specified in
configuration file. PLAIN mechanism needs one
Jan 12 09:40:59 imap1 dovecot: master: Error: service(auth): command startup
failed, throttling
--
Nicolas
Re: [Dovecot] proxy, managesieve and ssl?
On Wed, Jan 11, 2012 at 10:06:51PM +0100, Stephan Bosch wrote:
On 1/11/2012 8:01 PM, Nicolas KOWALSKI wrote:
I would like to use IMAPs, instead of IMAP+STARTTLS, from proxy to
backend, and have Managesieve still working. Is this supported?
Although there is no such thing as a standard sieveS protocol, you
can make Dovecot v2.x talk SSL from the start at a ManageSieve
socket. Since normally people will not use something like this, it
is not available by default.
In conf.d/20-managesieve.conf you can adjust the service definition
of ManageSieve as follows:
service managesieve-login {
inet_listener sieve {
port = 4190
}
inet_listener sieves {
port = 5190
ssl = yes
}
}
This works well, when using (as Timo wrote) a different ldap pass_attrs
for sieve, specifying this specific 5190 port. Thanks for your
suggestion.
This starts the normal protocol on port 4190 and the direct-SSL
version on an alternative port. You can also put the ssl=yes
directly in the port 4190 listener, as long as no client will have
to connect to this server directly (no client will support it).
Well, as this is non-standard, I guess I will not use it. I much prefer
to stick with what has been RFCed.
--
Nicolas
[Dovecot] proxy, managesieve and ssl?
Hello, On a dovecot 2.0.14 proxy, I found that proxying managesieve works well when using 'starttls' option in pass_attrs, but does not work when using 'ssl' option. The backend server is also dovecot 2.0.14; when using the ssl option, it reports no auth attempts in the logs about managesieve-login, and meanwhile the MUA, Thunderbird with sieve plugin, reports [TRYLATER] account is temporary disabled; no problem when using starttls option on the proxy, all works well. I would like to use IMAPs, instead of IMAP+STARTTLS, from proxy to backend, and have Managesieve still working. Is this supported? Thanks, -- Nicolas
Re: [Dovecot] LMTP-Server: missing headers
Timo Sirainen t...@iki.fi writes: In the first case there are *no* Return-Path and Delivered-To Headers. In the (most common) second case the *are* present. Why these Headers are not included while using the LMTP-Server? I agree about the Return-Path missing, but the Delivered-To is specific to Postfix, see: http://www.postfix.org/faq.html#delivered I guess I could add Return-Path header. I could also add Delivered-To as long as there is only a single recipient, but adding it for multiple recipients would make everything much more difficult than I'd like. I was wondering about Delivered-To header before too. What do people use it for? According to the above link: The purpose is to stop mail forwarding loops as early as possible -- Nicolas
[Dovecot] Discard duplicate messages at delivery?
Hello, I am using dovecot 1.2.9, and the sieve plugin for filtering incoming messages into specific folders. The MTA is postfix, and deliver is called using the mailbox_command = /usr/lib/dovecot/deliver directive. Is it possible to make dovecot's deliver discard duplicate messages? With cyrus there is a duplicatesuppression directive which works well (http://cyrusimap.web.cmu.edu/imapd/overview.html#duplicate). With procmail, this can be done with the following recipe, but I did not found an equivalent for dovecot: # One often receives duplicate messages for cross-postings to mailing # lists, or explicit replies to a post from you in addition to the # mailing list message. # # The following recipe eliminates all duplicate messages. It tells # formail(1) to keep a cache file of the Message-IDs of the most # recent messages you've received. Since Message-IDs are guaranteed # unique for distinct messages, they are ideally suited to weed out # duplicates. # :0 Wh: msgid.lock | formail -D 65536 .saves.msgid Thanks, -- Nicolas
Re: [Dovecot] Discard duplicate messages at delivery?
Steffen Kaiser skdove...@smail.inf.fh-brs.de writes: On Tue, 12 Jan 2010, Nicolas KOWALSKI wrote: Is it possible to make dovecot's deliver discard duplicate messages? No, currently not. Ok. BTW: if two copies of a message with the same message-id and the same envelope receipient are received. I know that MessageIDs are supposed to be globally unique, but one cannot count on it. I agree, but IMHO, most of the times it is ok, and by using a short lifetime for the Message-IDS stored, the risk of having false duplicates is even less important. Thanks for your reply, -- Nicolas
Re: [Dovecot] Sieve mails with decoded subject
Timo Sirainen t...@iki.fi writes: On Thu, 2009-12-10 at 20:22 +0100, Johannes Bauer wrote: I'm still somewhat reluctant to change to 1.2, because that would mean that I cannot rely on my distros packages anymore (Etch that is for that server) but must maintain the packages myself. Well... How about using backports.org? Well, for etch the backport is not enough for 1.2.x: http://packages.debian.org/etch-backports/dovecot-imapd BTW, according to http://wiki.debian.org/DebianEtch, on Feb 2010, Etch will be declared as EOLed, so, imho, an Etch-to-Lenny upgrade should be planned very soon there. -- Nicolas
Re: [Dovecot] Problems with listescape and mutt
Daniel Spannbauer d...@marco.de writes: my ~.muttrc is completly empty. But in my globnal /etc/Muttrc there are some configs. IMHO, there is a script somewhere in your configuration generating the list of mailboxes, and it generates it wrong, probably because it thinks that the maildir structure is of the type LAYOUT=FS, and not Maildir++. folder=imap://d...@homedirs/ spoolfile=imap://d...@homedirs/INBOX This is fine. postponed=imap://d...@homedirs/.Drafts record=imap://d...@homedirs/.Sent This is wrong. imap_list_subscribed is set Not sure about this one, because you told that there were no dots in the subscription file. -- Nicolas
Re: [Dovecot] Problems with listescape and mutt
Daniel Spannbauer d...@marco.de writes: Hmm, I log in with mutt over the dovecot imap, so a c shows exactly: 1 0 imap://d...@homedirs/ 2 0 imap://d...@homedirs/.ADMIN 3 0 imap://d...@homedirs/.DOVECOT 4 0 imap://d...@homedirs/.Drafts It looks like you have defined this list in your ~/.muttrc mailboxes variable. The rawlog you showed later also indicates these mailboxes do not exist. What about this setting instead: set folder=imap://d...@homedirs/ mailboxes \ =ADMIN \ =DOVECOT \ =Drafts \ ... \ ... -- Nicolas
Re: [Dovecot] Dovecot and SATA Backend
Robert Schetterer rob...@schetterer.org writes: sorry for the stupid question what is DAS do you have a link etc for it, to get more info See http://en.wikipedia.org/wiki/Direct-attached_storage -- Nicolas
Re: [Dovecot] [OT] preferred clients
On Fri, 20 Nov 2009, Jonathan wrote: So what IMAP clients do people prefer these days? Preferably windows or cross platform and it needs to have decent key bindings because (probably like many of you) I get 100s of emails a day via lists and anything that speeds my way through them is good. I would recommend mutt and alpine. They both works well with dovecot. Mutt is more powerfull and configurable (after learning how to set it up); alpine is more straightforward at first. -- Nicolas
Re: [Dovecot] Transfer incomming email to INBOX
Claude Gélinas cla...@phyto.qc.ca writes: I've installed dovecot with maildir format in /home/claude/mail. I fetch my email with fetchmail and they are placed in /var/spool/mail/claude. How can I transfer them automatically in /home/claude/mail/INBOX/new How can I setup something to transfer my email automatically as they arrive. Sure, see : http://wiki.dovecot.org/LDA http://www.dovecot.org/list/dovecot/2007-July/024012.html: In your ~/.fetchmailrc, you may use something like the following: poll your.pop.server with proto POP3 user claude there with pass password options fetchall mda /usr/lib/dovecot/deliver -- Nicolas
Re: [Dovecot] dovecot 1.2 ubuntu horde xi.rename-it.nl
Stephan Bosch step...@rename-it.nl writes: Yep, that's the current status unfortunately. The build server runs Debian testing and that won't install directly on stable. [...] Eventually I should build an automated sbuild environment to make the binaries available to more Debian/Ubuntu releases. If you have this possibility, it would be great! Thanks for your reply, -- Nicolas
Re: [Dovecot] dovecot 1.2 ubuntu horde xi.rename-it.nl
Robert Schetterer rob...@schetterer.org writes: Hi, i used to use Hello, http://xi.rename-it.nl/debian/ experimental-auto main to update dovecot 1.2 with ubuntu horde didnt done for a time now i get broken deps with apt I encountered the same problem with Debian Lenny, so I now recompile the package myself. It works well. -- Nicolas
Re: [Dovecot] dovecot 1.2 ubuntu horde xi.rename-it.nl
Nicolas KOWALSKI n...@petole.demisel.net writes: Robert Schetterer rob...@schetterer.org writes: http://xi.rename-it.nl/debian/ experimental-auto main Oops, I am not using experimental-auto source package, but the testing-auto one in my /etc/apt/sources.list: deb-src http://xi.rename-it.nl/debian/ testing-auto main -- Nicolas
Re: [Dovecot] Maildir structure question
On Sun, Feb 08, 2009 at 03:44:44PM -0500, Timo Sirainen wrote: On Feb 7, 2009, at 4:06 AM, Nicolas KOWALSKI wrote: Yes, dovecot find the mails in INBOX from ~/Maildir/.INBOX . The deliver tool also stores incoming mail in this folder. .. namespace: type: private separator: / list: yes subscriptions: yes Oh, right, now I get it. You don't have inbox=yes set. Perhaps it should do it automatically or give an error message.. That's it. With inbox=yes set in the namespace configuration, dovecot finds and stores mail from/in INBOX in ~/Maildir/(cur|new|tmp). Thanks a lot Timo, -- Nicolas
Re: [Dovecot] Maildir structure question
On Fri, Feb 06, 2009 at 05:14:16PM -0500, Timo Sirainen wrote: On Fri, 2009-02-06 at 21:50 +0100, Nicolas KOWALSKI wrote: On Fri, Feb 06, 2009 at 03:15:17PM -0500, Timo Sirainen wrote: There are no 'cur', 'new' and 'tmp' directories in ~/Maildir, as written in the wiki, but instead this .INBOX directory which contains these 'cur', 'new' and 'tmp'. Is this expected ? Thanks. No, it's not expected. And you mean Dovecot actually finds the mails from the .INBOX? I don't really see how/why it would with your configuration. Yes, dovecot find the mails in INBOX from ~/Maildir/.INBOX . The deliver tool also stores incoming mail in this folder. If you want, I have strace output of a sample deliver run. Better than strace would be to set mail_debug=yes and show the logs. Here are the logs for a deliver run: Feb 7 10:01:20 petole deliver(niko): Loading modules from directory: /usr/lib/dovecot/modules/lda Feb 7 10:01:20 petole deliver(niko): Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so Feb 7 10:01:20 petole deliver(niko): Namespace: type=private, prefix=, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes Feb 7 10:01:20 petole deliver(niko): maildir: data=/home/niko/Maildir Feb 7 10:01:20 petole deliver(niko): maildir++: root=/home/niko/Maildir, index=, control=, inbox= Feb 7 10:01:20 petole deliver(niko): cmusieve: Using sieve path: /home/niko/.dovecot.sieve Feb 7 10:01:20 petole deliver(niko): cmusieve: Executing script /home/niko/.dovecot.sievec Feb 7 10:01:20 petole deliver(niko): msgid=20090207090120.5ba2e8...@petole.demisel.net: saved mail to INBOX Here are the logs when using Alpine: Feb 7 10:02:49 petole dovecot: IMAP(niko): Effective uid=1000, gid=1000, home=/home/niko Feb 7 10:02:49 petole dovecot: IMAP(niko): Namespace: type=private, prefix=, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes Feb 7 10:02:49 petole dovecot: IMAP(niko): maildir: data=~/Maildir Feb 7 10:02:49 petole dovecot: IMAP(niko): maildir++: root=/home/niko/Maildir, index=, control=, inbox= Feb 7 10:02:49 petole dovecot: imap-login: Login: user=niko, method=PLAIN, rip=192.168.0.1, lip=192.168.0.1, TLS My current configuration: petole:~# dovecot -n # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28.3 i686 Debian 4.0 ssl_cert_file: /etc/ssl/certs/petole.demisel.net.pem ssl_key_file: /etc/ssl/private/petole.demisel.net.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:~/Maildir mail_debug: yes namespace: type: private separator: / list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 -- Nicolas
Re: [Dovecot] Maildir structure question
On Fri, Feb 06, 2009 at 11:32:41AM +0100, Matthias Andree wrote: Nicolas KOWALSKI schrieb: There are no 'cur', 'new' and 'tmp' directories in ~/Maildir, as written in the wiki, but instead this .INBOX directory which contains these 'cur', 'new' and 'tmp'. Is this expected ? Thanks. The namespace and folder structure needs to be reflected in Maildir - I presume that namespace configuration also has a say in the layout. For me, who runs Dovecot without namespace configuration, Dovecot has the layout you expect. So I'd say it's the namespace configuration that causes INBOX to appear as a subdirectory of Maildir/. Well, I expected the namespace to change the folder layout presentation to the IMAP client, not to modify the underlying folder layout. Thanks for your reply, -- Nicolas
[Dovecot] Maildir structure question
Hello, About the INBOX location when using maildir, in the wiki, http://wiki.dovecot.org/MailboxFormat/Maildir, I can read: Directory Structure ~/Maildir/new, ~/Maildir/cur and ~/Maildir/tmp directories contain the messages for INBOX. The tmp directory is used during delivery, new messages arrive in new and read shall be moved to cur by the clients. But in my Maildir, I see this: n...@petole:~$ ls -la Maildir/ total 144 drwxr-xr-x 35 niko niko 4096 2009-02-06 08:37 . drwxr-xr-x 25 niko niko 4096 2009-02-06 10:26 .. drwxr-xr-x 5 niko niko 4096 2009-02-06 09:16 .INBOX ... There are no 'cur', 'new' and 'tmp' directories in ~/Maildir, as written in the wiki, but instead this .INBOX directory which contains these 'cur', 'new' and 'tmp'. Is this expected ? Thanks. My configuration: petole:~# dovecot -n # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28.3 i686 Debian 4.0 ssl_cert_file: /etc/ssl/certs/petole.demisel.net.pem ssl_key_file: /etc/ssl/private/petole.demisel.net.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:~/Maildir namespace: type: private separator: / list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 -- Nicolas
Re: [Dovecot] Maildir structure question
On Fri, Feb 06, 2009 at 03:15:17PM -0500, Timo Sirainen wrote: There are no 'cur', 'new' and 'tmp' directories in ~/Maildir, as written in the wiki, but instead this .INBOX directory which contains these 'cur', 'new' and 'tmp'. Is this expected ? Thanks. No, it's not expected. And you mean Dovecot actually finds the mails from the .INBOX? I don't really see how/why it would with your configuration. Yes, dovecot find the mails in INBOX from ~/Maildir/.INBOX . The deliver tool also stores incoming mail in this folder. If you want, I have strace output of a sample deliver run. -- Nicolas
Re: [Dovecot] Dovecot (Al)pine - resaving messages to Inbox
On Wed, Aug 20, 2008 at 09:09:57AM +0200, Nicolas KOWALSKI wrote:
On Wed, Aug 20, 2008 at 08:34:03AM +0200, Steffen Kaiser wrote:
On Tue, 19 Aug 2008, Jonathan Herbach wrote:
I've noticed a change since Dovecot was upgraded. I used to reorder
items within my INBOX in al/pine by saving messages back to the
INBOX, which I was connecting via IMAP
I can Save a message from INBOX to INBOX and a message from another
folder to the INBOX just fine. But I use Dovecot v1.0.13.
I notice the same thing than Jonathan, when using mbox format. No
problem with maildir format.
I forgot to write:
- this is with dovecot 1.1.2
- this is not specific to INBOX: when saving a message from a folder to
the same folder, Alpine complaints with the message
[Can't copy mails inside same folder ]
- the debug journal of Alpine shows, with a 'news' folder:
IMAP DEBUG 09:46:05 8/20: 090b COPY 100 news
IMAP DEBUG 09:46:05 8/20: 090b NO Can't copy mails inside same mailbox
- a quick grep shows this is 'normal' behaviour, as written in
src/lib-storage/index/mbox/mbox-save.c
if (mbox-mbox_lock_type == F_RDLCK) {
/* FIXME: we shouldn't fail here. it's just
a locking issue that should be possible to
fix.. */
mail_storage_set_error(storage,
MAIL_ERROR_NOTPOSSIBLE,
Can't copy mails inside same mailbox);
return -1;
}
--
Nicolas
Re: [Dovecot] Dovecot (Al)pine - resaving messages to Inbox
On Wed, Aug 20, 2008 at 07:25:38AM -0400, Charles Marcus wrote: On 8/20/2008, Nicolas KOWALSKI ([EMAIL PROTECTED]) wrote: I suppose the OP does not sort by date but Arrival time (this means arrival time in the mailbox). It was my understanding that arrival time is the time the message was DELIVERED (by whatever mechanism is in place for final delivery of messages), NOT the time that some IMAP CLIENT moves a message around. Well, I should not have used the 'time' word. The alpine documentation states about 'Arrival' sorting: The Arrival sort option arranges messages in the MESSAGE INDEX in the order that they exist in the folder. This is usually the same as the order in which they arrived. This option is comparable to not sorting the messages at all. It is the same (non-)ordering available in Mozilla mail clients, with the 'Order Received' option. -- Nicolas
Re: [Dovecot] Sent Date/time vs Received Date/time
On Wed, Aug 20, 2008 at 08:43:02AM -0400, Charles Marcus wrote: In my mind, there should be two primary date/time columns: Sent Date/Time = Date/time of the Client system when message was sent (this is already there as the plain 'Date' column) and Received Date/Time = Date/time the receiving SERVER DELIVERED it [...] The main question is - is there a proper IMAP/RFC for providing/getting this date/time? I think this is called INTERNALDATE in the IMAP world (see rfc2060). -- Nicolas
Re: [Dovecot] spamassassin, postfix with dovecot lda?
George Mamalakis [EMAIL PROTECTED] writes:
So my question is as follows:
Is there a way to call spamc from dovecot-LDA (and/or
dovecot-sieve), or is there an alternate way to do this for a site
with virtual mailboxes configured with dovecot-lda?
Hello,
I am currently running a similar setup, with spamc called per user at
delivery time, from postfix. I use the following settings (on a Debian
Etch system, so installation paths must be adapated).
- dovecot's deliver binary must be set setuid root,
- /etc/postfix/main.cf:
mailbox_transport = dovecot
dovecot_destination_recipient_limit = 1
- /etc/postfix/master.cf:
#
# dovecot
#
dovecot unix- n n - 1 pipe
flags=Rh user=dovecot argv=/usr/bin/spamc -u ${user} -e
/usr/lib/dovecot/deliver -d ${user} -f ${sender}
--
Nicolas
[Dovecot] mbox From escaping implementation ?
Hello, I read in the wiki (http://wiki.dovecot.org/MailboxFormat/mbox) about From Escaping: Dovecot doesn't currently do this escaping however. Instead it prevents this confusion by adding Content-Length headers so it knows later where the next message begins. Dovecot doesn't either remove the '' characters before sending the data to clients. Both of these will probably be implemented later. As I understand it, this makes the mbox format of dovecot slightly incompatible with other mbox-capable clients, because if they read the data files directly, they may understand a line starting with an unescaped 'From ' as the start of a new message. Right ? Are there any plans to implement this escaping in the future (1.1.x or 2.0.x?) Thanks, -- Nicolas
Re: [Dovecot] mbox From escaping implementation ?
Timo Sirainen [EMAIL PROTECTED] writes: On Tue, 2008-05-27 at 11:30 +0200, Nicolas KOWALSKI wrote: As I understand it, this makes the mbox format of dovecot slightly incompatible with other mbox-capable clients, because if they read the data files directly, they may understand a line starting with an unescaped 'From ' as the start of a new message. Right ? Just for the record, I found this page, http://homepages.tesco.net/~J.deBoynePollard/FGA/mail-mbox-formats.html which explains the multiple mbox formats available. I was not aware of this before. Finally, Maildir is the solution... Maybe. I got this Content-Length: idea originally from mutt which also uses (used? don't know) Content-Length: instead of From-escaping. Described in the above page as The mboxcl2 mailbox format. Are there any plans to implement this escaping in the future (1.1.x or 2.0.x?) It's a very low priority for me. The Content-Length: usage has actually been completely broken in all v1.0 releases and only a couple of people ever noticed it. I finally fixed it in v1.1 some weeks ago. Thanks for your reply Timo. Regards, -- Nicolas
Re: [Dovecot] Recent message flag unavailable ?
On Fri, 21 Dec 2007, Timo Sirainen wrote: On Wed, 2007-12-12 at 12:06 +0100, Nicolas KOWALSKI wrote: When a message is copied or newly-delivered to a folder, it does not have the recent flag set. Is there something in the configuration to activate it ? Looks like it's buggy with v1.0 + mbox + mbox_lazy_writes=yes. I think I won't bother trying to fix it for v1.0, since it probably requires too large changes. I did now fix one related bug for v1.1, and I've yet to fix it for maildir with v1.1. Ok, I will use the 1.1 series. Thanks for your reply, -- Nicolas
[Dovecot] Recent message flag unavailable ?
Hello, When a message is copied or newly-delivered to a folder, it does not have the recent flag set. Is there something in the configuration to activate it ? Thanks. # dovecot -n # 1.0.9: /usr/local/etc/dovecot.conf protocols: imap login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot mbox_write_locks: fcntl auth default: passdb: driver: pam userdb: driver: passwd The MUA which shows it is Alpine 0.99. -- Nicolas
[Dovecot] mbox File too large error
Hello, I have a rather large (~400MB) INBOX file in mbox format. When using deliver, it complains in the logs: Dec 2 16:47:13 petole deliver(niko): write() failed with mbox file /home/niko/mail/INBOX: File too large I do not see anything related in the configuration. And ulimit shows nothing special: $ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited max nice(-e) 0 file size (blocks, -f) unlimited pending signals (-i) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) unlimited max rt priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) unlimited virtual memory (kbytes, -v) unlimited file locks (-x) unlimited This is with dovecot 1.0.8, sieve plugin 1.0.2: # dovecot -n # 1.0.8: /usr/local/etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: mbox:~/mail:INBOX=~/mail/INBOX mbox_write_locks: fcntl auth default: passdb: driver: pam userdb: driver: passwd What can I do to be able to deliver to large mbox files ? Thanks, -- Nicolas
Re: [Dovecot] mbox vs maildir
Timo Sirainen [EMAIL PROTECTED] writes: The upcoming dbox and cydir formats of course beat everything in performance :) cydir ? Does this mean there is a cyrus-like storage coming soon ? -- Nicolas
Re: [Dovecot] mbox vs maildir
Timo Sirainen [EMAIL PROTECTED] writes: On Fri, 2007-06-29 at 20:26 +0200, Nicolas KOWALSKI wrote: Timo Sirainen [EMAIL PROTECTED] writes: The upcoming dbox and cydir formats of course beat everything in performance :) cydir ? Does this mean there is a cyrus-like storage coming soon ? Already in v1.1 tree. It's what I'm using for my index file stress tests, because the format is practically just the index files and uid. named files. I just read http://www.dovecot.org/list/dovecot/2007-May/022772.html, and the results look really impressive. 10 times faster than Maildir... Time to upgrade and test ! :-) Thanks Timo, -- Nicolas
Re: [Dovecot] mbox vs maildir
Timo Sirainen [EMAIL PROTECTED] writes: On Fri, 2007-06-29 at 21:49 +0200, Nicolas KOWALSKI wrote: Timo Sirainen [EMAIL PROTECTED] writes: On Fri, 2007-06-29 at 20:26 +0200, Nicolas KOWALSKI wrote: Timo Sirainen [EMAIL PROTECTED] writes: The upcoming dbox and cydir formats of course beat everything in performance :) cydir ? Does this mean there is a cyrus-like storage coming soon ? Already in v1.1 tree. It's what I'm using for my index file stress tests, because the format is practically just the index files and uid. named files. I just read http://www.dovecot.org/list/dovecot/2007-May/022772.html, and the results look really impressive. 10 times faster than Maildir... Time to upgrade and test ! :-) Just remember that if you lose the index files there's no easy way to recover the mailbox. Well, except by copying the files to maildir.. Good to know, Thanks. I'm not sure if I should try to make cydir anything else than a benchmark format or a simple example for writing mail storage backends. I'm hoping that dbox will be practically as fast in all situations. If performance of dbox is as fast as cydir, and if cydir is not easily recoverable (a cyrus reconstruct-like tool would help a lot here), well, cydir could stay as benchmark format. But... As I noticed almost no difference in performance (no real numbers here, just a usage feeling with 5-10k messages mailboxes) between dovecot 1.0 + maildir and cyrus 2.2.13/2.3.8, having dovecot use a storage format 10 times faster than Maildir is really attractive. -- Nicolas
Re: [Dovecot] mbox vs maildir
On 6/29/07, Charles Marcus [EMAIL PROTECTED] wrote: Just remember that if you lose the index files there's no easy way to recover the mailbox. Well, except by copying the files to maildir.. I'm not sure if I should try to make cydir anything else than a benchmark format or a simple example for writing mail storage backends. I'm hoping that dbox will be practically as fast in all situations. One advantage of cydir over dbox was mentioned by Mark above re incremental backups - with dbox, you'd still have to backup the entire mailbox file, while with cydir, you'd only have to copy newer messages. True. In my old job, this was the main reason I switched users mailboxes from UW-imap MBX to Cyrus. Performance was also much better after the switch. -- Nicolas
