July 2002 - Smartlist - lists.rwth-aachen.de

problemes with Subject field
by Anne Avaro 29 Jul '02

29 Jul '02

Hello, I customised my rc.custom file and my rc.local.s10 fiel so that in the subject line, the name of mys list appears in all messages. Unfortunately, the subject line is duplicated every time the person who first originated a thread gets an answer. To explain more clearly, when someone answers to a message, all members of the list get the message with the correct subjetc line (like thise [List name] Subject), but the orginator of the message, gets the subject quoted twice like this : [List name] Re: [List name]: subject. How can I stop the pre-customised subject to be duplicated in the subject line ? Thanks

2 1

non-accept list subscriber problem
by Gyan Penrose-Kafka 27 Jul '02

27 Jul '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In configuring Smartlist, I delinked the accept list so that anyone could subscribe, but only actual club members could post. In testing, I subscribed via one of my accounts and set that acct. as the only user in the accept list. I then subscribed as a seperate user from a different account. I then sent an e:mail from the subscribed but non-accept list address and the accept.txt message got sent to me 25 times. Anyone know how to fix this? Peace, Gyan Life is a mystery to be lived, not a problem to be solved. -- Osho. ��`��`��o,,,,o��`��o��`��o,,,,o��`��o��`�� Gyan Penrose-Kafka * gyan(a)zenmonkey.net * ICQ # 37394131 P.O. Box 232092, Encinitas, CA 92023 USA -- tel: +760.613-4926 ��`��`��o,,,,o��`��o��`��o,,,,o��`��o��`�� For my PGP key send a message to pgpkey(a)zenmonkey.net -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and its affiliated companies. iQA/AwUBPT9wKqpfFVI4NVzFEQKWkACgvQ74BUY0l2DQe9if6mE49ZhD2zoAnRxb ITJCF+qhL02w2CXzA0HUEfvh =fc+j -----END PGP SIGNATURE-----

2 2

Generating list usage statistics
by Harshal 23 Jul '02

23 Jul '02

Hi, This is not necessarily a SmartList question but with all the list admins here I was hoping someone might be able to help. Does anyone generate statistics of their list(s) like number of messages per subscriber, subscribers with largest messages, largest threads etc.? If so, what do you use for this? Thanks, Harshal ===== http://www.mumbai-central.com : Where Mumbaikars meet __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com

1 0

Looking for help.
by Gyan Penrose-Kafka 23 Jul '02

23 Jul '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an account with a web hosting service. I would like to set up SmartList to work on this, and I've been able to do everything except for setting up the alias file because I don't have write access to the directory. How do I work around this? Peace, Gyan Life is a mystery to be lived, not a problem to be solved. -- Osho. ��`��`��o,,,,o��`��o��`��o,,,,o��`��o��`�� Gyan Penrose-Kafka * gyan(a)zenmonkey.net * ICQ # 37394131 P.O. Box 232092, Encinitas, CA 92023 USA -- tel: +760.613-4926 ��`��`��o,,,,o��`��o��`��o,,,,o��`��o��`�� For my PGP key send a message to pgpkey(a)zenmonkey.net -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and its affiliated companies. iQA/AwUBPTzZu6pfFVI4NVzFEQKeSACgqDQNFWSSfdI5HhfY9lUDlqMquLQAoIfV 0U9sTp101Jn3MtjXj8oexB6T =bD6a -----END PGP SIGNATURE-----

2 1

Can I remotely create a list ?
by Kapoor, Nishikant X 23 Jul '02

23 Jul '02

I have a very basic question: Is it possible to create a list remotely say, by a perl script or something... The SmartList manual talks about maintaining lists remotely but I was wondering if it could be created as well. Thanks Nishi

2 1

Re: X-Commands in body longer than 72-80 characters?
by KEVIN ZEMBOWER 20 Jul '02

20 Jul '02

