March 2001 - Smartlist - lists.rwth-aachen.de

Re: multipart/digest...again
by Charlie Summers 10 Mar '01

10 Mar '01

At 10:49 AM -0500 3/9/01, Tom Mahoney is rumored to have typed: > If I should have sent to the list...I shall. And, I note, forwarded to the list a message sent by me to you PRIVATELY without my permission. Perhaps you should spend more time learning proper netiquette, and less time b*tching about SmartList. Forwarding mail sent PRIVATELY to a PUBLIC mailing list without the permission of the author is about as low as you can get...which is exactly why I _didn't_ reply to you on-list, but rather privately, suggesting you should have sent your message to the list instead of to me since my views on this issue should be well-known to you from my previous responses. Note I had the decency NOT to send your posting to the list without your permission - something you need to learn immediately before you post to _any_ mailing list on the net. (This improper behavior is grounds for immediate explusion on the mailing lists _I_ operate. I would have expected more from someone at F&M...they appear to have considerably lowered their standards in CS.) As to the rest...there's no point to my wasting the time responding. Knock yourself out having the last word...I won't bother replying to you again. Charlie (who apologizes to the list for this unseemly exchange)

3 2

confirmation email
by Chris Woodhouse 10 Mar '01

10 Mar '01

I may be blind but I can't find anywhere in the docs, faq or list archives that explain how to setup smartlist to send a confirmation before it will subscribe someone to a list. Can someone please help? Chris

3 2

flist: Insufficient privileges to become "listserv"
by Chris Woodhouse 09 Mar '01

09 Mar '01

I have just installed Smartlist on a redhat linux 6.2 box that has all the latest security patches installed and has procmail installed at the time the OS was installed. When I send a subscrib request I get a returned error that I have included at the bottom of this message. I looked at the FAQ and it addresses a smillar problem but I think this is something different. here are the permisions for my procmail and Smartlist programs [root@p590 bin]# pwd /usr/bin [root@p590 bin]# ll |grep mail lrwxrwxrwx 1 root root 14 Feb 2 18:05 Mail -> ../../bin/mail -rwxr-xr-x 1 root root 6125 Feb 7 2000 Rnmail -rwxr-xr-x 1 root root 67608 Mar 8 2000 clockmail_applet -rwxr-xr-x 1 root root 66537 Feb 28 2000 cmail -rwxr-xr-x 1 root root 15696 Feb 29 2000 fastmail -rwxr-xr-x 1 root root 156016 Mar 6 2000 fetchmail -rwxr-xr-x 1 root root 68824 Mar 6 2000 fetchmailconf -rwxr-xr-x 1 root root 27060 Feb 7 2000 formail lrwxrwxrwx 1 root root 16 Feb 2 18:10 hoststat -> ../sbin/sendmail -r-xr-x--- 1 news news 1748 Mar 2 2000 innmail -rwxr-xr-x 1 root root 672712 Mar 7 2000 kmail -rwxr-sr-x 1 root mail 11620 Feb 7 2000 lockfile -rwxr-xr-x 1 root root 1764 Feb 7 2000 mail-files -rwxr-xr-x 1 root root 9552 Mar 7 2000 mail.local -r-xr-xr-x 1 news news 10690 Mar 2 2000 mailpost lrwxrwxrwx 1 root root 16 Feb 2 18:10 mailq -> ../sbin/sendmail -rwxr-xr-x 1 root root 5369 Feb 7 2000 mailserver -rwxr-xr-x 1 root root 2132 Feb 7 2000 mailshar -rwxr-xr-x 1 root root 5859 Feb 7 2000 mailstat -rwxr-xr-x 1 root root 42160 Feb 7 2000 mailto -rwxr-xr-x 1 root root 775 Feb 7 2000 mailto-hebrew -rwxr-xr-x 1 root root 41328 Feb 7 2000 metamail -rwxr-xr-x 1 root root 53680 Feb 29 2000 mhmail lrwxrwxrwx 1 root root 16 Feb 2 18:10 newaliases -> ../sbin/sendmail -rwxr-xr-x 2 root root 34256 Feb 29 2000 newmail -r-xr-xr-x 1 news news 3514 Mar 2 2000 news2mail -rwxr-xr-x 1 root root 1789 Feb 7 2000 patch-metamail -rwxr-xr-x 1 root root 27088 Mar 7 2000 pilot-mail -rwxr-xr-x 1 root root 449 Feb 29 2000 printmail -rwsr-sr-x 1 root mail 76432 Feb 7 2000 procmail lrwxrwxrwx 1 root root 16 Feb 2 18:10 purgestat -> ../sbin/sendmail -rwxr-xr-x 1 root root 10672 Feb 17 2000 rmail -rwxr-xr-x 1 root root 11632 Feb 7 2000 splitmail -rwxr-xr-x 1 root root 731 Mar 7 2000 vboxmail -rwxr-xr-x 1 root root 79696 Feb 29 2000 viamail -rwxr-xr-x 2 root root 34256 Feb 29 2000 wnewmail [root@p590 .bin]# pwd /var/spool/listserv/.bin [root@p590 .bin]# ll total 140 drwxrwsr-x 2 listserv listserv 4096 Mar 9 12:34 . drwxr-sr-x 7 listserv listserv 4096 Mar 9 12:25 .. -rwxr-xr-x 1 listserv listserv 9491 Apr 25 1999 arch_retrieve -rwxr-xr-x 1 listserv listserv 444 Apr 25 1999 arch_trunc -rwxr-xr-x 1 listserv listserv 5839 Apr 25 1999 createlist -rwxr-xr-x 1 listserv listserv 1220 Apr 25 1999 cronlist -rwxr-xr-x 1 listserv listserv 818 Apr 25 1999 delink -rwxr-xr-x 1 listserv listserv 3541 Apr 25 1999 digest -rwxr-xr-x 1 listserv listserv 2142 Apr 25 1999 donatelist -rwsr-xr-x 1 listserv listserv 22892 Apr 25 1999 flist -rwxr-xr-x 1 listserv listserv 3382 Apr 25 1999 flush_digests -rwxr-xr-x 1 listserv listserv 3599 Apr 25 1999 led -rw-r--r-- 1 listserv listserv 1566 Apr 25 1999 mimencap -rw-r--r-- 1 listserv listserv 4363 Apr 25 1999 mimencap.local -rwxr-xr-x 1 listserv listserv 2488 Apr 25 1999 mimesend -rwxr-xr-x 1 listserv listserv 9283 Apr 25 1999 mindlist -rwxr-xr-x 1 listserv listserv 3347 Apr 25 1999 procbounce lrwxrwxrwx 1 root listserv 17 Mar 9 11:50 procmail -> /usr/bin/procmail -rwxr-xr-x 1 listserv listserv 1887 Apr 25 1999 removelist -rwxr-xr-x 1 listserv listserv 1217 Apr 25 1999 sendmails -rwxr-xr-x 1 listserv listserv 2126 Apr 25 1999 showlink -rwxr-xr-x 1 listserv listserv 4018 Apr 25 1999 showlist -rwxr-xr-x 1 listserv listserv 3655 Apr 25 1999 subscribe -rwxr-xr-x 1 listserv listserv 2461 Apr 25 1999 unsubscribe -rwxr-xr-x 1 listserv listserv 3098 Apr 25 1999 x_command finaly the email error message ----- The following addresses had permanent fatal errors ----- "|exec /var/spool/listserv/.bin/flist cdwtest-request" (expanded from: <cdwtest-request(a)cx350498-a.okcds1.ok.home.com>) ----- Transcript of session follows ----- flist: Insufficient privileges to become "listserv" 550 "|exec /var/spool/listserv/.bin/flist cdwtest-request"... Insufficient permission Reporting-MTA: dns; p590.locoldomain Received-From-MTA: DNS; mail.oklahoman.net Arrival-Date: Fri, 9 Mar 2001 13:03:48 -0600 Final-Recipient: RFC822; <cdwtest-request(a)cx350498-a.okcds1.ok.home.com> X-Actual-Recipient: RFC822; |exec /var/spool/listserv/.bin/flist cdwtest-request(a)p590.locoldomain Action: failed Status: 5.3.0 Last-Attempt-Date: Fri, 9 Mar 2001 13:03:49 -0600

