Viktor Dukhovni wrote: > On Wed, Jun 25, 2014 at 02:31:18PM -0700, Julian Mehnle wrote: > >> Here's a log excerpt: >> >>> Jun 25 00:17:14 etl-qa-00 postfix/qmgr[19911]: 8830140409E9E: >>> from=<mailer-dae...@athena.vistabroadband.net>, >>> size=3023, nrcpt=2 (queue active) >>> Jun 25 00:44:26 etl-qa-00 postfix/pipe[29392]: 8830140409E9E: >>> to=<automat...@etl.qa.agari.com>, relay=dmarc-aggregate, >>> delay=1632, delays=0.03/1613/0/19, dsn=2.0.0, status=sent >>> (delivered via dmarc-aggregate service) >>> Jun 25 00:44:27 etl-qa-00 postfix/pipe[28007]: 8830140409E9E: >>> to=<automat...@etl.qa.agari.com>, relay=dmarc-aggregate, >>> delay=1633, delays=0.03/1614/0/19, dsn=2.0.0, status=sent >>> (delivered via dmarc-aggregate service) >>> Jun 25 00:44:27 etl-qa-00 postfix/qmgr[19911]: 8830140409E9E: removed > > Yes, this is two deliveries, for two recipient records in the queue > file, that are in fact the same recipient address? Why does this > message have to identical envelope recipients? The pipe(8) pid > would be the same for a single delivery with two recipients, as > would "delays".
The original RCPT TO addresses are actually different, but they resolve to the same destination internally. If there was a way to make Postfix collapse them into a single delivery, that would solve my problem as well. >> This happens only for messages that have two "<queue-id>: to=? >> (delivered via dmarc-aggregate service)" lines in the Postfix log, >> not for any other message delivered via the dmarc-aggregate service. > > So do any other messages deliver multiple recipients together via > this transport? No, I have just one sender that does this (and there is a legitimate reason for them doing this in general, it just so happens that sometimes both of the recipient addresses they send to ultimately are on our Postfix service, in which case I want to have it delivered only once). >> I don't think we're delivering messages via any means other than >> our dmarc-aggregate service, which is defined as a pipe delivery. >> How do I verify whether "mailbox_transport" is involved? > > What is the address class of the recipient domain (etl.qa.agari.com)? > What configuration settings result in the use of the pipe transport? Address class? I assume you're referring to this, but I haven't configured any classes explicitly. We have this in master.cf: > dmarc-aggregate unix - n n - - pipe > flags=RXq user=automation argv=/usr/bin/ruby1.9.1 > /usr/local/agari/hawking/qa/current/bin/dmarc_receive -e production -p > /data/pipeline/queue automation and in main.cf: > mailbox_transport_maps = hash:/etc/postfix/mailbox and in mailbox: > automation dmarc-aggregate Would you like to see any other configuration? -Julian
