Re: [Dovecot] 1.1.5 abort with mal-formed address in header
On Friday 24 of October 2008, Timo Sirainen wrote: On Oct 24, 2008, at 1:49 AM, Richard Platel wrote: To:([EMAIL PROTECTED] (Starting with a comment, with no closing ')' ) causes dovecot 1.1.5 to panic and abort. This is similar to the problem fixed by: http://hg.dovecot.org/dovecot-1.1/rev/04fdaa2f831e This patch seems to resolve the problem: Thanks, committed. I guess it's time for 1.1.6 release.. I'll leave it for tomorrow. Ping? :-) -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/
Re: [Dovecot] read only FS access
Asheesh Laroia a écrit : On Tue, 28 Oct 2008, Mathieu Kretchner wrote: Hello, I would like to know if it's possible to subscribe to a folder that is on a read only File System ? We have a snapshot mechanism that create a .snapshot directly in the user folder. This is done by our NAS and we would like to give an access to this backup to our users. If you tell Dovecot to store the cache and indexes elsewhere, that should work fine. I haven't tried it, though. -- Asheesh. My problem is that dovecot complain when I subscribe to the folder in read only I've found this (after my e-mail to this list, forgive me :) ) http://markmail.org/message/l7rybsx27ofq57cp#query:dovecot%20read%20only+page:3+mid:c2ut2u4bajyx22fh+state:results But could someone tell me if it's working now ? Because it's a little bit old ! begin:vcard fn:Mathieu Kretchner n:Kretchner;Mathieu org:INRIA;Syslog adr;dom:;;2004 route des lucioles - BP93;Sophia Antipolis;;06902 CEDEX email;internet:[EMAIL PROTECTED] tel;work:04 92 38 76 67 x-mozilla-html:FALSE version:2.1 end:vcard
Re: [Dovecot] Dovecot and quota enforcement - only reporting?
On 10/28/2008, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: Wow, that clearly shows I'm not really sure what I'm doing, as I don't really understand the question. I'm running Postfix, with Dovecot on top. Uses check mail via Outlook/IMAP, or Web/Squirrelmail. Postfix is an MTA (Mail Transfer Agent). It has its own built in 'Delivery Agents' - LDA (Local Delivery Agent) and VDA (Virtual Delivery Agent). A barebones postfix install will use one of these. Dovecot is a POP/IMAP server - it allows clients to access existing messages located on a filesystem somewhere. 'Deliver' is the act of the final placement of an email message to the final destination filesystem. It sounds like you have some reading to do... Here is the dovecot wiki page on dopvecots 'Deliver' program: http://wiki.dovecot.org/MDA -- Best regards, Charles
[Dovecot] antispam plugin claims antispam signature not found
Hi, I am trying to setup the antispam plugin using the direct dspam backend. I have set antispam_signature = X-DSPAM-Signature in dovecot.conf and in all mails I have signature lines like X-DSPAM-Signature: 1,49084a24139132188715614 but still, if I try to move a mail into the spam folder, i get the IMAP error message antispam signature not found. I thought it might have to do with permissions and made sure that the user running dovecot is able to execute the dspam binary. I also tried to enable debug logging to syslog (via the .config file in the make process) but I do not see any debug messages showing up; where should these go? to the mail facility? Perhaps somebody who has a working setup can shed some light on this? Yours, JC
[Dovecot] Dovecot failing to save email
Hi, Just wondered if anyone could help me with an issue im having with a new email server im setting up. These are the errors i have been getting: deliver([EMAIL PROTECTED]): Oct 29 13:32:13 Info: msgid= [EMAIL PROTECTED]: save failed to INBOX: Quota exceeded deliver([EMAIL PROTECTED]): Oct 29 13:32:13 Info: msgid= [EMAIL PROTECTED]: Rejected: Quota exceeded Dovecot Version - 1.0.15 Using MySQL # 1.0.15: /etc/dovecot.conf ssl_ca_file: /etc/pki/tls/certs/ca-bundle.crt login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 5000 last_valid_uid: 5000 mail_access_groups: mail mail_location: maildir:/var/vmail/%d/%u maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login user: nobody passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: #quota: maildir:storage=100:messages=1000 acl: vfile:/etc/dovecot/acls trash: /etc/dovecot/trash.conf Kind Regards Tony
[Dovecot] Authentication Error Message formats
I have been using UW's IMAP server and I am converting to Dovecot for Maildir support. When a user fails authentication, or a user does not exist, it appears that the same message is used for these events. Is there a way to indicate that the user does not exist (Invalid user), and authentication Failure (Failed Password)? Clearly these two failures indicate a different error in the system. One that some forgot their password, the other indicates a dictionary attack. -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*.
Re: [Dovecot] patch: list shared namespace
On 28.10.2008, Bernhard Herzog wrote: I've been working on a patch for dovecot 1.2 from the Kolab branch (http://hg.intevation.org/kolab/dovecot-1.2_kolab-branch/) that implements listing of shared namespaces. I've got something that works in some basic way but is still missing some pieces. See the attached patch, which also contains some installation and configuration notes. The patch is now available in the kolab branch hg repository: http://hg.intevation.org/kolab/dovecot-1.2_kolab-branch/rev/c2396923cd2f Bernhard -- Bernhard Herzog | ++49-541-335 08 30 | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Quick question regarding autocreate plugin
just a quick question: if I want to use the autocreate plugin with 1.1.5, I have to compile it by hand, right? How do I do that? Can I adapt a Makefile from another plugin? I meanwhile solved this and updated the WIKI to explain how the plugin can be compiled with the 1.1.x source tree. cf. http://wiki.dovecot.org/Plugins/Autocreate Regards, Jakob
Re: [Dovecot] dovecot expire doesn't work (?)
e-frog wrote:
Anybody has this working?
Yes.
Great! Then all hope is not lost :)
plugin {
expire = spamassassin/SPAM 1
expire_dict = proxy::expire
}
For me it works by using '.' as hierarchy separator. So in your case
expire = spamassassin.SPAM 1 should work. This could be different when
using namespaces, which I don't.
I don't use namespaces either, and I've changed my dovecot.conf to use
the '.' as separator.
That is, if I want to expire the emails under the spamassassin/SPAM
directory, after 1 day. Is this correct? I'm asking this because with
this setup, the expire-tool does nothing... nothing in the logs either.
Try and set mail_debug=yes. It should log more.
Done.
When I ran `dovecot --exec-mail ext
/usr/local/libexec/dovecot/expire-tool --test', it told me that:
Info: leva/spamassassin.SPAM: stop, expire time in future: 1225290174
Since I've run it without the --test option, it outputs nothing anymore,
and nothing in the logs.
What else did you configure? Or is there some other thing I should do?
Thanks!
Daniel
--
LEVAI Daniel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
Re: [Dovecot] Dovecot and quota enforcement - only reporting?
Still no answer to my original question of what exactly updates maildirsize? Is that also the dovecot LDA? At 06:14 AM 10/29/2008, Charles Marcus wrote: On 10/28/2008, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: I'm running Postfix, with Dovecot on top. Uses check mail via Outlook/IMAP, or Web/Squirrelmail. Postfix is an MTA (Mail Transfer Agent). It has its own built in 'Delivery Agents' - LDA (Local Delivery Agent) and VDA (Virtual Delivery Agent). A barebones postfix install will use one of these. I'm using virtual delivery in postfix (mysql users). Postfix is running the default delivery agent: mailbox_command = So the only way to get quota enforcing with Dovecot is to have Postfix use the dovecot LDA? And from the wiki it indicates: dovecot_destination_recipient_limit = 1 virtual_mailbox_domains = your.domain.here virtual_transport = dovecot but I'm currently running multiple domains. How does virtual_mailbox_domains configure to handle that? Rick
Re: [Dovecot] dovecot expire doesn't work (?)
On Wed, 2008-10-29 at 15:25 +0100, LÉVAI Dániel wrote: That is, if I want to expire the emails under the spamassassin/SPAM directory, after 1 day. Is this correct? I'm asking this because with this setup, the expire-tool does nothing... nothing in the logs either. Try and set mail_debug=yes. It should log more. Done. When I ran `dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test', it told me that: Info: leva/spamassassin.SPAM: stop, expire time in future: 1225290174 Sounds like it's working. It just wasn't time yet to expunge the oldest mail from there: % unix2date.sh -u 1225290174 Wed Oct 29 14:22:54 UTC 2008 Running it again now would show that it's going to expunge it? I suppose I should change the code to show the timestamp in user-understandable form. :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Cannot use userdb to update Maildir
e-frog wrote: more /home/dovecot.passwd health:$1$MCtvt/Tz$FmKqU/cbWlBhKnhc5W.Ko.:1152:1152:/home/health:userdb_mail=mai ldir:~/Maildir I guess you need two ':' between 1152 and /home/health and userdb_mail=maildir:~/Maildir So the line should look like this: health:$1$MCtvt/Tz$FmKqU/cbWlBhKnhc5W.Ko.:1152:1152::/home/health::userdb_mail=maildir:~/Maildir Thank you to everyone that responded to this posting. This issue is now resolved. -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*.
Re: [Dovecot] Authentication Error Message formats
On 10/29/2008, Albert E. Whale ([EMAIL PROTECTED]) wrote: When a user fails authentication, or a user does not exist, it appears that the same message is used for these events. When asking for help, it is always a good idea to provide some basic info... in this case, sample log entries from failed events, and output of dovecot -n? -- Best regards, Charles
Re: [Dovecot] Authentication Error Message formats
On Wed, 2008-10-29 at 09:49 -0400, Albert E. Whale wrote: I have been using UW's IMAP server and I am converting to Dovecot for Maildir support. When a user fails authentication, or a user does not exist, it appears that the same message is used for these events. Is there a way to indicate that the user does not exist (Invalid user), and authentication Failure (Failed Password)? To user: no. In logs: yes, with auth_verbose=yes. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot failing to save email
on 10-29-2008 6:41 AM [EMAIL PROTECTED] spake the following: Hi, Just wondered if anyone could help me with an issue im having with a new email server im setting up. These are the errors i have been getting: deliver([EMAIL PROTECTED]): Oct 29 13:32:13 Info: msgid= [EMAIL PROTECTED]: save failed to INBOX: Quota exceeded deliver([EMAIL PROTECTED]): Oct 29 13:32:13 Info: msgid= [EMAIL PROTECTED]: Rejected: Quota exceeded Dovecot Version - 1.0.15 Using MySQL # 1.0.15: /etc/dovecot.conf ssl_ca_file: /etc/pki/tls/certs/ca-bundle.crt login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 5000 last_valid_uid: 5000 mail_access_groups: mail mail_location: maildir:/var/vmail/%d/%u maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login user: nobody passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: #quota: maildir:storage=100:messages=1000 acl: vfile:/etc/dovecot/acls trash: /etc/dovecot/trash.conf Kind Regards Tony You have set a quota, and those messages make the user go over that quota. Isn't that what it is supposed to do? -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] read only FS access
On Wed, 2008-10-29 at 10:10 +0100, Mathieu Kretchner wrote: My problem is that dovecot complain when I subscribe to the folder in read only What does it complain? signature.asc Description: This is a digitally signed message part
[Dovecot] POP3 auth failures
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Have a strange problem with just POP3 users. Their email clients will fail every so often with the following: Logging into POP Server, PASS [09:16:29 PM] There has been an error transferring your mail. I said PASS s! Don't tell anyone. and then the POP server ([EMAIL PROTECTED]) said: ERR Authentication failed. This example is from a Eudora client, but same things happen with Thunderbird and Outlook. Here are logs. This user has his client checking every 10 minutes. First log entry here is last good one before it fails: Oct 28 21:06:27 goku dovecot: [ID 107833 mail.info] auth(default): client in: AUTH 1 PLAIN service=pop3secured lip=129.82.224.16 rip=129.82.224.206 lport=110 rport=3716 resp=hiddenOct 28 21:06:27 goku dovecot: [ID 107833 mail.info] auth-worker(default): pam(us er,129.82.224.206): lookup service=dovecotOct 28 21:06:27 goku dovecot: [ID 107833 mail.info] auth-worker(default): pam(us er,129.82.224.206): #1/1 style=1 msg=Password:Oct 28 21:06:27 goku dovecot: [ID 107833 mail.info] auth(default): client out: O K 1 user=user Oct 28 21:06:27 goku dovecot: [ID 107833 mail.info] auth(default): master in: REQUEST 387983 28091 Oct 28 21:06:27 goku dovecot: [ID 107833 mail.info] auth-worker(default): passwd(user,129.82.224.206): lookup Oct 28 21:06:27 goku dovecot: [ID 107833 mail.info] auth(default): master out: USER 387983 usersystem_user=useruid=12550 gid=32 home=/to p/admin/ENS/people/user/home Oct 28 21:06:27 goku dovecot: [ID 107833 mail.info] pop3-login: Login: user=use r, method=PLAIN, rip=129.82.224.206, lip=129.82.224.16, TLS Oct 28 21:06:27 goku dovecot: [ID 107833 mail.info] POP3(user): Effective uid=12 550, gid=32 Everything went fine here, then the next auth attempt fails: Oct 28 21:16:27 goku dovecot: [ID 107833 mail.info] auth(default): client in: AUTH 1 PLAIN service=pop3secured lip=129.82.224.16 rip=129.82.224.206 lport=110 rport=3757 resp=hiddenOct 28 21:16:27 goku dovecot: [ID 107833 mail.info] auth-worker(default): pam(user,129.82.224.206): lookup service=dovecotOct 28 21:16:27 goku dovecot: [ID 107833 mail.info] auth-worker(default): pam(user,129.82.224.206): #1/1 style=1 msg=Password:Oct 28 21:16:27 goku dovecot: [ID 107833 mail.error] auth-worker(default): pam(user,129.82.224.206): pam_authenticate() failed: No account present for user Oct 28 21:16:27 goku dovecot: [ID 107833 mail.info] auth-worker(default): passwd(user,129.82.224.206): lookup Oct 28 21:16:27 goku dovecot: [ID 107833 mail.info] auth-worker(default): passwd(user,129.82.224.206): Password mismatch Running dovecot 1.1.3 on Solaris 10 goku % ./dovecot -n # 1.1.3: /userM/mail-services/dovecot/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 3072). Either grow the limit or change login_max_processes_count and max_mail_processes settings base_dir: /userM/mail-services/dovecot/var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /userM/mail-services/dovecot/etc/ssl/dovecot.pem ssl_key_file: /userM/mail-services/dovecot/etc/ssl/privkey.pem ssl_parameters_regenerate: 0 ssl_cipher_list: MEDIUM:!LOW disable_plaintext_auth: no login_dir: /userM/mail-services/dovecot/var/run/dovecot/login login_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3-login login_greeting: Cyrus ready. login_max_processes_count: 1024 max_mail_processes: 1024 mail_location: mbox:~/:INBOX=/userM/mail/%u mail_debug: yes mmap_disable: yes mail_nfs_index: yes mbox_write_locks: fcntl dotlock mbox_dotlock_change_timeout: 60 mail_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3 mail_plugins(default): convert mail_plugins(imap): convert mail_plugins(pop3): mail_plugin_dir(default): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /userM/mail-services/dovecot/lib/dovecot/pop3 auth default: mechanisms: plain login verbose: yes debug: yes worker_max_count: 1024 worker_max_request_count: 2 passdb: driver: pam passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/lib/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /userM/mail-services/dovecot/var/run/dovecot//auth-master mode: 384 plugin: convert_mail: Maildir:~/Maildir:INBOX=/userM/mail/%u - -- C. J. Keist Email: [EMAIL PROTECTED] UNIX/Network
Re: [Dovecot] read only FS access
On Wed, 2008-10-29 at 17:01 +0200, Timo Sirainen wrote: On Wed, 2008-10-29 at 10:10 +0100, Mathieu Kretchner wrote: My problem is that dovecot complain when I subscribe to the folder in read only What does it complain? If the problem is that you've a namespace created for a read-only partition, you can simply set subscriptions=no. If that doesn't help, post your dovecot -n output and describe your setup. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] POP3 auth failures
On Wed, 2008-10-29 at 09:02 -0600, CJ Keist wrote: Have a strange problem with just POP3 users. Their email clients will fail every so often with the following: .. auth-worker(default): pam(user,129.82.224.206): pam_authenticate() failed: No account present for user So PAM thinks it doesn't exist. The only solution to issues with PAM that I can think of is to decrease how many lookups it can do before restarting the process: worker_max_request_count: 2 Try e.g. a value of 1000 to see if that happens to fix it. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Keep the email on the server
On Tue, 2008-10-28 at 11:18 -0200, Rubens A. Mascari wrote: All mail in the inbox, are brought all the time that you check your mailbox input via POP3, causing a large traffic of unnecessary data every time. In my opinion you should bring only the new mail, unread. The same mails are downloaded over and over again? I'm guessing using Outlook as the client? What do you have in pop3_uidl_format? Your dovecot -n output didn't provide it, which means you're using a distribution package that set a default for it. Perhaps a bad default. See http://wiki.dovecot.org/POP3Server - UIDL format. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Authentication Error Message formats
Charles Marcus wrote: On 10/29/2008, Albert E. Whale ([EMAIL PROTECTED]) wrote: When a user fails authentication, or a user does not exist, it appears that the same message is used for these events. When asking for help, it is always a good idea to provide some basic info... in this case, sample log entries from failed events, and output of dovecot -n? Thank Charles, my apologies. Here is the Logging info: Oct 29 09:43:12 192.168.50.5 dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=darrel, method=PLAIN, rip=217.168.145.51, lip=66.207.133.234 Oct 29 09:43:15 192.168.50.5 dovecot: auth-worker(default): pam(darrel,217.168.145.51): pam_authenticate() failed: Authentication failure Oct 29 09:43:17 192.168.50.5 dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=darrel, method=PLAIN, rip=217.168.145.51, lip=66.207.133.234 Oct 29 09:43:20 192.168.50.5 dovecot: auth-worker(default): pam(darrel,217.168.145.51): pam_authenticate() failed: Authentication failure Oct 29 09:43:22 192.168.50.5 dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=darrel, method=PLAIN, rip=217.168.145.51, lip=66.207.133.234 And my dovecot.conf is attached. BTW, these entries are samples of invalid users. -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*. ns6.ABS-CompTech.com root [/root] dovecot -n # 1.1.4: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: SpamZapper Email ready. mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 verbose_proctitle: yes mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: username_format: %Lu verbose: yes debug: yes passdb: driver: passwd-file args: /home/dovecot.passwd passdb: driver: pam userdb: driver: passwd-file args: /home/dovecot.passwd userdb: driver: passwd
Re: [Dovecot] Empty/corrupt mail leads to duplicate delivery
On Mon, 2008-10-27 at 20:12 +0100, Marc Herbrechter wrote: Hi, when the attached mail was stored in a maildir, fetching mail via POP3 lead to multiple delivery of mails in that maildir to the client (Outlook). I replaced the domain with dots. Sounds like an Outlook bug. The only thing Dovecot could do wrong is to provide duplicate UIDL for the messages. You could verify this yourself by giving UIDL command and seeing if there are duplicates. But I highly doubt that, because you're using: pop3_uidl_format = %08Xu%08Xv Which means your UIDL is based on message UID and UIDVALIDITY. Neither depend on message contents. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Authentication Error Message formats
Timo Sirainen wrote: On Wed, 2008-10-29 at 09:49 -0400, Albert E. Whale wrote: I have been using UW's IMAP server and I am converting to Dovecot for Maildir support. When a user fails authentication, or a user does not exist, it appears that the same message is used for these events. Is there a way to indicate that the user does not exist (Invalid user), and authentication Failure (Failed Password)? To user: no. In logs: yes, with auth_verbose=yes. Timo, Thank you. I already have auth_verbose=yes. Here is what I am seeing: Oct 29 09:43:31 192.168.50.5 dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=darrin, method=PLAIN, rip=217.168.145.51, lip=66.207.133.234 Oct 29 09:43:34 192.168.50.5 dovecot: auth-worker(default): pam(darrin,217.168.145.51): pam_authenticate() failed: Authentication failure Oct 29 09:43:36 192.168.50.5 dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=darrin, method=PLAIN, rip=217.168.145.51, lip=66.207.133.234 Oct 29 09:43:38 192.168.50.5 dovecot: auth-worker(default): pam(darrin,217.168.145.51): pam_authenticate() failed: Authentication failure Oct 29 09:43:40 192.168.50.5 dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=darrin, method=PLAIN, rip=217.168.145.51, lip=66.207.133.234 These attempts to authenticate Darrin will not complete, as this is not a valid user. The IP Address 217.168.145.51 was cycling through 1364 attempts. I would like to identify this type of activity sooner, as this is not a valid user. -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*.
Re: [Dovecot] mail_location: mbox: mkdir failed
On Mon, 2008-10-27 at 12:30 -0400, Albert E. Whale wrote: Timo Sirainen wrote: On Oct 27, 2008, at 2:15 PM, Albert E. Whale wrote: Is there an automatic solution to this? Oct 27 08:00:48 192.168.50.5 dovecot: POP3(evelina2): mail_location: mbox: mkdir(/home/popuser_evelina2/mail) failed: Permission denied You mean /home/popuser_evelina2 doesn't exist and Dovecot doesn't have write permissions to /home? Choices would be: a) Create the directory automatically whenever you add new users b) Give Dovecot write permissions to /home c) If you're using PAM, use pam_mkhomedir Actually the /home/popuser_evelina2 directory exists. I had thought that we were making the directory. It's just the mail subdirectory that is missing. Then I guess your userdb isn't returning correct UID for the user. You're using system users? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Authentication Error Message formats
On Wed, 2008-10-29 at 11:17 -0400, Albert E. Whale wrote: Oct 29 09:43:34 192.168.50.5 dovecot: auth-worker(default): pam(darrin,217.168.145.51): pam_authenticate() failed: Authentication failure .. These attempts to authenticate Darrin will not complete, as this is not a valid user. The IP Address 217.168.145.51 was cycling through 1364 attempts. I would like to identify this type of activity sooner, as this is not a valid user. OK, so you're using PAM. PAM doesn't tell Dovecot why the authentication failed. There are two possible solutions for your problem: a) Look at PAM's own log (auth.log probably) instead. It probably tells the reason. b) Don't use PAM. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot read only for users
On Sat, 2008-10-25 at 23:24 -0500, JC wrote: All, I have hopefully a base question. How do you give users only read access to their inbox and folders? If I use chmod 600 they have full access. If I do a 400 they have read access but cannot access their inbox. The config file is the out of the box config other than advertising IMAP and IMAPS. mbox or maildir? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot deliver mail bounce problem
On Fri, 2008-10-24 at 17:57 +0530, Dhaval Thakar wrote: but when mail is sent to invalid user, it gets bounced back with error I'm not going to try again; this message has been in the queue too long. rather no mailbox here by that name .. Oct 24 23:03:27 backup dovecot: auth(default): master out: NOTFOUND 1 dovecot-auth successfully figures out that the user doesn't exist. .qmail-default |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -n -e -d [EMAIL PROTECTED] Try manually running: /usr/local/libexec/dovecot/deliver -n -e -d blabla echo $? What does the echo print? If it prints 67, the problem isn't deliver but qmail. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] mail_location: mbox: mkdir failed
Timo Sirainen wrote: On Mon, 2008-10-27 at 12:30 -0400, Albert E. Whale wrote: Timo Sirainen wrote: On Oct 27, 2008, at 2:15 PM, Albert E. Whale wrote: Is there an automatic solution to this? Oct 27 08:00:48 192.168.50.5 dovecot: POP3(evelina2): mail_location: mbox: mkdir(/home/popuser_evelina2/mail) failed: Permission denied You mean /home/popuser_evelina2 doesn't exist and Dovecot doesn't have write permissions to /home? Choices would be: a) Create the directory automatically whenever you add new users b) Give Dovecot write permissions to /home c) If you're using PAM, use pam_mkhomedir Actually the /home/popuser_evelina2 directory exists. I had thought that we were making the directory. It's just the mail subdirectory that is missing. Then I guess your userdb isn't returning correct UID for the user. You're using system users? Yes, the system users (/etc/passwd) files. Here's that dovecot.conf file. I would have hoped that it would have been able to create the mail folder, if it was not there. -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*. ns6.ABS-CompTech.com root [/root] dovecot -n # 1.1.4: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: SpamZapper Email ready. mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 verbose_proctitle: yes mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: username_format: %Lu verbose: yes debug: yes passdb: driver: passwd-file args: /home/dovecot.passwd passdb: driver: pam userdb: driver: passwd-file args: /home/dovecot.passwd userdb: driver: passwd
Re: [Dovecot] mail_location: mbox: mkdir failed
On Wed, 2008-10-29 at 11:23 -0400, Albert E. Whale wrote: Oct 27 08:00:48 192.168.50.5 dovecot: POP3(evelina2): mail_location: mbox: mkdir(/home/popuser_evelina2/mail) failed: Permission denied .. Then I guess your userdb isn't returning correct UID for the user. You're using system users? Yes, the system users (/etc/passwd) files. Well: passdb: driver: passwd-file args: /home/dovecot.passwd passdb: driver: pam userdb: driver: passwd-file args: /home/dovecot.passwd userdb: driver: passwd What does dovecot.passwd contain? Does it contains popuser_evelina2? Set mail_debug=yes and log in, what are the full logs about it? What does ls -lnd /home/popuser_evelina2 show? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Best configuration of dovecot for limit Outlook problems with IMAP
On Thu, 2008-10-23 at 18:53 +0200, Alessio Cecchi wrote: Hi, in some installation where users using IMAP and Outlook Express I have some problems. Outolook randomly presents problems in messages retrieving, for example: Outlook Express is unable to retrieve the requested message because the server no longer has the message available server response: Fecth Completed Fetch completed is a success reply. Is there anything in Dovecot's logs? Message could not be displayed error message when I try to view an Outlook Express e-mail message Have you set synchronization to headers only? If so, this error message can happen and there's nothing the IMAP server can do about it. What further changes to the configuration of dovecot could I do? My guess is that OE is just buggy and there's nothing that can be done to fix it. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Best configuration of dovecot for limit Outlook problems with IMAP
My guess is that OE is just buggy and there's nothing that can be done to fix it. That's also my view. Or, to use a more neutral term: Outlook and Outlook Express do support IMAP, but their support of the IMAP format is limited. For an IMAP mail server, they are probably not the best client to use. JC
Re: [Dovecot] mail_executable's process environment
On Mon, 2008-10-20 at 20:02 -0400, Mike Malsman wrote: Upon inspection of the processes' environment I'm pleased to see that there's a load of useful information in there. However, one essential component in my case is the destination network address, which is missing. I added it with the attached patch, exposed as 'LOCAL_IP'. Works for me. Is this something that would be useful to anyone else? OK, added: http://hg.dovecot.org/dovecot-1.1/rev/a5495e3e90c9 signature.asc Description: This is a digitally signed message part
[Dovecot] Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client-auth_request == request)
Running Dovecot-1.1.5, I see this assertion failure: Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client-auth_request == request) Error: pop3-login: Raw backtrace: 2 pop3-login 0x0001ac41 default_fatal_finish + 41 - 3 pop3-login 0x0001acac i_syslog_fatal_handler + 0 - 4 pop3-login 0x0001a446 i_info + 0 - 5 pop3-login 0x000153a2 authenticate_callback + 126 - 6 pop3-login 0x0001841c auth_client_input_fail + 280 - 7 pop3-login 0x00017910 auth_client_input + 358 - 8 pop3-login 0x0001e074 io_loop_handler_run + 272 - 9 pop3-login 0x0001d449 io_loop_run + 38 - 10 pop3-login 0x00014864 main + 1572 - 11 pop3-login 0x000112fc start + 52 Error: child 1302 (login) killed with signal 6 This happens when I feed multiple user/pass lines to Dovecot all at once like this: $ telnet gromit 110 Connected. Escape character is '^]'. +OK Dovecot ready. user x pass y user x pass y +OK +OK Connection closed by foreign host. The four user/pass lines I pasted in all at once. IMAP login does not crash when presented with multiple login commands, but it does not read them all at once and needs prodding (in the form of extra command lines sent later on) to read them. Actually it appears to read the first two lines then stops reading until more data comes in: $ telnet gromit 143 Connected. Escape character is '^]'. * OK Dovecot ready. a login a b b login c d c login e f d login g h e login i j a NO Authentication failed. b NO Authentication failed. c NO Authentication failed. d NO Authentication failed. e NO Authentication failed. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. ^] telnet q Connection closed. You probably don't care about the odd imap-login behavior, but I tried it and mentioned it just for completeness after seeing pop3-login crash.
Re: [Dovecot] Best configuration of dovecot for limit Outlook problems with IMAP
Recently I encountered a situation where Outlook Express was giving me a similar error, although it was only on certain emails. It started when I tried to tell Outlook Express to synchronize less than 'All messages' and I must have used 'New headers' or something instead. Switching it back to 'All messages' made it continue to download the entire body + headers of new mail, but they were accessible. For the messages that were inaccessible, to regain access I had to select them, right click the selection, click Move to Folder, and select the Inbox under the same mail server, then Click Send/Recv and the fixed messages would appear. Alessio Cecchi wrote: Hi, in some installation where users using IMAP and Outlook Express I have some problems. Outolook randomly presents problems in messages retrieving, for example: Outlook Express is unable to retrieve the requested message because the server no longer has the message available server response: Fecth Completed or Message could not be displayed error message when I try to view an Outlook Express e-mail message I'm using dovecot 1.1.4 with qmail and vpopmail. This is my dovecot configure options: ./configure --prefix=/usr --sysconfdir=/etc/dovecot --localstatedir=/var --with-ssldir=/etc/ssl and this my dovecot config: # dovecot -n # 1.1.4: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot/dovecot-err.log info_log_path: /var/log/dovecot/dovecot.log ssl_cert_file: /etc/apache2/ssl/comun.crt ssl_key_file: /etc/apache2/ssl/comun.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting: Ready login_process_per_connection: no 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_debug: yes mail_plugins: quota imap_quota imap_client_workarounds: outlook-idle delay-newmail namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: verbose: yes debug: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: prefetch args: uid=89 gid=89 home=/home/vpopmail/domains/%d/%u plugin: quota: maildir What further changes to the configuration of dovecot could I do? Do you have other suggestions? Thanks
Re: [Dovecot] Best configuration of dovecot for limit Outlook problems with IMAP
Generally a straightforward way to cure suche MS client errors is to remove the account in Outlook or OE and re-create it. One can also delete the cache files for the account but the first way is more explainable to a user. JC
Re: [Dovecot] Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client-auth_request == request)
On Wed, 2008-10-29 at 11:03 -0500, Mike Abbott wrote: Running Dovecot-1.1.5, I see this assertion failure: Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client-auth_request == request) Thanks, fixed: http://hg.dovecot.org/dovecot-1.1/rev/0c7bfad031d2 Looks like I had actually fixed it already in v1.2 tree. IMAP login does not crash when presented with multiple login commands, but it does not read them all at once and needs prodding (in the form of extra command lines sent later on) to read them. Actually it appears to read the first two lines then stops reading until more data comes in: Fixed: http://hg.dovecot.org/dovecot-1.1/rev/59c997c38079 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot pop3 and SonicWall?
On Wed, 2008-10-29 at 09:21 -0700, Brandon Lamb wrote: Hello Has anyone else run into a problem with dovecot pop3 and sonicwall? A week after switching to dovecot we had two local customers call and report they could no longer download emails with attachments. It turned out to be the email macro filter on the router. After the first report I thought maybe the customer had just changed something or it was a fluke, but then a day later we had the second call with the same issue. For some reason, after us switching the sonicwall's email macro filter was catching any attachments as a threat. I couldnt see how changing pop3 servers could affect that, but I guess anything is possible. I just emailed sonicwall and am waiting for a response from them now as well. Hopefully maybe someone has heard of this before. Unfortunately, I dont know if this was pure coincidence, or if both customers happened to have updated their sonicwall software, or maybe it autoupdates, I have no information on it.Of course to them it looks like we broke it. We just had them both turn this rule off for now. I've no idea, but perhaps sonicwall only looks at IP packets instead of following entire TCP streams and perhaps Dovecot is sending larger IP packets (or alternatively smaller/differently) than your previous POP3 server? Just a guess. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] allow_nets overridden by cache
On Tue, 2008-10-28 at 13:55 +, Guy wrote:
auth_cache_ttl is set to 300. If I set it to 1 then the allow_nets
successfully rejects. Once I set it back up to 300 the cache overrides
the result from the allow_nets check and let's the account log in even
though the allow_nets check fails.
I've tried waiting for longer than the 300 seconds and then logged in
again, but I still get the same result as above.
What Dovecot version? Post your dovecot -n output? Seems to work fine
with the almost-v1.1.6 (and I don't remember doing changes related to
this for a long time):
client in: AUTH 5 PLAIN service=imap secured lip=127.0.1.1
rip=127.0.1.1 lport=143 rport=49704 resp=AHRzcwBwYXNz
cache(tss,127.0.1.1): hit: {plain}passallow_nets=127.0.0.1
auth(tss,127.0.1.1): allow_nets: Matching for network 127.0.0.1
passdb(tss,127.0.1.1): allow_nets check failed: IP not in allowed networks
client out: FAIL 5 user=tss
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] quota warning not working
On Mon, 2008-10-27 at 15:38 +0100, Claudio Prono wrote: quota_warning = storage=70%% /usr/bin/quota_warning.sh 70 In the plugin section naturally. All seems to work fine, the quota is calculated right, but seems the script is not executed... In dovecot logs i have this: The warning script should be executed when going from under 70% to over 70% quota or vice versa. Whether is really works like that in all situations, I don't know. People seem to have been complaining every once in a while. I have added the echo for debug pourpose, but no file was created, so the script is not executed. I thinked is a permission problem, but seems not. Now the script is like this: If your script exits with non-zero, Dovecot logs an error: system(/usr/bin/quota_warning.sh 70) exited with status %d Also I just added this code to make it always log when executing the quota warning script if mail_debug=yes: http://hg.dovecot.org/dovecot-1.1/rev/dcea00b0e290 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] quota warning not working
Thank u very much, my problem is the permissions. Now quota_warning.sh is owned by postfix.postfix and works great. Strange only a thing, i don't have errors in log for wrong permissions... Ty, Claudio. Timo Sirainen ha scritto: On Mon, 2008-10-27 at 15:38 +0100, Claudio Prono wrote: quota_warning = storage=70%% /usr/bin/quota_warning.sh 70 In the plugin section naturally. All seems to work fine, the quota is calculated right, but seems the script is not executed... In dovecot logs i have this: The warning script should be executed when going from under 70% to over 70% quota or vice versa. Whether is really works like that in all situations, I don't know. People seem to have been complaining every once in a while. I have added the echo for debug pourpose, but no file was created, so the script is not executed. I thinked is a permission problem, but seems not. Now the script is like this: If your script exits with non-zero, Dovecot logs an error: system(/usr/bin/quota_warning.sh 70) exited with status %d Also I just added this code to make it always log when executing the quota warning script if mail_debug=yes: http://hg.dovecot.org/dovecot-1.1/rev/dcea00b0e290 -- Claudio Prono Systems Development @ Atpss.net Srl, Divisione Implementazione Sistemi Via San Bernardino, 17 - 10137 Torino (TO) - IT Tel +39-011.32.72.100 Fax +39-011.32.46.497 PGP Fingerprint: 75C2 4049 E23D 2FBF A65F 40DB EA5C 11AC C2B0 3647 Disclaimer: http://atpss.net/disclaimer
Re: [Dovecot] Dovecot and quota enforcement - only reporting?
At 10:50 AM 10/29/2008, Timo Sirainen wrote: Still no answer to my original question of what exactly updates maildirsize? Is that also the dovecot LDA? 1) Dovecot LDA for newly delivered mails 2) Dovecot IMAP for messages saved/copied via IMAP client Thanks, that perfectly explains why I haven't been able to figure out what makes maildirsize update. So the only way to get quota enforcing with Dovecot is to have Postfix use the dovecot LDA? Yes, the only way to enforce quota for newly delivered mails is to deliver mails via LDA capable of enforcing the quota. :) (It doesn't have to be Dovecot LDA though, there are other LDAs that understand Maildir++ quota too. Dovecot LDA is recommended though.) Excellent. Now off to figure out whether I'll break anything by changing it! :-) Is it different between virtual users (mysql using a dovecot-mysql.conf file) and local users? Rick
[Dovecot] dovecot 1.1.5 mbox bug (From_-line separator related)
If I send mail with content like this: From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 and instead single messages created many messages. Inside mbox file it looks like real_message_headers Status: O X-Keywords: Content-Length: 2859 X-UID: 1471 From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 X-UID: 1472 Status: O From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 X-UID: 1473 Status: O From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 X-UID: 1474 Status: O Yes, Content-Length headers present, but: 1. Why X-UID: and Status: headers inserted into message body? 2. Why IMAP client (thunderbird) show many empty messages instead single message? Mbox related settings from dovecot -n is only: mmap_disable: yes mbox_write_locks: fcntl mbox_min_index_size: 1024 To store messages used dovecot deliver. -- WBR, Anton Yuzhaninov
Re: [Dovecot] Embedded Fromspace Lines
On Mon, 2008-10-27 at 14:29 -0700, Lennart Lövstrand wrote: However, I also noted that there's a case which the fix doesn't cover, and that's where the Fromspace line appears as the first line of the body of the message. When this happens, the body_offset will point to the blank line between the headers and the body and not the actual first line of the body. This will cause the stream to be mispositioned at the time of the Fromspace verification check in istream_raw_mbox_get_body_size and the (actually correct) expected_body_size will be rejected. I have enclosed a simple diff that will work around this by adjusting the body_offset to point to the next line at the time of call to istream_raw_mbox_is_valid_from in istream_raw_mbox_get_body_size. This appears to handle the problem correctly in all the test cases I have. Thanks. I fixed it basically the same way but with a bit different code: http://hg.dovecot.org/dovecot-1.1/rev/9c3fa81a721d signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Two more to add: /etc/sourcemage-release /etc/slackware-version :) - -- Andraž ruskie Levstik Source Mage GNU/Linux Games grimoire guru Geek/Hacker/Tinker Be sure brain is in gear before engaging mouth. Quis custodiet ipsos custodies. Ryle hira. Key id = F4C1F89C Key fingerprint = 6FF2 8F20 4C9D DB36 B5B6 F134 884D 72CC F4C1 F89C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJCKjziE1yzPTB+JwRAqzUAKClFkLWdNULjg0wgSPE60PYz2TjtgCZAa0k 3W/5a5AzIcGFT7OS8RjWn2c= =9GJI -END PGP SIGNATURE-
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
On Wed, 2008-10-29 at 19:18 +0100, Andraž 'ruskie' Levstik wrote: /etc/sourcemage-release Does this contain Sourcemage name in some way? /etc/slackware-version Does this contain Slackware name in some way? (Most seem to, but Debian is an exception and contains only lenny/sid with me, so I prefix manually it with Debian ). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 29 Oct 2008, Timo Sirainen wrote: On Wed, 2008-10-29 at 19:18 +0100, Andraž 'ruskie' Levstik wrote: /etc/sourcemage-release Does this contain Sourcemage name in some way? cat /etc/sourcemage-release Source Mage GNU/Linux 0.9.6.1 i486-pc-linux-gnu Installed from CD using installer v. 0.9.6.1 on Fri Feb 23 17:44:19 UTC 2007 /etc/slackware-version Does this contain Slackware name in some way? cat /etc/slackware-version Slackware 12.0.0 (Most seem to, but Debian is an exception and contains only lenny/sid with me, so I prefix manually it with Debian ). So that would be yes ;) - -- Andraž ruskie Levstik Source Mage GNU/Linux Games grimoire guru Geek/Hacker/Tinker Be sure brain is in gear before engaging mouth. Quis custodiet ipsos custodies. Ryle hira. Key id = F4C1F89C Key fingerprint = 6FF2 8F20 4C9D DB36 B5B6 F134 884D 72CC F4C1 F89C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJCKrAiE1yzPTB+JwRArpDAJ9blGntt9XwVehbm9C6qDoC+HT+CACgqyoi rCbFVfar/FNHwhWpPeUKJss= =Slio -END PGP SIGNATURE-
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
On 10/29/2008, Andra~ 'ruskie' Levstik ([EMAIL PROTECTED]) wrote: Two more to add: /etc/sourcemage-release /etc/slackware-version One more: /etc/gentoo-release Hmmm... this doesn't really contain useful info though... ~ # cat /etc/gentoo release Gentoo Base System release 1.12.11.1 maybe some forme of the uname command? ~ # uname -orpm 2.6.23-gentoo-r9 x86_64 AMD Opteron(tm) Processor 244 GNU/Linux -- Best regards, Charles
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
On Wed, 2008-10-29 at 19:39 +0200, Timo Sirainen wrote: The filesystem is looked up by getting the mount information for the directory in mail_location. That's not correct in all setups, but probably correct for most. I was wondering why this felt like it was too easy. dovecot -n can't easily look up user's home directories. So the only time when it now prints the filesystem is if mail_location contains something like: mail_location = maildir:/home/%u/Maildir It cuts after the first % character and if there's more than 1 character left, that directory is used in the mount lookup. But perhaps it'll show up once in a while in bug reports. :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
On Wed, 2008-10-29 at 14:37 -0400, Charles Marcus wrote: On 10/29/2008, Andra~ 'ruskie' Levstik ([EMAIL PROTECTED]) wrote: Two more to add: /etc/sourcemage-release /etc/slackware-version One more: /etc/gentoo-release Added. Hmmm... this doesn't really contain useful info though... ~ # cat /etc/gentoo release Gentoo Base System release 1.12.11.1 Looks just fine. maybe some forme of the uname command? ~ # uname -orpm 2.6.23-gentoo-r9 x86_64 AMD Opteron(tm) Processor 244 GNU/Linux uname() is also used. It would probably print with you: # OS: Linux 2.6.23-gentoo-r9 x86_64 Gentoo Base System release 1.12.11.1 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot expire doesn't work (?)
On Wednesday 29 October 2008 15.53.24 you wrote: On Wed, 2008-10-29 at 15:25 +0100, LÉVAI Dániel wrote: That is, if I want to expire the emails under the spamassassin/SPAM directory, after 1 day. Is this correct? I'm asking this because with this setup, the expire-tool does nothing... nothing in the logs either. Try and set mail_debug=yes. It should log more. Done. When I ran `dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test', it told me that: Info: leva/spamassassin.SPAM: stop, expire time in future: 1225290174 Sounds like it's working. It just wasn't time yet to expunge the oldest mail from there: % unix2date.sh -u 1225290174 Wed Oct 29 14:22:54 UTC 2008 Running it again now would show that it's going to expunge it? Unfortunately not: # ls -lrt $USER/Maildir/.spamassassin.SPAM/cur/ 1840 Oct 25 03:17:55 2008 1225137329.[...],W=1890,S=1840:2,S 1978 Oct 25 04:32:37 2008 1225137329.[...],W=2028,S=1978:2,S 3773 Oct 25 13:12:23 2008 1225137329.[...],W=3841,S=3773:2,S 2749 Oct 26 02:10:28 2008 1225137329.[...],W=2835,S=2749:2,S 3783 Oct 26 13:15:36 2008 1225137329.[...],W=3852,S=3783:2,S 13172 Oct 26 18:30:16 2008 1225137329.[...],W=13377,S=13172:2,S 2292 Oct 27 08:00:07 2008 1225137329.[...],W=2340,S=2292:2,S 1985 Oct 27 08:00:10 2008 1225137329.[...],W=2031,S=1985:2,S 26644 Oct 27 16:02:35 2008 1225137329.[...],W=27234,S=26644:2,S 3209 Oct 27 16:23:57 2008 1225137329.[...],W=3282,S=3209:2,S 3155 Oct 27 19:13:38 2008 1225290969.[...],W=3210,S=3155:2,S 3193 Oct 27 22:11:38 2008 1225291087.[...],W=3267,S=3193:2,S Oct 28 01:06:51 2008 1225203774.[...],W=4502,S=:2,S 4793 Oct 28 09:42:31 2008 1225203785.[...],W=4849,S=4793:2,S 2925 Oct 28 14:04:10 2008 1225203793.[...],W=2977,S=2925:2,S 3727 Oct 28 17:51:33 2008 1225218230.[...],W=3819,S=3727:2,S 255537 Oct 29 00:27:32 2008 1225236452.[...],S=255537,W=259071:2,S 4021 Oct 29 04:02:59 2008 1225249379.[...],S=4021,W=4119:2,S 2802 Oct 29 16:03:29 2008 1225292609.[...],S=2802,W=2874:2,S You see the oldest message is dated back four days from now, and no matter if I run the expire-tool without the --test option, it won't expunge them. Although all of the messages was saved by dovecot's deliver, the expire-tool doesn't seem to recognize but one of the messages. That is the last one, created on Oct 29, 16:03. # /usr/local/sbin/dovecot --exec-mail \ ext /usr/local/libexec/dovecot/expire-tool --test Info: leva/spamassassin.SPAM: stop, expire time in future: 1225379009 # date -r 1225379009 Thu Oct 30 16:03:29 CET 2008 Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
[Dovecot] Backing Up
What is the best way to do a (server-side) backup of all mail in a user's mail? I don't think I'm doing anything weird as far as configs go; here's dovecot -n if it helps: # 1.1.4: /etc/dovecot/dovecot.conf protocols: imaps listen: *, [::] ssl_cert_file: /etc/ssl/dovecot/cert.pem ssl_key_file: /etc/ssl/dovecot/key.pem login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/.maildir auth default: mechanisms: plain login passdb: driver: pam args: * userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
On 10/29/2008 2:41 PM, Timo Sirainen wrote: /etc/gentoo-release Added. Hmmm... this doesn't really contain useful info though... ~ # cat /etc/gentoo release Gentoo Base System release 1.12.11.1 Looks just fine. maybe some forme of the uname command? ~ # uname -orpm 2.6.23-gentoo-r9 x86_64 AMD Opteron(tm) Processor 244 GNU/Linux uname() is also used. It would probably print with you: # OS: Linux 2.6.23-gentoo-r9 x86_64 Gentoo Base System release 1.12.11.1 Ahh... well, there ya go... thanks Timo, maybe this will save you some few precious seconds... ;) -- Best regards, Charles
Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
sergey ivanov schreef: Hi Stephan, Thank you for quick fix. I've built it (from changeset 646:747107b816dc) and it looks like working with dovecot-1.2. I'm doing some testing before put it into Sisyphus repository (http://en.altlinux.org). What I saw - it does not recognize lines like: --- sieve = /var/sievescripts/%n/sieve --- as cmusieve did. But it works ok with default .dovecot.sieve files in user home directories Hmm, I'll look into that. This is not intended and would be a bug. Then, it reports --- error: failed to store into mailbox 'Inbox/R/Commits': Invalid mailbox name. --- where cmusieve did --- fileinto fileinto Inbox/R/Commits; --- this new plugin require changing slashes to dots: --- fileinto fileinto Inbox.R.Commits; This doesn't look like something that has changed for the Sieve implementation specifically. Did you try dovecot-sieve-1.1 with dovecot 1.2 to verify? I'll ask Timo about this. What is the configuration of your mail store. Did you perhaps migrate from mbox to maildir? I think this changes should be described somewhere. May be, it's already needed to create wiki page for libsieve at wiki.dovecot.org? Well, first one is probably a bug. The second one I am not sure about yet. I'll get back to you when I do. PS: please reply to the mailing list as well. Your problems and solutions may interest others as well. Regards, -- Stephan Bosch [EMAIL PROTECTED]
Re: [Dovecot] allow_nets overridden by cache
Hi Timo, 2008/10/29 Timo Sirainen [EMAIL PROTECTED]: What Dovecot version? Post your dovecot -n output? Seems to work fine with the almost-v1.1.6 (and I don't remember doing changes related to this for a long time): Sorry, should have included that before. I've just upgraded to 1.1.5, compiled from source with nothing extra added. Although I did just do a make install without doing an uninstall on the old 1.1.2, could that effect it? [EMAIL PROTECTED]:/opt/src/dovecot/1.1.5/dovecot-1.1.5# dovecot -n # 1.1.5: /etc/dovecot/dovecot.conf protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_process_per_connection: no login_processes_count: 10 max_mail_processes: 1024 verbose_proctitle: yes mail_location: maildir:%h/Maildir/ mail_full_filesystem_access: yes mmap_disable: yes dotlock_use_excl: no mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_process_size: 128 mail_plugins(default): imap_quota quota mail_plugins(imap): imap_quota quota mail_plugins(pop3): quota mail_log_max_lines_per_sec: 30 imap_client_workarounds: outlook-idle delay-newmail pop3_uidl_format: %08Xv%08Xu pop3_client_workarounds: outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ location: maildir:%h/Maildir/ hidden: yes subscriptions: yes auth default: cache_size: 2048 cache_ttl: 1 cache_negative_ttl: 1 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@' master_user_separator: * verbose: yes worker_max_count: 5 passdb: driver: passwd-file args: /etc/dovecot/dovecot-master.pwd master: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf plugin: quota: maildir quota_rule: *:storage=100M quota_rule2: Trash:ignore In the section of logs that I showed you could see the client out:FAIL after the allow_nets check but a cache hit immediately afterwards would allow the account to login. Even if I set the auth_cache_ttl to 15 seconds it would still fail the allow_nets check and then get a cache hit and be logged in. If there's any other information I can provide please let me know. Thanks Guy -- Don't just do something...sit there!
Re: [Dovecot] Backing Up
on 10-29-2008 12:25 PM Neil spake the following: What is the best way to do a (server-side) backup of all mail in a user's mail? I don't think I'm doing anything weird as far as configs go; here's dovecot -n if it helps: # 1.1.4: /etc/dovecot/dovecot.conf protocols: imaps listen: *, [::] ssl_cert_file: /etc/ssl/dovecot/cert.pem ssl_key_file: /etc/ssl/dovecot/key.pem login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/.maildir auth default: mechanisms: plain login passdb: driver: pam args: * userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Backing Up
On Oct 29, 2008, at 3:42 PM, Scott Silva wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! -Dave -- Dave McGuire Port Charlotte, FL
Re: [Dovecot] dovecot expire doesn't work (?)
# /usr/local/sbin/dovecot --exec-mail \ ext /usr/local/libexec/dovecot/expire-tool --test Info: leva/spamassassin.SPAM: stop, expire time in future: 1225379009 # date -r 1225379009 Thu Oct 30 16:03:29 CET 2008 Try it again tomorrow past 16:03:29 and it will expunge all your messages older than Oct 29 16:03:29. The expire database was most likely not updated till you fixed the configuration today. This means it doesn't know about the old messages.
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
On 10/29/2008 1:39 PM, Timo Sirainen wrote: Any other suggestions that I could add before 1.1.6 release, which I'm really trying to release today? :) Add the contents of non-default dovecot-sql.conf, dovecot-ldap.conf and maybe dovecot-db.conf to the output? ;) -- Best regards, Charles
Re: [Dovecot] Backing Up
on 10-29-2008 12:47 PM Dave McGuire spake the following: On Oct 29, 2008, at 3:42 PM, Scott Silva wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! -Dave Mbox syncs fairly quickly also. Rsync is very good at working with large text files like mbox, even if users purge stuff from the middle. But since he did show Maildir was in use, I left out also backing up /var/spool/mail/* for the inboxes on a default mbox installation. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] dovecot 1.1.5 mbox bug (From_-line separator related)
On 29.10.2008 21:24, Timo Sirainen wrote: On Wed, 2008-10-29 at 20:23 +0300, Anton Yuzhaninov wrote: If I send mail with content like this: From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 .. So a message whose body begins with From line? Fixed: http://hg.dovecot.org/dovecot-1.1/rev/9c3fa81a721d This patch help only when message begins with From line, but bug still exits if message begins with empty line, then From line. -- WBR, Anton Yuzhaninov
Re: [Dovecot] Variable substitution and folder separator problems, WAS: First release (v0.1.0) of the new Sieve
sergey ivanov schreef: Hi Stephan, I've tried dovecot-sieve cmusieve with at the same place. As I can see, both problems I've though to be in libsieve, actually are that of dovecot. Both plugins do not expand variables like %n, %h, %u. But just filename works, - if I've set --- sieve = sievescript --- then both have used ~/sievescript file, like: --- deliver(seriv): Oct 29 20:14:08 Info: sieve: using sieve path: /home/seriv/sievescript deliver(seriv): Oct 29 20:14:08 Info: sieve: opening script /home/seriv/sievescript deliver(seriv): Oct 29 20:14:08 Info: sieve: executing compiled script /home/seriv/sievescript --- Buth implementations don't work wihth slashes. I took a piece of sieve script from working installation of dovecot-1.1.2 with Maildirs, and here on dovecot-1.2-alpha3 I have default mail location with inbox as mbox in /var/spool/log/mail/user and Maildir in /home/user/Maildir. I should test cmusieve before reporting these as libsieve bugs, I'm sorry. No problem. I think for obtaining further support you should post the output of dovecot -n here. To spot problems with sieve script paths more quickly, I've added some debug messages that are printed to the log when mail_debug=yes. Some of these are actually already similarly present in cmusieve, but were probably added after I copied this particular section of code. Maybe this helps to spot your problem. Regards, -- Stephan Bosch [EMAIL PROTECTED]
Re: [Dovecot] dovecot expire doesn't work (?)
On Wed, 2008-10-29 at 20:14 +0100, LÉVAI Dániel wrote: Running it again now would show that it's going to expunge it? Unfortunately not: # ls -lrt $USER/Maildir/.spamassassin.SPAM/cur/ 1840 Oct 25 03:17:55 2008 1225137329.[...],W=1890,S=1840:2,S 1978 Oct 25 04:32:37 2008 1225137329.[...],W=2028,S=1978:2,S .. You see the oldest message is dated back four days from now, and no matter if I run the expire-tool without the --test option, it won't expunge them. Ah, but expunge plugin works on save dates, not by mtime. The save date is cached to dovecot.index.cache file and it's always older or equal to file's ctime. So use ls -lc instead. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Backing Up
On Wednesday 29 of October 2008, Dave McGuire wrote: On Oct 29, 2008, at 3:42 PM, Scott Silva wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! Not for rsyncing. Tons of small files means much slower rsync. -Dave -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/
Re: [Dovecot] allow_nets overridden by cache
On Wed, 2008-10-29 at 19:32 +, Guy wrote: passdb: driver: passwd-file args: /etc/dovecot/dovecot-master.pwd master: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf Is the allow_nets in the master passdb or sql passdb? In the section of logs that I showed you could see the client out:FAIL after the allow_nets check but a cache hit immediately afterwards would allow the account to login. Even if I set the auth_cache_ttl to 15 seconds it would still fail the allow_nets check and then get a cache hit and be logged in. The cache hit in your log was marked with hidden since it contained a password. Could you enable auth_debug_passwords=yes and show the logs again? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Backing Up
On 29 Oct 2008, at 16:02, Scott Silva wrote: on 10-29-2008 12:47 PM Dave McGuire spake the following: On Oct 29, 2008, at 3:42 PM, Scott Silva wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! -Dave Mbox syncs fairly quickly also. Rsync is very good at working with large text files like mbox, even if users purge stuff from the middle. But since he did show Maildir was in use, I left out also backing up /var/spool/mail/* for the inboxes on a default mbox installation. Yeah, the maildir line was mostly why I put the dovecot -n there. Do you think rsync will be easier on my servers than tarball/bzip2/scp ? Thanks for the help, -Neil.
Re: [Dovecot] dovecot 1.1.5 mbox bug (From_-line separator related)
On Wed, 2008-10-29 at 23:31 +0300, Anton Yuzhaninov wrote: On 29.10.2008 21:24, Timo Sirainen wrote: On Wed, 2008-10-29 at 20:23 +0300, Anton Yuzhaninov wrote: If I send mail with content like this: From [EMAIL PROTECTED] Wed Jan 09 01:33:55 2008 .. So a message whose body begins with From line? Fixed: http://hg.dovecot.org/dovecot-1.1/rev/9c3fa81a721d This patch help only when message begins with From line, but bug still exits if message begins with empty line, then From line. This should fix both: http://hg.dovecot.org/dovecot-1.1/rev/c89c9d0bc877 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot -n - provide sys info too? - WAS: Re: Dovecot read only for users
On Wed, 2008-10-29 at 16:02 -0400, Charles Marcus wrote: On 10/29/2008 1:39 PM, Timo Sirainen wrote: Any other suggestions that I could add before 1.1.6 release, which I'm really trying to release today? :) Add the contents of non-default dovecot-sql.conf, dovecot-ldap.conf and maybe dovecot-db.conf to the output? That'll have to wait for v2.0 or perhaps v1.3. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
On Wed, 2008-10-29 at 20:31 +0100, Stephan Bosch wrote:
sergey ivanov schreef:
Hi Stephan,
Thank you for quick fix. I've built it (from changeset
646:747107b816dc) and it looks like working with dovecot-1.2.
I'm doing some testing before put it into Sisyphus repository
(http://en.altlinux.org).
What I saw - it does not recognize lines like:
---
sieve = /var/sievescripts/%n/sieve
Is this inside protocol lda {} or plugin {}? In former it's not supposed
to be expanded (shouldn't have been with cmusieve either), in latter it
should be.
where cmusieve did
---
fileinto fileinto Inbox/R/Commits;
---
this new plugin require changing slashes to dots:
---
fileinto fileinto Inbox.R.Commits;
With a namespace configuration like:
namespace private {
separator = /
prefix = INBOX/
inbox = yes
}
And a script:
require [fileinto];
fileinto INBOX/foo/bar;
It seems to work just fine:
deliver(tss): Oct 30 00:04:36 Info: sieve: msgid=unspecified: stored
mail into mailbox 'foo.bar'
Although it probably should use the full untranslated INBOX/foo/bar name
when logging (same with deliver -m INBOX/foo/bar).
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Backing Up
On Oct 29, 2008, at 5:32 PM, Arkadiusz Miskiewicz wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! Not for rsyncing. Tons of small files means much slower rsync. Due to connection turnaround latency, I assume? (I've never looked at the rsync protocol) If that's the case, then I stand very much corrected, thank you. I was going from the same logic regarding mbox vs. maildir in the context of backups. One new message delivered and a 400MB mail spool gets backed up again.. -Dave -- Dave McGuire Port Charlotte, FL
Re: [Dovecot] Backing Up
on 10-29-2008 2:46 PM Neil spake the following: On 29 Oct 2008, at 16:02, Scott Silva wrote: on 10-29-2008 12:47 PM Dave McGuire spake the following: On Oct 29, 2008, at 3:42 PM, Scott Silva wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! -Dave Mbox syncs fairly quickly also. Rsync is very good at working with large text files like mbox, even if users purge stuff from the middle. But since he did show Maildir was in use, I left out also backing up /var/spool/mail/* for the inboxes on a default mbox installation. Yeah, the maildir line was mostly why I put the dovecot -n there. Do you think rsync will be easier on my servers than tarball/bzip2/scp ? Thanks for the help, -Neil. Rsync will use more memory on large filesystems, but it is usually lighter in CPU, network, and IO time. But tar gives you multiple backups. To achieve that with rsync you need the rbackup script or rsnapshot. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
[Dovecot] v1.1.6 released
http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig The invalid message address parsing bug is pretty important since it allows a remote user to send broken mail headers and prevent the recipient from accessing the mailbox afterwards, because the process will always just crash trying to parse the header. This is assuming that the IMAP client uses FETCH ENVELOPE command, not all do. Note that it doesn't affect versions older than v1.1.4. + dovecot -n and -a now prints some system information at the top. + More error/debug message logging improvements. - pop3-login: Fixed assert-crash if a client sent USER+PASS+USER+PASS commands in the same IP packet. - Parsing an invalid message address like From: ( caused an assert-crash in v1.1.4 and v1.1.5. - Folding whitespace wasn't handled correctly inside quoted-strings, causing some messages to be parsed incorrectly. - mbox: Fixed saving messages that begin with a valid From_-line. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Backing Up
on 10-29-2008 3:18 PM Dave McGuire spake the following: On Oct 29, 2008, at 5:32 PM, Arkadiusz Miskiewicz wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! Not for rsyncing. Tons of small files means much slower rsync. Due to connection turnaround latency, I assume? (I've never looked at the rsync protocol) If that's the case, then I stand very much corrected, thank you. I was going from the same logic regarding mbox vs. maildir in the context of backups. One new message delivered and a 400MB mail spool gets backed up again.. -Dave Rsync adds some latency as it indexes and compares files on both ends. Obviously it would take more time to compare 40,000 1K files then 1000 40K files even though the data size is similar. It would still be better than tar/bzip/scp which has to compress everything and transfer the lot every time. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
Hi Stephan, I've tried dovecot-sieve cmusieve with at the same place. As I can see, both problems I've though to be in libsieve, actually are that of dovecot. Both plugins do not expand variables like %n, %h, %u. But just filename works, - if I've set --- sieve = sievescript --- then both have used ~/sievescript file, like: --- deliver(seriv): Oct 29 20:14:08 Info: sieve: using sieve path: /home/seriv/sievescript deliver(seriv): Oct 29 20:14:08 Info: sieve: opening script /home/seriv/sievescript deliver(seriv): Oct 29 20:14:08 Info: sieve: executing compiled script /home/seriv/sievescript --- Buth implementations don't work wihth slashes. I took a piece of sieve script from working installation of dovecot-1.1.2 with Maildirs, and here on dovecot-1.2-alpha3 I have default mail location with inbox as mbox in /var/spool/log/mail/user and Maildir in /home/user/Maildir. I should test cmusieve before reporting these as libsieve bugs, I'm sorry. -- WBR, Sergey. On Wed, Oct 29, 2008 at 3:31 PM, Stephan Bosch [EMAIL PROTECTED] wrote: sergey ivanov schreef: Hi Stephan, Thank you for quick fix. I've built it (from changeset 646:747107b816dc) and it looks like working with dovecot-1.2. I'm doing some testing before put it into Sisyphus repository (http://en.altlinux.org). What I saw - it does not recognize lines like: --- sieve = /var/sievescripts/%n/sieve --- as cmusieve did. But it works ok with default .dovecot.sieve files in user home directories Hmm, I'll look into that. This is not intended and would be a bug. Then, it reports --- error: failed to store into mailbox 'Inbox/R/Commits': Invalid mailbox name. --- where cmusieve did --- fileinto fileinto Inbox/R/Commits; --- this new plugin require changing slashes to dots: --- fileinto fileinto Inbox.R.Commits; This doesn't look like something that has changed for the Sieve implementation specifically. Did you try dovecot-sieve-1.1 with dovecot 1.2 to verify? I'll ask Timo about this. What is the configuration of your mail store. Did you perhaps migrate from mbox to maildir? I think this changes should be described somewhere. May be, it's already needed to create wiki page for libsieve at wiki.dovecot.org? Well, first one is probably a bug. The second one I am not sure about yet. I'll get back to you when I do.
Re: [Dovecot] FTS index generation
On Oct 25, 2008, at 8:47 AM, Timo Sirainen wrote: Hi folks. I'm experimenting with the Squat plugin. I can execute search commands via direct interaction with IMAP, but I never see the expected dovecot.index.search index file appear in the spool. I'm concerned that I've misconfigured something that is preventing the creation of those indices. Is there a facility to have the squat plugin generate debugging messages so I can see what it's doing? 1. Set mail_debug=yes. It should log about loading fts and fts_squat plugins. 2. Do you have fts=squat set in plugin section? It looks like it's loading the plugins successfully: ILoading modules from directory: /usr/local/lib/dovecot/imap IModule loaded: /usr/local/lib/dovecot/imap/lib20_fts_plugin.so IModule loaded: /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so ...yet those index files still do not appear. Any ideas on how to pursue this further? (this is with 1.1.4, by the way...I'm compiling 1.1.6 now) Thanks, -Dave -- Dave McGuire Port Charlotte, FL
Re: [Dovecot] v1.1.6 released (managesieve updated)
Timo Sirainen schreef: http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig I've refreshed the managesieve patch for the new Dovecot release. http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.6-managesieve-0.10.3.diff.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.6-managesieve-0.10.3.diff.gz.sig Regards, -- Stephan Bosch [EMAIL PROTECTED]
Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
Hi Stephan, I've tried dovecot-sieve cmusieve with at the same place. As I can see, both problems I've though to be in libsieve, actually are that of dovecot. Both plugins do not expand variables like %n, %h, %u. But just filename works, - if I've set --- sieve = sievescript --- then both have used ~/sievescript file, like: --- deliver(seriv): Oct 29 20:14:08 Info: sieve: using sieve path: /home/seriv/sievescript deliver(seriv): Oct 29 20:14:08 Info: sieve: opening script /home/seriv/sievescript deliver(seriv): Oct 29 20:14:08 Info: sieve: executing compiled script /home/seriv/sievescript --- Buth implementations don't work wihth slashes. I took a piece of sieve script from working installation of dovecot-1.1.2 with Maildirs, and here on dovecot-1.2-alpha3 I have default mail location with inbox as mbox in /var/spool/log/mail/user and Maildir in /home/user/Maildir. I should test cmusieve before reporting these as libsieve bugs, I'm sorry.
Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
Thank you Timo,
it was my mistake.
In 'plugin {}' section line 'sieve = /var/sievescripts/%n/sieve' worked for
both cmusieve and sieve plugins.
Command 'fileinto INBOX/foo/bar' with private namespace configuration you
proposed - also worked in both plugins.
I suspected that they have different behavior: cmusieve saved message into
INBOX/foo/bar, while sieve - into foo/bar as in the deliver log I'm pasting
here. But both messages were filed into the same mail folder. Difference in the
logging, I think, is not a big problem.
---
ls -l Maildir/.foo.bar/new
total 8
-rw--- 1 seriv seriv 513 Oct 30 01:57
1225331850.M790093P1351.sisyphus.office.omniti.com,W=526
-rw--- 1 seriv seriv 518 Oct 30 01:59
1225331966.M468658P1400.sisyphus.office.omniti.com,W=531
tail -n 18 /var/log/deliver/dovecot-deliver.log
---
deliver(seriv): Oct 30 01:57:30 Info: Loading modules from directory:
/usr/lib64/dovecot/modules/lda/
deliver(seriv): Oct 30 01:57:30 Info: Module loaded:
/usr/lib64/dovecot/modules/lda//lib90_cmusieve_plugin.so
deliver(seriv): Oct 30 01:57:30 Info: Namespace: type=private, prefix=INBOX/,
sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes
deliver(seriv): Oct 30 01:57:30 Info: maildir: root exists (/home/seriv/Maildir)
deliver(seriv): Oct 30 01:57:30 Info: maildir++: root=/home/seriv/Maildir,
index=, control=, inbox=/home/seriv/Maildir
deliver(seriv): Oct 30 01:57:30 Info: cmusieve: Using sieve path:
/var/sieve-scripts/seriv.sieve
deliver(seriv): Oct 30 01:57:30 Info: cmusieve: Executing script
/var/sieve-scripts/seriv.sievec
deliver(seriv): Oct 30 01:57:30 Info: Namespace INBOX/: Using permissions from
/home/seriv/Maildir: mode=0644 gid=-1
deliver(seriv): Oct 30 01:57:30 Info: msgid=[EMAIL PROTECTED]: saved mail to
INBOX/foo/bar
deliver(seriv): Oct 30 01:59:26 Info: Loading modules from directory:
/usr/lib64/dovecot/modules/lda/
deliver(seriv): Oct 30 01:59:26 Info: Module loaded:
/usr/lib64/dovecot/modules/lda//lib90_sieve_plugin.so
deliver(seriv): Oct 30 01:59:26 Info: Namespace: type=private, prefix=INBOX/,
sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes
deliver(seriv): Oct 30 01:59:26 Info: maildir: root exists (/home/seriv/Maildir)
deliver(seriv): Oct 30 01:59:26 Info: maildir++: root=/home/seriv/Maildir,
index=, control=, inbox=/home/seriv/Maildir
deliver(seriv): Oct 30 01:59:26 Info: sieve: using sieve path:
/var/sieve-scripts/seriv.sieve
deliver(seriv): Oct 30 01:59:26 Info: sieve: opening script
/var/sieve-scripts/seriv.sieve
deliver(seriv): Oct 30 01:59:26 Info: sieve: executing compiled script
/var/sieve-scripts/seriv.sieve
deliver(seriv): Oct 30 01:59:26 Info: sieve: msgid=[EMAIL PROTECTED]: stored
mail into mailbox 'foo/bar'
--
WBR,
Sergey Ivanov.
- Timo Sirainen [EMAIL PROTECTED] wrote:
On Wed, 2008-10-29 at 20:31 +0100, Stephan Bosch wrote:
sergey ivanov schreef:
Hi Stephan,
Thank you for quick fix. I've built it (from changeset
646:747107b816dc) and it looks like working with dovecot-1.2.
I'm doing some testing before put it into Sisyphus repository
(http://en.altlinux.org).
What I saw - it does not recognize lines like:
---
sieve = /var/sievescripts/%n/sieve
Is this inside protocol lda {} or plugin {}? In former it's not
supposed
to be expanded (shouldn't have been with cmusieve either), in latter
it
should be.
where cmusieve did
---
fileinto fileinto Inbox/R/Commits;
---
this new plugin require changing slashes to dots:
---
fileinto fileinto Inbox.R.Commits;
With a namespace configuration like:
namespace private {
separator = /
prefix = INBOX/
inbox = yes
}
And a script:
require [fileinto];
fileinto INBOX/foo/bar;
It seems to work just fine:
deliver(tss): Oct 30 00:04:36 Info: sieve: msgid=unspecified: stored
mail into mailbox 'foo.bar'
Although it probably should use the full untranslated INBOX/foo/bar
name
when logging (same with deliver -m INBOX/foo/bar).
Re: [Dovecot] Backing Up
Scott Silva wrote, On 10/30/2008 12:34 AM: on 10-29-2008 3:18 PM Dave McGuire spake the following: On Oct 29, 2008, at 5:32 PM, Arkadiusz Miskiewicz wrote: What is the best way to do a (server-side) backup of all mail in a user's mail? I usually just rsync the /home directories to another server. The inital sync can take a while, but it gets faster after there is a base to work from. ...and it's much less painful if you're using maildir instead of mbox! Not for rsyncing. Tons of small files means much slower rsync. Due to connection turnaround latency, I assume? (I've never looked at the rsync protocol) If that's the case, then I stand very much corrected, thank you. I was going from the same logic regarding mbox vs. maildir in the context of backups. One new message delivered and a 400MB mail spool gets backed up again.. -Dave Rsync adds some latency as it indexes and compares files on both ends. Obviously it would take more time to compare 40,000 1K files then 1000 40K files even though the data size is similar. It would still be better than tar/bzip/scp which has to compress everything and transfer the lot every time. Maildirsync it an Online synchronizer for Maildir-format mailboxes See http://hacks.dlux.hu/maildirsync/ Sot.