2 1

Re: multipart/digest...again
by Tom Mahoney 09 Mar '01

09 Mar '01

If I should have sent to the list...I shall. Drop the attitude with me, Charlie. I said at the very top of my message that it was not a complaint, just an observation. And I also said that I have no idea whether SL is right or wrong. But maybe, just maybe, if SL is the only one doing it the way it does, there's an issue, I have no idea. I'll be the first to admit that the likes of Topica and Yahoo are non-standard and impossible to deal with, but out of curiosity - what committee of all that's right with mail lists decreed that SL is perfect? And how do you presume to know all of the mail programs that I receive mail from? I'm not guru enough like you to edit my shell script - I'm not sure even sure I know what it is. I'm a network guy, OK. SL's doing what I want it to now, no thanks to anyone on this list. I asked some questions and got nothing but flak and answers I didn't understand. I used trial and error - a great learning tool. Tom *** What I typed to Charlie: I got myself in trouble here last time I asked about this whole subject, so let me just throw a quick comment in here - not a complaint, just an observation. I belong to quite a few lists, almost all on digest. SmartList is the only one that I know of that does whatever it does to digests. Yes, I have Eudora configured to NOT receive as attachments and the digests DO display correctly for me. Having said that, I should point out that my SmartList is the ONLY list for which this has been necessary. Whether this means SmartList is the only one doing it right or the only one doing it wrong, I couldn't say. My only comment is that it is the only one I've come in contact with that does what it does to digests. *** Which prompted him to retort: >At 9:48 AM -0500 3/9/01, Tom Mahoney is rumored to have typed: > >> I belong to quite a few lists, almost all on digest. SmartList is >> the only one that I know of that does whatever it does to digests. > > First, I think you _really_ wanted to send this to the list, since sending >it only to me doesn't make much sense...you should be aware of my strong >opinions on this subject by now. > > Secondly, if SmartList is the only one that "does what it does," that says >a whole lot more negatively about the other lists you are on than it does >SmartList. > > Look, if you want to follow Topica, YahooGroups, and the other >non-standard outfits, simply edit your digest shell script. Or use another >mailing list package, like majordomo or mailman, and change _those_ to taste. >Or solve all your problems and _use_ the freebies like Topica or YahooGroups, >which allege to give you mind-numbingly simple administrative controls and >pander to the lowest-common-denominator mail clients like the completely >broken AOL 6.x client. Personally, I'd rather do things the right way than >follow those who are non-standard. You are welcomed to do whatever you want, >of course...except, perhaps, complain about SmartList mazking every attempt >to follow the rules. > > Charlie