Peter, the only criticism I have of this method is that it requires the person sending the X-Command to know in advance that it's going to be wrapped, and to put the magic "_END" at the end of this. This was not my situation; the X-Commands just suddenly stopped working (for only long email addresses, we discovered later) and no one knew why. I prefer a solution which says: "X-Commands, if they appear in the body of a message, must be the first line, and must be followed by a blank line before the rest of the body of the message, or be the only thing in the message. If there's more than one X-Command in the body, they must not be separated by a blank line." I think that this would work more intuitively and naturally. It should also work for automatic word wrapping which occurs without the author's knowledge or consent. Unfortunately, I don't know how to write the perl code for this. Sorry. Thank you for your efforts to update the FAQ. I've found it very valuable. -Kevin Zembower >>> Peter Hartzler <pete(a)hartzler.net> 07/18/02 07:59PM >>> Hmm... I'm interested in updating the FAQ, but the code seems to be a bit crazy yet. (Ironically, the word-wrapping doesn't help. ;-) Now, I could be way off on this one, so don't go jumping up to place this into production; there are some dark corners to this stuff that I'm sure I don't know about! If the goal here is to pick out and unwrap text from a message and inject that text as a header using perl, then I'm thinking this might be saner: --- cut here --- # Allow embedding a single X-Command on multiple lines # within the body of an email. (Lines will be joined.) # Look for FIRST magic X_CMD: token. If found, # take from there to __END and add to message header. # Like this: X_CMD: X-Command: blah blah blah __END # (X-Command: blah blah blah..) can be across multiple lines... # Note that this is kind of expensive, but X-Commands should # be somewhat rare. :0 Bw * X_CMD: * __END { XCMD=`perl -p -0077 -e \ 's/[\n\r\s]+/ /sg; \ s/^.*?X_CMD:\s*(.*?)\s*__END.*/$1/;'` :0 f |formail -i "$XCMD" } # End of recipe --- cut here --- Please let me know if I'm out to lunch on this one. Check out the SmartList FAQ at http://www.hartzler.net/smartlist/ Regards, Pete. _______________________________________________ Smartlist mailing list Smartlist(a)lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist

3 3

Re: X-Commands in body longer than 72-80 characters?
by KEVIN ZEMBOWER 19 Jul '02

19 Jul '02

Richard's solution, below, seems to work like a champ. No problems in testing with it so far. For others who may implement this, make sure that, if you used the original X-Commands-in-the-body recipe, from the FAQ, that you remove the older recipe before you install and run this one. Forgetting to do that cost me about an hour's work. Richard, and all others who contributed to this discussion, thank you very much. -Kevin Zembower >>> "Richard G. Ball" <Richard_Ball(a)merck.com> 07/16/02 04:25PM >>> On [2002-Jul-16] Tim Pierce <twp(a)rootsweb.com> wrote: > In article <sd342c82.076(a)ccp2.jhuccp.org>, KEVIN ZEMBOWER <KZEMBOWER(a)jhuccp.org> wrote: > > > > We're using GroupWise here. As far as I can tell, there's no option to [snip] > So, are there any alternative solutions? > > It's supposed to be legal to break headers into multiple lines > by adding whitespace at the front of each "continuation line." [snip] > > So you could try forcing the issue by breaking the X-Command into > these continuation lines yourself well before the 72-character limit. > I don't know if SmartList/procmail will actually handle the > continuation line correctly, but it seems like it ought to. If Kevin can't turn off line-wrap he probably can't enforce headers either :-( Since x-commands are not common there isn't much of a performance penalty for using the Perl sledge-hammer to make things fit. So: put the x-command in the body on as many lines as needed and then in rc.local.r00 do: :0 B * $ ^[ ]*\/$\X_COMMAND:.*[^ ] { # Remove the X_Command from the body, and insert it in the header # allow it to extend over multiple lines. the perl script concatenates the # whole body together and removes irrelevant whitespace. this is then fed back # to procmail to extract the command and put it in the header. :0 fw |perl -ne 'if(/^$/ .. eof()) {chomp;push(@l,$_);}else{print;}if(eof()){forea ch (@l){$i++;last if /__END/}$l=join(" ",@l[0..$i-1]);$l.="\n";$l=~tr/ / /s;$l= ~s/^\s+//;$l.=join("\n",@l[$i..$#l]);print "\n$l\n";}' :0 B * $ ^\/$\X_COMMAND:.*[^ ] { :0 fw | grep -v "^$X_COMMAND:" | formail -I"$MATCH" } } Note: this assumes there are no x-commands in the headers (if there are you need to account for that case separately. I think the above comes out of code Alan Stebbens put out for handling this "problem". Rich -- richard_ball(a)merck.com (I regret the presence of the legal disclaimer but I have no control over it) ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA) that may be confidential, proprietary copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please immediately return this by e-mail and then delete it. ============================================================================== _______________________________________________ Smartlist mailing list Smartlist(a)lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist

2 1

Re:X-Commands in body longer than 72-80 characters?
by KEVIN ZEMBOWER 17 Jul '02

17 Jul '02

Well, I would be laughing too, if the answer was so simple. However, I think it is not. We're using GroupWise here. As far as I can tell, there's no option to turn on or off automatic line wrapping by the user. As an experiment, I typed a message from myself (on a Win PC using GroupWise) to myself (on a Linux host). In this message, I typed one long line with no hard returns. I examined the message on the Linux host, using both PINE, and catting the /var/spool/mail file. Both showed the message broken into lines shorter than 72 characters. I'm stuck with this system. I don't run the email system, and the folks who do are not amenable to suggestion. So, are there any alternative solutions? Thank you, Charlie, for giving me a hand. -Kevin Zembower >>> Charlie Summers <charlie(a)lofcom.com> 07/16/02 12:46PM >>> At 9:47 AM -0400 7/16/02, KEVIN ZEMBOWER is rumored to have typed: > Are there any scripts or work-arounds for the problem of X-Command lines > in the body of an email message being broken into two lines if they're > longer than 72-80 characters? ROTFLMAO! (Sorry, couldn't resist.) > I don't know if something's changed in our > organization, or if we just happened to not process any longer than > this, ...or if client defaults were changed, or more likely people who don't know any better were hired... > but I can see in the mail logs that an X-Command that's too long > gets broken into two lines, usually before the email address. These > X-Commands then fail. Ok, now sit down and brace yourself. THe solution requires no additional programming, indeed practically no computer-based work whatsoever on your part. But you're going to feel a little silly when I tell you the solution is to... Tell your people to stop word-wrapping their outbound messages. He, he...this isn't a procmail problem, nor is it a SmartList problem. The X-Command: is being wrapped by the CLIENT (that is, these people have word-wrap set to say 80-characters, and their client adds a hard return to wrap the text for a human reader), so teach your people how to properly turn off word-wrapping. In Eudora, it's simple to do on a per-message basis (there's a little clickable icon on each composition window); in Outhouse Expressed, lord only knows how many hoops they'll need to jump through. But this "Suspicious X-Command Format" problem isn't yours, it's theirs. Charlie (who _refuses_ to consider possible procmail-based solutions to rebuild the X-Command line when the senders are hard-wrapping their messages) _______________________________________________ Smartlist mailing list Smartlist(a)lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist

5 11

Re: X-Commands in body longer than 72-80 characters?
by KEVIN ZEMBOWER 17 Jul '02

17 Jul '02

Just to clarify, as the original poster: I was talking about X-Commands in the body of the message. I don't think I can, using GroupWise, control or change any headers other than the To:, Subject:, CC:, and BCC: headers. I'll be putting Richard's suggestion, using the perl script, into effect this week, and will report back on my success in doing in, and if it needs any further modifications. Thank you all very much for your suggestions and clarifying comments. -Kevin Zembower >>> "Richard G. Ball" <Richard_Ball(a)merck.com> 07/17/02 12:17PM >>> On [2002-Jul-17] Tim Pierce <twp(a)rootsweb.com> wrote: > In article <20020716202554.GA76902(a)actis2.merck.com>, Richard G. Ball <Richard_Ball(a)merck.com> wrote: > > On [2002-Jul-16] Tim Pierce <twp(a)rootsweb.com> wrote: > > > > > > So you could try forcing the issue by breaking the X-Command into > > > these continuation lines yourself well before the 72-character limit. > > > I don't know if SmartList/procmail will actually handle the > > > continuation line correctly, but it seems like it ought to. > > > > If Kevin can't turn off line-wrap he probably can't enforce headers either :-( > > I understood his message to say they were already putting X-Commands > in the body. Oh. Then why did you say: On [2002-Jul-16] Tim Pierce <twp(a)rootsweb.com> wrote: > It's supposed to be legal to break headers into multiple lines > by adding whitespace at the front of each "continuation line." [example snipped] > > So you could try forcing the issue by breaking the X-Command into > these continuation lines yourself well before the 72-character limit. Which seemed to be asking Kevin to put short *header* lines into the message with whitespace to cause "continuation"? That was why I emphasized the body-centric approach since Kevin was saying he was using x-commands in the body. Rich -- richard_ball(a)merck.com (I regret the presence of the legal disclaimer but I have no control over it) ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA) that may be confidential, proprietary copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by e-mail and then delete it. ============================================================================== _______________________________________________ Smartlist mailing list Smartlist(a)lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist

1 0

smartlist 3.15 new install
by ScaryG 17 Jul '02

17 Jul '02

I'm working on a freebsd 4.3-R server. Went to the ports, installed procmail 3.22 Downloaded Smartlist 3.15 and untar-d overtop. Went to /usr/ports/mail/procmail/work/procmail-3.22/SmartList added the user:group slist... edited sendmail.cf to add the trusted user. Then I run: ./install.sh /home/slist and I get: make: don't know how to make gethome.c. Stop Any suggestions? Thanks. -Gerry

1 0