<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 05/29/2015 03:30 PM, Michael Neumann wrote:<br>
<blockquote cite="mid:5568CC65.90407@ub.tu-dortmund.de" type="cite">
<pre wrap="">Am 29.05.2015 um 22:19 schrieb Ken Murchison:
</pre>
<blockquote type="cite">
<pre wrap="">
Also, are you sure that your MTA isn't breaking up the recipients into
separate LMTP transactions? lmtpd can/will only do single instance
store for recipients that are part of the same transaction (MAIL FROM,
RCPT TO, DATA sequence). If the recipients are sent one at a time with
duplicate DATA commands, there are treated as distinct messages.
</pre>
</blockquote>
<pre wrap="">
That is the problem, postfix default local transport does only one at a
time, that breaks single instance storage. We had to redefine it to:
local_transport = lmtp:unix:/lmtp/lmtp
Please read about the consequences in postconf manual.
Hope that helps
</pre>
</blockquote>
<br>
Michael is right on the money here. I hadn't noticed that you had
defined mailbox_transport rather than local_transport.<br>
<br>
This is our typical postfix configuration in support of
singleinstancestore:<br>
<blockquote>
<pre>local_recipient_maps = <a class="moz-txt-link-freetext" href="ldap:/etc/postfix/local_recipient_map.ldap">ldap:/etc/postfix/local_recipient_map.ldap</a>,
<a class="moz-txt-link-freetext" href="ldap:/etc/postfix/alias_map.ldap">ldap:/etc/postfix/alias_map.ldap</a>
local_transport = lmtp:unix:/mailstore/lib/imap/socket/lmtp
local_destination_recipient_limit = 300
local_destination_concurrency_limit = 5
</pre>
</blockquote>
The warnings Michael was referring to are covered in
<a class="moz-txt-link-freetext" href="http://www.postfix.org/LOCAL_RECIPIENT_README.html">http://www.postfix.org/LOCAL_RECIPIENT_README.html</a><br>
<br>
Specifically, if one overrides the local_transport, it's important
that one also properly qualifies all local_recipients (quoting):<br>
<blockquote>
<p> Problem: you don't use the default Postfix <a
href="http://www.postfix.org/local.8.html">local(8)</a>
delivery agent for domains matching $<a
href="http://www.postfix.org/postconf.5.html#mydestination">mydestination</a>,
$<a
href="http://www.postfix.org/postconf.5.html#inet_interfaces">inet_interfaces</a>,
or $<a
href="http://www.postfix.org/postconf.5.html#proxy_interfaces">proxy_interfaces</a>.
For example, you redefined the "<a
href="http://www.postfix.org/postconf.5.html#local_transport">local_transport</a>"
setting in <a href="http://www.postfix.org/postconf.5.html">main.cf</a>.
</p>
Solution: your <a
href="http://www.postfix.org/postconf.5.html#local_recipient_maps">local_recipient_maps</a>
setting needs to specify a database that lists all the known user
names or addresses for that delivery agent.</blockquote>
In our case we most often use LDAP for this, as shown above, but
whatever DB is best for you, etc.<br>
<br>
Cheers,<br>
-nic<br>
<pre class="moz-signature" cols="72">--
Nic Bernstein <a class="moz-txt-link-abbreviated" href="mailto:nic@onlight.com">nic@onlight.com</a>
Onlight llc. <a class="moz-txt-link-abbreviated" href="http://www.onlight.com">www.onlight.com</a>
219 N. Milwaukee St., Ste. 2A v. 414.272.4477
Milwaukee, Wisconsin 53202 f. 414.290.0335
</pre>
</body>
</html>