Hi, I am cc:ing the list since you indicated it would be acceptable.
The only thing we need to be clear on before I really get into the
possibilities of what you are trying to do, is define "the db". I
had assumed you meant it to be the list subscriber file. Which is
really just a flat text file with one address per line. If this
is also your definition, we are already on the same wavelength.
When you append names to the file at the OS level rather than going
through majordomo, the users do not get notification they are on
the list until they receive their first distributed message. They
will receive the next message that is sent to the list, as long as
they provided an accurate email address during registration. The
problem here is when an inaccurate address is entered, the list
owner and/or the majordomo owner are the only ones notified, and
only after the bad address has delayed the distribution of the
original email.
Adding the user by sending majordomo email on behalf of the user
and sending them a welcome message will at least confirm that the
address is a good one, but not necessarily the address of the
user filling out the web form. That is why the +confirm setting
came into the list.config files. If your page announces and
explains this confirmation requirement, and that it helps the
user to preserve their privacy as well as prove their email
address is valid, you will not get (as many) complaints about
having to respond to the confirmation message.
The ultimate decision will have to be balanced carefully over
customer (subscriber) happines, business communication needs,
and maintenance of the list. A poorly maintained list will be
a very slow list.
Dan Liston
"Atilla S. Kocsis" wrote:
>
> HI Dan,
>
> First thanks for taking the time to respond to me. I think this should be a
> paid position for you. I see you helping so many people. And if you like i
> would gladly pay for your time.
>
> Second. It appears that i should just email on behalf of the person. the
> bounced message is reason enough, and since i can turn off the welcome
> message nothing is lost.
>
> just curious, if i just added the name to the db, would the system use that
> list the next time with the added name without a problem?
>
> atilla
> ps: i didnt send this to the list, shall i go back and do so?
>
> -----Original Message-----
> From: Dan Liston [mailto:dliston@netscape.com]
> Sent: Tuesday, October 03, 2000 4:31 PM
> To: Atilla S. Kocsis
> Cc: MajorDomo List
> Subject: Re: Signing up for multiple lists
>
> My first thought is to mail the request to majordomo on behalf of the user.
> At least that way, if the welcome letter bounces, you are notified almost
> immediately and you can remove the bad address.
>
> Is it your desire that the users receive welcome notices? If not, you could
> always say welcome = no in the list's .config file.
>
> Dan Liston
>
> "Atilla S. Kocsis" wrote:
> >
> > Hello,
> > I am a new to majordomo so please let me know if i have any flaws with my
> > ideas.
> > I was looking to sign people up for 4 different majordomo lists via one
> web
> > form.
> >
> > Here is my plan:
> >
> > Create a form and if a user checks a box for list1. their email address
> is
> > added to the db file for list1, etc...
> >
> > Would you all recommend me making a symbolic link from
> > /usr/local/majordomo/list/list1 file to the db file in the directory where
> > the form is.
> >
> > it is my assumption that when a new name is added to the db that majordomo
> > will send out the Welcome letter?
> >
> > or should i have the form email the majordomo system on behalf of the
> person
> > signing up? thus initiating the Welcome letter
> >
> > Thank you in advance.
> >
> > Atilla Kocsis
|
|
