- dovecot - dovecot.org

[Dovecot] Only using LMTP-delivery, where should domain & user aliases be configured, Dovecot or MTA conf?
by mephistopheles＠operamail.com 06 Oct '11

06 Oct '11

I have my MTA (Postfix) check Dovecot2 LMTP for existing users. No other delivery is done; this is a virtual/LMTP-only setup. I define known users in a Dovecot passwd-file, specified in conf.d/10-auth.conf passdb { args = ... username_format=%n /stor01/vmail/auth.d/%d/passwd e.g., vi /stor01/vmail/auth.d/mx1.domain1.com/passwd myuser:{scheme}####:... mail to: myuser(a)mx1.domain1.com is correctly auth'd and stored. I want two things to happen: (1) all mail to existing-users "@domain1.com" gets re-routed to "@mx1.domain1.com", i.e., map: myuser(a)domain1.com -> myuser(a)mx1.domain1.com and is accepted/not-rejected ONLY if 'myuser' is defined as a user in mx1.domain1.com/passwd and, (2) specific 'user' aliasing/remapping within a given domain, i.e. map: whatever(a)mx1.domain1.com -> myuser(a)mx1.domain1.com as long as 'myuser' is a defined user in mx1.domain1.com In these cases, where should I assign domain & mail aliases, Dovecot or the MTA's conf ?

1 0

[Dovecot] trouble setting up director, "invalid argument" for connect() call
by Jim Lawson 05 Oct '11

05 Oct '11

Hi Timo & everyone, I'm trying out a 2-node director setup, but I keep getting the following error: Oct 3 16:11:29 imapdir1 dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) Oct 3 16:11:34 imapdir1 dovecot: director: Error: connect(132.198.100.150:9090) failed: Invalid argument Oct 3 16:11:41 imapdir1 last message repeated 3 times Both nodes report this error. The director on each node is listening on port 9090 just fine: > [root@imapdir1 ~]# nc imapdir2 9090 > VERSION director 1 0 > ME 127.0.0.1 9090 > [root@imapdir2 ~]# nc imapdir1 9090 > VERSION director 1 0 > ME 127.0.0.1 9090 "doveadm director ring status" always reports failure of the peer: > [root@imapdir1 ~]# doveadm director ring status > director ip port type last > failed > 127.0.0.1 9090 self > never > 132.198.100.150 9090 2011-10-04 > 13:28:55 > [root@imapdir2 ~]# doveadm director ring status > director ip port type last > failed > 127.0.0.1 9090 self > never > 132.198.100.149 9090 2011-10-04 > 13:24:08 Has anyone else seen this? FWIW, a single-node director works fine, proxying IMAP, LMTP and POP. I'm guessing I have a broken config, but if I do I can't figure it out. Hope I'm not missing something *too* obvious... Here's doveconf -n from imapdir1: # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-274.3.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.7 (Tikanga) base_dir = /var/run/dovecot/ director_mail_servers = penguina.uvm.edu penguinb.uvm.edu penguinc.uvm.edu director_servers = imapdir1.uvm.edu imapdir2.uvm.edu lmtp_proxy = yes login_trusted_networks = 132.198.101.211,132.198.101.212,132.198.101.213,132.198.101.214,132.198.101.215,132.198.101.216,132.198.100.45,132.198.100.46,132.198.100.47 passdb { args = proxy=y nopassword=y protocol=smtp driver = static } service auth { unix_listener auth-userdb { group = mail mode = 0660 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { client_limit = 1 inet_listener lmtp { port = 24 } unix_listener /var/lib/dovecot/lmtp-socket { group = root mode = 0600 user = root } } Best, Jim

1 1

[Dovecot] Dovecot + managesieve + ldap not working
by Philip Brechler 05 Oct '11

05 Oct '11

Hi, I want to use managesieve in my dovecot server which uses virtual users and a ldap for the users. This is in my dovecot.conf: # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-x86_64-jb1 x86_64 Debian 6.0.1 ext3 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): * listen(imap): * listen(managesieve): *:2000 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(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_uid: 5000 mail_gid: 5000 mail_location: maildir:/var/mail/%u/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve lda: postmaster_address: pbrechler(a)piratenfraktion-berlin.de mail_plugins: sieve mail_plugin_dir: /usr/lib/dovecot/modules/lda auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: pam passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf 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_dir: /var/mail/sievescript/%u_scripts/ sieve_extensions: +imapflags And my ldap conf: hosts = ldap.piratenfraktion-berlin.de auth_bind = yes auth_bind_userdn = uid=%u,ou=people,dc=domain,dc=de ldap_version = 3 base = dc=domaindc=de deref = never scope = subtree user_attrs = uid=mail=maildir:/var/mail/%$/Maildir/ user_filter = (|(&(objectClass=organizationalPerson)(uid=%Ln))(&(objectClass=organizationalPerson)(mail=%Lu))) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=organizationalPerson)(uid=%u)) If I try to talk to managesieve with telnet this happens: Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. "IMPLEMENTATION" "dovecot" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator- i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date imapflags" "SASL" "PLAIN LOGIN" "STARTTLS" "NOTIFY" "mailto" "VERSION" "1.0" OK "Dovecot ready." # ca. 2 Seconds pause AUTHENTICATE "PLAIN" "xxxxxxxxxxxxx" BYE "Internal error occured. Refer to server log for more information. [2011-10-02 00:48:09]" Connection closed by foreign host. Dies is a log reading 2011-10-02 00:48:09 MANAGESIEVE(user): Fatal: Failed to create sieve storage with data: /var/mail/sievescript/user_scripts But the permissions are 775 dovecot:dovecot and the system tells me that dovecot was the last user who had access to the directory. Can someone help me? Thanks! kind regards Philip Brechler

2 3

[Dovecot] doveadm(user001): Fatal: passdb lookup failed
by mailing lists 05 Oct '11

05 Oct '11

Hello all, why I can run whis command: imap1:~ # doveadm user user001 userdb: user001 mail : maildir:/var/maildir/vol04/4/46/user001 home : /var/mailfilter/vol04/4/46/user001 quota_rule: *:bytes=100000000 but not this one: imap1:~ # doveadm quota get -u user001 doveadm(user001): Error: user user001: Auth PASS lookup failed doveadm(user001): Fatal: passdb lookup failed what I'm missing ? /-------------------/ imap1:/etc/dovecot # grep ^[^#] dovecot-ldap.conf.ext uris = ldap://ldap.example.com dn = cn=admin,dc=example,dc=com dnpass = secret sasl_bind = no tls = no auth_bind = yes ldap_version = 3 base = dc=example,dc=com deref = never scope = subtree user_attrs = mailbox=mail=maildir:/var/maildir/%$,homeFilter=home,mailQuota=quota_rule=*:bytes=%$ user_filter = (&(objectClass=CourierMailAccount)(uid=%n)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=CourierMailAccount)(uid=%n)) iterate_filter = (objectClass=CourierMailAccount) imap1:/etc/dovecot # dovecot -n # 2.0.14: /etc/dovecot/dovecot.conf # OS: Linux 2.6.34.7-0.7-xen x86_64 openSUSE 11.3 (x86_64) auth_debug = yes auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no doveadm_proxy_port = 24244 doveadm_socket_path = localhost:24244 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_fsync = always mail_gid = 5000 mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl quota notify quota = maildir:User Quota quota_exceeded_message = Quota exceded quota_rule2 = Trash:storage=+50M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u mail_uid = 5000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes namespace { inbox = yes list = yes location = prefix = separator = . subscriptions = yes } namespace { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . subscriptions = no } namespace { list = children location = maildir:/var/virtual-maildir/%%n:INDEX=~/shared.%%n prefix = shared.%%n. separator = . subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/maildir/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_fields = uid box msgid from subject size vsize flags mail_plugins = " mail_log notify" sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = nonresponse(a)example.com service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service doveadm { inet_listener { port = 24244 } } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { port = 24 } unix_listener lmtp { group = vmail mode = 0666 user = vmail } } service pop3-login { inet_listener pop3 { port = 110 } } service pop3 { process_limit = 1024 } service quota-warning { executable = script /etc/dovecot/quota-warning.sh user = vmail } ssl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = acl quota notify sieve } protocol lda { mail_plugins = acl quota notify sieve } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl quota notify imap_acl autocreate imap_quota } protocol pop3 { pop3_uidl_format = %v-%u } local 100.1.245.101/28/28 { doveadm_password = secret }

1 0

[Dovecot] sieve vacation reply
by Wojciech Giel 04 Oct '11

04 Oct '11

Hi, I'm configuring postfix with dovecot and roundcube. I'm using flat files as passwdb userdb. Everything works fine except sieve vacation reply. when i send mail from ex. user dennis to tytus I get "discarding vacation response for message implicitly delivered to". What Am i doing wrong? thanks sieve: using sieve path for user's script: /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: opening script /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: executing compiled script /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: msgid=<20110517155641.GA3452(a)badger.example.com>: discarding vacation response for message implicitly delivered to <tytus@badger> /etc/postfix/main.cf ... mailbox_command = /usr/lib/dovecot/deliver -n -m "${EXTENSION}" ... # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.1 log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): * listen(imap): * listen(managesieve): 127.0.0.1:2000 ssl_ca_file: /etc/postfix/ssl/cacert.pem ssl_cert_file: /etc/postfix/ssl/servercrt.pem ssl_key_file: /etc/postfix/ssl/serverkey.pem ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_location: maildir:~/Maildir:INDEX=~/Maildir/indexes mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota autocreate mail_plugins(imap): quota imap_quota autocreate mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): tb-extra-mailbox-sep netscape-eoh delay-newmail outlook-idle imap_client_workarounds(imap): tb-extra-mailbox-sep netscape-eoh delay-newmail outlook-idle imap_client_workarounds(managesieve): lda: postmaster_address: postmaster mail_plugins: sieve quota autocreate quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r log_path: /var/log/sieve.log auth default: mechanisms: plain login cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd-file args: scheme=cram-md5 /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve autocreate: INBOX autocreate2: Sent autocreate3: Trash autocreate4: Drafts autocreate5: Junk autosubscribe: INBOX autosubscribe2: Sent autosubscribe3: Trash autosubscribe4: Drafts autosubscribe5: Junk quota: maildir:User quota quota_rule: Trash:storage=10M quota_warning: storage=85%% /usr/bin/dovecot-quota-warning.sh 85 quota_warning2: storage=90%% /usr/bin/dovecot-quota-warning.sh 90 quota_warning3: storage=95%% /usr/bin/dovecot-quota-warning.sh 95

5 7

[Dovecot] Missing man page for doveadm move
by Jeetu 04 Oct '11

04 Oct '11

Hi, i cant see man pages for doveadm-move, though the command "doveadm move ..." works on new version of dovecot. http://hg.dovecot.org/dovecot-2.0/rev/d7a02077d91f -- -Jeetu

2 2

[Dovecot] What best decision to make for flatfiles or SQL when I use Dovecot2 + Postfix together?
by terryjames9461＠mm.st 04 Oct '11

04 Oct '11

Hello, I'm moving my mail server from Exchange to an opensource one. After a bunch of reading, I decided on building a Dovecot2 + Postfix server in a VirtualUsers-only + Multiple-domains configuration. Since my messages will be stored by Dovecot, and the documentation is really good, I figured that it's smartest to configure Dovecot, then make Postfix 'fit' to it, sharing the data files that way. I read through lots of the Dovecot wiki for v2. There are many ways for storing the database data. My goal is to only have data in one instances, used by both Postfix & Dovecot. I'm a little confused about: to do that sharing-in-one-place, do I have to use SQL or can I use the flatfiles like passwd-db? I think for sure someone already decided the best approach for this, and maybe I'm not understanding the logic to it. The data I think I need to share are: users (user(a)domain.com) passwords user aliases (mapping user2(a)domain.com -> user1(a)domain.com) domains domain aliases (domain.com also receives email for domain2.com) And I think all of this can be in passwd-db in Dovecot. But I also want to make sure that Postfix ONLY accepts email for users/domains that exist, so it has to read that data too. Can I do this that way with the flatfiles? Or do I have to use the SQL approach? TJ

12 20

Re: [Dovecot] SSL only for external connections
by Joseph Tam 04 Oct '11

04 Oct '11

On Sun, 2 Oct 2011, Simon Brereton writes: > I don't have that file. Part of the problem is that I'm confused > between protocols and wrappers and interfaces :) Dick and Michael have > persuaded me that it's just easier to for Horde not to ask for TLS on > port 143 - because that's in fact what I was doing - and it's > pointless. > > Nonetheless, I think it would be nice to tell Dovecot listen on the > local interface for IMAP. Listen on the external interface for IMAP, > IMAPS, POP and POP3S. But if there's not simple way to do that I don't > have a valid use-case for doing it right now. I got into this thread rather late so maybe I missed something here. If you have different policies for your interface, you can run two different instances of dovecot (with 2 different base directories and sets of configuration files). I haven't tried it, but maybe it's also possible have interface specific CAPA strings and remove STARTTLS. Dovecot will support unencrypted sessions over the localhost interface, but your webmail seems to opportunistcally use it when offered, so don't offer it. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Intermittent authentication failures
by Eric Shubert 03 Oct '11

