- dovecot - dovecot.org

[Dovecot] Unknown column username in where clause
by Daniel Luttermann 20 Jul '10

20 Jul '10

Version: Dovecot 2.0 rc2 I'm testing Dovecot with MySQL quotas but I get always this error for incoming mails: tux dovecot: lmtp(4928): Error: user testuser(a)dlutt.de: Auth USER lookup failed tux dovecot: auth: Error: mysql: Query failed, retrying: Unknown column 'username' in 'where clause' I dont' know where the field "username" should come from because I don't use this field (or query). The relevant files are: dovecot-sql.conf.ext ==================== password_query = SELECT userid AS user, password, \ home AS userdb_home, uid AS userdb_uid, gid AS userdb_gid, \ concat('*:bytes=', quota_bytes) as userdb_quota_rule \ FROM users WHERE userid = '%u' auth-sql.conf.ext ================= passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } userdb { driver = prefetch } userdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } 90-quota.conf ============= plugin { quota = dict:user::proxy::quota quota_rule = *:storage=0 } dovecot-dict-sql.conf.ext ========================= map { pattern = priv/quota/storage table = quota username_field = userid value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = userid value_field = messages } I've grepped through all config files but I can't find any (active) query which uses the above "where username=...". The quota db gets correctly updated if an user logs in so the problem only exists during mail delivery. My SQL tables were crated as follows: CREATE TABLE IF NOT EXISTS `users` ( `userid` varchar(100) NOT NULL, `password` varchar(64) NOT NULL, `home` varchar(255) NOT NULL, `uid` int(11) NOT NULL, `gid` int(11) NOT NULL, `quota_bytes` varchar(10) NOT NULL, PRIMARY KEY (`userid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; CREATE TABLE IF NOT EXISTS `quota` ( `userid` varchar(100) NOT NULL, `bytes` bigint(20) NOT NULL default '0', `messages` int(11) NOT NULL default '0', PRIMARY KEY (`userid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; -- Daniel

3 4

[Dovecot] Dovecot 1.1 migration to 1.2
by Claudio Prono 20 Jul '10

20 Jul '10

Hello all, Here is my dovecot 1.1 conf: # 1.1.3: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot-err.log info_log_path: /var/log/dovecot-inf.log protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 51 last_valid_uid: 51 first_valid_gid: 51 last_valid_gid: 51 mail_location: maildir:/var/mail/virtual/%d/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/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/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %Mf auth default: passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota: maildir:user quota quota_warning: storage=80%% /usr/bin/quota_warning.sh 80 quota_warning2: storage=90%% /usr/bin/quota_warning.sh 90 quota_warning3: storage=99%% /usr/bin/quota_warning.sh 90 Now, is out the OpenSuSE 11.3, and i have noticed it uses dovecot 1.2.11. My question is: there is any difference or incompatibility in my configuration for the 1.2 serie of dovecot? Any hint for a clean migration to the new dovecot? Cordially, Claudio Prono. -- -------------------------------------------------------------------------------- Claudio Prono OPST System Developer Gsm: +39-349-54.33.258 @PSS Srl Tel: +39-011-32.72.100 Via San Bernardino, 17 Fax: +39-011-32.46.497 10141 Torino - ITALY http://atpss.net/disclaimer -------------------------------------------------------------------------------- PGP Key - http://keys.atpss.net/c_prono.asc

4 4

[Dovecot] namespace trouble
by Kevin Faulkner 19 Jul '10

19 Jul '10

