[Dovecot] Dovecot Support Added to OSSEC
I have added (beta) Dovecot support for the OSSEC HIDs. It will detect certain attacks and error conditions, and optionally block the attacker (similar to fail2ban). Rather than re-hash the details here, I refer you to the OSSEC mailing list for details on how to install. I would appreciate any feedback either here, there, or privately. The idea is to get a few people trying it so I thought a post here would be good, too.
Re: [Dovecot] v1.2.0 released
On Thu, Jul 2, 2009 at 6:38 PM, alexus wrote: > On Thu, Jul 2, 2009 at 4:48 PM, Timo Sirainen wrote: >> On Jul 2, 2009, at 9:20 PM, alexus wrote: >> >>> okay, after doing that I'm getting new errors >>> >>> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Effective uid=89, >>> gid=89, home=(none) >>> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir: >>> data=~vpopmail/domains/alexus.org/X/Maildir/ >>> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir++: >>> root=~vpopmail/domains/alexus.org/X/Maildir, index=, control=, >>> inbox=~vpopmail/domains/alexus.org/postmaster/Maildir >>> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : >>> Permission lookup failed from >>> ~vpopmail/domains/alexus.org/X/Maildir >> >> That's an informational more kind of like a warning. It's not written unless >> you have mail_debug=yes. So it's not an error. >> >>> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : Using >>> permissions from ~vpopmail/domains/alexus.org/X/Maildir: mode=0700 >>> gid=-1 >> >> This isn't an error either. You should have had a separate actual error >> message, which could have given more information. >> >> Anyway it looks like the problem is that ~vpopmail/ doesn't get expanded to >> something like /home/vpopmail/. Hmm. I've changed that part of the code, so >> I guess there could be a bug. Or perhaps I decided to drop that feature.. >> Anyway, I'll look into it next week once I get back to US. >> > > yeah, that was it... i changed ~vpopmail to /home/vpopmail and that > seems to be working now > > thanks > > -- > http://alexus.org/ > this is a bit off topic, but i also get following msg in my syslog Jul 2 18:48:55 mx1 dovecot: auth(default): digest-md5(?,24.185.130.236): Invalid realm: alexus.org when I check my email, any ideas what could be wrong? -- http://alexus.org/
Re: [Dovecot] v1.2.0 released
On Thu, Jul 2, 2009 at 4:48 PM, Timo Sirainen wrote: > On Jul 2, 2009, at 9:20 PM, alexus wrote: > >> okay, after doing that I'm getting new errors >> >> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Effective uid=89, >> gid=89, home=(none) >> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir: >> data=~vpopmail/domains/alexus.org/X/Maildir/ >> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir++: >> root=~vpopmail/domains/alexus.org/X/Maildir, index=, control=, >> inbox=~vpopmail/domains/alexus.org/postmaster/Maildir >> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : >> Permission lookup failed from >> ~vpopmail/domains/alexus.org/X/Maildir > > That's an informational more kind of like a warning. It's not written unless > you have mail_debug=yes. So it's not an error. > >> Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : Using >> permissions from ~vpopmail/domains/alexus.org/X/Maildir: mode=0700 >> gid=-1 > > This isn't an error either. You should have had a separate actual error > message, which could have given more information. > > Anyway it looks like the problem is that ~vpopmail/ doesn't get expanded to > something like /home/vpopmail/. Hmm. I've changed that part of the code, so > I guess there could be a bug. Or perhaps I decided to drop that feature.. > Anyway, I'll look into it next week once I get back to US. > yeah, that was it... i changed ~vpopmail to /home/vpopmail and that seems to be working now thanks -- http://alexus.org/
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
Dear Timo, Thanks for your reply. In Courier-Imap via webmail when delete a email, this was in the INBOX, but it showed as shading and in the server appends the flag T, but was not automatically moved to the Trash. When calculating the quota through maildirsize did not consider the emails with flag T. Dovecot is working perfectly, the problem is that as Courier had this feature, users will not purge mails and when migrating to Dovecot, these emails deleted if considered to calculate the quota for which there are many accounts after the migration have reached 100% usage. Thanks Jose Luis > CC: dovecot@dovecot.org > From: t...@iki.fi > To: jolumape...@hotmail.com > Subject: Re: [Dovecot] Urgent problem with deleting emails and maildirsize > Date: Thu, 2 Jul 2009 22:44:36 +0200 > > On Jul 2, 2009, at 8:57 PM, Jose Luis Marin Perez wrote: > > > I told you that before migrating from Courier to Dovecot deleted > > mails (With flag T and not purged) were considered when calculating > > the quota. > > Or is it that in Courier you had enabled this "move messages marked as > \Deleted to Trash immediately"? I've no plans for implementing that > IMAP protocol breaking feature. > _ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx
Re: [Dovecot] v1.2.0 released
On Jul 2, 2009, at 9:20 PM, alexus wrote: okay, after doing that I'm getting new errors Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Effective uid=89, gid=89, home=(none) Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir: data=~vpopmail/domains/alexus.org/X/Maildir/ Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir++: root=~vpopmail/domains/alexus.org/X/Maildir, index=, control=, inbox=~vpopmail/domains/alexus.org/postmaster/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : Permission lookup failed from ~vpopmail/domains/alexus.org/X/Maildir That's an informational more kind of like a warning. It's not written unless you have mail_debug=yes. So it's not an error. Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : Using permissions from ~vpopmail/domains/alexus.org/X/Maildir: mode=0700 gid=-1 This isn't an error either. You should have had a separate actual error message, which could have given more information. Anyway it looks like the problem is that ~vpopmail/ doesn't get expanded to something like /home/vpopmail/. Hmm. I've changed that part of the code, so I guess there could be a bug. Or perhaps I decided to drop that feature.. Anyway, I'll look into it next week once I get back to US.
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
On Jul 2, 2009, at 8:57 PM, Jose Luis Marin Perez wrote: I told you that before migrating from Courier to Dovecot deleted mails (With flag T and not purged) were considered when calculating the quota. Or is it that in Courier you had enabled this "move messages marked as \Deleted to Trash immediately"? I've no plans for implementing that IMAP protocol breaking feature.
Re: [Dovecot] v1.2.0 released
On Thu, Jul 2, 2009 at 11:45 AM, Timo Sirainen wrote: > On Jul 2, 2009, at 2:27 PM, alexus wrote: > >> passdb: >> driver: vpopmail >> args: cache_key=%u vpopmail > > Remove "vpopmail" from args. v1.1 ignored it, v1.2 gives error messages > about unknown settings > > okay, after doing that I'm getting new errors Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Effective uid=89, gid=89, home=(none) Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir: data=~vpopmail/domains/alexus.org/X/Maildir/ Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): maildir++: root=~vpopmail/domains/alexus.org/X/Maildir, index=, control=, inbox=~vpopmail/domains/alexus.org/postmaster/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : Permission lookup failed from ~vpopmail/domains/alexus.org/X/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(xx...@alexus.org): Namespace : Using permissions from ~vpopmail/domains/alexus.org/X/Maildir: mode=0700 gid=-1 as soon as I roll it back to 1.1.16 and my old dovecot.conf, everything works no problem -- http://alexus.org/
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
On 7/2/2009 2:57 PM, Jose Luis Marin Perez wrote: > There is a way that considers Dovecot mails deleted (not purged) to calculate > the quota? I would vote (were it up to a vote) against such behavior... The message is not deleted - and therefore is still taking up physical storage space - until it is DELETED. -- Best regards, Charles Marcus I.T. Director Media Brokers International, Inc. 678.514.6200 x224 678.514.6299 fax
Re: [Dovecot] ManageSieve for 1.2.0?
Joan wrote: yes, Mercurial repository has a working status. Anybody to help on teh following ? : -> how managesieve works between the "sieve script per virtual user" and the main script in the storage directory. ManageSieve shouldn't be used to modify global scripts, only personal ones. With older versions of Sieve, once a user creates a personal script (and marks it active), the global script will no longer be called. You can work around this by 'include'ing the global script in each personal script. Here is my active script, which runs the global script followed by a personal one: require ["include"]; include :global "spamassassin-header-filter.sieve"; include :personal "mailing-lists.sieve"; In newer versions of Sieve (newer than v0.1.3 or v0.1.4, I think), you can use sieve_before or sieve_after to accomplish the same thing. Check the wiki: http://wiki.dovecot.org/LDA/Sieve/Dovecot If I were using sieve_before in my configuration, there would be no need to include the global script manually; it would always be executed before my active personal script.
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
Thanks for your answers. I told you that before migrating from Courier to Dovecot deleted mails (With flag T and not purged) were considered when calculating the quota. There is a way that considers Dovecot mails deleted (not purged) to calculate the quota? Thanks Jose Luis > Date: Thu, 2 Jul 2009 15:11:46 -0300 > From: edua...@kalinowski.com.br > To: dovecot@dovecot.org > Subject: Re: [Dovecot] Urgent problem with deleting emails and maildirsize > > On Qui, 02 Jul 2009, Jose Luis Marin Perez wrote: > > Thanks for your response Eduardo. > > > > Apologies to the list by the rush and lack of information when > > reporting a problem. > > > > One of the webmails is configured so that when delete some > > mail move to Trash directory, I have no problem here because I've > > configured Dovecot to ignore this folder to quota > > > > The other > > two webmails are not configured to use the Trash directory and when you > > delete some mail will be maintained in the INBOX but it shows shading > > and the server adds the flag T: > > > > 1244457746.11461.domain.com, S = 5413:2, ST > > > > So no updates maildirsize and quota does not change, this may > > result in the accounts quickly reach 100% usage. > > The quote does not change because the mail is not deleted. It's only > marked as deleted (T flag). Once the folder is expunged (that's how > IMAP call it; your webmail mail give a different name for this action) > all mails flagged as deleted are actually deleted and space is released. > > The easiest solution would be to use a Trash folder also for this > domain. Or, if you do not want that, you'll have to instruct your > users to expunge their folders when they want to claim space. I > believe there is also a plugin that should do automatic expunging, but > I don't known when it's triggered. > > > -- > Eduardo M KALINOWSKI > edua...@kalinowski.com.br > _ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
You may also consider using an inotify tool like inotifywait to build up a list of maildirs to be expunged, then run an imaptool on the clock every hour, with an extreme nice priority, to do a background expunge. Eduardo M KALINOWSKI wrote: On Qui, 02 Jul 2009, Jose Luis Marin Perez wrote: Thanks for your response Eduardo. Apologies to the list by the rush and lack of information when reporting a problem. One of the webmails is configured so that when delete some mail move to Trash directory, I have no problem here because I've configured Dovecot to ignore this folder to quota The other two webmails are not configured to use the Trash directory and when you delete some mail will be maintained in the INBOX but it shows shading and the server adds the flag T: 1244457746.11461.domain.com, S = 5413:2, ST So no updates maildirsize and quota does not change, this may result in the accounts quickly reach 100% usage. The quote does not change because the mail is not deleted. It's only marked as deleted (T flag). Once the folder is expunged (that's how IMAP call it; your webmail mail give a different name for this action) all mails flagged as deleted are actually deleted and space is released. The easiest solution would be to use a Trash folder also for this domain. Or, if you do not want that, you'll have to instruct your users to expunge their folders when they want to claim space. I believe there is also a plugin that should do automatic expunging, but I don't known when it's triggered. -- Love feeling your best ever, all day, every day? Click http://RadicalHealth.com/join for the easy way.
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
On Qui, 02 Jul 2009, Jose Luis Marin Perez wrote: Thanks for your response Eduardo. Apologies to the list by the rush and lack of information when reporting a problem. One of the webmails is configured so that when delete some mail move to Trash directory, I have no problem here because I've configured Dovecot to ignore this folder to quota The other two webmails are not configured to use the Trash directory and when you delete some mail will be maintained in the INBOX but it shows shading and the server adds the flag T: 1244457746.11461.domain.com, S = 5413:2, ST So no updates maildirsize and quota does not change, this may result in the accounts quickly reach 100% usage. The quote does not change because the mail is not deleted. It's only marked as deleted (T flag). Once the folder is expunged (that's how IMAP call it; your webmail mail give a different name for this action) all mails flagged as deleted are actually deleted and space is released. The easiest solution would be to use a Trash folder also for this domain. Or, if you do not want that, you'll have to instruct your users to expunge their folders when they want to claim space. I believe there is also a plugin that should do automatic expunging, but I don't known when it's triggered. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
Thanks for your response Eduardo. Apologies to the list by the rush and lack of information when reporting a problem. I have installed on a server as follows: Qmail Vpopmail Dovecot Horde With three mail domains using three different webmails. One of the webmails is configured so that when delete some mail move to Trash directory, I have no problem here because I've configured Dovecot to ignore this folder to quota The other two webmails are not configured to use the Trash directory and when you delete some mail will be maintained in the INBOX but it shows shading and the server adds the flag T: 1244457746.11461.domain.com, S = 5413:2, ST So no updates maildirsize and quota does not change, this may result in the accounts quickly reach 100% usage. Dovecot configuration # 1.1.16: /usr/local/etc/dovecot.conf # OS: Linux 2.6.9-78.0.22.ELsmp i686 CentOS release 4.7 (Final) log_path: /var/log/dovecot.log protocols: imap listen: *:10143 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 89 last_valid_uid: 89 first_valid_gid: 89 last_valid_gid: 89 mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mail_plugins: quota namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: passdb: driver: checkpassword args: /usr/vpopmail/bin/vchkpw /usr/local/bin/vchkpw-wrapper.sh userdb: driver: prefetch args: uid=89 gid=89 home=/usr/vpopmail/domains/%d/%u plugin: quota: maildir quota_rule: ?:storage=0 quota_rule2: Trash:ignore quota_rule3: Papelera:ignore Thanks Jose Luis > Date: Thu, 2 Jul 2009 14:14:10 -0300 > From: edua...@kalinowski.com.br > To: dovecot@dovecot.org > Subject: Re: [Dovecot] Urgent problem with deleting emails and maildirsize > > On Qui, 02 Jul 2009, Jose Luis Marin Perez wrote: > > Dears Sirs, > > > > I hope they can help me with this problem since it is urgent. > > > > I've completed the migration from Courier to Dovecot that has been > > running correctly, the only problem is that maildirsize file is not > > updated when you delete the emails, resulting in accounts that reach to > > 100% faster, so I have to manually delete this file. > > > > Through Dovecot can be configured to automatically update when > > maildirsize delete emails? > > Posting the same request twice in two hours in not going to get an > answer faster. Especially if you do not add the missing information in > the first post to the second one. > > Please show us your dovecot -n output. > > That will answer the question, but anyway: do you have the quota > plugin configured? > > > -- > Eduardo M KALINOWSKI > edua...@kalinowski.com.br > _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
Re: [Dovecot] Urgent problem with deleting emails and maildirsize
On Qui, 02 Jul 2009, Jose Luis Marin Perez wrote: Dears Sirs, I hope they can help me with this problem since it is urgent. I've completed the migration from Courier to Dovecot that has been running correctly, the only problem is that maildirsize file is not updated when you delete the emails, resulting in accounts that reach to 100% faster, so I have to manually delete this file. Through Dovecot can be configured to automatically update when maildirsize delete emails? Posting the same request twice in two hours in not going to get an answer faster. Especially if you do not add the missing information in the first post to the second one. Please show us your dovecot -n output. That will answer the question, but anyway: do you have the quota plugin configured? -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
[Dovecot] Urgent problem with deleting emails and maildirsize
Dears Sirs, I hope they can help me with this problem since it is urgent. I've completed the migration from Courier to Dovecot that has been running correctly, the only problem is that maildirsize file is not updated when you delete the emails, resulting in accounts that reach to 100% faster, so I have to manually delete this file. Through Dovecot can be configured to automatically update when maildirsize delete emails? Thanks Jose Luis _ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx
Re: [Dovecot] ManageSieve for 1.2.0?
> I'm using the Mercurial repository, see > http://wiki.dovecot.org/ManageSieve#Mercurial I guess this is not an option for pkgsrc.
Re: [Dovecot] mbox format and UIDVALIDITY
On Jul 1, 2009, at 5:48 PM, Axel Luttgens wrote: * OK [UIDVALIDITY 1] UIDs valid Hmm. Wonder when that got broken. It used to work, but yes, I can reproduce it with v1.2 too. I'll take a look at it in a few days.
Re: [Dovecot] Problem no update maildirsize
Dear Sirs, Doing the analysis I have seen that when a new mail arrives updates maildirsize but when delete any email no update maildirsize. I need to add some configuration dovecot.conf? Thanks > From: jolumape...@hotmail.com > To: dovecot@dovecot.org > Date: Thu, 2 Jul 2009 09:50:07 -0500 > Subject: [Dovecot] Problem no update maildirsize > > > Dears Sirs, > > I've noticed that since the Courier to Dovecot migration have had few > problems with the %usage of email accounts as they do not reflect the real > use, to fix this I have to manually delete the file maildirsize and run the > command vuserinfo u...@domain.com, depending on your experience may be the > cause of this problem? > > thanks > > Jose Luis > _ > Discover the new Windows Vista > http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE _ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
Re: [Dovecot] v1.2.0 released
On Jul 2, 2009, at 2:27 PM, alexus wrote: passdb: driver: vpopmail args: cache_key=%u vpopmail Remove "vpopmail" from args. v1.1 ignored it, v1.2 gives error messages about unknown settings
[Dovecot] Problem no update maildirsize
Dears Sirs, I've noticed that since the Courier to Dovecot migration have had few problems with the %usage of email accounts as they do not reflect the real use, to fix this I have to manually delete the file maildirsize and run the command vuserinfo u...@domain.com, depending on your experience may be the cause of this problem? thanks Jose Luis _ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
Re: [Dovecot] mbox format and UIDVALIDITY
Going further with my question... ;-)
It stemmed from that consideration (and related ones) of RFC3501:
2.3.1.1.Unique Identifier (UID) Message Attribute
A 32-bit value assigned to each message, which when used with the
unique identifier validity value (see below) forms a 64-bit value
that MUST NOT refer to any other message in the mailbox or any
subsequent mailbox with the same name forever. [...]
Assuming the behavior shown by Dovecot isn't related to a bad config
of mine (see my previous post) but really indicates a slight
oversight, I quickly and dirtily added some lines in the code of
function mbox_mailbox_create().
The resulting binary seems to behave correctly (this is with
dovecot-1.2.0).
But I must sure be overlooking something, or? Not only because I
perhaps dangerously make use of some functions beyond what they are
intended for, but also wrt the overall logics of Dovecot.
Anyway, here's my attempt:
/* create the mailbox file */
fd = open(path, O_RDWR | O_CREAT | O_EXCL, 0660);
if (fd != -1) {
/* A shameless adaptation of mbox_write_pseudo() from:
src/lib-storage/index/mbox/mbox-storage.c */
#include "str.h"
#include "mbox-from.h"
#include "message-date.h"
#include "write-full.h"
#include "hostpid.h"
string_t *str;
/* Let's prepare the pseudo message, without trying to be
clever wrt the
uidvalidity value: just make use of the current time. */
str = t_str_new(1024);
str_printfa(str,
"%s"
"Date: %s\n"
"From: Mail System Internal Data \n"
"Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL
DATA"
"\nMessage-ID: <%...@%s>\n"
"X-IMAP: %u %010u\n"
"Status: RO\n"
"\n"
"This text is part of the internal format of your mail
folder, and is not\n"
"a real message. It is created automatically by the mail
system software.\n"
"If deleted, important folder data will be lost, and it
will be re-created\n"
"with the data reset to initial values.\n"
"\n",
mbox_from_create("MAILER_DAEMON", ioloop_time),
message_date_create(ioloop_time),
my_hostname,
dec2str(ioloop_time), my_hostname,
(uint32_t)ioloop_time, 0
);
/* Write the message to the mailbox file; in case of problem,
just try
to revert to the original behavior by truncating the file
(i.e. no
pseudo message at all). */
if (pwrite_full(fd, str_data(str), str_len(str), 0) < 0) {
i_info("mbox_mailbox_create(): failed to write pseudo
message to %s(%d)", path, errno);
/* Should a failure here be considered fatal? */
if (ftruncate(fd, 0) < 0)
i_info("mbox_mailbox_create(): failed to truncate
file %s(%d)", path, errno);
}
/* OK, it should now be safe to rely on Dovecot's ability to
build the
indexes and to correctly recognize the pseudo message. */
(void)close(fd);
return 0;
}
In the hope this may prove useful as a skeleton for a better code,
should a better handling of the UIDVALIDITY with the mbox format be
considered useful,
Axel
Re: [Dovecot] about Update Road and no IDLE in CAPABILITY
Timo Sirainen wrote: On Jul 2, 2009, at 1:18 PM, kfx wrote: My second question is how to have the IDLE mode to appear in the server's CAPABILITY announce (without touching imap_capability in the conf ?) .. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] My Message Are you sure it's not working? The capabilities listed above are the pre-login capabilities. If client issues CAPABILITY command or after client logs in, the full capability list is sent which contains IDLE. Oh ok it is indeed working ! # telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] MyMessage WILLITBLEND? CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA STARTTLS AUTH=PLAIN WILLITBLEND? OK Capability completed. So if now some sysadmin can tell how do they manage to update their dovecot (from source) installation, it would be great ! Thanks again, kfx
Re: [Dovecot] ManageSieve for 1.2.0?
yes, Mercurial repository has a working status. Anybody to help on teh following ? : -> how managesieve works between the "sieve script per virtual user" and the main script in the storage directory. thanks jm Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 2 Jul 2009, Edgar Fuß wrote: Date: Thu, 2 Jul 2009 12:53:00 +0200 From: Edgar Fuß To: dovecot@dovecot.org Subject: Re: [Dovecot] ManageSieve for 1.2.0? managesieve works fine for me on 1.2.0 How do you make that work? $ tail +41 dovecot-1.2.0/src/imap-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS < AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be larger than authentication timeout #endif $ tail +47 dovecot-1.2-managesieve-0.11.5/src/managesieve-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS >= AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be smaller than authentication timeout #endif I'm using the Mercurial repository, see http://wiki.dovecot.org/ManageSieve#Mercurial - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSkynMnWSIuGy1ktrAQI98gf/bM1/dBoNPOzQb1Z5ec2Yf0YWEQr4s/FT cO1cO3d0IPtHQf6sfmTHKoa7MqrMRKigX0hv4ykgA2dcbJ5aRLt00+PRpFd/lT1V EGClgrBJZYtFDnN+GnEVd/y/yGIluiW6h/t75L4s9W3VtvqZgkL8rI5BtVvggw3b 6sWo2N+ODmC+qit7GFhfTfRl69UbREXScM1Zj5cAm/9Y1yn1yb8fqEL5GdMpnL/R UUc9qTwTR/SWoqKy8f09a8Cdli774lof6FmtnInfbKzS5+6JUrbC+qKZ1Nydl0UU 41SY0vdARbiUHIEYAJE29rCO8ZoWK0rMxo6YMFL9e8tUX1drmmjPbw== =FIo7 -END PGP SIGNATURE-
Re: [Dovecot] dovecot start up messages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 2 Jul 2009, Xueron Nee wrote: IModule loaded: /home/mail/lib/dovecot/imap/lib02_imap_acl_plugin.so Disable mail_debug, I'd say. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSkyoInWSIuGy1ktrAQKWFAf/d2YzW52phvYO653/xV4XM8SmuHmqUFQ1 GryZlLfyjYaDRVctKzXi6ng7u0UIzAdIhl5IMrzW+sYbvtJD+CDbxcwS3kHh0TB3 vX4I0hEmpuULcZM0u6pzzAf9J64LvnLSEzyxqzucM0mrXmBFyd5N3PJamIcfQDrR GJmcbZMPB/RJfrBiqjwFk7rco9zDq5hUqnrHwY0w4IKNLxB6MTGKkv5Oxhplxhd+ 6wwcrFALhJUlDR0+d2j6AniqFJ67oVkoD/U1DTFj+jQiqsM+9a2AeiiSZuiK46Nd Sv0n5gvJ19TcMLyE50QWNwvv1lT2tBVjF8hkLYv6yYTDebr2pzDuMg== =Wj2U -END PGP SIGNATURE-
Re: [Dovecot] v1.2.0 released
On Thu, Jul 2, 2009 at 12:45 AM, Timo Sirainen wrote: > On Jul 2, 2009, at 6:40 AM, alexus wrote: > >> Jul 2 00:36:09 mx1 dovecot: Dovecot v1.2.0 starting up >> Jul 2 00:36:09 mx1 dovecot: auth(default): Fatal: passdb vpopmail: >> Unknown setting: vpopmail > > dovecot -n output? > > -bash-3.2# ./src/master/dovecot -n # 1.2.0: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p1 amd64 protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/etc/ssl/certs/dovecot.pem ssl_key_file: /usr/local/etc/ssl/private/dovecot.pem disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login first_valid_uid: 89 last_valid_uid: 89 mail_uid: 89 mail_gid: 89 mail_location: maildir:~vpopmail/domains/%d/%n/Maildir/ mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 auth default: mechanisms: plain login digest-md5 cram-md5 cache_size: 1024 debug: yes debug_passwords: yes passdb: driver: vpopmail args: cache_key=%u vpopmail -bash-3.2# -- http://alexus.org/
Re: [Dovecot] ManageSieve for 1.2.0?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 2 Jul 2009, Edgar Fuß wrote: Date: Thu, 2 Jul 2009 12:53:00 +0200 From: Edgar Fuß To: dovecot@dovecot.org Subject: Re: [Dovecot] ManageSieve for 1.2.0? managesieve works fine for me on 1.2.0 How do you make that work? $ tail +41 dovecot-1.2.0/src/imap-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS < AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be larger than authentication timeout #endif $ tail +47 dovecot-1.2-managesieve-0.11.5/src/managesieve-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS >= AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be smaller than authentication timeout #endif I'm using the Mercurial repository, see http://wiki.dovecot.org/ManageSieve#Mercurial - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSkynMnWSIuGy1ktrAQI98gf/bM1/dBoNPOzQb1Z5ec2Yf0YWEQr4s/FT cO1cO3d0IPtHQf6sfmTHKoa7MqrMRKigX0hv4ykgA2dcbJ5aRLt00+PRpFd/lT1V EGClgrBJZYtFDnN+GnEVd/y/yGIluiW6h/t75L4s9W3VtvqZgkL8rI5BtVvggw3b 6sWo2N+ODmC+qit7GFhfTfRl69UbREXScM1Zj5cAm/9Y1yn1yb8fqEL5GdMpnL/R UUc9qTwTR/SWoqKy8f09a8Cdli774lof6FmtnInfbKzS5+6JUrbC+qKZ1Nydl0UU 41SY0vdARbiUHIEYAJE29rCO8ZoWK0rMxo6YMFL9e8tUX1drmmjPbw== =FIo7 -END PGP SIGNATURE-
[Dovecot] dovecot start up messages
Hi, Why dovecot prints these messages when start up? And how to suppress it? # /home/mail/init/dovecot.init restart Stopping Dovecot: [ OK ] ILoading modules from directory: /home/mail/lib/dovecot/imap IModule loaded: /home/mail/lib/dovecot/imap/lib01_acl_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib02_imap_acl_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib11_imap_quota_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_autocreate_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_convert_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_expire_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_fts_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_mail_log_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_virtual_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib21_fts_squat_plugin.so IEffective uid=99, gid=99, home=/tmp IQuota root: name=user backend=dict args=:proxy::quota_dict Startting Dovecot: [ OK ] Thanks :) -- Xueron Nee http://www.xueron.com
Re: [Dovecot] Directory Layout Performance
On 7/2/2009, to...@tuxteam.de (to...@tuxteam.de) wrote: >> If you based your decision of what filesystem to use on whether or not >> there have ever been any serious problems encountered with it, you >> wouldn't have a computer. > No. I base my assessment on other people's experiences. I said, '... any serious problems encountered with it'... by *anyone*, not just you... so this includes other peoples experiences. > One of the real downsides or Reiser at the moment seems to be that it > is more prone to silent corruption (triggered by hardware problems). All filesystems are prone to this problem... hardware problems can cause all kinds of nasty things to happen, many of them 'silently'. I am *not* saying reiserfs is perfect - no fs is... I'm just saying that there are *plenty* of people who have had just as serious problems with ext3, xfs, and every other filesystem out there. The fact is, reiserfs performance is awesome for mail servers (especially IMAP servers), and has been rock solid for me for as long as I've been using it... > I don't have the time now to provide references, but if interested, > I'll dig it up (maybe it's time to take this off-list anyway :) Not necessary, I'm fully aware of them. All that said, I'll probably be migrating my next systems to either ext4 or brtfs, depending on *when*... I wish zfs was gpl so it could make it into the linux kernel. Heck, I've been considering trying out FreeBSD for that one reason... But you're right, this is way OT now, and I don't have time to carry it on privately... good luck (to you and everyone) with whatever fs you choose... -- Best regards, Charles
Re: [Dovecot] about Update Road and no IDLE in CAPABILITY
On Jul 2, 2009, at 1:18 PM, kfx wrote: My second question is how to have the IDLE mode to appear in the server's CAPABILITY announce (without touching imap_capability in the conf ?) .. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] My Message Are you sure it's not working? The capabilities listed above are the pre-login capabilities. If client issues CAPABILITY command or after client logs in, the full capability list is sent which contains IDLE.
[Dovecot] about Update Road and no IDLE in CAPABILITY
Hi list, I'm in the path of moving from courier-imap to dovecot and testing it since 1.2-rc3. So far it is very promising. Thank you for your amazing work. So my first question is: what is the recommended update road ? For now, I first "managesieve patch"/compile the source, go on to the old source folder and do a "make uninstall", switch back to the new source folder and do the "make install". As I am using dovecot-sieve and managesieve, the update is a little bit tricky. My second question is how to have the IDLE mode to appear in the server's CAPABILITY announce (without touching imap_capability in the conf ?) I think the IDLE mode is working because when I send me a mail from the server directly in command line like: " echo test | mail -s test m...@address.com" The mail immediately pop-up in my thunderbird from my workstation. # !tel telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] My Message --- No IDLE. Details: - Centos 5.3 x86_64 (Selinux in permissive mode) - /proc/sys/fs/inotify/ exist - # rpm -qa | grep gamin gamin-0.1.7-8.el5 gamin-0.1.7-8.el5 gamin-devel-0.1.7-8.el5 gamin-devel-0.1.7-8.el5 - Dovecote 1.2.0 Compilation: $ ./configure --with-ldap=yes --with-notify=inotify Install prefix . : /usr/local File offsets ... : 64bit I/O polling : epoll I/O notifys : inotify SSL : yes (OpenSSL) GSSAPI . : no passdbs : passwd passwd-file shadow checkpassword ldap : -pam -bsdauth -sia -sql -vpopmail userdbs : static prefetch passwd passwd-file checkpassword ldap nss : -sql -vpopmail SQL drivers : : -pgsql -mysql -sqlite - # dovecot --version 1.2.0 - # dovecot -n # 1.2.0: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-128.1.10.el5 x86_64 CentOS release 5.3 (Final) ext3 log_path: /var/log/dovecot-error.log info_log_path: /var/log/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve ssl_ca_file: /etc/pki/CA/chaine.crt ssl_cert_file: /etc/pki/dovecot/certs/server.pem ssl_key_file: /etc/pki/dovecot/private/server.key login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting: My Message verbose_proctitle: yes mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/vmail/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota expire mail_plugins(imap): quota imap_quota expire mail_plugins(pop3): quota expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): auth default: username_format: %Ln verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap-userdb.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:User quota quota_rule: *:storage=10GB quota_rule2: Trash:storage=10%% expire: Trash 1 Trash/* 1 expire_dict: proxy::expire sieve_dir: /var/sieve-upload/ sieve: /var/sieve-scripts/%u.sieve dict: expire: db:/var/lib/dovecot/expire.db Thank you, kfx
Re: [Dovecot] ManageSieve for 1.2.0?
On 7/2/2009, Joan (j...@grosjo.net) wrote: > managesieve works fine for me on 1.2.0 > > However > -> it would be however a nice idea to include the patch of ManageSieve > directly into the branch 1.2 of dovecot. This is getting to be an FAQ (asked and answered in the archives)... The patch will no longer be needed for 2.0, but Sieve/Managesieve support will still be a separate package... -- Best regards, Charles
Re: [Dovecot] Directory Layout Performance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jul 02, 2009 at 06:01:01AM -0400, Charles Marcus wrote: > On 7/2/2009, to...@tuxteam.de (to...@tuxteam.de) wrote: [...] > > Hm. I think Reiser is [...] > Lets please stop with the FUD. Oops. Sorry. I didn't want to step on anyone's toes. > Yes, Reiserfs had a few bugs early on... but I have been running 3 > production servers on it for 4 years [...] YMMV. As I said, I have a couple of big (albeit not heavily used) FS on Reiser and am quite happy up to now. > If you based your decision of what filesystem to use on whether or not > there have ever been any serious problems encountered with it, you > wouldn't have a computer. No. I base my assessment on other people's experiences. One of the real downsides or Reiser at the moment seems to be that it is more prone to silent corruption (triggered by hardware problems). I don't have the time now to provide references, but if interested, I'll dig it up (maybe it's time to take this off-list anyway :) Regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKTJXiBcgs9XrR2kYRAilGAJ4uRlV5jjEw8mFCuvsVzacF28UWzwCfUX5B hTuJyygkx8BY2C0ks1gmS7Y= =X8xH -END PGP SIGNATURE-
Re: [Dovecot] ManageSieve for 1.2.0?
> managesieve works fine for me on 1.2.0 How do you make that work? $ tail +41 dovecot-1.2.0/src/imap-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS < AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be larger than authentication timeout #endif $ tail +47 dovecot-1.2-managesieve-0.11.5/src/managesieve-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS >= AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be smaller than authentication timeout #endif Am I missing something?
Re: [Dovecot] ManageSieve for 1.2.0?
managesieve works fine for me on 1.2.0 However -> it would be however a nice idea to include the patch of ManageSieve directly into the branch 1.2 of dovecot. -> I am still wondering how managesieve works between the "sieve script per virtual user" and the main script in the storage directory. Edgar Fuß wrote: Sorry to ask again, but what's the status of the ManageSieve patch for 1.2? The rc5 version doesn't work and I would like to get 1.2 into pkgsrc.
Re: [Dovecot] v1.2.0 released
> http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz > http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig > > As promised. No changes since v1.2.rc8 (except packaged in OS X, since > CentOS 5 autotools didn't add support for configure --docdir). download page suggest using new dovecot sieve plugin. It's version 0.1.6 so I wonder how much stable and feature complete it is comparing to the old sieve plugin? Which one is better and why? Regards, Michal Hlavinka
Re: [Dovecot] keeping 2 dovcots in sync?
On 2009-07-02 11:39:22 +0200, joa...@verona.se wrote: > > I would like to have one master dovecot instance that gets email, and a > slave dovecot on my laptop. > > I use maildir, and I was thinking of doing this with unison, but I > suppose dovecots indexes would go out of sync whenever I used unison. > > There seems to be a number of imap folder synchronizers, but I have > heard they are troublesome. isync offlineimap darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] Directory Layout Performance
On 7/2/2009, to...@tuxteam.de (to...@tuxteam.de) wrote: > [...] Yeah, I know Reiser should have better performance with [...] > > Hm. I think Reiser is for those "make sure you know what aou're doing". > I have myself some partitions on Reiser, but I'm not so sure I would > base critical stuff on it. Lets please stop with the FUD. Yes, Reiserfs had a few bugs early on... but I have been running 3 production servers on it for 4 years, with zero problems (even went through 3 unclean shutdowns)... yes, there have been problems, but, the same can be said of every single filesystem out there. If you based your decision of what filesystem to use on whether or not there have ever been any serious problems encountered with it, you wouldn't have a computer. -- Best regards, Charles
[Dovecot] keeping 2 dovcots in sync?
I would like to have one master dovecot instance that gets email, and a slave dovecot on my laptop. I use maildir, and I was thinking of doing this with unison, but I suppose dovecots indexes would go out of sync whenever I used unison. There seems to be a number of imap folder synchronizers, but I have heard they are troublesome. Any hints? -- Joakim Verona
[Dovecot] ManageSieve for 1.2.0?
Sorry to ask again, but what's the status of the ManageSieve patch for 1.2? The rc5 version doesn't work and I would like to get 1.2 into pkgsrc.
Re: [Dovecot] dovecot lda and postfix
Le 1 juil. 09 à 18:05, I wrote: [...] Could you augment your description with the output of postconf -n dovecot -n as well as all the log entries written by both Postfix and Dovecot when you send your email to r...@domain.com, please without obfuscating the data: its already sufficiently complicated... ;-) [...] I forgot an essential piece of information: postconf mail_version Thanks, Axel
Re: [Dovecot] Dovecot / Sieve
Ok, I made it happen. Now, 2 questions: * I have a generic script in the Virtual Mailboxes directory (to handle spam, virus, etc...). How the general script and the one defined by the user will compete/interact ? * How to convert Thunderbird filters to Sieve filters ? Thanks JM Stephan Bosch wrote: Joan wrote: Thanks What does the "patch" stand for ? I mean, do I need to apply the patch each time I update dovecot (from mercurial) ? The patch is needed to let Dovecot know of the existence of the ManageSieve protocol. Read the wiki for more info on this patch and how to apply it for Mercurial repositories: http://wiki.dovecot.org/ManageSieve Why not merging the 2 branches (dovecot and sieve) ? Everyone using Dovecot needs a Seive implementation I beleive. With the advent of Dovecot v2.0, the patch is gone. However, the Sieve/ManageSieve support will remain a separate package. Regards, Stephan.