03 Oct '11

I'm running dovecot with vpopmail. Here's the configuration: [root@wong log]# dovecot -n # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-238.9.1.el5 i686 CentOS release 5.6 (Final) auth_cache_size = 32 M auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Lu first_valid_uid = 89 log_path = /var/log/dovecot.log login_greeting = Dovecot toaster ready. mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes mmap_disable = yes namespace { inbox = yes location = prefix = separator = . type = private } passdb { args = cache_key=%u webmail=127.0.0.1 driver = vpopmail } plugin/quota = maildir protocols = imap ssl_cert = </var/qmail/control/servercert.pem ssl_key = </var/qmail/control/servercert.pem userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q driver = vpopmail } protocol imap { imap_client_workarounds = delay-newmail } Most clients use TLS and PLAIN login for verification, which works flawlessly. I also run SquirrelMail that is slightly dated and has no TLS capability, so it is using CRAM-MD5. CRAM-MD5 works sometimes: Sep 30 08:15:43 imap-login: Info: Login: user=<userA(a)domain.com>, method=CRAM-MD5, rip=192.168.252.8, lip=192.168.252.14, mpid=20301 but (seemingly more frequently) the authentication fails: Sep 30 08:16:41 imap-login: Info: Aborted login (auth failed, 1 attempts): user=<userA(a)domain.com>, method=CRAM-MD5, rip=192.168.252.8, lip=192.168.252.14 I restarted dovecot, and that apparently cleared the problem for one user, but not others. Is this perhaps a bug in dovecot, or would the problem lie with vpopmail? TIA for any pointers. -- -Eric 'shubes'

2 6

[Dovecot] Multiple LDAP authentication servers
by Romer Ventura 03 Oct '11

03 Oct '11

Hello, We are performing a Domain migration and I was wondering if there was any way to get Dovecot to authenticate to more than 1 LDAP server? Currently dovecot is configure to query the "mail" attribute from Active Directory and when found it binds with the credentials the user provided. This works fine, but when migrating user accounts, they get disabled in the source domain so that the user can no longer log on to it. But disabling the account in the source domain, causes the user to be unable to use his email account. Is there any way to get dovecot to try a second LDAP server if the first one fails to authenticate..? ~# dovecot -n # 1.2.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.29-xs5.5.0.15 i686 Debian 5.0.4 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps imap ssl_cert_file: /etc/ssl/certs/smtpd.crt ssl_key_file: /etc/ssl/private/smtpd.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: postfix mail_privileged_group: mail mail_uid: vmail mail_gid: vmail mail_location: maildir:/srv/mail/vmail/%Ud/%Ln/Maildir mbox_write_locks: fcntl dotlock imap_client_workarounds: delay-newmail outlook-idle netscape-eoh lda: postmaster_address: postmaster(a)h-st.com auth_socket_path: /var/run/dovecot/auth-master log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver-info.log auth default: mechanisms: plain login passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail Thanks -------- Romer Ventura

2 4

[Dovecot] clarifications on shared mailboxes
by Frank Bonnet 03 Oct '11

03 Oct '11

Hello I need some clarifications on shared mailboxes. Actually we use MBOX format with "real" unix users , but I've been asked to create some shared mailboxes for some users who need to have some for their working groups. What would be the best way to create those shared mailboxes ? Would it be possible to create some "shared space" on the server in maildir format to get advantage of the last seen flag ? If yes some config examples would be a great help. See attach the doveconf -n output ( certificates names have been obscured ;-) ) Thank you.

1 0

[Dovecot] 1.2.17 Program terminated with signal 11, Segmentation fault.
by Andrew Hearn 03 Oct '11

03 Oct '11

Hello, We've had seg faults a couple of times a day on our servers, we upgraded to 1.2.17 and still have them. running a coredump through dbg says: Reading symbols from /usr/local/libexec/dovecot/imap-login...done. [New Thread 27962] Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff083f4000 Core was generated by `imap-login -D'. Program terminated with signal 11, Segmentation fault. #0 0x000000000041388b in io_file_unlink (_io=<value optimized out>, closed=true) at ioloop.c:70 70 if (io->next != NULL) dovecot -n is at http://pastebin.ca/SQjrseJD (pass timo) Linux 2.6.18-274.3.1.el5 #1 SMP Tue Sep 6 20:13:52 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux We use NFS for mail store, and ramdisk for dovecot indexes. We do run the mail_log plugin. Let me know if you need any more info though. -- Andrew Hearn. AAISP Technical Support Team Leader Tel: 03333 400999

1 0

[Dovecot] problem with getting outlook to work with IMAP server
by Daminto Lie 03 Oct '11

03 Oct '11

Hi, I am having difficulty in getting the outlook 2010 to connect to my server running on Ubuntu Server 10.04. I can login to Squirrelmail webmail, and am able to send & receive emails through squirrelmail with no problem whatsoever. However, this morning, I was trying to add a new account for the same user on Outlook 2010 and I got the following error from outlook as follows Send test e-mail message: Your outgoing (SMTP) e-mail server has reported an internal error. The server responded: 554 5.7.7 No Spoofing Allowed. I then, went to check /var/log/mail.log and I found the following Oct 3 12:19:27 mymailServer dovecot: auth(default): ldap(sbernett,50.4.39.163): pass search: base=ou=accounts,dc=example,dc=com scope=subtree filter=(&(objectClass=posixAccount)(uid=sbernett)) fields=uid,userPassword,homeDirectory,uidNumber,gidNumber Oct 3 12:19:27 mymailServer dovecot: auth(default): ldap(sbernett,50.4.39.163): result: uid(user)=sbernett uidNumber(userdb_uid)=106 gidNumber(userdb_gid)=106 userPassword(password)={CRYPT}xGHI86Ktls homeDirectory(userdb_home)=/home/vmail/sbernett Oct 3 12:19:27 mymailServer dovecot: auth(default): client out: OK#0111#011user=sbernett Oct 3 12:19:27 mymailServer dovecot: auth(default): master in: REQUEST#0114#0112686#0111 Oct 3 12:19:27 mymailServer dovecot: auth(default): passwd(sbernett,50.4.39.163): lookup Oct 3 12:19:27 mymailServer dovecot: auth(default): passwd(sbernett,50.4.39.163): unknown user Oct 3 12:19:27 mymailServer dovecot: auth(default): master out: USER#0114#011sbernett#011uid=106#011gid=106#011home=/home/vmail/sbernett Oct 3 12:19:27 mymailServer dovecot: imap-login: Login: user=<sbernett>, method=PLAIN, rip=50.4.39.163, lip=50.4.39.164 Oct 3 12:19:27 mymailServer dovecot: IMAP(sbernett): Disconnected in IDLE bytes=9/292 Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: warning: No server certs available. TLS won't be enabled Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: connect from localhost[127.0.0.1] Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: 182292400AE: client=localhost[127.0.0.1] Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: lost connection after DATA (0 bytes) from localhost[127.0.0.1] Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: disconnect from localhost[127.0.0.1] Next, I tried to see if there are any the difference in the mail.log when logging into the squirrelmail (which is working for me) Oct 3 12:31:32 mymailServer dovecot: auth(default): ldap(sbernett,127.0.0.1): pass search: base=ou=accounts,dc=example,dc=com scope=subtree filter=(&(objectClass=posixAccount)(uid=sbernett)) fields=uid,userPassword,homeDirectory,uidNumber,gidNumber Oct 3 12:31:32 mymailServer dovecot: auth(default): ldap(sbernett,127.0.0.1): result: uid(user)=sbernett uidNumber(userdb_uid)=106 gidNumber(userdb_gid)=106 userPassword(password)={CRYPT}xGHI86Ktls homeDirectory(userdb_home)=/home/vmail/sbernett Oct 3 12:31:32 mymailServer dovecot: auth(default): client out: OK#0111#011user=sbernett Oct 3 12:31:32 mymailServer dovecot: auth(default): master in: REQUEST#0114#0112485#0111 Oct 3 12:31:32 mymailServer dovecot: auth(default): passwd(sbernett,127.0.0.1): lookup Oct 3 12:31:32 mymailServer dovecot: auth(default): passwd(sbernett,127.0.0.1): unknown user Oct 3 12:31:32 mymailServer dovecot: auth(default): master out: USER#0114#011sbernett#011uid=1004#011gid=1004#011home=/home/vmail/sbernett Oct 3 12:31:32 mymailServer dovecot: imap-login: Login: user=<sbernett>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured The only thing I noticed different between the two is the IP addresses in rip and lip. Is there a way to tell the IMAP server to allow the remote IP addresses to connect. Here is my dovecot.conf # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-34-generic-pae i686 Ubuntu 10.04.3 LTS ext4 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap listen: *:143 ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 106 last_valid_uid: 1000 mail_privileged_group: mail mail_location: maildir:/home/vmail/%u/Maildir mbox_write_locks: fcntl dotlock mail_plugins: quota imap_quota imap_client_workarounds: delay-newmail outlook-idle netscape-eoh lda: postmaster_address: postmaster(a)mailtest.dyndns-free.com mail_plugins: quota sendmail_path: /usr/lib/sendmail rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot-auth-master auth default: mechanisms: plain login username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: passwd userdb: driver: static args: uid=106 gid=106 home=/home/vmail/%u allow_all_users=yes 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: vmail plugin: quota: maildir quota_rule: *:storage=3GB quota_rule2: Trash:storage=20%% quota_rule3: Spam:storage=10%% quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 Here is my postfix.cf myhostname = mymailserver mydomain = example.com mydestination = localhost.$mydomain,localhost,$mydomain,$myhostname local_recipient_maps = ldap:/etc/postfix/ldap-user-auth.cf virtual_transport = dovecot virtual_mailbox_domains = vexample.com virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual_mailboxes virtual_minimum_uid = 100 virtual_uid_maps = static:106 virtual_gid_maps = static:106 relayhost = mynetworks = 127.0.0.0/8, 192.168.1.0/24, 50.4.39.163, 50.4.39.164 mynetworks_style = subnet mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 mail_spool_directory = /var/spool/mail smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanomymous smtpd_tls_auth_only = yes smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,reject_sender_login_mismatch smtpd_sasl_local_domain = vexample.com dovecot_destination_recipient_limit = 1 Any help would be greatly appreciated. Thank you

