[Dovecot] Dovecot as LDA with Postfix
I have been attempting to replace Procmail with Dovecot as the LDA for my Postfix mail server, but without success. Below is a truncated output from the /var/log/maillog.
Aug 9 11:56:20 scorpio postfix/local[4338]: 88C3FC3D1: to=gerard@localhost.seibercom.net, orig_to=gerard@localhost, relay=local, delay=1119, delays=1118/0.71/0/0.11, dsn=4.3.0, status=deferred (temporary failure) Aug 9 11:56:20 scorpio postfix/local[4324]: 818AEBF6F: to=gerard-gmail@localhost.seibercom.net, orig_to=gerard-gmail@localhost, relay=local, delay=495, delays=494/0.06/0/0.81, dsn=4.3.0, status=deferred (temporary failure) Aug 9 11:57:37 scorpio postfix/postfix-script: stopping the Postfix mail system Aug 9 11:57:37 scorpio postfix/master[4233]: terminating on signal 15 Aug 9 12:00:09 scorpio postfix/postfix-script: starting the Postfix mail system Aug 9 12:00:09 scorpio postfix/master[4501]: daemon started -- version 2.4-2000727, configuration /usr/local/etc/postfix Aug 9 12:00:28 scorpio postfix/smtpd[4522]: connect from localhost[127.0.0.1] Aug 9 12:00:28 scorpio postfix/smtpd[4522]: A269EC46D: client=localhost[127.0.0.1] Aug 9 12:00:28 scorpio postfix/cleanup[4526]: A269EC46D: message-id=44DA0115.40500@dlr.de Aug 9 12:00:28 scorpio postfix/qmgr[4503]: A269EC46D: from=samba-bounces+gerard=seibercom.net@lists.samba.org, size=7308, nrcpt=1 (queue active) Aug 9 12:00:29 scorpio postfix/local[4527]: A269EC46D: to=gerard@localhost.seibercom.net, orig_to=gerard@localhost, relay=local, delay=0.58, delays=0.2/0.06/0/0.33, dsn=2.0.0, status=sent (delivered to command: /usr/local/bin/procmail) Aug 9 12:00:29 scorpio postfix/qmgr[4503]: A269EC46D: removed
With Dovecot as the LDA, no mail is ever delivered. I keep getting this temporary failure message. As soon as I revert to Procmail everything works fine. I am simply trying to deliver to mbox format on a FreeBSD 6.1 STABLE system. Nothing exotic.
I am using SASL2. Authentication is via saslauthd -a sasldb. Perhaps I do not have that configured correctly in Dovecot. Dovecot does work fine as a POP server though, so it is running at least partially correctly.
I would appreciate any assistance.
-- Gerard Seibert gerard@seibercom.net
Democracy is a device that insures we shall be governed no better than we deserve.
George Bernard Shaw
Gerard Seibert wrote:
I have been attempting to replace Procmail with Dovecot as the LDA for my Postfix mail server, but without success. Below is a truncated output from the /var/log/maillog.
I floundered with something that looked like this before. Verify all your permissions carefully and your dovecot transport in master.cf. You may find something I didn't, but I resolved the problem by making deliver suid. I can't decide whether I have introduced a security flaw I need to be concerned about here or not.
-- Duncan Hutty System Administrator, ECE Carnegie Mellon University
Please use informative subject lines
Duncan Hutty wrote:
I floundered with something that looked like this before. Verify all your permissions carefully and your dovecot transport in master.cf. You may find something I didn't, but I resolved the problem by making deliver suid. I can't decide whether I have introduced a security flaw I need to be concerned about here or not.
There must be somethng wrong with the way this is configured. I have to have:
disable_plaintext_auth = no
In my dovecot.conf file or else this is all I get when I attempt to POP email:
+OK Dovecot ready. [ISafe POP3 Proxy]
USER bud
-ERR Plaintext authentication disabled.
QUIT
+OK Logging out
I am unable to use TLS with Dovecot, although it does work with Postfix.
-- Gerard Seibert gerard@seibercom.net
On Wed, 2006-08-09 at 12:36 -0400, Gerard Seibert wrote:
Aug 9 11:56:20 scorpio postfix/local[4324]: 818AEBF6F: to=gerard-gmail@localhost.seibercom.net, orig_to=gerard-gmail@localhost, relay=local, delay=495, delays=494/0.06/0/0.81, dsn=4.3.0, status=deferred (temporary failure)
Most likely deliver wrote the actual error message to Dovecot's log file. However because deliver tries to write to logs directly instead of through master process like Dovecot normally does, it may not have permissions to write. So, try making sure that it does or set different log path to deliver with:
protocol lda{ .. log_path = /var/log/deliver.log }
Timo Sirainen wrote:
On Wed, 2006-08-09 at 12:36 -0400, Gerard Seibert wrote:
Aug 9 11:56:20 scorpio postfix/local[4324]: 818AEBF6F: to=gerard-gmail@localhost.seibercom.net, orig_to=gerard-gmail@localhost, relay=local, delay=495, delays=494/0.06/0/0.81, dsn=4.3.0, status=deferred (temporary failure)
Most likely deliver wrote the actual error message to Dovecot's log file. However because deliver tries to write to logs directly instead of through master process like Dovecot normally does, it may not have permissions to write. So, try making sure that it does or set different log path to deliver with:
protocol lda{ .. log_path = /var/log/deliver.log }
I am not following you here. There is no entry in my dovecot.conf file under 'protocol lda; for 'log_path'. Are you inferring that I should create one?
Second, what would that have to do with the failure of any mail to be properly delivered. Postfix simply stuck them back into the queue until I switched back to Procmail to get them delivered.
-- Gerard Seibert gerard@seibercom.net
Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise.
On Wed, 2006-08-09 at 13:49 -0400, Gerard Seibert wrote:
Timo Sirainen wrote:
On Wed, 2006-08-09 at 12:36 -0400, Gerard Seibert wrote:
Aug 9 11:56:20 scorpio postfix/local[4324]: 818AEBF6F: to=gerard-gmail@localhost.seibercom.net, orig_to=gerard-gmail@localhost, relay=local, delay=495, delays=494/0.06/0/0.81, dsn=4.3.0, status=deferred (temporary failure)
Most likely deliver wrote the actual error message to Dovecot's log file. However because deliver tries to write to logs directly instead of through master process like Dovecot normally does, it may not have permissions to write. So, try making sure that it does or set different log path to deliver with:
protocol lda{ .. log_path = /var/log/deliver.log }
I am not following you here. There is no entry in my dovecot.conf file under 'protocol lda; for 'log_path'. Are you inferring that I should create one?
Yes.
Second, what would that have to do with the failure of any mail to be properly delivered. Postfix simply stuck them back into the queue until I switched back to Procmail to get them delivered.
It'd most likely write a nice understandable error message to the log file. "Temporary failure" tells nothing about what the actual problem is.
On 2006-08-09 12:36:49 -0400, Gerard Seibert wrote:
I have been attempting to replace Procmail with Dovecot as the LDA for my Postfix mail server, but without success. Below is a truncated output from the /var/log/maillog.
did you configure dovecot as transport or mailbox command?
darix
-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
On August 10, 2006 7:05:05 PM -0400 Gerard Seibert gerard@seibercom.net wrote:
Marcus Rueckert wrote:
did you configure dovecot as transport or mailbox command?
darix
mailbox_command = /usr/local/libexec/dovecot/deliver
But this is not a good idea; see the thread "Problems with deliver (LDA)". Better to configure it is a content filter.
-frank
On August 10, 2006 5:39:58 PM -0700 Frank Cusack fcusack@fcusack.com wrote:
On August 10, 2006 7:05:05 PM -0400 Gerard Seibert gerard@seibercom.net wrote:
Marcus Rueckert wrote:
did you configure dovecot as transport or mailbox command?
darix
mailbox_command = /usr/local/libexec/dovecot/deliver
But this is not a good idea; see the thread "Problems with deliver (LDA)". Better to configure it is a content filter.
eh, sorry I was thinking about dspam, not deliver.
-frank
On 2006-08-10 17:39:58 -0700, Frank Cusack wrote:
mailbox_command = /usr/local/libexec/dovecot/deliver
i have the same here. for virtual users i configured it as transport. but for local users i use mailbox_command.
darix
-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Marcus Rueckert wrote:
On 2006-08-10 17:39:58 -0700, Frank Cusack wrote:
mailbox_command = /usr/local/libexec/dovecot/deliver
i have the same here. for virtual users i configured it as transport. but for local users i use mailbox_command.
OK, is it working correctly for you then? If so, then what could be the cause of the problems I am experiencing?
-- Gerard Seibert gerard@seibercom.net
Frank Cusack wrote:
On August 10, 2006 7:05:05 PM -0400 Gerard Seibert gerard@seibercom.net wrote:
Marcus Rueckert wrote:
did you configure dovecot as transport or mailbox command?
[...]
mailbox_command = /usr/local/libexec/dovecot/deliver
But this is not a good idea; see the thread "Problems with deliver (LDA)". Better to configure it is a content filter.
Could you be a little more specific? I tried searching for the "Problems with deliver (LDA)"; however, I am not sure if I found the one you are referring to.
In any case, I would like to know why it is not working as an LDA correctly on my system. Procmail, or just the build-in Postfix LDA works fine. According to the literature I have read, it should be working.
-- Gerard Seibert gerard@seibercom.net
Think about it: The *average* American has one tit and one testicle.
On August 31, 2006 11:58:59 AM -0400 Gerard Seibert gerard@seibercom.net wrote:
Frank Cusack wrote:
On August 10, 2006 7:05:05 PM -0400 Gerard Seibert gerard@seibercom.net wrote:
Marcus Rueckert wrote:
did you configure dovecot as transport or mailbox command?
[...]
mailbox_command = /usr/local/libexec/dovecot/deliver
But this is not a good idea; see the thread "Problems with deliver (LDA)". Better to configure it is a content filter.
Could you be a little more specific? I tried searching for the "Problems with deliver (LDA)"; however, I am not sure if I found the one you are referring to.
In any case, I would like to know why it is not working as an LDA correctly on my system. Procmail, or just the build-in Postfix LDA works fine. According to the literature I have read, it should be working.
Maybe you missed my followup. I was thinking of dspam, which should not be configured as a mailbox command. I have deliver (the sieve version from cvs) working in my setup. It does not add a 'From ' header as the thread indicates.
-frank
participants (5)
-
Duncan Hutty
-
Frank Cusack
-
Gerard Seibert
-
Marcus Rueckert
-
Timo Sirainen