> > - Authorized poster file. As an alternative to a passworded list, which
I
> > dread having to explain to people, I have a subscriber only list that
has
> a
> > subscriber list of around 640, and a kill file of around 620 - that is,
my
> > 20 authorized posters are the only ones NOT on the kill file. It's a
pain.
> > I'd rather have a list of people who are authorized to post. This
could
> > also be set up so that a authorized posters needn't be subscribers. That
> > way, I could let a guest (Bill Gates, Bill Clinton?) post, without
making
> > them read all the list mail.
>
> Isn't this the same thing as a private list where only authorized people
can
> subscribe?
Nope. A private list allows ALL subscribers to post, or only the moderator.
(All or nothing). I'd like to see an option to allow only authorized
subscribers to post, because it opens up a lot of new ways to use lists. The
thing is, if you only want your experts, board members, or advertisers, etc.
to post, you have to take unusual measures, such as managing passwords for
them, or adding all unauthorized subscribers to your kill file.
The list in my example HAS to be private, because that's the only way I can
get them on the killfile at the same time the get on the user file. - But
the option should be available whether the list is public or private. I can
think of uses in either case.
> > - Rename the kill file if you're going to notify people that they are
not
> > authorized to post. In my realm, a spot on the kill file needn't be
> > permanent, but the kill file message seems to needlessly worsen the
> > relationship between a moderator and a borderline bozo. It sounds
> > combative - how about "nopost"? - and how about allowing the admin to
edit
> > the message?
> >
>
> Well that is certainly a good point, but in my suggestion I specifically
> asked for people in the kill list not to receive notification that they
were
> there.
That's why I said "if" - in case you didn't get your notification. Actually,
I'd like to see it renamed anyway. I know it's called that because it does
"kill" messages, but the name causes people problems. Even if they don't see
it the name, I have to discuss it the killfile with these guys, and I'd
rather be calling is something else.
> > - Truncate digest messages. When you read individual messages in
> continuing
> > threads, you often don't realize how much quoted material there is, down
> > below - but in a digest, it's just awful reading. Plus it makes the
digest
> > several times larger than it has to be. I'd like to be able to set my
> digest
> > to truncate any message at, say the 10th line starting with a ">"
>
>
> Yes I agree, but I think this would be nearly impossible to implement.
Many
> people (such as me) add replies in the middle of other's posts.
Maybe you mean to say you can't see yourself using it - that's not the same
as saying it's nearly impossible for technical reasons.
If it's possible, I'd really love that option, because I get complaints
about trash in the digest.
But I can see where many would not want to use it, particularly if
paragraphs were running long on a particular list - for whatever reason.
But over here, the people posting messages are not the ones reading the
digest, for the most part, and I don't think they'd mind if a few of their
comments didn't make it into the digest.
As an admin, if I thought 10 lines was cutting it too tight, (I'm already
thinking that) I could increase the number, or turn off the option. I just
think it's a choice you should be able to make, to weigh readability against
the possibility that some material would be missing.
And if auto truncation couldn't be offered, I'd at least like to be able to
edit messages that are in the digest mailbox.
Lastly, thanks for working with them on listserver improvements. I'm sure it
helps them to have users sum up what they want - so they don't have to guess
what people want.
Gary Mauer
[EMAIL PROTECTED]
Host/Moderator of the Window Cleaning Network
- Your People, Product and Information Site -
http://www.window-cleaning-net.com/
Email Groups - 900 Networking Links
8 Bulletin Board and 21 Trade Show Links
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 10, 1999 12:55 PM
Subject: Re: [IMail Forum] (FYI) Updated Listserv Improvements Request
> > I would add these three
> >
> > - Authorized poster file. As an alternative to a passworded list, which
I
> > dread having to explain to people, I have a subscriber only list that
has
> a
> > subscriber list of around 640, and a kill file of around 620 - that is,
my
> > 20 authorized posters are the only ones NOT on the kill file. It's a
pain.
> > I'd rather have a list of people who are authorized to post. This
could
> > also be set up so that a authorized posters needn't be subscribers. That
> > way, I could let a guest (Bill Gates, Bill Clinton?) post, without
making
> > them read all the list mail.
>
> Isn't this the same thing as a private list where only authorized people
can
> subscribe?
>
>
> >
> > - Rename the kill file if you're going to notify people that they are
not
> > authorized to post. In my realm, a spot on the kill file needn't be
> > permanent, but the kill file message seems to needlessly worsen the
> > relationship between a moderator and a borderline bozo. It sounds
> > combative - how about "nopost"? - and how about allowing the admin to
edit
> > the message?
> >
>
> Well that is certainly a good point, but in my suggestion I specifically
> asked for people in the kill list not to receive notification that they
were
> there. Their post simply would not make it on to the list, but would be
> forwarded to the list admin with the verbage that the individual was in
the
> kill list. The user should never be told and I do agree that messages
back
> to them regarding their status often inflame a situation.
>
> > - Truncate digest messages. When you read individual messages in
> continuing
> > threads, you often don't realize how much quoted material there is, down
> > below - but in a digest, it's just awful reading. Plus it makes the
digest
> > several times larger than it has to be. I'd like to be able to set my
> digest
> > to truncate any message at, say the 10th line starting with a ">"
>
>
> Yes I agree, but I think this would be nearly impossible to implement.
Many
> people (such as me) add replies in the middle of other's posts.
>
> >
> > And my comments on a couple of your suggestions.
> >
> > > - Add capability for user to set account not to email them their own
> > posts.
> >
> > I'm really surprised that's a problem. I've never heard a complaint over
> > here about getting your own post back. I think an admin who sets his
list
> > not to email them their own posts by default will get a surprise when
> people
> > start reposting messages, because they don't think the list is working.
>
> I have not received one either, but I do know that this is asked for from
> time to time. That's why it was at the bottom of the list. Personally I
> like to see my own posts exactly for the reasons you site.
>
> >
> > > - Automatically remove individuals for bounced posts. Remove people
> > > automatically if account has been closed or domain not found. Remove
> > > people after a predetermined number of bounces (set by admin) when
> > > mailboxes are full.
> >
> > Not clear enough. "Domain not found" should be automatic. But many of
the
> > other bounce errors cannot be taken literally - AOL sometimes tells me a
> > bunch of addresses don't exist, and a day later send them along like
> nothing
> > ever happened. I know, serves them right for using AOL, or some clueless
> > small ISP that can't get their mail working right, but I'm in a service
> > business, and I want to be able to decide to keep a subscriber.
> > Anyway, the admin should be able to set a bounce limit, but it shouldn't
> be
> > limited to full mailboxes.
> >
>
> Good point. I'll amend the Upgrade requests to reflect this...
>
>
> Thanks
> Anthony
>
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