I am having some trouble with dovecot 1.2.12 and some namespace issues, or at least that's what I think is the issue. I setup a virtual mailhosting using mysql and postfix. I can receive email and send email without a problem, but when I use mutt to sign in to dovecot, I can't list any Folders, it see's INBOX but it doesn't see any mail. I generally try to not post my problems online, but I searched around on the Internet and I couldn't find anything similar to this issue. I also used kmail to connect to the and it is able to see the mail, but when I can't create any folders. mutt connecting option: mutt set spoolfile=imaps://server.here/INBOX." Here is the mutt debug (mutt -d 3) 4< a0001 OK Capability completed. 4< * LIST (\Noselect) "." "" 4< a0002 OK List completed. 4> a0003 STATUS "Drafts" (MESSAGES) a0004 SELECT "INBOX" 4< a0003 NO Unknown namespace. 4< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) dovecot.conf (part of it, tell me if you want more) mail_location = maildir:/home/vmail/%d/%n/Maildir log_path = /var/log/dovecot.log namespace private { separator = . prefix = INBOX. inbox = yes hidden = no list = yes } listen = * protocol imap { } protocol pop3 { } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster@.com mail_plugins = sieve global_script_path = /home/vmail/globalsieverc } auth default { mechanisms = plain userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } Thank you Very much.

3 2

[Dovecot] Unable to get Dovecot LDA/deliver working
by Frank van Amsterdam 19 Jul '10

19 Jul '10

I want to setup Dovecot LDA, but I don't understand what I'm doing anymore. I have to note that I'm a Linux beginner. I've been trying now for several months and I'm about to give up. Till so far I'm having no result. :-( My current setup is done as described at http://www.linuxmail.info. We use Postfix 2.3.3 (with Postgrey, Spamassassin and ClamAV), Dovecot 1.2.11 and OpenLDAP 2.4.1 on CentOS 5.5. All incoming e-mail are delivered by Postfix in the users' maildir. We use this as a base for SOGo, our groupware solution and it runs smoothly. I have to setup a new mailserver, because we're standardising on Debian. My employer wants to have new functions like out-of-office-replies and forwarding. I want to make use of sieve. Unfortunately I don't know anyone who can help me. My problem is that I don't understand how the delivery process is working. I've read much documentation from Postfix and Dovecot, but I find it too difficult to understand. What do I understand? I know that I have to make changes in /etc/dovecot, /etc/postfix/main.cf and /etc/postfix/master.cf as described at http://wiki.dovecot.org/LDA. /etc/dovecot.conf # OS: Linux 2.6.18-028stab064.7 i686 CentOS release 5.5 (Final) reiserfs base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s managesieve ssl: no version_ignore: yes login_dir: /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/libexec/dovecot/managesieve-login mail_location: maildir:/home/vmail/%u/Maildir 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/libexec/dovecot/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): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) lda: postmaster_address: postmaster(a)domain.nl mail_plugins: cmusieve mail_plugin_dir: /usr/lib/dovecot/lda deliver_log_format: msgid=%m: %$ -- FROM=%f SUBJECT=%s log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log syslog_facility: mail sendmail_path: /usr/lib/sendmail rejection_subject: Rejected: %s rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /usr/local/var/run/dovecot-auth-master auth default: mechanisms: plain login username_format: %Lu passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: static args: uid=500 gid=500 home=/home/vmail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: /var/sieve-scripts/%u.sieve sieve_dir: %h/sieve sieve_global_dir: /var/lib/dovecot/sieve/global/ /etc/postfix/main.cf virtual_mailbox_domains = /etc/postfix/domains ## Plain text file with the domains virtual_mailbox_base = /home/vmail virtual_mailbox_maps = ldap:/etc/postfix/ldap-users.cf virtual_alias_maps = ldap:/etc/postfix/ldap-groups.cf virtual_uid_maps = static:500 virtual_gid_maps = static:500 dovecot_destination_recipient_limit = 1 #virtual_transport = dovecot ## Commented out to deliver by Postfix /etc/postfix/ldap-users.cf server_host = localhost search_base = dc=domain,dc=com version = 3 query_filter = (&(objectclass=mailUser)(mail=%s)) result_attribute = uid result_format = %s/Maildir/ /etc/postfix/ldap-groups.cf server_host = localhost search_base = dc=domain,dc=com version = 3 query_filter = (&(objectclass=mailGroup)(mail=%s)) leaf_result_attribute = mail special_result_attribute = member /etc/postfix/master.cf dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -d <username> I hope someone can help me, because many people on the internet say that it is easy. If anyone needs more information or anyone can help me, please contact me. Best, Frank --- LS: I know that I'm using Hotmail, but I want to post this anonymously.

4 6

[Dovecot] How to install sieve
by Carsten Laun-De Lellis 19 Jul '10

19 Jul '10

Hi all I do have a problem. I have an installation on opensuse 11.2 with postfix, amavis, spamassassin and dovecot 1.2.9 with a mysql authtentication backend. Everything works fine. I want now to install sieve, but i failed all the time. I downloaded dovecot-1.2-sieve-0.1.17 and followed the installation how-to. First when i tried to ./configure the installation i was always asked for dovecot-config. I managed this problem with a symlink. But when i try to run make i always got the following error message. I would appreciate any help. Kind regards, Carsten Laun-De Lellis ../../sieve-result.h:143: error: expected declaration specifiers or â...â before âboolâ In file included from cmd-vacation.c:27: ../../sieve-message.h:18: warning: empty declaration ../../sieve-message.h:27: error: expected declaration specifiers before âpool_tâ In file included from cmd-vacation.c:29: ext-vacation-common.h:13: error: storage class specified for parameter âvacation_commandâ ext-vacation-common.h:19: error: storage class specified for parameter âvacation_operationâ ext-vacation-common.h:23: error: storage class specified for parameter âvacation_extensionâ cmd-vacation.c:37: error: storage class specified for parameter âvacation_days_tagâ cmd-vacation.c:38: error: storage class specified for parameter âvacation_subject_tagâ cmd-vacation.c:39: error: storage class specified for parameter âvacation_from_tagâ cmd-vacation.c:40: error: storage class specified for parameter âvacation_addresses_tagâ cmd-vacation.c:41: error: storage class specified for parameter âvacation_mime_tagâ cmd-vacation.c:42: error: storage class specified for parameter âvacation_handle_tagâ cmd-vacation.c:53: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_registeredâ cmd-vacation.c:56: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_pre_validateâ cmd-vacation.c:58: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validateâ cmd-vacation.c:60: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_generateâ cmd-vacation.c:63: error: parameter âvacation_commandâ is initialized cmd-vacation.c:63: error: redefinition of parameter âvacation_commandâ ext-vacation-common.h:13: note: previous definition of âvacation_commandâ was here cmd-vacation.c:66: error: âFALSEâ undeclared (first use in this function) cmd-vacation.c:66: error: (Each undeclared identifier is reported only once cmd-vacation.c:66: error: for each function it appears in.) cmd-vacation.c:66: warning: excess elements in struct initializer cmd-vacation.c:66: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:66: warning: excess elements in struct initializer cmd-vacation.c:66: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:67: error: âcmd_vacation_registeredâ undeclared (first use in this function) cmd-vacation.c:67: warning: excess elements in struct initializer cmd-vacation.c:67: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:68: error: âcmd_vacation_pre_validateâ undeclared (first use in this function) cmd-vacation.c:68: warning: excess elements in struct initializer cmd-vacation.c:68: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:69: error: âcmd_vacation_validateâ undeclared (first use in this function) cmd-vacation.c:69: warning: excess elements in struct initializer cmd-vacation.c:69: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:70: error: âcmd_vacation_generateâ undeclared (first use in this function) cmd-vacation.c:70: warning: excess elements in struct initializer cmd-vacation.c:70: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:72: warning: excess elements in struct initializer cmd-vacation.c:72: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:80: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_number_tagâ cmd-vacation.c:83: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_string_tagâ cmd-vacation.c:86: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_stringlist_tagâ cmd-vacation.c:89: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_mime_tagâ cmd-vacation.c:95: error: storage class specified for parameter âvacation_days_tagâ cmd-vacation.c:95: error: parameter âvacation_days_tagâ is initialized cmd-vacation.c:95: error: redefinition of parameter âvacation_days_tagâ cmd-vacation.c:37: note: previous definition of âvacation_days_tagâ was here cmd-vacation.c:97: warning: excess elements in struct initializer cmd-vacation.c:97: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:98: error: âcmd_vacation_validate_number_tagâ undeclared (first use in this function) cmd-vacation.c:98: warning: excess elements in struct initializer cmd-vacation.c:98: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:99: warning: excess elements in struct initializer cmd-vacation.c:99: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:99: warning: excess elements in struct initializer cmd-vacation.c:99: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:99: warning: excess elements in struct initializer cmd-vacation.c:99: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:102: error: storage class specified for parameter âvacation_subject_tagâ cmd-vacation.c:102: error: parameter âvacation_subject_tagâ is initialized cmd-vacation.c:102: error: redefinition of parameter âvacation_subject_tagâ cmd-vacation.c:38: note: previous definition of âvacation_subject_tagâ was here cmd-vacation.c:104: warning: excess elements in struct initializer cmd-vacation.c:104: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:105: error: âcmd_vacation_validate_string_tagâ undeclared (first use in this function) cmd-vacation.c:105: warning: excess elements in struct initializer cmd-vacation.c:105: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:106: warning: excess elements in struct initializer cmd-vacation.c:106: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:106: warning: excess elements in struct initializer cmd-vacation.c:106: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:107: warning: excess elements in struct initializer cmd-vacation.c:107: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:109: error: storage class specified for parameter âvacation_from_tagâ cmd-vacation.c:109: error: parameter âvacation_from_tagâ is initialized cmd-vacation.c:109: error: redefinition of parameter âvacation_from_tagâ cmd-vacation.c:39: note: previous definition of âvacation_from_tagâ was here cmd-vacation.c:111: warning: excess elements in struct initializer cmd-vacation.c:111: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:112: warning: excess elements in struct initializer cmd-vacation.c:112: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:113: warning: excess elements in struct initializer cmd-vacation.c:113: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:113: warning: excess elements in struct initializer cmd-vacation.c:113: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:114: warning: excess elements in struct initializer cmd-vacation.c:114: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:116: error: storage class specified for parameter âvacation_addresses_tagâ cmd-vacation.c:116: error: parameter âvacation_addresses_tagâ is initialized cmd-vacation.c:116: error: redefinition of parameter âvacation_addresses_tagâ cmd-vacation.c:40: note: previous definition of âvacation_addresses_tagâ was here cmd-vacation.c:118: warning: excess elements in struct initializer cmd-vacation.c:118: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:119: error: âcmd_vacation_validate_stringlist_tagâ undeclared (first use in this function) cmd-vacation.c:119: warning: excess elements in struct initializer cmd-vacation.c:119: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:120: warning: excess elements in struct initializer cmd-vacation.c:120: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:120: warning: excess elements in struct initializer cmd-vacation.c:120: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:121: warning: excess elements in struct initializer cmd-vacation.c:121: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:123: error: storage class specified for parameter âvacation_mime_tagâ cmd-vacation.c:123: error: parameter âvacation_mime_tagâ is initialized cmd-vacation.c:123: error: redefinition of parameter âvacation_mime_tagâ cmd-vacation.c:41: note: previous definition of âvacation_mime_tagâ was here cmd-vacation.c:125: warning: excess elements in struct initializer cmd-vacation.c:125: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:126: error: âcmd_vacation_validate_mime_tagâ undeclared (first use in this function) cmd-vacation.c:126: warning: excess elements in struct initializer cmd-vacation.c:126: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:127: warning: excess elements in struct initializer cmd-vacation.c:127: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:127: warning: excess elements in struct initializer cmd-vacation.c:127: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:128: warning: excess elements in struct initializer cmd-vacation.c:128: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:130: error: storage class specified for parameter âvacation_handle_tagâ cmd-vacation.c:130: error: parameter âvacation_handle_tagâ is initialized cmd-vacation.c:130: error: redefinition of parameter âvacation_handle_tagâ cmd-vacation.c:42: note: previous definition of âvacation_handle_tagâ was here cmd-vacation.c:132: warning: excess elements in struct initializer cmd-vacation.c:132: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:133: warning: excess elements in struct initializer cmd-vacation.c:133: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:134: warning: excess elements in struct initializer cmd-vacation.c:134: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:134: warning: excess elements in struct initializer cmd-vacation.c:134: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:135: warning: excess elements in struct initializer cmd-vacation.c:135: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:139: warning: empty declaration cmd-vacation.c:152: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âext_vacation_operation_dumpâ cmd-vacation.c:155: error: expected declaration specifiers or â...â before âsieve_size_tâ cmd-vacation.c:155: error: storage class specified for parameter âext_vacation_operation_executeâ cmd-vacation.c:157: error: parameter âvacation_operationâ is initialized cmd-vacation.c:157: error: redefinition of parameter âvacation_operationâ ext-vacation-common.h:19: note: previous definition of âvacation_operationâ was here cmd-vacation.c:161: error: âext_vacation_operation_dumpâ undeclared (first use in this function) cmd-vacation.c:161: warning: excess elements in struct initializer cmd-vacation.c:161: warning: (near initialization for âvacation_operationâ) cmd-vacation.c:163: warning: excess elements in struct initializer cmd-vacation.c:163: warning: (near initialization for âvacation_operationâ) cmd-vacation.c:174: error: storage class specified for parameter âact_vacation_check_duplicateâ cmd-vacation.c:181: error: expected declaration specifiers or â...â before âboolâ cmd-vacation.c:181: error: storage class specified for parameter âact_vacation_printâ cmd-vacation.c:182: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âact_vacation_commitâ cmd-vacation.c:188: error: parameter âact_vacationâ is initialized cmd-vacation.c:191: warning: excess elements in struct initializer cmd-vacation.c:191: warning: (near initialization for âact_vacationâ) cmd-vacation.c:192: warning: excess elements in struct initializer cmd-vacation.c:192: warning: (near initialization for âact_vacationâ) cmd-vacation.c:193: warning: excess elements in struct initializer cmd-vacation.c:193: warning: (near initialization for âact_vacationâ) cmd-vacation.c:194: warning: excess elements in struct initializer cmd-vacation.c:194: warning: (near initialization for âact_vacationâ) cmd-vacation.c:195: warning: excess elements in struct initializer cmd-vacation.c:195: warning: (near initialization for âact_vacationâ) cmd-vacation.c:195: warning: excess elements in struct initializer cmd-vacation.c:195: warning: (near initialization for âact_vacationâ) cmd-vacation.c:196: error: âact_vacation_commitâ undeclared (first use in this function) cmd-vacation.c:196: warning: excess elements in struct initializer cmd-vacation.c:196: warning: (near initialization for âact_vacationâ) cmd-vacation.c:198: warning: excess elements in struct initializer cmd-vacation.c:198: warning: (near initialization for âact_vacationâ) cmd-vacation.c:205: error: expected specifier-qualifier-list before âsieve_number_tâ cmd-vacation.c:202: warning: empty declaration cmd-vacation.c:219: error: expected specifier-qualifier-list before âstring_tâ cmd-vacation.c:218: warning: empty declaration cmd-vacation.c:231: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_number_tagâ cmd-vacation.c:259: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_string_tagâ cmd-vacation.c:321: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_stringlist_tagâ cmd-vacation.c:344: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_mime_tagâ cmd-vacation.c:363: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_registeredâ cmd-vacation.c:387: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_pre_validateâ cmd-vacation.c:401: error: storage class specified for parameter â_handle_empty_subjectâ cmd-vacation.c:401: error: parameter â_handle_empty_subjectâ is initialized cmd-vacation.c:402: error: storage class specified for parameter â_handle_empty_fromâ cmd-vacation.c:402: error: parameter â_handle_empty_fromâ is initialized cmd-vacation.c:403: error: storage class specified for parameter â_handle_mime_enabledâ cmd-vacation.c:403: error: parameter â_handle_mime_enabledâ is initialized cmd-vacation.c:404: error: storage class specified for parameter â_handle_mime_disabledâ cmd-vacation.c:404: error: parameter â_handle_mime_disabledâ is initialized cmd-vacation.c:406: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validateâ cmd-vacation.c:459: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_generateâ cmd-vacation.c:484: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âext_vacation_operation_dumpâ cmd-vacation.c:544: error: expected declaration specifiers or â...â before âsieve_size_tâ cmd-vacation.c:545: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token cmd-vacation.c:715: error: expected â;â, â,â or â)â before âATTR_UNUSEDâ cmd-vacation.c:734: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token cmd-vacation.c:754: error: expected â;â, â,â or â)â before âATTR_UNUSEDâ cmd-vacation.c:775: error: storage class specified for parameter â_list_headersâ cmd-vacation.c:775: error: parameter â_list_headersâ is initialized cmd-vacation.c:776: warning: initialization from incompatible pointer type cmd-vacation.c:777: warning: excess elements in scalar initializer cmd-vacation.c:777: warning: (near initialization for â_list_headersâ) cmd-vacation.c:778: warning: excess elements in scalar initializer cmd-vacation.c:778: warning: (near initialization for â_list_headersâ) cmd-vacation.c:779: warning: excess elements in scalar initializer cmd-vacation.c:779: warning: (near initialization for â_list_headersâ) cmd-vacation.c:780: warning: excess elements in scalar initializer cmd-vacation.c:780: warning: (near initialization for â_list_headersâ) cmd-vacation.c:781: warning: excess elements in scalar initializer cmd-vacation.c:781: warning: (near initialization for â_list_headersâ) cmd-vacation.c:782: warning: excess elements in scalar initializer cmd-vacation.c:782: warning: (near initialization for â_list_headersâ) cmd-vacation.c:784: warning: excess elements in scalar initializer cmd-vacation.c:784: warning: (near initialization for â_list_headersâ) cmd-vacation.c:789: error: storage class specified for parameter â_my_address_headersâ cmd-vacation.c:789: error: parameter â_my_address_headersâ is initialized cmd-vacation.c:790: warning: initialization from incompatible pointer type cmd-vacation.c:791: warning: excess elements in scalar initializer cmd-vacation.c:791: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:792: warning: excess elements in scalar initializer cmd-vacation.c:792: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:793: warning: excess elements in scalar initializer cmd-vacation.c:793: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:794: warning: excess elements in scalar initializer cmd-vacation.c:794: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:795: warning: excess elements in scalar initializer cmd-vacation.c:795: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:797: warning: excess elements in scalar initializer cmd-vacation.c:797: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:799: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â_is_system_addressâ cmd-vacation.c:819: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â_contains_my_addressâ cmd-vacation.c:857: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â_contains_8bitâ cmd-vacation.c:868: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âact_vacation_sendâ cmd-vacation.c:975: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token cmd-vacation.c:987: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âact_vacation_commitâ ../../rfc2822.h:33: error: old-style parameter declarations in prototyped function definition cmd-vacation.c:1144: error: expected â{â at end of input make[5]: *** [cmd-vacation.lo] Error 1 make[5]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src/lib-sieve/plugins/vacation' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src/lib-sieve/plugins' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src/lib-sieve' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17' make: *** [all] Error 2 Mit freundlichem Gruß Carsten Laun-De Lellis Dipl.-Ing. Elektrotechnik Certified Information Systems Auditor (CISA) Hauptstrasse 13 D-67705 Trippstadt Phone: +49 (6306) 992140 Mobile: +49 (151) 27530865 email: carsten.laun-delellis(a)delellis.net

1 0

[Dovecot] Deleting Index Files and Expire Tool
by Tom Goerger 19 Jul '10

19 Jul '10

Hi, In order to periodically deal with corrupted index files in Dovecot, we routinely will remove a users .imap folder in order to have the indexes rebuild. This hasn't ever caused a problem previously. However, removing the user's index files seems to break the ability of the expire plugin to update the expire stamp correctly, or expunge mail from the user folder. This seems logical, with the reliance of expire on the index.cache files. In testing, actually emptying the trash (since we're only concerned about Trash folders) resets the mailbox to a degree that the expire tool functions properly again. My question is, is there a better way to handle corrupted cache files? Is there a more graceful way to rebuild these using Dovecot tools? Or is there a more specific index file that can be removed, rather than removing the entire hierarchy? We're using Dovecot 1.1.6, on Solaris 10. -- Tom Goerger University of Minnesota - Internet Services

2 3

Re: [Dovecot] SSL / TLS Problem
by Leander S. 19 Jul '10

19 Jul '10

Thanks for your reply. What do you mean by "pipe" See, I can even connect via the console from the outside: |Notebook [~]$ openssl s_client -CApath ~/.cert/XYZ.com/ -connect XYZ.com:993 CONNECTED(00000003) depth=0 /C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com verify error:num=18:self signed certificate verify return:1 depth=0 /C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com verify return:1 --- Certificate chain 0 s:/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com i:/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com --- Server certificate -----BEGIN CERTIFICATE----- MIIC6TCCAlKgAwIBAgIJAN4Jfaj9QgEhMA0GCSqGSIb3DQEBBQUAMIGqMQswCQYD VQQGEwJERTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMREwDwYDVQQHEwhO ZXVicm9ubjEWMBQGA1UEChMNTmV0T2NlYW4gR21iSDETMBEGA1UECxMKV2ViSG9z dGluZzEYMBYGA1UEAxMPc2VydmVyLm5ldG9jZWFuMSQwIgYJKoZIhvcNAQkBFhVh ZG1pbkBzZXJ2ZXIubmV0b2NlYW4wHhcNMTAwNzExMTgwMzQ4WhcNMzAwNzA2MTgw MzQ4WjCBqjELMAkGA1UEBhMCREUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVy ZzERMA8GA1UEBxMITmV1YnJvbm4xFjAUBgNVBAoTDU5ldE9jZWFuIEdtYkgxEzAR BgNVBAsTCldlYkhvc3RpbmcxGDAWBgNVBAMTD3NlcnZlci5uZXRvY2VhbjEkMCIG CSqGSIb3DQEJARYVYWRtaW5Ac2VydmVyLm5ldG9jZWFuMIGfMA0GCSqGSIb3DQEB AQUAA4GNADCBiQKBgQDFiBWAJ893Ocm4dooDHHkNRZcvC4N5qjfx1wywoS2DlnV4 GwBQPYcyewx5ptcjqq863r3rvHhbNeJbcnh8jNATTxto8r2NkadwccXw4LtqpfAS A2dhuYt8zKhiI2tlfZNCzSzDmqid4NuxKiNQGNB6OU6/x2vp0ZFTwstIr7TMAwID AQABoxUwEzARBglghkgBhvhCAQEEBAMCBkAwDQYJKoZIhvcNAQEFBQADgYEAtlPa GQ4Weyi9vlIDLL4PgGsNk4sR4Ca2gbYLTd5HaSkww+BKIfz1OkFEmsNozNSo19PJ WaOp7exCN23j5Z/+qfZSGgUAelJHxRJ0Mc8YmtTuLKaNHxWYBJit3T3n1lbuFENe vdh8oCo6GKjjm7RkbkEvTvdzrOdztXZt3Ij4gLE= -----END CERTIFICATE----- subject=/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com issuer=/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com --- No client certificate CA names sent --- SSL handshake has read 1313 bytes and written 325 bytes --- New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA Server public key is 1024 bit Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : DHE-RSA-AES256-SHA Session-ID: 54DC3526DB721308D460CBAF21D562958D34ED146332F0B4ACBE9E1311633ED1 Session-ID-ctx: Master-Key: 1BCB1FA49855FC38ACB52C2CD8D54594C006116220D66FA0E74F68663AFE3FC09086B9BFB1FE0E515681A2E0DC7C1AFC Key-Arg : None Start Time: 1278952607 Timeout : 300 (sec) Verify return code: 18 (self signed certificate) --- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=CRAM-MD5] NetOcean MailSystem ^C Notebook [~]$| Am 12.07.10 19:11, schrieb Daniel Petre: > dude, whats the pipe at the end of the mail.key location? > >> It's always the same when it fails ... >> >> >> And this is how my dovecot.conf looks like: >> >> [...] >> >> |## >> ## SSL settings >> ## >> ssl = yes >> ssl_cert_file = /etc/ssl/mail/mail.cert >> ssl_key_file = /etc/ssl/mail/mail.key| >> >> [...] >> >> >> Thank you

4 6

[Dovecot] Plugins/Virtual for save searches & last 30 days incomming Email
by No body ist Perfect 19 Jul '10

19 Jul '10

Hello! How can i configure the virtal-dovecot (virtal folder) file for search the complete Mailbox for email not older as 30 Days ? Thanks a lot

2 1

[Dovecot] Proxy IMAP/POP/ManageSieve/SMTP in a large cluster enviroment
by Aliet Santiesteban Sifontes 19 Jul '10

19 Jul '10

Hi to all in the list, we are trying to do some tests lab for a large scale mail system having this requirements: - Scale to maybe 1million users(Only for testing). - Server side filters. - User quotas. - High concurrency. - High performance and High Availability. We plan to test this using RHEL5 and maybe RHEL6. As a storage we are going to use an HP EVA 8400 FC(8 GB/s) We defined this functional roles. 1- Outgoing SMTP gateway servers. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using Postfix Latest version Amavisd-new Clamav Spamassasin maybe some other filters. 2- Incomming SMTP gateway servers. - Load balanced with Piranha LVS using Direct Routing. - RHEL5/6 using Postfix Latest version Amavisd-new Clamav Spamassasin( n servers) maybe some other filters. 3- Webmail Cluster farm. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using RHCS Active/Active. Apache2 PHP5 Horde. 4- Openldap load balanced openldap cluster. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using Openldap. 5- IMAP/POP/ManageSieve/SMTP Proxy or Director. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using Dovecot - Postfix(Director or Proxy). 6- Mail backend. - ( n servers)RHEL5/6 using Dovecot. Now for functional role 6 "Mail Backend" we have some dilemmas. - Recommended scalable filesystem to use for such scenario(Clustered or not). -GFS2?? We have very bad experiences with GFS1 and maildir, GFS2 doesn't seems to improve this also. Using some techniques for session afinity with a backend server seems to help with the locking problems of GFS and the cache. Using GFS many IMAP SMTP servers can in parallel write or read to user mailboxes, if GFS can perform well we prefer this, will have to proxy o use director for the cache problem. - Ext4, Ext3 well tested with many setups but only one backend server can access one ext4 lun, so we have to proxy a user always to a ip backend address or VIP in a case of failure cluster software has to move the server to another node, the cluster service is formed by a IP Address and one or many Luns wich moves from node to node in a case of failure. - Recommended scalable method for partition divition. - Directory Hashing(How it actually works the theory behind this), we see the wiki but we need to understand the theory to balance the directory structure. - Using some criteria ex Lun1(a-h users), Lun2(i-m users).... - Proxy or Director is a must for a Clustered Filsystem or for the solution of a user belonging to one server. - In case we use a Proxy with dovecot we know we can use it with IMAP/POP but are not sure for ManageSieve and more important for SMTP. The question is, how can we proxy for the same user IMAP/POP/ManageSieve and SMTP delivery to mailbox at the same time, can the incoming mail gateways send the email to the proxy servers and dovecot proxy the request for smtp or lmtp appply the same proxy criteria that uses for the protocols IMAP and POP and send the email to the correct backend server and this server do the final delivery?? I mean proxy all the protocols for a user IMAP/POP/SMTP-LMTP?? Any example... Right now we have doubts on this stuff, we are really going to appreciate any help or advice on this... best regards

4 4

[Dovecot] Haha wow, thats freakin cool... mdbox
by Brandon Lamb 19 Jul '10

19 Jul '10

It didnt really click until I had a "ls -ald *" on watch while I moved messages around folders using mdbox... I moved about 200 first to an Archive folder, and scratched my head wondering why i didnt see any new m.* files being created after the move. So then I moved some 5k other messages from other folders to my archive folder... Then it dawned on me, how damn cool, the data never changes, dovecot just updates its index of what folder the message is in?! That is awesome! Also, I ended up answering my own question on the 2m mdbox_rotate_size, if a 10 meg email comes through it will write a 10 meg file, so thats cool too.

4 4