Anderson Goulart wrote:
>
>I've just installed mailman, apache and postfix on a debian squeeze machine. 
>Everything seems to be correct, 
>
>What I can do until now:
>
>- I can create a list and manage it by the web browser
>- /etc/aliases are created correctly
>- I can subscribe to a list and a confirmation email arrives correct. 
>- Confirmation link are ok
>- If I send an email to a list without subscription, the list-owner receive 
>the pending for approval email.
>
>What is wrong? When i send an email using a subscribed user, it is bounced by 
>mailman. I can't figure out what is wrong... any clues? Why it tries to send 
>an email as [email protected]?
>
>See the mail.info log below:
>
>Mar 17 23:48:09 xray274 postfix/smtpd[19066]: connect from 
>mail-gw0-f52.google.com[74.125.83.52]
>Mar 17 23:48:10 xray274 postfix/smtpd[19066]: AEF01CC0041: 
>client=mail-gw0-f52.google.com[74.125.83.52]
>Mar 17 23:48:10 xray274 postfix/cleanup[19071]: AEF01CC0041: 
>message-id=<[email protected]>
>Mar 17 23:48:10 xray274 postfix/qmgr[18432]: AEF01CC0041: 
>from=<[email protected]>, size=1049, nrcpt=1 (queue active)
>Mar 17 23:48:11 xray274 postfix/pipe[19072]: AEF01CC0041: 
>to=<[email protected]>, relay=mailman, delay=0.59, 
>delays=0.38/0.01/0/0.21, dsn=2.0.0, status=sent (delivered via mailman service)
>Mar 17 23:48:11 xray274 postfix/qmgr[18432]: AEF01CC0041: removed


The above indicates a successful delivery of the message from
<[email protected]> to <[email protected]> via the 'mailman'
transport which I'm guessing postfix_to_mailman.py.


>Mar 17 23:48:12 xray274 postfix/smtpd[19074]: connect from 
>localhost.localdomain[127.0.0.1]
>Mar 17 23:48:12 xray274 postfix/smtpd[19074]: 60CCDCC0041: 
>client=localhost.localdomain[127.0.0.1]
>Mar 17 23:48:12 xray274 postfix/cleanup[19071]: 60CCDCC0041: 
>message-id=<[email protected]>
>Mar 17 23:48:12 xray274 postfix/qmgr[18432]: 60CCDCC0041: 
>from=<[email protected]>, size=2037, nrcpt=1 (queue active)
>Mar 17 23:48:12 xray274 postfix/smtpd[19074]: disconnect from 
>localhost.localdomain[127.0.0.1]
>Mar 17 23:48:14 xray274 postfix/smtp[19075]: 60CCDCC0041: 
>to=<[email protected]>, relay=aspmx.l.google.com[74.125.43.27]:25, 
>delay=1.8, delays=0.01/0.01/0.06/1.7, dsn=2.0.0, status=sent (250 2.0.0 OK 
>1300405694 r25si7312502bkw.93)
>Mar 17 23:48:14 xray274 postfix/qmgr[18432]: 60CCDCC0041: removed
>Mar 17 23:48:41 xray274 postfix/smtpd[19066]: disconnect from 
>mail-gw0-f52.google.com[74.125.83.52]


And this looks like successful delivery of the post from the
<[email protected]> to <[email protected]>.


>Mar 17 23:50:02 xray274 postfix/pickup[19008]: 07005CC0046: uid=33 
>from=<www-data>
>Mar 17 23:50:02 xray274 postfix/cleanup[19091]: 07005CC0046: 
>message-id=<[email protected]>
>Mar 17 23:50:02 xray274 postfix/qmgr[18432]: 07005CC0046: 
>from=<[email protected]>, size=873, nrcpt=1 (queue active)
>Mar 17 23:50:02 xray274 postfix/pipe[19092]: 07005CC0046: 
>to=<[email protected]>, orig_to=<www-data>, relay=mailman, 
>delay=0.15, delays=0.04/0.01/0/0.11, dsn=5.1.1, status=bounced (user unknown)
>Mar 17 23:50:02 xray274 postfix/cleanup[19091]: 23A4ACC0047: 
>message-id=<[email protected]>
>Mar 17 23:50:02 xray274 postfix/bounce[19094]: 07005CC0046: sender 
>non-delivery notification: 23A4ACC0047
>Mar 17 23:50:02 xray274 postfix/qmgr[18432]: 23A4ACC0047: from=<>, size=2743, 
>nrcpt=1 (queue active)
>Mar 17 23:50:02 xray274 postfix/qmgr[18432]: 07005CC0046: removed
>Mar 17 23:50:02 xray274 postfix/pipe[19092]: 23A4ACC0047: 
>to=<[email protected]>, relay=mailman, delay=0.1, delays=0/0/0/0.1, 
>dsn=5.1.1, status=bounced (user unknown)
>Mar 17 23:50:02 xray274 postfix/qmgr[18432]: 23A4ACC0047: removed


And then nearly 2 minutes later another message arrives from
<[email protected]> and to <www-data> which expands to
<[email protected]> and which is bounced because there is no
list named www-data.

In short, Mailman didn't bounce the message to <[email protected]>
with message id <[email protected]>,
it delivered it to <[email protected]>.

postfix_to_mailman.py or whatever the mailman transport is bounced a
totally different message with message id
<[email protected]> from
<[email protected]> to <www-data>.

I have no clue as to what generated this message or why, but it doesn't
appear to have been generated by Mailman.

Since the sender and recipient of this message
<[email protected]> is a non-existent list, you don't see
the message or the DSN, and you presumably also have no clue as to
what generated it or why.

You could at least temporarily create a list named 'www-data' and maybe
at least see this message for a clue.

What happened to the message post from the list that was apparently
successfully delivered to <[email protected]>? I suspect that you
don't see it because <[email protected]> is a googlemail account and
the FAQ at <http://wiki.list.org/x/2IA9> applies. I also suspect you
will see it in the list's archive if the list is archiving, and if you
add another address to the list, even another googlemail address, that
address will receive it.

-- 
Mark Sapiro <[email protected]>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list [email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to