1 0

Re: [Dovecot] FTS and compound searches
by Nikolai Schupbach 01 Oct '11

01 Oct '11

>> New subscriber here. I noticed that the FTS index is not used in compound searches. >> Is this expected? Tested in 2.0.0 and 2.0.8: > >Yep. It's been in TODO for a while. I know this thread is quite old, but we have the same issue with v2.0.14 and squat. Would this issue also affect the Solr FTS backend? Thanks, Nikolai.

2 1

Re: [Dovecot] Error message in log
by Joseph Tam 01 Oct '11

01 Oct '11

On Fri, 30 Sep 2011, Knute Johnson wrote: > I'm getting the following message in my log; > > dovecot: IMAP(knute): > fchown(/home/knute/mail/.imap/INBOX/dovecot.index.tmp, -1, 8(mail)) > failed: Operation not permitted (egid=1000(knute), group based on > /var/mail/knute): 4 Time(s) > > I got these once before on the /var/mail/user files and changed the > permissions to 600. /home/knute/mail/.imap/INBOX is 770 and the index > files are 600. Is this a problem with the directory privilege? Probably. This was discussed a few times before. Check the mailing list archives. Dovecot tries to retain the same file access for the indices as the mailbox/message file it indexes; if the permissions allow access to the group, but the owner is not part of that group, then the dovecot process (which sets UID to the owner) cannot recreate the same permissions, hence the error. Either change the group ownership of "/var/mail/knute", put user "knute" in group "mail", or chmod it to 0600. The last one is probably the best solution. And fix the problem that created these permissions in the first place. Check your other users (if you have any) for the same situation. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: [Dovecot] SSL only for external connections
by Dick Middleton 30 Sep '11

30 Sep '11

On 09/30/11 20:25, Simon Brereton wrote: > But the question remains - if only because it's now there - how does one limit services effectively in Dovecot. In Courier it was fairly easy and well documented. There's no reason for me to offer IMAPS or POP3S to localhost (because of the certificate issue) and there's also no reason for me to offer POP3 to localhost either. > > For posterity and for my own edification it would be nice to know how to do that. I don't think you can do that. However if you don't want to use tls/ssl just connect to port 143 plain. I don't know about horde but Roundcube you use tls://localhost, ssl://locahost or just localhost. i.e the choice is with the client not the server. Dick

3 2

Re: [Dovecot] SSL only for external connections
by Michael M Slusarz 30 Sep '11

30 Sep '11

Quoting Simon Brereton <simon.brereton(a)buongiorno.com>: >> -----Original Message----- >> From: dovecot-bounces(a)dovecot.org [mailto:dovecot- >> bounces(a)dovecot.org] On Behalf Of Stan Hoeppner >> On 9/30/2011 12:34 PM, Simon Brereton wrote: >> >> -----Original Message----- >> >> From: dovecot-bounces(a)dovecot.org [mailto:dovecot- >> >> bounces(a)dovecot.org] On Behalf Of Terry Carmen >> > >> >> >> >> If SSL/TLS works from the outside, but not the inside, you should >> >> probably find out why and fix that instead. >> > >> > You'd think so - but since I don't actually need TLS from the >> inside, >> > and given my skill level - disabling it seems easier :) >> >> You don't need TLS/SSL from the outside either, if this is strictly a >> webmail box. In this case, configure Apache/lighttpd+Horde to only >> accept HTTPS connections from the outside, and configure Horde to >> connect via the Dovecot localhost:143 listener. This is how I've >> been doing it with Roundcube for years. Works like a champ. > > It's not strictly a webmail box though. IMAP clients (fixed and > mobile) connect to it. So what I'd like is IMAP, IMAPS, POP3 and > POP3S on the outside and IMAP only on the local host (there's no > actual reason to offer POP to the localhost either... You can also configure the MUA (e.g. Horde) to not use a secure connection, as opposed to turning off features on the server level. michael

2 1

Re: [Dovecot] SSL only for external connections
by Michael M Slusarz 30 Sep '11

30 Sep '11

Quoting Simon Brereton <simon.brereton(a)buongiorno.com>: > But the question remains - if only because it's now there - how does > one limit services effectively in Dovecot. In Courier it was fairly > easy and well documented. There's no reason for me to offer IMAPS > or POP3S to localhost (because of the certificate issue) and there's > also no reason for me to offer POP3 to localhost either. > > For posterity and for my own edification it would be nice to know > how to do that. At a minimum, you can't disable TLS. If you disable TLS support in dovecot, the server is no longer IMAP 4rev1 compliant (see RFC 3501 [6.1.1] - STARTTLS MUST be supported by server). michael

1 0

[Dovecot] SSL only for external connections
by Terry Carmen 30 Sep '11

30 Sep '11

If SSL/TLS works from the outside, but not the inside, you should probably find out why and fix that instead. What is the actual error text? Terry -- Terry Carmen CNY Support, LLC https://www.cnysupport.com

3 3

Re: [Dovecot] SSL only for external connections
by Stan Hoeppner 30 Sep '11

30 Sep '11

On 9/30/2011 12:34 PM, Simon Brereton wrote: >> -----Original Message----- >> From: dovecot-bounces(a)dovecot.org [mailto:dovecot- >> bounces(a)dovecot.org] On Behalf Of Terry Carmen > >> >> If SSL/TLS works from the outside, but not the inside, you should >> probably find out why and fix that instead. > > You'd think so - but since I don't actually need TLS from the inside, and given my skill level - disabling it seems easier :) You don't need TLS/SSL from the outside either, if this is strictly a webmail box. In this case, configure Apache/lighttpd+Horde to only accept HTTPS connections from the outside, and configure Horde to connect via the Dovecot localhost:143 listener. This is how I've been doing it with Roundcube for years. Works like a champ. With encrypted sessions between browser and web server, and both Horde and Dovecot running on the same host, you don't need to, nor want to, use IMAPS. -- Stan

2 1

[Dovecot] SSL only for external connections
by Simon Brereton 30 Sep '11

30 Sep '11

Hi I'm running dovecot 1:1.2.15-7 and php webmail application is throwing errors when connecting to IMAP with TLS. Is there away to disable SSL/TLS for localhost connections? I googled, but didn't see anything specific. Can I assume that it's as simple as setting ssl_listen = to the external IP address(es) and leaving listen = * as it is? Thanks. Simon

1 0

[Dovecot] Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof)
by mailing lists 30 Sep '11

30 Sep '11

Hello all, today I got this crash from dovecot (2.0.14) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f9aa) [0x7f18f10299aa] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f9f6) [0x7f18f10299f6] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f18f1003211] -> dovecot/lmtp(+0x7a4f) [0x7f18f1982a4f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xcb) [0x7f18f103590b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5b) [0x7f18f103680b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f18f1035768] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f18f1023423] -> dovecot/lmtp(main+0x183) [0x7f18f197fa93] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f18f0ca8b7d] -> dovecot/lmtp(+0x4819) [0x7f18f197f819] Sep 29 14:09:32 imap1 dovecot: master: Error: service(lmtp): child 17693 killed with signal 6 (core dumps disabled) /-----------------/ # dovecot -n -c /etc/dovecot-director/dovecot.conf # 2.0.14: /etc/dovecot-director/dovecot.conf # OS: Linux 2.6.34.7-0.7-xen x86_64 openSUSE 11.3 (x86_64) auth_debug = yes auth_verbose = yes base_dir = /var/run/dovecot-director/ director_mail_servers = 100.1.245.101 100.1.245.105 director_servers = 100.1.245.101:9091 100.1.245.105:9091 100.1.241.204:9091 disable_plaintext_auth = no doveadm_proxy_port = 24245 lmtp_proxy = yes mail_debug = yes mail_fsync = always mail_gid = 5000 mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl mail_uid = 5000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes passdb { args = proxy=y nopassword=y driver = static } plugin { acl = vfile sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp pop3 service auth { unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9091 } unix_listener director-userdb { mode = 0666 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 24245 } } service imap-login { executable = imap-login director inet_listener imap { port = 10143 } } service lmtp { inet_listener lmtp { port = 1024 } } service pop3-login { executable = pop3-login director inet_listener pop3 { port = 10110 } } ssl = no verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb passdb { args = proxy=y nopassword=y port=24 driver = static } } protocol imap { mail_max_userip_connections = 100 } local 100.1.245.101/28/28 { doveadm_password = secret }

