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 Monospaced Font
Show Text Part by Default
Show All Mail Headers

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

Print Reply
Subject:
Re: Problem with GETPOST
From:
Karen <[log in to unmask]>
Reply To:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Mon, 21 Jun 1999 16:23:15 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (65 lines)
Once again (I sent this yesterday)

I agree, it is a major pain -- especially when I was limited to this
account which batches mail and uploads and downloads only a few times a
day. It could take days to do a search and print the results.

As far as sending in those 100 numbers to retrieve the posts, there is a
way around the "unknown command" line. Once the text wraps to a new
line, Listserv no longer reads it as part of the previous command unless
the following is added at the start of the line:

// GETPOST <post numbers>,
<more post numbers>,
<even more post numbers>

This tells the listserv to keep going to the next line(s) until it no
longer encounters a comma at the end of the line. Alternatively, you can
add a GETPOST at the start of every line, which has the advantage of
sending several smaller messages, rather than one huge one of 100+
posts.

The // <command> ... , is also useful when doing commands involving long
addresses that might wrap, such as adds or changes.

BTW, what are you doing with 10 years of archives? Every listowner was
requested to remove all archives prior to 1998 quite a while ago due to
the space crunch. Kary has been known to just delete the larger archives
of lists that haven't complied as we run out of space. I recommend that
you back up your older archives and remove them from Maelstrom before
they are removed for you without backups.

Karen Reznek
[log in to unmask], [log in to unmask]

>When searching the archives,  GETPOST works fine for a few items.  However,
>when number of items exceeds 100 items or (More) you must search again to
>get the (More) part.  Then to make matters worse, when you cut and paste the
>100 numbers, you get UNKNOWN COMMAND errors for all lines beyond the first
>GETPOST line.

>Am I doing something wrong?  Must searches of 10 years of archives be this
>difficult?

>Best,    . . . Max---
>--
>Mad Max
>[log in to unmask]
>Phone:  785-842-6445  FAX:  785-841-1022
>Lawrence, KS.,  USA     66049-2449


mad-max wrote:
>
> A search has returned 100 items.  When I "cut" and "paste" and send to
> LISTSERV to retrieve the posts, I get UNKNOWN COMMAND for all lines but the
> first line.  How do I tell LISTSERV to continue the "fetching" until all 100
> posts are returned.
>
> TIA!     . . . Max---
> --
> Mad Max
> [log in to unmask]
> Phone:  785-842-6445  FAX:  785-841-1022
> Lawrence, KS.,  USA     66049-2449

ATOM RSS1 RSS2

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