At 1:26 PM -0400 7/31/02, Jim Osborn is rumored to have typed:

I've wondered, if the addresses are properly formatted with RFC822 comments, will they be handled correctly at distribution time?

<snip>

Maybe one of the experts can say for sure one way or the other.

(*sigh*)

At the risk of yet again upsetting Ms. Judge's delicate constitution by pointing out the painfully obvious in my finely-honed, highly ascerbic fashion, please read the Manual file which comes with the SmartList distribution, specifically section 5. Of course, you'll need to write your own routines if you want to retain this information at subscription time (I suppose there is some sensible reason for a mailing list server to retain human names, but it escapes me at the moment) since the supplied routines will not, but the Manual file will clearly note what format is and what format is not acceptable to multigram. That's the beauty of open-source software...if you don't like the way it works, you're free to change it to do anything you can imagine whether I think it makes sense or not.

Charlie (who may not be an expert, but DOES know how to read)

P.S. For those very few people on virtual machines who routinely say, "but I don't HAVE the Manual file, can't find it, and don't want to spend the time to actually LOOK for it since my provider shifted his support costs to the unpaid 'staff' on this mailing list," Peter has posted it right beside the FAQ at http://www.hartzler.net/smartlist/ (with whiz-band direct section links included!) so there's no excuse.

Me

-- A virtual chihuahua, gnawing on the pantleg of the annoying and foolish. It's futile, but I am undaunted.

At 5:04 PM -0400 7/31/02, Anne Judge annoyed us with:

Here's an example:

Better to be maintained in an external database with the additional data you'd want to store, and generate the dist file from it (possibly a nightly cron job; oh, yeah, another unix command you don't want to hear about - maybe there's a button you can push on the Mac?). I did exactly that for a client using MySQL to maintain the data, PHP to securely manage it remotely, and SmartList to handle the list mailings.

Or a list for club or organization directors & officers

