Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTOWN-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Menu
LISTSERV Archives LISTSERV Archives
LSTOWN-L Home LSTOWN-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
Re: Incorrect Password Supplied
From:
Winship <[log in to unmask]>
Date:
Wed, 27 Apr 1994 12:27:26 -0500
In-Reply-To:
<[log in to unmask]>
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
Parts/Attachments:
text/plain (38 lines)
> I use a Pine mailer, and it does some magical things that I'm not aware of
> and that in some instances are "overly smart".  (If your mailer acts
> similarly, then this may be the problem.)   Sometimes I'm sent a file
> which I believe to be composed solely of low-order ascii characters, but in
> fact there are stray high-order characters or tabs or what-not, but
> they're no apparent when viewed through the Pine mailer.
>
> When I try to PUT such a file to Listserv, Pine detects the high-order
> characters and before transmission, alters the entire file, specifically
> by tansforming any instance of "=" to "=3D" (and several other
> tranformations).  Since the PUT cpmmand always requires a PW=XXXXXXXX
> command, Pine changes this to PW=3DXXXXXXXX and thus when Listserv
> receives the file, it rejects the PUT because the password *it* sees is
> indeed incorrect.
>
> The solution for me is to make doubly sure that all high-order ascii
> characters are stripped away from any file I send to Listserv via the Pine
> mailer.  (These error-laden files are often the result of trying to create
> an ascii file from a word-processor document.)  If you have a "smart"
> mailer like Pine, it might be doing these same things to files -- and only
> those files -- that contain high-order ascii characters.
>
> -- Roger Burns   [log in to unmask]
 
I have run into this problem also, and it was a file created by a word
processor program that had code I couldn't see.  I'm the only one who
generally does anything with our filelist, but every time I tried to
put the file it was rejected for a faulty password.
 
I got around the problem by sending the file to the primary listowner
and having her install it with an LSVPUT (Idon't have that, but she's
at the node running the list so could do it).  I then got the file
from the list and voila!, there were =s and =20s all over the place.
I edited them out and reput the file with no problem.
 
        Douglas Winship    Austin, Texas    [log in to unmask]
                    Secondary AUTOCAT Listowner

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV