Re: [courier-users] [couriermlm] Problem with headerdel
Sam Varshavchik writes: Jean-Christophe Boggio writes: Le 23/07/2013 00:30, Sam Varshavchik a écrit : > Wild guess: check for spurious trailing whitespace, in headerdel. Make > sure lines are terminated with newlines I triple-checked, tried by adding another Delivered-To: line (no change), added User-Agent: (works). Everything looks good to me : $ hd headerdel 46 72 6f 6d 3a 0a 44 65 6c 69 76 65 72 65 64 2d | From:.Delivered-| 0010 54 6f 3a 0a 52 65 70 6c 79 2d 54 6f 3a 0a 54 6f |To:.Reply- To:.To| 0020 3a 0a 43 63 3a 0a 53 65 6e 64 65 72 3a 0a 58 2d |:.Cc:.Sender:.X-| 0030 4f 72 69 67 69 6e 61 74 69 6e 67 2d 45 6d 61 69 |Originating- Emai| 0040 6c 3a 0a 4f 6c 64 2d 52 65 74 75 72 6e 2d 50 61 |l:.Old-Return- Pa| 0050 74 68 3a 0a 52 65 63 65 69 76 65 64 3a 0a 55 73 | th:.Received:.Us| 0060 65 72 2d 41 67 65 6e 74 3a 0a|er-Agent:.| I can't see an immediate reason. Are you sure the Delivered-To: header does not get added after couriermlm distributes the message. What is that email address that's subscribed to the list. Ok, I did a little bit more digging. The Delivered-To: line is "special". It's not part of the actual message. It gets added when Courier delivers a message to a mailbox, additional couriermlm manually adds it to distributed mail. If you want to get rid of it, you can remove the DTLINE environment variable, which you can do in the .courier file that executes couriermlm. Instead of | couriermlm msg Try doing this instead | unset DTLINE; couriermlm msg But, you better know what you're doing. The Delivered-To: line is key to preventing mail loops. If someone can forward their mail to the mailing list, since you're stripping Delivered-To: and Received:, you'll end up mailbombing each other. pgpCse7ayMuPh.pgp Description: PGP signature -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] [couriermlm] Problem with headerdel
Jean-Christophe Boggio writes: Le 23/07/2013 00:30, Sam Varshavchik a écrit : > Wild guess: check for spurious trailing whitespace, in headerdel. Make > sure lines are terminated with newlines I triple-checked, tried by adding another Delivered-To: line (no change), added User-Agent: (works). Everything looks good to me : $ hd headerdel 46 72 6f 6d 3a 0a 44 65 6c 69 76 65 72 65 64 2d | From:.Delivered-| 0010 54 6f 3a 0a 52 65 70 6c 79 2d 54 6f 3a 0a 54 6f |To:.Reply- To:.To| 0020 3a 0a 43 63 3a 0a 53 65 6e 64 65 72 3a 0a 58 2d |:.Cc:.Sender:.X-| 0030 4f 72 69 67 69 6e 61 74 69 6e 67 2d 45 6d 61 69 |Originating- Emai| 0040 6c 3a 0a 4f 6c 64 2d 52 65 74 75 72 6e 2d 50 61 |l:.Old-Return- Pa| 0050 74 68 3a 0a 52 65 63 65 69 76 65 64 3a 0a 55 73 | th:.Received:.Us| 0060 65 72 2d 41 67 65 6e 74 3a 0a|er-Agent:.| I can't see an immediate reason. Are you sure the Delivered-To: header does not get added after couriermlm distributes the message. What is that email address that's subscribed to the list. pgpXxIuJUur2g.pgp Description: PGP signature -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] [couriermlm] Problem with headerdel
Le 23/07/2013 00:30, Sam Varshavchik a écrit : > Wild guess: check for spurious trailing whitespace, in headerdel. Make > sure lines are terminated with newlines I triple-checked, tried by adding another Delivered-To: line (no change), added User-Agent: (works). Everything looks good to me : $ hd headerdel 46 72 6f 6d 3a 0a 44 65 6c 69 76 65 72 65 64 2d |From:.Delivered-| 0010 54 6f 3a 0a 52 65 70 6c 79 2d 54 6f 3a 0a 54 6f |To:.Reply-To:.To| 0020 3a 0a 43 63 3a 0a 53 65 6e 64 65 72 3a 0a 58 2d |:.Cc:.Sender:.X-| 0030 4f 72 69 67 69 6e 61 74 69 6e 67 2d 45 6d 61 69 |Originating-Emai| 0040 6c 3a 0a 4f 6c 64 2d 52 65 74 75 72 6e 2d 50 61 |l:.Old-Return-Pa| 0050 74 68 3a 0a 52 65 63 65 69 76 65 64 3a 0a 55 73 |th:.Received:.Us| 0060 65 72 2d 41 67 65 6e 74 3a 0a|er-Agent:.| -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] [couriermlm] Problem with headerdel
Jean-Christophe Boggio writes: Hello, For my "pirtest" mailing list, I have the following headerdel file : $ cat headerdel From: Reply-To: To: Cc: Delivered-To: Sender: X-Originating-Email: Old-Return-Path: Received: But the "Delivered-To" header does not get deleted (the original one). Following is the message I receive after moderation. The first Delivered-To (the one with "mytestingaddress@gmail") is legit but the "original" one, the one that is sent to the list (cat-pirtest@joker...), should be removed. Am I doing something wrong ? Wild guess: check for spurious trailing whitespace, in headerdel. Make sure lines are terminated with newlines pgpV59QabULwF.pgp Description: PGP signature -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] [couriermlm] Problem with headerdel
Hello, For my "pirtest" mailing list, I have the following headerdel file : $ cat headerdel From: Reply-To: To: Cc: Delivered-To: Sender: X-Originating-Email: Old-Return-Path: Received: But the "Delivered-To" header does not get deleted (the original one). Following is the message I receive after moderation. The first Delivered-To (the one with "mytestingaddress@gmail") is legit but the "original" one, the one that is sent to the list (cat-pirtest@joker...), should be removed. Am I doing something wrong ? >From - Mon Jul 22 16:05:47 2013 X-Account-Key: account11 X-UIDL: GmailId14006ab61d0e9f83 X-Mozilla-Status: 0001 X-Mozilla-Status2: X-Mozilla-Keys: Delivered-To: mytestingaddr...@gmail.com Received: by 10.194.55.130 with SMTP id s2csp96668wjp; Mon, 22 Jul 2013 07:03:33 -0700 (PDT) X-Received: by 10.194.78.42 with SMTP id y10mr19293384wjw.93.1374501429520; Mon, 22 Jul 2013 06:57:09 -0700 (PDT) Return-Path: .org> Received: from joker..org (joker..org. [88.190.56.198]) by mx.google.com with ESMTPS id wl8si11010154wjc.17.2013.07.22.06.56.39 for (version=TLSv1.2 cipher=AES128-SHA bits=128/128); Mon, 22 Jul 2013 06:57:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of pirtest-bounce-4-mytestingaddress=gmail.com@.org designates 88.190.56.198 as permitted sender) client-ip=88.190.56.198; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of pirtest-bounce-4-mytestingaddress=gmail.com@.org designates 88.190.56.198 as permitted sender) smtp.mail=pirtest-bounce-4-mytestingaddress=gmail.com@.org Received: from localhost (localhost [127.0.0.1]) (uid 1003) by joker..org with local; Mon, 22 Jul 2013 15:56:39 +0200 id 044A000D.51ED3A17.A080 Delivered-To: cat-pirtest@joker..org From: Irrelevants Message-ID: <51ED39FC.1040007@.org> Date: Mon, 22 Jul 2013 15:56:12 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 Subject: test6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: undisclosed-recipients: ; test6 Thanks (again), JC PS: Using courier 0.68.2-1 (debian wheezy official) -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Ricardo Kleemann writes:
Then, don't start Courier on the test machine. Even if Courier is not
running, it will still accept new messages, which will simply get writted
into the ${localstatedir}/tmp directory (/var/spool/courier/tmp, or
/usr/lib/courier/var/tmp). You can then invoke "couriermlm msg directory"
manually, with a test message supplied on standard input. couriermlm should
then go through the subscriber list, and generate outgoing messages. They'll
be accepted, but queued up in the tmp directory without being processed. As
long as you don't start Courier, they won't go anywhere.
This is a good way to confirm which messages go out to the entire subscriber
base. Then, the tmp directory can be wiped, with no further harm done.
If you do not have a test message, run couriermlm export to export the
subscriber list, compress it, and send it to me. I'll try to set it up on a
test box, and see if I can figure out something.
I don't really have a way of doing this. Maybe I can try exporting,
wiping out the list and importing?
I can also send you the compressed list if you have any way of testing
it.
Yes, send me the compressed list.
You should really have a test machine. That's just good practice.
pgpmZ5OsPIOsN.pgp
Description: PGP signature
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Ricardo Kleemann writes: Sam, If I want to export and import back in, what is the best way to wipe out a list's subscribers? Considering I have over 18,000 in there, can I simply rm -rf sublist/*? Yes, that'll work. pgptVXGVERjIG.pgp Description: PGP signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Sam,
If I want to export and import back in, what is the best way to wipe out
a list's subscribers? Considering I have over 18,000 in there, can I
simply rm -rf sublist/*?
On Fri, 2008-11-21 at 22:57 -0500, Sam Varshavchik wrote:
> Ricardo Kleemann writes:
>
> >> > To add more to the mystery, even though lsub lists those 2 addresses,
> >> > the
> >> > sublist directory does NOT have any directory for the edm.co.mz domain:
> >> >
> >> > # ls -d /shared/data/couriermlm/reflexoes1/sublist/*mz*
> >> > /shared/data/couriermlm/reflexoes1/sublist/teledata.mz
> >> >
> >> > So why would the sublist not cover those 2 addresses that are said to be
> >> > subscribed?
> >>
> >> This is fine. A separate subscription file does not get created until
> >> there
> >> are three addresses subscribed to the list from the domain. Domains with
> >> two
> >> or fewer subscribers are all stored in the same file.
> >>
> > Ok, that makes sense.
> >
> > However, what doesn't make sense is that a few of the subscribed
> > addresses don't appear to be even tried, it's almost like courier
> > "overlooked" them. It's not a list address or configuration thing
> > because 99+% of the addresses do get acted upon, and only a few simply
> > get overlooked.
> >
> > I'd like to somehow debug this further...
>
> Well, it's straightforward debugging from this point on. Unless you can
> figure a pattern that all the problematic addresses fit into, that might
> point towards a clue.
>
> Your log grep included the list's return address. Try grepping for the
> problematic subscriber addresses without the list address, see, if anything,
> gets logged for the subscriber addresses that might not directly reference
> the list's address, but might be related.
>
> There's one possible thing you can try if you have a separate test machine
> which is not processing any mail, otherwise. Export the subscriber list, and
> import it into a test mailing list on the test machine.
>
> Then, don't start Courier on the test machine. Even if Courier is not
> running, it will still accept new messages, which will simply get writted
> into the ${localstatedir}/tmp directory (/var/spool/courier/tmp, or
> /usr/lib/courier/var/tmp). You can then invoke "couriermlm msg directory"
> manually, with a test message supplied on standard input. couriermlm should
> then go through the subscriber list, and generate outgoing messages. They'll
> be accepted, but queued up in the tmp directory without being processed. As
> long as you don't start Courier, they won't go anywhere.
>
> This is a good way to confirm which messages go out to the entire subscriber
> base. Then, the tmp directory can be wiped, with no further harm done.
>
> If you do not have a test message, run couriermlm export to export the
> subscriber list, compress it, and send it to me. I'll try to set it up on a
> test box, and see if I can figure out something.
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___ courier-users mailing list
> courier-users@lists.sourceforge.net Unsubscribe:
> https://lists.sourceforge.net/lists/listinfo/courier-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Hi Sam,
Thanks for the tips.
> > However, what doesn't make sense is that a few of the subscribed
> > addresses don't appear to be even tried, it's almost like courier
> > "overlooked" them. It's not a list address or configuration thing
> > because 99+% of the addresses do get acted upon, and only a few simply
> > get overlooked.
> >
> > I'd like to somehow debug this further...
>
> Well, it's straightforward debugging from this point on. Unless you can
> figure a pattern that all the problematic addresses fit into, that might
> point towards a clue.
>
> Your log grep included the list's return address. Try grepping for the
> problematic subscriber addresses without the list address, see, if anything,
> gets logged for the subscriber addresses that might not directly reference
> the list's address, but might be related.
>
Well actually I've grepped the log for the domain only, not even
regarding the user or the list addresses. The only matches for the
domain in question is that one address in the reflexoes4 list. The
reflexoes1 list which has 2 addresses in that domain, there's no
evidence at all in the log of any attempt to deliver.
> There's one possible thing you can try if you have a separate test machine
> which is not processing any mail, otherwise. Export the subscriber list, and
> import it into a test mailing list on the test machine.
>
> Then, don't start Courier on the test machine. Even if Courier is not
> running, it will still accept new messages, which will simply get writted
> into the ${localstatedir}/tmp directory (/var/spool/courier/tmp, or
> /usr/lib/courier/var/tmp). You can then invoke "couriermlm msg directory"
> manually, with a test message supplied on standard input. couriermlm should
> then go through the subscriber list, and generate outgoing messages. They'll
> be accepted, but queued up in the tmp directory without being processed. As
> long as you don't start Courier, they won't go anywhere.
>
> This is a good way to confirm which messages go out to the entire subscriber
> base. Then, the tmp directory can be wiped, with no further harm done.
>
> If you do not have a test message, run couriermlm export to export the
> subscriber list, compress it, and send it to me. I'll try to set it up on a
> test box, and see if I can figure out something.
>
I don't really have a way of doing this. Maybe I can try exporting,
wiping out the list and importing?
I can also send you the compressed list if you have any way of testing
it.
Thanks
Ricardo
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Ricardo Kleemann wrote: > However, what doesn't make sense is that a few of the subscribed > addresses don't appear to be even tried, it's almost like courier > "overlooked" them. It's not a list address or configuration thing > because 99+% of the addresses do get acted upon, and only a few simply > get overlooked. > > I'd like to somehow debug this further... Are you sure that your list server is not configured to handle mail for problematic domains? Maybe you have alias for problematic user. In this case you need to check for addresses _after_ alias processing in your logs. -- Aidas Kasparas IT administrator GM Consult Group, UAB - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Ricardo Kleemann writes:
> To add more to the mystery, even though lsub lists those 2 addresses, the
> sublist directory does NOT have any directory for the edm.co.mz domain:
>
> # ls -d /shared/data/couriermlm/reflexoes1/sublist/*mz*
> /shared/data/couriermlm/reflexoes1/sublist/teledata.mz
>
> So why would the sublist not cover those 2 addresses that are said to be
> subscribed?
This is fine. A separate subscription file does not get created until there
are three addresses subscribed to the list from the domain. Domains with two
or fewer subscribers are all stored in the same file.
Ok, that makes sense.
However, what doesn't make sense is that a few of the subscribed
addresses don't appear to be even tried, it's almost like courier
"overlooked" them. It's not a list address or configuration thing
because 99+% of the addresses do get acted upon, and only a few simply
get overlooked.
I'd like to somehow debug this further...
Well, it's straightforward debugging from this point on. Unless you can
figure a pattern that all the problematic addresses fit into, that might
point towards a clue.
Your log grep included the list's return address. Try grepping for the
problematic subscriber addresses without the list address, see, if anything,
gets logged for the subscriber addresses that might not directly reference
the list's address, but might be related.
There's one possible thing you can try if you have a separate test machine
which is not processing any mail, otherwise. Export the subscriber list, and
import it into a test mailing list on the test machine.
Then, don't start Courier on the test machine. Even if Courier is not
running, it will still accept new messages, which will simply get writted
into the ${localstatedir}/tmp directory (/var/spool/courier/tmp, or
/usr/lib/courier/var/tmp). You can then invoke "couriermlm msg directory"
manually, with a test message supplied on standard input. couriermlm should
then go through the subscriber list, and generate outgoing messages. They'll
be accepted, but queued up in the tmp directory without being processed. As
long as you don't start Courier, they won't go anywhere.
This is a good way to confirm which messages go out to the entire subscriber
base. Then, the tmp directory can be wiped, with no further harm done.
If you do not have a test message, run couriermlm export to export the
subscriber list, compress it, and send it to me. I'll try to set it up on a
test box, and see if I can figure out something.
pgpvSSf1NkF0M.pgp
Description: PGP signature
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Hi Sam. > > Now, the ones that DON'T work: > > > > # couriermlm lsub /shared/data/couriermlm/reflexoes1|grep edm.co.mz > > [EMAIL PROTECTED] (06-Nov-2008) > > [EMAIL PROTECTED] (6-Nov-2008) > > > > # grep edm.co.mz /var/log/mail.log.0 |grep reflexoes1 > > (returns nothing at all) > > You are expecting that bounces have 'reflexoes1' in the return address. Your > first mailing list's address is, apparently, [EMAIL PROTECTED] Do you have > any > reflexoes1 entries in your maillog, at all? > > Maybe this list's ADDRESS setting is not set correctly. > Unfortunately that's not the case. The list has over 18,000 subscribers, and every night over 12,000 definitely get delivered successfully. I run a script every night that checks "success: delivered" for each of the lists, including both reflexoes1 and reflexoes4. I've also written a script that checks ANY attempt by courier against each the subscribed addresses and there are certainly a few, just like this one I'm tracking down, that never even have a mention in the log. > > To add more to the mystery, even though lsub lists those 2 addresses, the > > sublist directory does NOT have any directory for the edm.co.mz domain: > > > > # ls -d /shared/data/couriermlm/reflexoes1/sublist/*mz* > > /shared/data/couriermlm/reflexoes1/sublist/teledata.mz > > > > So why would the sublist not cover those 2 addresses that are said to be > > subscribed? > > This is fine. A separate subscription file does not get created until there > are three addresses subscribed to the list from the domain. Domains with two > or fewer subscribers are all stored in the same file. > Ok, that makes sense. However, what doesn't make sense is that a few of the subscribed addresses don't appear to be even tried, it's almost like courier "overlooked" them. It's not a list address or configuration thing because 99+% of the addresses do get acted upon, and only a few simply get overlooked. I'd like to somehow debug this further... Ricardo - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Ricardo Kleemann writes: Here's the one that DOES work: # couriermlm lsub /shared/data/couriermlm/reflexoes4|grep edm.co.mz [EMAIL PROTECTED] (05-Nov-2008) # grep edm.co.mz /var/log/mail.log.0 |grep reflexoes4 Nov 20 16:37:45 email1 courierd: started,id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,module=esmtp,host=edm.co.mz,addr=<[EMAIL PROTECTED]> Nov 20 16:37:53 email1 courieresmtp: id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>: 250 OK id=1L3K2V-x1-Sk Nov 20 16:37:53 email1 courieresmtp: id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=8270,success: delivered: mta.edm.co.mz [196.28.228.18] Nov 20 16:37:53 email1 courieresmtp: id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=8270,status: success Now, the ones that DON'T work: # couriermlm lsub /shared/data/couriermlm/reflexoes1|grep edm.co.mz [EMAIL PROTECTED] (06-Nov-2008) [EMAIL PROTECTED] (6-Nov-2008) # grep edm.co.mz /var/log/mail.log.0 |grep reflexoes1 (returns nothing at all) You are expecting that bounces have 'reflexoes1' in the return address. Your first mailing list's address is, apparently, [EMAIL PROTECTED] Do you have any reflexoes1 entries in your maillog, at all? Maybe this list's ADDRESS setting is not set correctly. To add more to the mystery, even though lsub lists those 2 addresses, the sublist directory does NOT have any directory for the edm.co.mz domain: # ls -d /shared/data/couriermlm/reflexoes1/sublist/*mz* /shared/data/couriermlm/reflexoes1/sublist/teledata.mz So why would the sublist not cover those 2 addresses that are said to be subscribed? This is fine. A separate subscription file does not get created until there are three addresses subscribed to the list from the domain. Domains with two or fewer subscribers are all stored in the same file. pgp09moepZpXQ.pgp Description: PGP signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
>> But a search in the bounces for the address also returns nothing (which >> makes sense because if there was a bounce then I'd see it in the logs) >> find /shared/data/couriermlm/reflexoes1/bounces/ -type f |xargs grep >> mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED] >> returns nothing > The mail address would not appear verbatim in the bounces. It gets > encoded, > in the return address, slightly, to escape special characters and > punctuations. Try grepping just for the username or the domainname. Ok, I did that, and found a couple more interesting things. For this list, "reflexoes1" I find nothing at all for the domain edm.co.mz. I have another list, which has one subscriber in that domain, and delivery to it is successful. Here's the one that DOES work: # couriermlm lsub /shared/data/couriermlm/reflexoes4|grep edm.co.mz [EMAIL PROTECTED] (05-Nov-2008) # grep edm.co.mz /var/log/mail.log.0 |grep reflexoes4 Nov 20 16:37:45 email1 courierd: started,id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,module=esmtp,host=edm.co.mz,addr=<[EMAIL PROTECTED]> Nov 20 16:37:53 email1 courieresmtp: id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>: 250 OK id=1L3K2V-x1-Sk Nov 20 16:37:53 email1 courieresmtp: id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=8270,success: delivered: mta.edm.co.mz [196.28.228.18] Nov 20 16:37:53 email1 courieresmtp: id=0013404D.492602D9.5D06,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=8270,status: success Now, the ones that DON'T work: # couriermlm lsub /shared/data/couriermlm/reflexoes1|grep edm.co.mz [EMAIL PROTECTED] (06-Nov-2008) [EMAIL PROTECTED] (6-Nov-2008) # grep edm.co.mz /var/log/mail.log.0 |grep reflexoes1 (returns nothing at all) To add more to the mystery, even though lsub lists those 2 addresses, the sublist directory does NOT have any directory for the edm.co.mz domain: # ls -d /shared/data/couriermlm/reflexoes1/sublist/*mz* /shared/data/couriermlm/reflexoes1/sublist/teledata.mz So why would the sublist not cover those 2 addresses that are said to be subscribed? Ricardo - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Ricardo Kleemann writes: The bounces directory has a lot of directories in it, mailto:[EMAIL PROTECTED]:/var/lib/mailman>[EMAIL PROTECTED]:/var/lib/mailman# ls /shared/data/couriermlm/reflexoes1/bounces|wc -l 5288 But a search in the bounces for the address also returns nothing (which makes sense because if there was a bounce then I'd see it in the logs) find /shared/data/couriermlm/reflexoes1/bounces/ -type f |xargs grep mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED] returns nothing The mail address would not appear verbatim in the bounces. It gets encoded, in the return address, slightly, to escape special characters and punctuations. Try grepping just for the username or the domainname. searching through mailq also results in nothing. So evidently there's not even an attempt to send the message to this address, even though couriermlm does list it as subscribed. This is only one example. There are many others exactly like it. How can I debug this? Maybe couriermlm is halting or crashing at a certain point in the subscriber list? If you're invoking couriermlm from a .courier file, and it crashes, the list message should get either bounced back to the sender, or deferred and redelivered. If it's redelivered, you'd get complaints about duplicate list messages. If it gets bounced, the senders should complain about their messages getting bounced. Whatever the problem is, I think that a couriermlm crash is unlikely. It might be worthwhile for you to analyze the collected bounces, to see if you can spot a common problem with non-deliveries, which might lead you to an answer to this question, too. Also, when there are more than two list subscribers in the same domain, couriermlm will use multiply-addressed message to deliver messages to the recipients in the same domain, up to 20 recipients per single message. You should also grep your log file to any list message to the same domain, and collect some additional diagnostic info. pgpZQzDti9AXk.pgp Description: PGP signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] couriermlm problem
Hi, I have a couple of very large lists with couriermlm (close to 20k users each). So far it seems to me both lists have been functioning well, however it has just come to my attention that a number of users are not receiving the daily message. So I started looking through the logs to see if I could find the reason why, and so far I have no clue what's going on. Here's one example. I have a list "reflexoes1" and a subscriber [EMAIL PROTECTED] [EMAIL PROTECTED]:/var/lib/mailman# couriermlm lsub /shared/data/couriermlm/reflexoes1 |wc -l 18330 [EMAIL PROTECTED]:/var/lib/mailman# couriermlm lsub /shared/data/couriermlm/reflexoes1 |grep [EMAIL PROTECTED] [EMAIL PROTECTED] (06-Nov-2008) So the address is indeed subscribed. But the person is not receiving messages. I looked back a few days on the mail.log.* (the list sends out daily messages) and there is no mention at all of this email address (either success or failure). The bounces directory has a lot of directories in it, [EMAIL PROTECTED]:/var/lib/mailman# ls /shared/data/couriermlm/reflexoes1/bounces|wc -l 5288 But a search in the bounces for the address also returns nothing (which makes sense because if there was a bounce then I'd see it in the logs) find /shared/data/couriermlm/reflexoes1/bounces/ -type f |xargs grep [EMAIL PROTECTED] returns nothing searching through mailq also results in nothing. So evidently there's not even an attempt to send the message to this address, even though couriermlm does list it as subscribed. This is only one example. There are many others exactly like it. How can I debug this? Maybe couriermlm is halting or crashing at a certain point in the subscriber list? Ricardo- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Couriermlm problem - no subscription replies
Bernd Plagge writes: On Fri, 01 Jun 2007 03:59:25 -0700 [EMAIL PROTECTED] wrote: One easy way to get back to the default settings is to edit the options file in the list directory, and remove everything except ADDRESS and LISTPW settings. Hi Sam, I did this. uid and gid for Courier are vpopmail.vchkpw - for historical reasons. Directory structure is: /home/enaki/mail/list1-> mailing list /home/enaki/mail/postmaster/Maildir -> for users That is, the LDAP directory is specified as /home/enaki/mail and the default Maildir directory is ./Maildir. I created the list directory : drwx--S-- vpopmail.vchkpw list1 mail to [EMAIL PROTECTED] resulted in "exec: No such file or directory, broken pipe" I do not believe that this is exactly the error message that you received. It's probably "exec: No such file or directory" on one line, and some other message, which includes the word "broken pipe". You also did not explain what form this error too, whether it appeared on the command line, as an error message in your mail client, or in a bounce message. And there were probably other things either before or after this message that would shed some light on this situation. You just can't omit crucial facts like this, otherwise this is just one big goose chase. This is why instead of explaining what you saw, in your words, you should always post the raw data, cut and paste whatever you see either on the console, or in the bounce message, verbatim, without commentary. Else everyone will be chasing ghosts. You posted the log files, verbatim, that's exactly what you should be doing for every other bit of information. When I searched the source code, there were exactly six places where this error message appears, in Courier. Of the six, one place was when couriermlm generating a message to send, but being unable to run Courier's sendmail wrapper. So one possibility is that /usr/lib/courier/bin/sendmail is missing. The other situation where this error might come up involves courierfilters. I doubt that it would come up here, but courierfilters are involved in the process of vetting all messages that come through the system, including messages coming out of couriermlm, so you'll need to clarify if you have any courier filters instead. But, again, we need to see the complete context of the error message. Also, you said that putting |/bin/echo ".courier-default" into the .courier-default file showed that this .courier file was getting invoked. Prepent | echo ".courier-default: $DEFAULT" in there, to check that the environment is what couriermlm expects it to be. Changing the ownership to root.vchkpw resulted in "unable to read .courier file" Changed ownership back to vpopmail.vchkpw and the permission of .courier* files to 755. Well, look, the permissions of these files and directories is not a guessing game. There's really only one way to get this right, and you just can't turn it into a trial-by-error. If you do, that tells me you have not fully worked out how the permissions should be set up on your system, and that's something that you need to figure out as a first order of business. Whatever the account's uid and gid is given in LDAP must match the ownership of all files in the account's home directory, and the permissions on everything needs to be sane, and reasonable. If you have a login session open that uses whatever uid and gid is given in LDAP, and with the home directory set to what LDAP tells you the home directory is, would you be able to access, create, or modify everything in the home directory? If the answer is no, the way you set it is wrong, and it needs to be right. This is not a guessing game, there's only one right answer here. But, whatever permissions are, that should not, in theory, affect couriermlm's ability to run the sendmail command, /usr/lib/courier/bin/sendmail. couriermlm is not something special. It's an ordinary process that's started from your .courier file. And, to send a message, it invokes /usr/lib/courier/bin/sendmail, whose permissions should allow anything to execute it. pgpZf4z15V9xV.pgp Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Couriermlm problem - no subscription replies
On Fri, 01 Jun 2007 03:59:25 -0700 [EMAIL PROTECTED] wrote: > 差出人: Sam Varshavchik <[EMAIL PROTECTED]> > 宛先:: courier-users@lists.sourceforge.net > 件名: Re: [courier-users] Couriermlm problem - no subscription replies > 日付: Thu, 31 May 2007 20:37:11 -0400 > > Bernd Plagge writes: > > > On Thu, 31 May 2007 07:42:46 -0700 > > [EMAIL PROTECTED] wrote: > > > >> 差出人: Sam Varshavchik <[EMAIL PROTECTED]> > >> 宛先:: courier-users@lists.sourceforge.net > >> 件名: Re: [courier-users] Couriermlm problem - no subscription replies > >> 日付: Wed, 30 May 2007 18:17:44 -0400 > >> > >> Bernd Plagge writes: > >> > >> > Added .courier, .courier-default, .courier-owner to the list directory. > >> > > >> > Setup ldap entry for the list user. > >> > > >> > Otherwise I use maildrop for local delivery. > >> > > >> > Now, if I send a subscription request to [EMAIL PROTECTED] > >> > (domains are changed!) the mail is delivered by courierlocal. > >> > > >> > But: Neither do I get a confirmation mail nor does the address show > >> > with couriermlm lsub . > >> > >> What did you put in .courier-default? > > > > Hi Sam, > > > > this is the content of my .courier-default file: > > > > # delivery of control messages > > |/usr/bin/couriermlm ctlmsg /home/enaki/mail/list1 > > > > > > For test purposes I replaced the command with > > |/bin/echo ".courier-default" > > > > and could see the message in the log. > > So, I'm sure that the file gets processed. > > > > I also played with permission and when courier can't access the file a > > error line like: "permission problem - can't open file" shows. > > > > What else can I check? > > I recall that you've set up certain list options: moderation, etc… > > Let's take it one step a time. Reset the configuration to the default list > config, and try subscribing. > > One easy way to get back to the default settings is to edit the options file > in the list directory, and remove everything except ADDRESS and LISTPW > settings. Hi Sam, I did this. uid and gid for Courier are vpopmail.vchkpw - for historical reasons. Directory structure is: /home/enaki/mail/list1-> mailing list /home/enaki/mail/postmaster/Maildir -> for users That is, the LDAP directory is specified as /home/enaki/mail and the default Maildir directory is ./Maildir. I created the list directory : drwx--S-- vpopmail.vchkpw list1 mail to [EMAIL PROTECTED] resulted in "exec: No such file or directory, broken pipe" Changing the ownership to root.vchkpw resulted in "unable to read .courier file" Changed ownership back to vpopmail.vchkpw and the permission of .courier* files to 755. Mail was delivered but no reply back. Log for the last attempt (mails to list1-subscribe and list1-help) are: Jun 2 10:46:43 tokyo courierd: started,id=00010432.4660CC03.09D9,from=<[EMAIL PROTECTED]>,module=local,[EMAIL PROTECTED] bscribe!64020!64020!/home/enaki/mail/list1!!,addr=<[EMAIL PROTECTED]> Jun 2 10:46:43 tokyo courierd: Waiting. shutdown time=none, wakeup time=Sat Jun 2 10:49:59 2007, queuedelivering=2, inprogress=1 Jun 2 10:46:43 tokyo courierlocal: id=00010432.4660CC03.09D9,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=10 71,success: Message delivered. Jun 2 10:46:43 tokyo courierd: completed,id=00010432.4660CC03.09D9 Jun 2 10:46:43 tokyo courierd: Waiting. shutdown time=Sat Jun 2 10:51:43 2007, wakeup time=Sat Jun 2 10:49:59 2007, queuedelivering=1 , inprogress=0 Jun 2 10:47:11 tokyo courierd: started,id=00010414.4660CB9B.09C3,from=<[EMAIL PROTECTED]>,module=local,[EMAIL PROTECTED] lp!64020!64020!/home/enaki/mail/list1!!,addr=<[EMAIL PROTECTED]> Jun 2 10:47:11 tokyo courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 Jun 2 10:47:11 tokyo courierlocal: id=00010414.4660CB9B.09C3,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=1061,su ccess: Message delivered. Jun 2 10:47:11 tokyo courierd: completed,id=00010414.4660CB9B.09C3 J Any ideas? Best regards, Bernd -- プラゲ ベェアント - Bernd Plagge ファースト・チョイス・インターネット(有) First Choice Internet Ltd., Tokyo Tel. 03-4500-7799 Fax. 03-4400-3723 mail: [EMAIL PROTECTED] url: http://www.choicenet.ne.jp - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Couriermlm problem - no subscription replies
Bernd Plagge writes: On Thu, 31 May 2007 07:42:46 -0700 [EMAIL PROTECTED] wrote: 差出人: Sam Varshavchik <[EMAIL PROTECTED]> 宛先:: courier-users@lists.sourceforge.net 件名: Re: [courier-users] Couriermlm problem - no subscription replies 日付: Wed, 30 May 2007 18:17:44 -0400 Bernd Plagge writes: > Added .courier, .courier-default, .courier-owner to the list directory. > > Setup ldap entry for the list user. > > Otherwise I use maildrop for local delivery. > > Now, if I send a subscription request to [EMAIL PROTECTED] > (domains are changed!) the mail is delivered by courierlocal. > > But: Neither do I get a confirmation mail nor does the address show > with couriermlm lsub . What did you put in .courier-default? Hi Sam, this is the content of my .courier-default file: # delivery of control messages |/usr/bin/couriermlm ctlmsg /home/enaki/mail/list1 For test purposes I replaced the command with |/bin/echo ".courier-default" and could see the message in the log. So, I'm sure that the file gets processed. I also played with permission and when courier can't access the file a error line like: "permission problem - can't open file" shows. What else can I check? I recall that you've set up certain list options: moderation, etc… Let's take it one step a time. Reset the configuration to the default list config, and try subscribing. One easy way to get back to the default settings is to edit the options file in the list directory, and remove everything except ADDRESS and LISTPW settings. pgpG6TngrsYjv.pgp Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Couriermlm problem - no subscription replies
On Thu, 31 May 2007 07:42:46 -0700 [EMAIL PROTECTED] wrote: > 差出人: Sam Varshavchik <[EMAIL PROTECTED]> > 宛先:: courier-users@lists.sourceforge.net > 件名: Re: [courier-users] Couriermlm problem - no subscription replies > 日付: Wed, 30 May 2007 18:17:44 -0400 > > Bernd Plagge writes: > > > Added .courier, .courier-default, .courier-owner to the list directory. > > > > Setup ldap entry for the list user. > > > > Otherwise I use maildrop for local delivery. > > > > Now, if I send a subscription request to [EMAIL PROTECTED] > > (domains are changed!) the mail is delivered by courierlocal. > > > > But: Neither do I get a confirmation mail nor does the address show > > with couriermlm lsub . > > What did you put in .courier-default? Hi Sam, this is the content of my .courier-default file: # delivery of control messages |/usr/bin/couriermlm ctlmsg /home/enaki/mail/list1 For test purposes I replaced the command with |/bin/echo ".courier-default" and could see the message in the log. So, I'm sure that the file gets processed. I also played with permission and when courier can't access the file a error line like: "permission problem - can't open file" shows. What else can I check? Thanks! Bernd - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Couriermlm problem - no subscription replies
Bernd Plagge writes: Added .courier, .courier-default, .courier-owner to the list directory. Setup ldap entry for the list user. Otherwise I use maildrop for local delivery. Now, if I send a subscription request to [EMAIL PROTECTED] (domains are changed!) the mail is delivered by courierlocal. But: Neither do I get a confirmation mail nor does the address show with couriermlm lsub . What did you put in .courier-default? pgpmEZcVHhKSb.pgp Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Couriermlm problem - no subscription replies
Hi everybody, I got a problem with the courier mailing list. Setting up worked fine (non-root user), set the options for the web access, updated /etc/courier/webmlmrc, updated Apache configuration. Web access worked fine, set list to 'subscription moderation'. Added .courier, .courier-default, .courier-owner to the list directory. Setup ldap entry for the list user. Otherwise I use maildrop for local delivery. Now, if I send a subscription request to [EMAIL PROTECTED] (domains are changed!) the mail is delivered by courierlocal. But: Neither do I get a confirmation mail nor does the address show with couriermlm lsub . The same happens if I send a mail to [EMAIL PROTECTED] However, a mail to [EMAIL PROTECTED] is correctly being forwarded to the list owners email address. I spent most of the day to solve this problem but probably I'm missing something fundamental. Any advice? Below are some system log entries. Thanks, Bernd May 31 00:40:31 tokyo courierd: started,id=00010414.465D9AEF.75CC,from=<[EMAIL PROTECTED]>,module=local,[EMAIL PROTECTED] scribe!64020!64020!/home/target/mail/list1!!,addr=<[EMAIL PROTECTED]> May 31 00:40:31 tokyo courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 May 31 00:40:31 tokyo courierlocal: id=00010414.465D9AEF.75CC,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=134 8,success: Message delivered. May 31 00:40:31 tokyo courierd: completed,id=00010414.465D9AEF.75CC M May 31 00:51:27 tokyo courierd: started,id=00010428.465D9D7F.7669,from=<[EMAIL PROTECTED]>,module=local,[EMAIL PROTECTED] !owner!64020!64020!/home/target/mail/list1!!,addr=<[EMAIL PROTECTED]> May 31 00:51:27 tokyo courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 May 31 00:51:27 tokyo courierlocal: id=00010428.465D9D7F.7669,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=108 4,success: Message delivered. May 31 00:51:27 tokyo courierd: newmsg,id=0001043B.465D9D7F.766D: dns; localhost (localhost [127.0.0.1]) May 31 00:51:27 tokyo courierd: started,id=0001043B.465D9D7F.766D,from=<[EMAIL PROTECTED]>,module=esmtp,host=mydomain.ne.j p,addr=<[EMAIL PROTECTED]> May 31 00:51:27 tokyo courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=2, inprogress=2 May 31 00:51:27 tokyo courierd: completed,id=00010428.465D9D7F.7669 May 31 00:51:27 tokyo courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 May 31 00:51:33 tokyo courieresmtp: id=0001043B.465D9D7F.766D,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>: 250 ok 1180540293 qp 3008 May 31 00:51:33 tokyo courieresmtp: id=0001043B.465D9D7F.766D,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=131 0,success: delivered: [203.141.151.199] [203.141.151.199] May 31 00:51:33 tokyo courieresmtp: id=0001043B.465D9D7F.766D,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=131 0,status: success May 31 00:51:33 tokyo courierd: completed,id=0001043B.465D9D7F.766D M Bernd -- プラゲ ベェアント - Bernd Plagge ファースト・チョイス・インターネット(有) First Choice Internet Ltd., Tokyo Tel. 03-4500-7799 Fax. 03-4400-3723 mail: [EMAIL PROTECTED] url: http://www.choicenet.ne.jp - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] couriermlm problem
Patryk Szajer writes: Hello, I have a strange problem with couriermlm and several (not all) mailing lists running on it. I'm running courier with ldap authentication. #cd /var/lib/courier/vmail #couriermlm lsub test/forum|grep patryk [EMAIL PROTECTED] (06/28/05) #cat /etc/courier/smtpaccess/default |grep 127 127.0.0.1 allow,RELAYCLIENT #telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 hostname.domain.pl ESMTP ehlo localhost 250-hostname.domain.pl Ok. 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN X-NETSCAPE-HAS-BUGS 250-XVERP=Courier 250-XEXDATA 250-XSECURITY=NONE,STARTTLS 250-PIPELINING 250-8BITMIME 250-SIZE 250 DSN mail from:<[EMAIL PROTECTED]> 250 Ok. rcpt to:<[EMAIL PROTECTED]> 250 Ok. data 354 Ok. Subject: test test . 250 Ok. 42C14970.44CB quit You need a matching From: header. couriermlm checks the From: header, not the envelope return address. pgphXf3bqOWuj.pgp Description: PGP signature
[courier-users] couriermlm problem
Hello, I have a strange problem with couriermlm and several (not all) mailing lists running on it. I'm running courier with ldap authentication. #cd /var/lib/courier/vmail #couriermlm lsub test/forum|grep patryk [EMAIL PROTECTED] (06/28/05) #cat /etc/courier/smtpaccess/default |grep 127 127.0.0.1 allow,RELAYCLIENT #telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 hostname.domain.pl ESMTP ehlo localhost 250-hostname.domain.pl Ok. 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN X-NETSCAPE-HAS-BUGS 250-XVERP=Courier 250-XEXDATA 250-XSECURITY=NONE,STARTTLS 250-PIPELINING 250-8BITMIME 250-SIZE 250 DSN mail from:<[EMAIL PROTECTED]> 250 Ok. rcpt to:<[EMAIL PROTECTED]> 250 Ok. data 354 Ok. Subject: test test . 250 Ok. 42C14970.44CB quit 221 Bye. Connection closed by foreign host. In mail.log i got this: Jun 28 14:58:35 hostname courierd: newmsg,id=0068C06F.42C14970.44CB: dns; localhost (softdnserr [:::127.0.0.1]) Jun 28 14:58:36 hostname courierd: started,id=0068C06F.42C14970.44CB,from=<[EMAIL PROTECTED]>,module=local,host=test!forum!1000!1000!/var/lib/courier /vmail/test!!2097152S,200C,addr= Jun 28 14:58:36 hostname courierd: Waiting. shutdown time=none, wakeup time=Tue Jun 28 14:59:08 2005, queuedelivering=88, inprogress=1 Jun 28 14:58:36 hostname courierlocal: id=0068C06F.42C14970.44CB,from=@portal.ngo.pl>,addr=<[EMAIL PROTECTED]>: You are not subscribed to this mailing list. Jun 28 14:58:36 hostname courierlocal: id=0068C06F.42C14970.44CB,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,status: failure Jun 28 14:58:37 hostname courierd: completed,id=0068C06F.42C14970.44CB After this courier sends me a bounce: Reporting-MTA: dns; hostname.domain.pl Arrival-Date: Tue, 28 Jun 2005 14:58:35 +0200 Received-From-MTA: dns; localhost (softdnserr [:::127.0.0.1]) Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: unknown; You are not subscribed to this mailing list. Some (but not all) of the subscribers have the same problem. When (properly) subscribed user sends a message to this mailing list, courier sends them to me with no problem. I'm running debian with courier 0.47-4 (earlier 0.37.3). I've tried couriermlm unsub and sub but it doesn't help. Any ideas what may be wrong ? Regards, -- Patryk Szajer --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Couriermlm problem
I'm trying to create a few lists, and one is working, another isn't. I need to create 3 total under one domain. I have one, [EMAIL PROTECTED], working. I try to create [EMAIL PROTECTED], and it won't work. If I try sending a message to [EMAIL PROTECTED] I get "user unknown" from the serverthough sending to [EMAIL PROTECTED] works. All mail for the domain insw.org goes to the user insw, with a home directory of /home/insw. Members is at /home/insw/members, and indiana is at /home/insw/indiana. I have all the .courier files in place, and I have all the permissions set the same on both lists. Is there something that prohibits me from having more than one list per domain? I can't see any other reason why this wouldn't work. Thanks, James J. Covington - KB9ZXY - Muncie, IN [EMAIL PROTECTED] InterNational Storm Watchers Association (INSWA) Founder and President www.insw.org and/or www.insw.org/indiana unit# 00 Indiana Chasers of Adverse and Severe wEather (INCHASE) www.inchase.org member #8 Owner www.Thrift-E-Design.com "Making professional web design affordable"
