- dovecot - dovecot.org

[Dovecot] LMTP Setup/Design Help Request
by Matthias Hofer 13 Apr '13

13 Apr '13

Hi again, Thank you for your first hints. I have now set up a dedicated test instance of postfix and dovecot to be able to recreate the problems in detail. Even after using your inputs, they do not seem to work with my setup I already mentioned above. I get errors like postfix/lmtp[10994]: C2DF4C000DF: to=<user1(a)mydomain.org>, relay=mail.mydomain.org[private/dovecot-lmtp], delay=0.1, delays=0.05/0/0/0.04, dsn=5.1.1, status=bounced (host mail.mydomain.org[private/dovecot-lmtp] said: 550 5.1.1 <user1(a)mydomain.org> User doesn't exist: user1(a)mydomain.org (in reply to RCPT TO command)) As stated before, my setup is as follows: > I only have virtual users and have set > > mail_uid = dovemail > mail_gid = dovemail > > For authentication, I simply use (for now) a flat file: > > passdb { > driver = passwd-file > args = scheme=PLAIN username_format=%u /etc/dovecot/mypasswd.file > } > > # cat /etc/dovecot/mypasswd.file > user1:{PLAIN}userpw1 > user2:{PLAIN}userpw2 > user3:{PLAIN}userpw3 > > And everything works fine with IMAP. I am completely domain-agnostic > here. I do not know how to strip the domain when the username is handed over from postfix to dovecot, and what would be the sane solution. I hope, you can give me a hint to that. Thank you, again, and greetings, Matthias Hofer

3 4

Re: [Dovecot] LMTP Setup/Design Help Request
by Matthias Hofer 13 Apr '13

13 Apr '13

>> So, is there a way for dovecot-{lda/lmtpd} to accept "user1(a)mydomain.org" but checks for "user1" in the >> user >> DB? > > Try username_format=%n so dovecot uses the username only: > http://wiki2.dovecot.org/Variables > > passdb { > driver = passwd-file > args = scheme=PLAIN username_format=%n /etc/dovecot/mypasswd.file > } Great! I did not think about that, but this solved this issue :D Thank you a lot. And I was now able to solve also my further issues. So I am prepared to try again to switch :) Have great day! Matthias Hofer

1 0

[Dovecot] Migration from courier to dovecot
by ChandranManikandan 12 Apr '13

12 Apr '13

Hi, I am using Courier imap+Qmail+Vpopmail. My IMAP having slow issues on our email client while download message as well switch to another folder. I would request you to give me the procedure for migration as well let me know if anything going wrong after migrate. We have 100 mailboxes and some email box more than 25 GB. I want to access email fast in oulook client 2010 as well squirrelmail. Kindly guide me . Am waiting for your reply asap. -- *Thanks & Best Regards, Manikandan.C *

2 1

[Dovecot] Dovecot / Postfix
by Dan Clovis 12 Apr '13

12 Apr '13

Ave Maria! I have Dovecot and Postifx setup with MySQL - emails seem to go through the server but for some reason the pipe into the wrong Virtual Domain any ideas? Also I notice If you need any other configurations please let me know... mail.info logs: Apr 12 13:30:14 Server1 postfix/smtpd[21411]: connect from mail-qe0-f48.google.com[209.85.128.48] Apr 12 13:30:14 Server1 postfix/trivial-rewrite[21415]: warning: do not list domain ccpop.itco.co in BOTH mydestination and virtual_mailbox_domains Apr 12 13:30:14 Server1 postfix/smtpd[21411]: F365B14EE1AE: client=mail-qe0-f48.google.com[209.85.128.48] Apr 12 13:30:15 Server1 postfix/cleanup[21416]: F365B14EE1AE: message-id=<CAObOquM=KoONc2QnF6HHuzZ_9AN+-+ndymjoDQJ29og=Lxe_og(a)mail.gmail.com> Apr 12 13:30:15 Server1 postfix/qmgr[21407]: F365B14EE1AE: from=<dan.clovis1(a)gmail.com>, size=1706, nrcpt=1 (queue active) Apr 12 13:30:15 Server1 dovecot: auth(default): master in: USER#0111#011dan(a)companycouk.com#011service=deliver Apr 12 13:30:15 Server1 dovecot: auth(default): master out: USER#0111#011dan@companycouk.com#011uid=5000#011gid=5000#011home=/home/vmail/companycouk.com/dan Apr 12 13:30:15 Server1 postfix/pipe[21417]: F365B14EE1AE: to=<dan(a)companycouk.com>, orig_to=<dan(a)ccpop.itco.co>, relay=dovecot, delay=0.29, delays=0.28/0/0/0.01, dsn=2.0.0, status=sent (delivered via dovecot service) Apr 12 13:30:15 Server1 postfix/qmgr[21407]: F365B14EE1AE: removed Postfix main.cf # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = /usr/share/doc/postfix # TLS parameters smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key smtpd_use_tls = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. myhostname = pop3.companycouk.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = ccpop.itco.co, localhost, localhost.localdomain, companycoServer1, companycoServer1.companycoServer1 relayhost = mynetworks = 127.0.0.0/8 mailbox_command = procmail -a "$EXTENSION" mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all html_directory = /usr/share/doc/postfix/html message_size_limit = 30720000 virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_mailbox_base = /home/vmail virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_authenticated_header = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination virtual_create_maildirsize = yes virtual_maildir_extended = yes proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps virtual_transport = dovecot dovecot_destination_recipient_limit = 1 God Bless Dan

4 4

[Dovecot] How to prevent delivery to mailboxes over quota at SMTP-time
by Ralf Hildebrandt 12 Apr '13

12 Apr '13

Hi! I wrote a little something about how to prevent delivery to mailboxes over quota while still being in the SMTP dialogue: http://sys4.de/en/blog/2013/04/08/postfix-dovecot-mailbox-quota/ (Postfix/Dovecot-2.2) -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich

3 5

[Dovecot] Problem with vpopmail + qmail + dovecot lda
by Davide 12 Apr '13

12 Apr '13

I have a little problem in my configuration (vpopmail + qmail + dovecot 2.1.12 with LDA) my .qmail-default is this | /var/qmail/bin/preline -f /usr/local/libexec/dovecot/dovecot-lda -d $EXT@$USER -e | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox I receive al mails to postmaster for non-existent users (all my users are virtual and live under group 89 vpopmail) and this is ok but all mails for quota-full users dosen't If i remove the vdelivermail part in .qmail-default i receive bounce for quota-full but not for non-existent users. If can be usefull this is my dovecot conf auth_cache_size = 10 k auth_cache_ttl = 5 hours auth_mechanisms = plain cram-md5 disable_plaintext_auth = yes dotlock_use_excl = yes first_valid_gid = 89 first_valid_uid = 89 info_log_path = /var/log/dovecot/dovecot.log last_valid_gid = 89 last_valid_uid = 89 listen = 127.0.0.1 log_path = /var/log/dovecot/dovecot-err.log debug_log_path = /var/log/dovecot/dovecot-debug.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_fsync = never mail_location = maildir:~/Maildir # mail_debug = yes mmap_disable = yes mail_plugins=$mail_plugins notify zlib fts fts_solr quota default_internal_user = dovecot default_login_user = dovenull default_vsz_limit = 512M maildir_very_dirty_syncs=yes verbose_ssl = no # syslog_facility = mail namespace { inbox = yes location = prefix = separator = / type = private } # Public namespace namespace { type = public separator = / prefix = Public/ location = maildir:/var/mail/public subscriptions = no list = children } passdb { args = webmail=127.0.0.1 cache_key=%u%s driver = vpopmail } plugin { fts = solr fts_decoder = decode2text fts_solr = url=http://192.168.10.103:8983/solr/ break-imap-search debug zlib_save_level = 9 # 1..9 zlib_save = gz # or bz2 # sieve = /usr/local/lib/dovecot/sieve/%n.sieve sieve=~/.dovecot.sieve sieve_dir=~/sieve # sieve_default = /usr/local/lib/dovecot/sieve/default.sieve # sieve_global_dir = /usr/local/lib/dovecot/sieve/ mail_log_events = delete undelete expunge copy mail_log_fields = uid box msgid size mail_log_group_events = quota = maildir:User quota quota_rule2 = Trash:storage=+20%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u # antispam_debug_target = syslog # antispam_verbose_debug = 1 antispam_backend = pipe antispam_spam = SPAM antispam_unsure = UNSURE antispam_trash_pattern_ignorecase = trash;Deleted * # antispam_signature = X-DSPAM-Signature # antispam_signature_missing = move # antispam_dspam_binary = /usr/local/bin/dspamc # antispam_crm_args = -u;%h;/usr/share/crm114/mailreaver.crm;--fileprefix=/usr/share/crm114/ #sa-learn -u clamav --spam /var/mail/public/.Spam --showdots # antispam_dspam_args = --deliver;--user;%u antispam_pipe_program = /usr/bin/sa-learn # (defaults to /usr/sbin/sendmail) antispam_pipe_program_args = -u;clamav antispam_pipe_program_spam_arg = --spam antispam_pipe_program_notspam_arg = --ham antispam_pipe_tmpdir = /mnt/ramdisk } protocols = imap sieve service auth { unix_listener auth-master { group = vchkpw mode = 0660 user = vpopmail } unix_listener auth-userdb { mode = 0600 user = vpopmail group = vchkpw } # user = vpopmail vsz_limit = 64 M } service imap-login { executable = /usr/local/libexec/dovecot/imap-login inet_listener imaps { address = 192.168.119.150 } process_limit = 500 process_min_avail = 8 service_count = 1 #user = dovecot } service managesieve-login { executable = managesieve-login inet_listener sieve { address = 127.0.0.1 port = 4190 } #inet_listener sieve_deprecated { # port = 2000 #} # Number of connections to handle before starting a new process. Typically # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0 # is faster. <doc/wiki/LoginProcess.txt> service_count = 1 # Number of processes to always keep waiting for more connections. process_min_avail = 1 # If you set service_count=0, you probably need to grow this. vsz_limit = 64M } service managesieve { # Max. number of ManageSieve processes (connections) process_limit = 10 } # Service configuration protocol sieve { # Maximum ManageSieve command line length in bytes. ManageSieve usually does # not involve overly long command lines, so this setting will not normally need # adjustment managesieve_max_line_length = 65536 # Maximum number of ManageSieve connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 # Space separated list of plugins to load (none known to be useful so far). Do NOT # try to load IMAP plugins here. #mail_plugins = # MANAGESIEVE logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client managesieve_logout_format = bytes=%i/%o # To fool ManageSieve clients that are focused on CMU's timesieved you can specify # the IMPLEMENTATION capability that the dovecot reports to clients. # For example: 'Cyrus timsieved v2.2.13' managesieve_implementation_string = Dovecot Pigeonhole # Explicitly specify the SIEVE and NOTIFY capability reported by the server before # login. If left unassigned these will be reported dynamically according to what # the Sieve interpreter supports by default (after login this may differ depending # on the user). #managesieve_sieve_capability = #managesieve_notify_capability = # The maximum number of compile errors that are returned to the client upon script # upload or script verification. #managesieve_max_compile_errors = 5 # Refer to 90-sieve.conf for script quota configuration and configuration of # Sieve execution limits. log_path = /var/log/dovecot/dovecot-sieve-error.log info_log_path = /var/log/dovecot/dovecot-sieve.log } service decode2text { executable = script /usr/local/libexec/dovecot/decode2text.sh unix_listener decode2text { mode = 0666 user = dovecot } #user = vpopmail } service imap { executable = /usr/local/libexec/dovecot/imap vsz_limit = 1024M } service quota-warning { executable = script /usr/local/libexec/dovecot/quota_warning # use some unprivileged user for executing the quota warnings user = vpopmail unix_listener quota-warning { group = vchkpw mode = 0660 user = vpopmail } } ssl_cert = </var/qmail/control/servercert.pem ssl_key = </var/qmail/control/servercert.pem userdb { args = quota_template=quota_rule=*:backend=%q driver = vpopmail } protocol imap { imap_client_workarounds = imap_max_line_length = 64 k mail_plugin_dir = /usr/local/lib/dovecot mail_plugins = $mail_plugins imap_quota mail_log antispam imap_zlib } protocol lda { mail_fsync = optimized auth_socket_path = /usr/local/var/run/dovecot/auth-userdb deliver_log_format = msgid=<%f>-<%s>-%m: %$ hostname = mail.cgilfe.it info_log_path = /var/log/dovecot/dovecot-deliver.log log_path = /var/log/dovecot/dovecot-deliver.log mail_plugin_dir = /usr/local/lib/dovecot mail_plugins = $mail_plugins mail_log sieve postmaster_address = postmaster(a)mail.cgilfe.it rejection_reason = Il Vostro messaggio a <%t> è stato automaticamente rifiutato:%n%r sendmail_path = /usr/bin/sendmail # quota_full_tempfail = yes } -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

1 0

Re: [Dovecot] Configuring dovecot to use tcp wrappers
by Joseph Tam 12 Apr '13

12 Apr '13

"Max Pyziur" <pyz(a)brama.com> wrote: > I've put in a test ip address in /etc/hosts.deny like so: > dovecot: 166.84.1.2 Maybe imap: 166.84.1.2 imaps: 166.84.1.2 pop3: 166.84.1.2 pop3s: 166.84.1.2 Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Reading dovecot-uidlist by external program (locking)
by Andrzej A. Filip 11 Apr '13

11 Apr '13

How to lock dovecot-uidlist file before reading by an external program? [perl script]

1 1

Re: [Dovecot] Configuring dovecot to use tcp wrappers
by Max Pyziur 11 Apr '13

11 Apr '13

On Thu, 11 Apr 2013, lists-dovecot wrote: > > [... snip ...] >> >> I've put in a test ip address in /etc/hosts.deny like so: >> dovecot: 166.84.1.2 >> >> And then I execute the following from 166.84.1.2 to port 110: >> bash-3.2$ telnet SiteWhereImConfiguringDovecot 110 >> Trying SiteWhereImConfiguringDovecot... >> Connected to SiteWhereImConfiguringDovecot. >> Escape character is '^]'. >> +OK Dovecot ready. >> quit >> +OK Logging out >> Connection closed by foreign host. >> >> If dovecot is configured with tcp wrappers (which it is; built on >> a CentOS 6 system, installed and configured per instructions), >> and the firewall has ports 110 and 143 open, >> but I'm blocking a particular host through /etc/hosts.deny >> then I should not be able to telnet to either port 110 or 143; both >> requests should be blocked from the originating IP, no? >> >> Much thanks for your help, >> >> Max Pyziur >> pyz(a)brama.com > > > What are you using as the service name in hosts.deny? I think it > should be "imap-login:", (that's what I have as an > historical/left-over entry) but don't have dovecot configured with > wrappers on my current centos system so can't test this to be > certain. Also make certain that you don't have anything in your > hosts.allow file that would override the hosts.deny entry. I was using dovecot, until you convinced me to do otherwise. Putting pop3 in /etc/hosts.deny with the associated ip seems to work, like so: pop3: 166.84.1.2 or imap imap: 166.84.1.2 (are there any challenges to this?) Given that services such sendmail and sshd respond to sshd: xxx.xxx.xxx.xxx sendmail: xxx.xxx.xxx.xxx I thought that it should be dovecot: xxx.xxx.xxx.xxx As a suggestion, can dovecot binaries for distributions such as CentOS and Fedora be compiled with tcp wrappers by default? > - Richard Much thanks. MP pyz(a)brama.com

1 0

[Dovecot] Questions about the upcoming Object Storage Plugin for 2.2
by Charles Marcus 11 Apr '13

11 Apr '13

Hi Timo, I'm curious and have questions about the new Object Storage Plugin (OSP), and how it can be leveraged by an SMB like us. First, am I reading this right where it could be used as a kind of 'live/realtime backup' solution, where everything is stored *both* locally and in the cloud, with two-way syncing, ie, so local users could access the local server for faster access, and when outside the office, they'd access the cloud based storage and any changes made there are sync'd back to the local server? Or is it intended to be more as an alternative storage for storing older emails in a separate namespace? Or both/either? Second, is SIS fully supported by the OSP? Third - I'm a little confused by the Amazon S3 pricing page, especially on how to try to estimate the costs for usage (bandwidth, etc)... do you have any idea how to go about estimating that? Is there some kind of process we could use on our existing server to measure it over a given period of time that would give us an estimate of what to expect if we decided to switch over? Last - have you established pricing for the OSP? Will it be per user, or per MB/GB, per month (or per year), or just a one-time cost? And/or will you include/bundle it with any/all of your support tiers? Sorry if I'm jumping the gun here... Thanks, really looking forward to the 2.2 release! -- Best regards, Charles

2 3