

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
1 message in net.sourceforge.lists.courier-maildrop[maildropl] Maildrop and Enemies of C...| From | Sent On | Attachments |
|---|---|---|
| Markus Törnqvist | Aug 31, 2003 8:57 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [maildropl] Maildrop and Enemies of Carlotta questions | Actions... |
|---|---|---|
| From: | Markus Törnqvist (mj...@nysv.org) | |
| Date: | Aug 31, 2003 8:57:40 am | |
| List: | net.sourceforge.lists.courier-maildrop | |
Hiyall
I've tried to get Lars Wirzenius' Enemies of Carlotta mailing list manager to work in Maildrop. Actually, I mentioned this roughly a couple of weeks ago here, but didn't get any answers. Anyhow, below are the main points from the mail I sent to the EoC list. Maybe someone might spot answers to the questions...
With a filter like this:
foreach (/^(To|Cc): .*/) { RECIPIENT=getaddr($MATCH) SENDER=$FROM
cc '|enemies-of-carlotta --name=$RECIPIENT --is-list'
if ($EXITCODE == 0) { to '|enemies-of-carlotta --incoming' } else { cc '|cat - > /dev/null' } }
I get the same behavior I had a month ago, that's to be expected, because it's essentially the same filter ;)
The difference is that the list owner can receive mail. "I check --is-list for one copy of the message, send the rest forward. Oh dear, $EXITCODE == 1, but I can't send it to the recipient because that would cause a bounce message, so I have to take one copy and /dev/null it so the other copy can be delivered normally." Or something...
Is there a bug in EoC, because when the mail is delivered to the list, it gets the headers twice, as if it went through the list_headers method twice. This is what the log looks like:
2003-08-31 17:31:12 [15648] Indeed a mailing list: <mjt2...@nysv.org> 2003-08-31 17:31:12 [15649] Processing incoming message. 2003-08-31 17:31:13 [15657] Indeed a mailing list: <mjt2...@nysv.org> 2003-08-31 17:31:13 [15658] Processing incoming message. 2003-08-31 17:31:13 [15669] Indeed a mailing list: <mjt2-borg-bounce-1-c134f4d2a 793e...@nysv.org>
Maildrop, as far as I know, should interpret the cc directive as "send one copy here and the next forward in the filter." But that log looks more like "oh yeah, let's ram it through here twice, then mess something up at the to section so that the other message gets double headers." They have the same Message-Id even.
That bounce is apparently due to a loop that comes when trying to deliver to the list owner, any ideas on that? It say "<mj...@nysv.org>: mail forwarding loop for mj...@nysv.org" in the mails stuck in the bounce-box. Is the bounce supposed to be seen as a mailing list?
When I try to use procmail, I get the following:
procmail: Executing "enemies-of-carlotta,--name=mj...@nysv.org,--is-list" Not a mailing list: <mj...@nysv.org> procmail: Non-zero exitcode (1) from "enemies-of-carlotta" procmail: No match on "enemies-of-carlotta --name=mj...@nysv.org --is-list"
So the $RECIPIENT variable gets broken somewhere... but the message is delivered to mjt2, anyhow. Has this happened elsewhere?
Am I really the only one fighting with this?-)
Thanks!
-- Markus Törnqvist







