At 4:50 AM -0400 5/11/01, Greg Matheson is rumored to have typed:
I have a front end for smartlist lists for penpals of my students. They introduce themselves, a list is created for them, and their first messages are piped to flist.
Depending on the size of these auto-created "lists," I'm betting setting up sendmail aliases would be more efficient. Of course, if you have hundreds of "subscribers" to these lists, I withdraw the comment.
Smartlist however, no doubt because hello messages in the traditional type of list are not welcome, puts messages like the following in the request file, with the X-Diagnostic header, Unprocessed.
Start doubting. It has nothing whatsoever to do with this being a "hello" message (SmartList isn't smart enough to read the message and determine the context; and I don't know why you would assume a "hello" indroduction message would _not_ be welcomed in a "traditional" kind of list - they certainly are in the "traditional" lists _I_ operate!)...it has more to do with goofy subjects and oddly-formed bodies.
The X-Diagnostic: header field you're seeing is coming from rc.request, not rc.submit; therefore the message is being redirected from rc.submit to rc.request in the mistaken belief that it is an administrative request (subscribe, unsubscribe, etc.) - I've seen this happen rarely with goofy messages like this one, with a bunch of punctuation (particularly lines of periods) in the subject field or "key" words in the first line of the body ("join" and the like). Infrequently (in "traditional" lists, which is what SmartList is designed to operate) these goofy lines will fool the regex scores high enough to cause a redirect. Once it's there. of course, rc.request can't make hide nor hair of it, and punts it off to the maintainer with the "No clue, Boss" X-Diagnostic.
It happens rarely enough for me I never bothered going through the programming in rc.submit that checks (easier to fix the broken subjects and request that the poster not do that anymore), but search for:
# # Does it look like a regular submission? # Or perhaps more like an administrative request? # Look at the start of the body, and see if this could be an administrative # request, pass it on to rc.request in that case. #
...in rc.submit; carefully read the recipies that follow, and modify (CAREFULLY!) to taste. (Considering that you seem to be using SmartList for something...unique...you might consider remming out the recipies entirely. Ugly, and will probably cause you other problems down the road, but will fix this one anyway.)
Charlie