See above, although in this case unless you have hundreds of "directors & officers" most normal people wouldn't need it, since they wouldn't be using a SmartList distribution list as their private address book. (There'd be all that FTPing back-and-forth to do.)

Maintaining this information in the distribution file of a mailing list server continues to make no sense whatsoever to me. But again, that's the nice thing about open source; if you take the time to learn it, you can make it do anything you want. If you don't, you're stuck with what you get out-of-the-box.

Oooh, I hope I'm not upsetting charlie's delicate ego by daring to offer a thought . . .

Hardly; it would take someone with actual unix knowledge to challenge my perfectly-healthy ego (like David Linn, who mentioned unlink in a private email and set me researching it since I'm embarassed to admit I never heard of it before). I see it's time for another twit filter, though, to immediately increase the s/n ratio of the list:

:0 * ^X-BeenThere: smartlist * ^Received:.*safepages.com * anne.judge /dev/null

(safepages.com is in a number of anti-spam filters already for providing cheap drop-box accounts, FWIW. Now I see why.)

With this filter in place, you're welcomed to waste time arguing with yourself. Please enjoy the sound of one hand clapping.

Charlie

-- A virtual chihuahua, gnawing on the pantleg of the truly ignorant. It's futile, of course, but I am undaunted.

I've been trying to configure Smartlist and have got a mixed bag of problems...

I'm trying to create a private list, so have developed an accept list which is an exact duplicate of the dist list. However, some messages not being received by everyone on the dist list. And it appear some users on the accept list are unable to reply or post.

And, to make matters worse, some of my users are receiving spam.

Can anyone help with thise problems? Thanks, Sue Bott

At 10:38 PM -0400 8/19/02, Susan Bott is rumored to have typed:

I'm trying to create a private list, so have developed an accept list which is an exact duplicate of the dist list.

I'd be interested in knowing what steps you took to make this happen...considering that this is the _default_ of SmartList. (Indeed, accept and dist are hard-linked, so both files point to the same hard drive sectors.) My guess is that by hand-editing the files you managed to create at least some of the problems to which you refer.

However, some messages not being received by everyone on the dist list.

Check your sendmail logs to see if you are delivering to their systems; hotmail/msn users, for example, generally lose a good bit of email routinely. That is, narrow the problem down to see if you are delivering, or not. If you are, it isn't your problem. If you _aren't,_ we need to start looking for another explainiation (and the first place I'd look is in the dist file for a stray control character).

And it appear some users on the accept list are unable to reply or post.

Again, this may have something to do with your, "develop[ing] an accept list which is an exact duplicate of the dist list." I have the feeling this would be less of a problem has you left these files in their default configuration. (If it ain't broke, don't fix it.)

And, to make matters worse, some of my users are receiving spam.

There's little you can do to keep your users from receiving spam; if you do solve their spam problem, please tell me how so I may solve mine as well. (I think what I'm trying to delicately ask is, what the heck does their getting spam have to do with your mailing list?)

Can anyone help with thise problems?

Not really, since to be honest you aren't telling us much. Saying, "they aren't getting the mail," or, "they are getting spam," doesn't exactly narrow the problem(s) down terribly far.

Charlie

Is there a way I can specify 2 maintainers for a single list?

Thanks, Sue Bott

On [2002-Jul-31] Anne Judge anne.judge@alum.mit.edu quoted & wrote:

...

(I suppose there is some sensible reason for a mailing list server to retain human names, but it escapes me at the moment)

Here's an example: A club list where the list manager wants to know which club members are on the list, and which people on the list are not (current) club members - since people often have multiple addresses and will sign up for an email list at a diffent address than they supply the club's membership director.

My need for a real_name <-> email_address connection wasn't strong enough to go the full database route (which is, as Charlie notes, the best full-strength solution) so I opted for just an additional file created during the subscription process. I called it "registry" and it holds just some very basic info on the subscriber. Since all subscription is done by a maintainer via xcommands it was easy enough to restructure the xcommands to handle this, e.g.

xcommand .... subscribe <email> name <firstname_lastname>

where "name" is a new xcommand which writes the <email> and <firstname_lastname> to the registry file.

Richard

On or about Mon, Aug 05, 2002 at 01:35:42PM +0300, Tapani Tarvainen typed:

Are there other reasons why the approach outline above would not work? (Any better ideas?)

If you use Exim, you can make it search for the existence of the file $LISTROOT/$LISTNAME/rc.init. This is what I do; it doesn't need to modify anything belonging to the mailserver. I'm sure other MTAs can do similar things.

If that's available as an option, you don't need the root access or any of the mucking around you'll have to do with your current scheme.

Roger

On Mon, Aug 05, 2002 at 03:56:44PM +0300, Tapani Tarvainen wrote:

on second thought I can do it with virtusertable so that "list@application.my.domain" is directed to a procmail recipe that can then pipe it as such to flist, without any need for '+' in the list name.

I meant mailertable, of course. In case anyone is interested (the technique is useful whenever you wish to allow someone to create and remove mailinglists without letting them mess with sendmail alias files &c), here's a summary of how it's done with SmartList & sendmail:

(1) Install a new instance of SmartList with suitable permissions using desired subdomain (e.g., "sub.my.domain" - you also need MX record pointing that to your mailserver). You might wish to edit createlist and removelist so they won't say anything about editing aliases, as it's not necessary here.

(2) Make sure sendmail has mailertable feature and procmail mailer defined (not just using it as local mailer), i.e., check there's MAILER(`procmail') and FEATURE(`mailertable') in the .mc file.

(3) Create mailertable with entry like this: sub.my.domain procmail:/whatever/sub.rc

(4) Create /whatever/sub.rc script looking something like this:

to=$2 :0 | /something/.bin/flist "`echo $to | cut -d@ -f1`"

That's it! Now lists can be created in the subdomain without any need to mess with sendmail aliases or the like, and without confusing them with similar addresses in the main domain.

Oh yeah, to be standard-compliant you should also define postmaster@sub.my.domain somehow (e.g., in virtusertable or add it to the procmail script above).

That said, I'm still curious about the planned support for special characters in list names createlist alludes to...