At 11:24 PM -0400 8/27/00, Bill Platt is rumored to have typed:
I sent it through my Netscape mail. Granted my main POP address is bplatt@poncacity.net, and the address I was subbing on was admin@windstormcomputing.com
Are the two items related?
Oh, yeah. X-Diagnostic: headers are your friend, and will tell you what SmartList is up to most of the time. (He, he...sometimes they are not _exactly_ specific, but they are always an indicator. In this case, however, they point us almost directly to the problem.) There is a macro in procmail named FROM_DAEMON, which is expanded to: `(^(Precedence:.*(junk|bulk|list)| (((Resent-)?(From|Sender)|X-Envelope-From):|>?From ) (.*[^(.%@a-z0-9])?(Post(ma?(st(e?r)?|n)|office)| (send)?Mail(er)?|daemon |mmdf|root|n?uucp|smtp|response| LISTSERV|owner|request|bounce|serv(ices?|er)|Admin(istrator)?) ([^).!:a-z0-9].*)?$[^>]))' Notice that an admin@ address will match that expression...SmartList, because rc.request is scoring on FROM_DAEMON, will assume the mail is being sent by a mailer daemon, and will ignore it. At the same time, it sends a copy of the original message to the list maintainer with a X-Diagnostic: header field added to tell the maintainer what it's done. Try subscribing the address dude@windstormcomputing.com instead, and check to see what happens. Again, check not only what SmartList sends to dude, but check the X-Diagnostic: header field(s) in the mail the maintainer gets after the transaction. Charlie