Path: news.nzbot.com!not-for-mail
NNTP-Posting-Date: Fri, 24 Nov 2017 12:23:05 -0600
Newsgroups: alt.binaries.multimedia.erotica.lesbians
Subject: Re: Please read - next set of SPOTs
From: Holden <craymore@home.com>
References: <XnsA8375250A90DEbgmailc@69.16.179.39> <fvfg1dlaoc99k50mao4aui3poqrhm6ervp@4ax.com>
Organization: Your Company
Message-ID: <XnsA83788298759beHoldenhomecom@127.0.0.1>
User-Agent: Xnews/5.04.25
Date: Fri, 24 Nov 2017 12:23:05 -0600
Lines: 33
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-bW511nFfNi56T7KLyWM/Ne09IhxlExLxvOOSI3r1hBqIWtXd1tiAilZDh61NUDd9P7hEjouIfTf+c+Y!T1MvxV8oWiPlcWUXnsu1tDU9DfY06EM32lBBDr31rAEe9nJubPN75Aieo7fgGbGWfb0=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2136
X-Received-Bytes: 2258
X-Received-Body-CRC: 777061850
Xref: news.nzbot.com alt.binaries.multimedia.erotica.lesbians:14674
Spotted@Dick.com wrote in news:fvfg1dlaoc99k50mao4aui3poqrhm6ervp@4ax.com:
> On Fri, 24 Nov 2017 13:05:34 GMT, "dr. who?" <noemail@none.com> wrote:
>
>>I tried Spot0218 and Spot0221 and got a Tag error in both
>>I'm using Xnews and SuperNZB.
>>This just happened to me today.
>>d.w
>>
>>---
>>This email has been checked for viruses by AVG.
>>http://www.avg.com
>
> The next set of SPOTs have come from nzbs downloaded from nzbindex,
> rather than ones I have created from Agent.
>
> If that doesn't work the original post names were:
>
> 0227 - AnwmqHryxcCmIlq yEnc
> 0228 - bmBACKSwOhLFGpgAtqDGHR yEnc
> 0229 - rvhNKPrACkGmdzx yEnc
> 0230 - rwOTsETgwzHkbJnnrpwODcLwP yEnc
>
> Let me know if this helps.
>
> Spotted
>
Giganews user here. These 4 worked. Last 2 days I had mixed results,
usually only getting 2 files (par2 and sfv). I did try copying the file
names and searching for them using Mimo (it's a giganews tool) and some I
was able to download from there, but some gave me other http issues. So
probably was something messed up in the NZB but in relation to giganews.
|
|