1 0

multipart/digest...again
by Charlie Summers 09 Mar '01

09 Mar '01

Morning, folks... (*sigh*) I'm catching grief for the multipart/digest MIME type again, apparently from someone with Outlook 2000 who either doesn't know how to configure it, or doesn't know it's damaged in not allowing him to see the messages the way he wants. Anyway, I removed this guy from the digest version of the list he was complaining about, which solves my problem with this guy, but I need a little supporting ammunition for the future when this happens again and someone ELSE whines that I should be sending the digested version of the list in plain text. Can anyone point me to an RFC or document that defines the multipart/digest MIME type (I did a search, but can't seem to find any)? Does anyone have instructions for the various Microsoft packages (the problem children are almost universally using OE or Outlook, since apparently the others, like the Eudora I use, have no problem setting a little checkbox to receive MIME digests as attachments, or not) to have them not explode a digest? Any advice on information I should put in a form letter when I get these annoying complaints from users? Yeah, I'm a little tired and cranky, and so apologize for the tone, and would appreciate any list-admin advice on how to deal with these folks, who can be even more self-assuredly obnoxious than those who want me to munge my Reply-To. ;) Charlie

3 4

RE: password moderated approval
by Peter Hartzler 09 Mar '01

09 Mar '01

Heh heh heh.. :) I don't mind being contradicted at all, and I *certainly* don't know anywhere near all there is to know about SL. I hope you don't mind my echoing your privately-sent helpful remarks onto the list, in case it helps with the case at hand... It looks like the manual could be slightly clearer on this point... Anyhow, I've updated the faq to include your clue. :) http://www.hartzler.net/smartlist/SmartList-FAQ.html#Section_8.1 I appreciate the feedback! Thanks, Pete. On Thu, 8 Mar 2001, Munday, Merrick wrote: > > The relevant section in the manual is 3f. It makes no mention of > > passwords... > > Well, you're the FAQ moderator, so I don't want to contradict you in public, > but in the rc.custom file there is a place for a moderators' password. If > set, the password must be placed after the moderators' email address in the > approved header. However, AFAIK there must be a space, not an underscore, > separating the email from the password. > > Merrick Munday >

3 2

RE: password moderated approval
by Munday, Merrick 09 Mar '01

09 Mar '01

> As you're using Outlook, you may need to look into setting up > the list to allow the top line(s) of the message body to be treated by > SmartList as headers for purposes of commands... There's a bigger issue with Outlook, which is that Outlook defaults to wrapping after 80 characters, and smartlist won't see the remainder of the approved: or x-command: header if it's wrapped. We would commonly exceed 80 characters with a subscribe request, whereupon Outlook would wrap the last "word" which is the whole email address. You'll then get a "X-Diagnostic: Missing argument for subscribe" header in the returned mail to the maintainer's box. Further, the corporate/workgroup (CW) configuration of Outlook does not allow configuration of the number of characters to wrap at. The simple solution for us was to use Outlook Express which is already there on the machines and allows configuration of a 132 character wrap limit. I guess the application to this problem is that if your maintainer's email address or the password is extrordinarily long, you won't be able to send approvals from Outlook. > approved: moderatorsEmail(a)service.net_password As far as I know, there should be a space, not an underscore, between the moderator's email address and the password. Anyone have a different view? Merrick Munday

1 0

password moderated approval
by Susan and Jack Brooks 09 Mar '01

09 Mar '01

I've had a moderated list running for some time, although I was not the moderator. It seem that I have forgotten how to approve the messages and the past moderator is gone. I can't seem to find the text in the manual. I believe the text for approval, with a password is as follows: approved: moderatorsEmail(a)service.net_password I have been trying to approve messages with the above text as well as several permutations, from an Email address which is included in the moderators file, but can't seem to get them out to the list. I've confirmed the password with what is in the rc.custom file. Might someone be able to let me know what I am doing wrong? Thank you and best regards, Jack

2 1

LTS Test Letter
by Michael Dunlap 04 Mar '01

04 Mar '01

Test

1 0

LTS Business Newsletter
by Michael Dunlap 04 Mar '01

04 Mar '01

Test

1 0