This is not a strictly smartlist question, but hoped someone might
have a recommendation.
I am the administrator for a non-profit groups website (and email
lists). The members (including myself) are all volunteers, using their
own software (in other words, there is no standard!).
One of the lists (about 200 members) used to notify members of urgent
news has been set up as moderated and works fine (for me). The actual
list moderator uses Juno (need I say more). I had added a recipe in
RC.LOCAL.S10 to capture an "Approved" message from the body and add it
to the header (since he has no way of directly affecting the header).
This works great for me, but apparently, it is somewhat random under
the Juno web based email. It appears there is no way to turn off the
HTML formatting under the Juno email.
OK, so then I create a web form that allows the moderator to fill in
the message, subject and has a password. I thought I could just let him
fill it in and then send the message to the list using a CGI script. It
seems that he can access the list and fill it in but submitting it
strips all of the info so that the CGI is never called, and he just gets
a "Can not display page" screen.
Has anyone run into similar problems or might suggest a work around?
Thanks,
David W. Gulley
Destiny Designs
Are there any scripts or work-arounds for the problem of X-Command lines
in the body of an email message being broken into two lines if they're
longer than 72-80 characters? I don't know if something's changed in our
organization, or if we just happened to not process any longer than
this, but I can see in the mail logs that an X-Command that's two long
gets broken into two lines, usually before the email address. These
X-Commands then fail.
I'm not much of a procmail user. Is it possible to tell the rc.local.00
script that if it finds an X-Command in the first line of a body, it
should concatenate all the subsequent lines into one, until it comes to
the first blank line? Then, the rule for X-Commands in the body of a
message would be that the X-Command must be the first line in the body,
and must be followed by a blank line.
Thank you for your help and suggestions.
-Kevin Zembower
-----
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Are there any scripts or work-arounds for the problem of X-Command lines
in the body of an email message being broken into two lines if they're
longer than 72-80 characters? I don't know if something's changed in our
organization, or if we just happened to not process any longer than
this, but I can see in the mail logs that an X-Command that's too long
gets broken into two lines, usually before the email address. These
X-Commands then fail.
I'm not much of a procmail user. Is it possible to tell the rc.local.00
script that if it finds an X-Command in the first line of a body, it
should concatenate all the subsequent lines into one, until it comes to
the first blank line? Then, the rule for X-Commands in the body of a
message would be that the X-Command must be the first line in the body,
and must be followed by a blank line.
Thank you for your help and suggestions.
-Kevin Zembower
-----
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
I know you want to look at pussy, but first you need to learn The Truth about the adult industry:
Get Into Paysites Free!
If you take 2 minutes to read what I have to say you will have full access to some of the largest membership sites for free.
http://www.americanteensluts.com/fpp/rune/rune2.html
This costs you nothing!
At 9:52 AM -0400 7/13/02, smartlist(a)informatik.RWTH-Aachen.DE is rumored to
have typed:
> <html><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
> <html>
> <head>
> <meta name="GENERATOR" content="Mozilla/4.77 [en] (Windows NT 5.0; U)
>[Netscape]">
> <title> Free porn passes to all the top sites
> </title>
Hum...interesting (but not terribly surprising) that Mailman can be fooled
by something so embarassingly simple. SmartList wouldn't be (assuming
foreign_submit is unset, which is the only way to run a list nowadays), since
the list name wouldn't be within the dist file. (If one sets up a digest the
"normal" way, subscribing the digest to the interactive, it might get
distributed to a digested list, however.)
Charlie
My SmartList log file is filled with these line:
procmail: Extraneous deliver-head flag ignored
It occurs in clusters of various sizes.
Anyone know what's causing it and how to get rid of it?
Thanks,
Harshal
=====
http://www.mumbai-central.com : Where Mumbaikars meet
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
The main new feature of confirm 1.2.6 is a check of the given email address
for conformity to RFC822. The most requirements of RFC822 are matched, one
exception are addresses with the local part in double qotes (I never
heard about a need for it).
If someone sends an invalid address like bla;user(a)dom.com an error message
is send back and no subscription or cookie creation happens. On the other
hand addresses with uncommon characters in the local part (*+#?%$) are
allowed.
confirm 1.2.6 is available at
ftp://ftp.pure.ch/pub/smartlist/
Werner