2 1

[Dovecot] Error message in log
by Knute Johnson 30 Sep '11

30 Sep '11

I'm getting the following message in my log; dovecot: IMAP(knute): fchown(/home/knute/mail/.imap/INBOX/dovecot.index.cache.lock, -1, 8(mail)) failed: Operation not permitted (egid=1000(knute), group based on /var/mail/knute): 1 Time(s) dovecot: IMAP(knute): fchown(/home/knute/mail/.imap/INBOX/dovecot.index.log.newlock, -1, 8(mail)) failed: Operation not permitted (egid=1000(knute), group based on /var/mail/knute): 2 Time(s) dovecot: IMAP(knute): fchown(/home/knute/mail/.imap/INBOX/dovecot.index.tmp, -1, 8(mail)) failed: Operation not permitted (egid=1000(knute), group based on /var/mail/knute): 4 Time(s) I got these once before on the /var/mail/user files and changed the permissions to 600. /home/knute/mail/.imap/INBOX is 770 and the index files are 600. Is this a problem with the directory privilege? Thanks, -- Knute Johnson knute2011(a)knutejohnson.com

1 0

[Dovecot] Broken mail clients? [MIME] Long attachment encoded filenames (for non-ASCII characters etc)
by Andrew Richards 30 Sep '11

30 Sep '11

Hi, I've noticed a possible minor issue with long encoded filenames for attachments where these filenames are split across multiple lines. My understanding of character encoding and MIME is not as good as it should be, so I may easily have got this all mixed up, in which case sorry for the noise... Although I understand the preferred method for handling filenames split across multiple lines (because they're too long to fit on one line in the message) is that suggested in RFC2184/2231, so for example, filename*0*=iso-8859-1''accented_characters_here_%EA%CA%E6 filename*1=etc%2Epdf I find that some mail clients do this instead, filename="=?ISO-8859-1?Q?accented_characters_here_=EA=CA=E6?= =?ISO-8859-1?Q?etc=2Epdf?=" In Dovecot this results in, 0 fetch 25 body * 25 FETCH (BODY (("text" "plain" ("charset" "ISO-8859-1") NIL NIL "7bit" 239 8)("application" "pdf" ("name" "=?ISO-8859-1?Q?accented_characters_here_=EA=CA=E6?= =?ISO-8859-1?Q?etc=2Epdf?=") NIL NIL "base64" 219130) "mixed")) esp. note the unwanted space - or in fact the sequence ?= =? between the two sections of the filename. I think a possible tweak for Dovecot would be to combine the filename parts in this situation to remove the ?= =?. I'm not sure if an IMAP client should know to combine the parts in their current format. FWIW I see that Courier does the same as Dovecot in this situation. I think the 'alternative' method of splitting filenames I'm raising breaks RFC2047 (details below), but unfortunately this method is used by some large email generators like gmail - also details below. Key bits from RFC2047 section 5 part (3) re. only a single encoded-word ('phrase') being allowed for a MIME Content-Type / Content-Disposition: phrase = 1*( encoded-word / word ) An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured field body except within a 'comment' or 'phrase'. Here are the mail clients I noted this issue with (original filenames destroyed because I've been examining my client's emails for this issue - with their permission), (AOL) X-Mailer: Webmail 33953-STANDARD Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?Q?abcde?= =?utf-8?Q?abcde=C3=A9abcde.jpg?=" Content-Type: image/jpeg; name="=?utf-8?Q?abcde?= =?utf-8?Q?abcde=C3=A9abcde.jpg?=" Gmail: Content-Type: application/pdf; name="=?ISO-8859-1?Q?with_a_=EA=CA=E6_super=2Dlong_name_that=27s_bound?= =?ISO-8859-1?Q?_to_overflow_a_line_boundary_to_test_gmail=2Epdf?=" Content-Disposition: attachment; filename="=?ISO-8859-1?Q?with_a_=EA=CA=E6_super=2Dlong_name_that=27s_bound?= =?ISO-8859-1?Q?_to_overflow_a_line_boundary_to_test_gmail=2Epdf?=" X-Mailer: YahooMailWebService/0.8.113.313619 Content-Type: application/vnd.openxmlformats- officedocument.wordprocessingml.document; name="=?utf-8?B?base64encodedstring?= =?utf-8?B?base64encodedstring?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?B?base64encodedstring?= =?utf-8?B?base64encodedstring?=" X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005: Content-type: application/pdf; name="=?ISO-8859-1?Q?abcde=E9abcde=E9abcde=E9?= =?ISO-8859-1?Q?abcde=2Cl=2Epdf?=" Content-Disposition: attachment; filename="=?ISO-8859-1?Q?abcde=E9abcde=E9_abcde=E9?= =?ISO-8859-1?Q?abcde=2Cl=2Epdf?=" Content-ID: <20__=snip> Content-transfer-encoding: base64 X-Mailer: Lotus Domino Web Server Release 6.5.5FP1 HF551 November 27, 2007: Content-type: application/pdf; name="=?windows-1252?Q?abcde_=28=E9?= =?windows-1252?Q?=29=2Epdf?=" Content-Disposition: attachment; filename="=?windows-1252?Q?abcde_=28=E9?= =?windows-1252?Q?=29=2Epdf?=" Content-transfer-encoding: base64 Timo also noted the same style of filename encoding in Apple Mail in the previous thread I started, it would be interesting to try Apple Mail with a very long filename to cause it to split across multiple lines and see how it encodes the filename then, > Looks like Apple Mail also sends: > > Content-Type: application/octet-stream; > > name="=?iso-8859-1?Q?p=E4=E4?=" Best regards, Andrew.

