On Wed, 18 May 2011 10:08:37 -0300
Gonzalo Rodriguez <gonz...@sepp0.com.ar> articulated:
> Hi all,
>
> I have a problem with my dovecot/postfix configuration:
>
> here is my dovecot -n
>
>
> # 1.2.16: /etc/dovecot.conf
> Warning: fd limit 128 is lower than what Dovecot can use under full
> load (more than 768). Either grow the limit or change
> login_max_processes_count and max_mail_processes settings
> # OS: OpenBSD 4.9 i386 nfs
> base_dir: /var/dovecot/
> log_path: /var/log/dovecot
> protocols: imaps pop3s
> login_dir: /var/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_user: _dovecot
> mail_location:
> maildir:/var/www/datos/correo/foobar.com.ar/%n:LAYOUT=fs mail_debug:
> yes mail_nfs_storage: yes
> mail_nfs_index: yes
> mbox_write_locks: fcntl
> mail_executable(default): /usr/local/libexec/dovecot/imap
> mail_executable(imap): /usr/local/libexec/dovecot/imap
> mail_executable(pop3): /usr/local/libexec/dovecot/pop3
> mail_plugin_dir(default): /usr/local/lib/dovecot/imap
> mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
> mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
> imap_client_workarounds(default): delay-newmail outlook-idle
> netscape-eoh tb-extra-mailbox-sep
> imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
> tb-extra-mailbox-sep
> imap_client_workarounds(pop3):
> pop3_client_workarounds(default):
> pop3_client_workarounds(imap):
> pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
> lda:
> mail_plugins: sieve
> postmaster_address: postmas...@foobar.com.ar
> log_path: /var/log/dovecot-deliver-errors.log
> info_log_path: /var/log/dovecot-deliver.log
> auth default:
> mechanisms: login plain
> verbose: yes
> debug: yes
> debug_passwords: yes
> passdb:
> driver: bsdauth
> userdb:
> driver: static
> args: uid=vmail gid=vmail
> home=/var/www/datos/correo/foobar.com.ar/%n, allow_all_users=yes
> socket:
> type: listen
> client:
> path: /var/spool/postfix/private/auth
> mode: 432
> user: _postfix
> group: _postfix
> master:
> path: /var/dovecot/auth-master
> mode: 384
> user: vmail
> group: vmail
> plugin:
> sieve_global_dir: /var/sieve
> sieve_global_path: /var/sieve/global-default.sieve
> sieve: /var/sieve/%n.sieve
>
>
> I use bsdauth to system users auth againts Active-Directory, and I use
> dovecot to deliver the mails, in my postfix master.cf I have this:
>
>
> ## Deliver con Dovecot en
> ## Mailboxes
> dovecot unix - n n - - pipe
> flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver
> -f ${sender} -d ${recipient}
>
>
>
> The problem is I don't any process like this:
>
>
> pipe -n dovecot -t unix flags=DRhu user=vmail
> /usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient}
>
>
> And in the dovecot log I don't see anything, but in maillog I have:
>
>
> May 18 09:49:35 FOOBAR-0010 postfix/local[16584]: 8808D26125:
> to=<gonza...@foobar.com.ar>, relay=local, delay=0.92,
> delays=0.91/0.01/0/0, dsn=2.0.0, status=sent (delivered to mailbox)
>
>
> But the mail it's not in the mailbox, what is wrong? any hint? the
> storage is a NFS with centos.
If I am reading this correctly, the mail is never being delivered to
Dovecot. You need to do the following:
1) Read the documentation at: <http://www.postfix.com/DEBUG_README.html>
Pay particular attention to the "Reporting problems to
postfix-us...@postfix.org at the end of the document. specifically:
<quote>
When reporting a problem, be sure to include the following information.
A summary of the problem. Please do not just send some logging without
explanation of what YOU believe is wrong.
Complete error messages. Please use cut-and-paste, or use attachments,
instead of reciting information from memory.
Postfix logging. See the text at the top of the DEBUG_README document
to find out where logging is stored. Please do not frustrate the
helpers by word wrapping the logging. If the logging is more than a few
kbytes of text, consider posting an URL on a web or ftp site.
Output from "postconf -n". Please do not send your main.cf file, or
500+ lines of postconf output.
Better, provide output from the postfinger tool. This can be found at
http://ftp.wl0.org/SOURCES/postfinger.
</quote>
The use of the "postfinger" tool is always the best procedure.
Then, post the above on the Postfix forum.
--
Jerry ✌
dovecot.u...@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