2 2

[Dovecot] Long attachment encoded filenames (for non-ASCII characters etc) in MIME headers & corresponding Dovecot behaviour
by Andrew Richards 30 Sep '11

30 Sep '11

(Correction: Subject was confused) Hi, I've noticed a possible minor issue with long encoded filenames for attachments where these filenames are split across multiple lines. My understanding of character encoding and MIME is not as good as it should be, so I may easily have got this all mixed up, in which case sorry for the noise... Although I understand the preferred method for handling filenames split across multiple lines (because they're too long to fit on one line in the message) is that suggested in RFC2184/2231, so for example, filename*0*=iso-8859-1''accented_characters_here_%EA%CA%E6 filename*1=etc%2Epdf I find that some mail clients do this instead, filename="=?ISO-8859-1?Q?accented_characters_here_=EA=CA=E6?= =?ISO-8859-1?Q?etc=2Epdf?=" In Dovecot this results in, 0 fetch 25 body * 25 FETCH (BODY (("text" "plain" ("charset" "ISO-8859-1") NIL NIL "7bit" 239 8)("application" "pdf" ("name" "=?ISO-8859-1?Q?accented_characters_here_=EA=CA=E6?= =?ISO-8859-1?Q?etc=2Epdf?=") NIL NIL "base64" 219130) "mixed")) esp. note the unwanted space - or in fact the sequence ?= =? between the two sections of the filename. I think a possible tweak for Dovecot would be to combine the filename parts in this situation to remove the ?= =?. I'm not sure if an IMAP client should know to combine the parts in their current format. FWIW I see that Courier does the same as Dovecot in this situation. I think the 'alternative' method of splitting filenames I'm raising breaks RFC2047 (details below), but unfortunately this method is used by some large email generators like gmail - also details below. Key bits from RFC2047 section 5 part (3) re. only a single encoded-word ('phrase') being allowed for a MIME Content-Type / Content-Disposition: phrase = 1*( encoded-word / word ) An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured field body except within a 'comment' or 'phrase'. Here are the mail clients I noted this issue with (original filenames destroyed because I've been examining my client's emails for this issue - with their permission), (AOL) X-Mailer: Webmail 33953-STANDARD Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?Q?abcde?= =?utf-8?Q?abcde=C3=A9abcde.jpg?=" Content-Type: image/jpeg; name="=?utf-8?Q?abcde?= =?utf-8?Q?abcde=C3=A9abcde.jpg?=" Gmail: Content-Type: application/pdf; name="=?ISO-8859-1?Q?with_a_=EA=CA=E6_super=2Dlong_name_that=27s_bound?= =?ISO-8859-1?Q?_to_overflow_a_line_boundary_to_test_gmail=2Epdf?=" Content-Disposition: attachment; filename="=?ISO-8859-1?Q?with_a_=EA=CA=E6_super=2Dlong_name_that=27s_bound?= =?ISO-8859-1?Q?_to_overflow_a_line_boundary_to_test_gmail=2Epdf?=" X-Mailer: YahooMailWebService/0.8.113.313619 Content-Type: application/vnd.openxmlformats- officedocument.wordprocessingml.document; name="=?utf-8?B?base64encodedstring?= =?utf-8?B?base64encodedstring?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?B?base64encodedstring?= =?utf-8?B?base64encodedstring?=" X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005: Content-type: application/pdf; name="=?ISO-8859-1?Q?abcde=E9abcde=E9abcde=E9?= =?ISO-8859-1?Q?abcde=2Cl=2Epdf?=" Content-Disposition: attachment; filename="=?ISO-8859-1?Q?abcde=E9abcde=E9_abcde=E9?= =?ISO-8859-1?Q?abcde=2Cl=2Epdf?=" Content-ID: <20__=snip> Content-transfer-encoding: base64 X-Mailer: Lotus Domino Web Server Release 6.5.5FP1 HF551 November 27, 2007: Content-type: application/pdf; name="=?windows-1252?Q?abcde_=28=E9?= =?windows-1252?Q?=29=2Epdf?=" Content-Disposition: attachment; filename="=?windows-1252?Q?abcde_=28=E9?= =?windows-1252?Q?=29=2Epdf?=" Content-transfer-encoding: base64 Timo also noted the same style of filename encoding in Apple Mail in the previous thread I started, it would be interesting to try Apple Mail with a very long filename to cause it to split across multiple lines and see how it encodes the filename then, > Looks like Apple Mail also sends: > > Content-Type: application/octet-stream; > > name="=?iso-8859-1?Q?p=E4=E4?=" Best regards, Andrew.

1 0