On Fri, 14 Nov 2014 01:19:03 -0600, BigC <BigC@rochester.rr.com>
wrote:
>On Thu, 13 Nov 2014 20:27:00 -0600, Old Geek
><eldergeekenator@gmail.com> wrote:
>
>>On Thu, 13 Nov 2014 01:42:15 -0600, BigC <BigC@rochester.rr.com>
>>wrote:
>>
>>>On Wed, 12 Nov 2014 19:32:52 -0600, Old Geek
>>><eldergeekenator@gmail.com> wrote:
>>>
>>>>On Wed, 12 Nov 2014 16:17:15 -0600, BigC <BigC@rochester.rr.com>
>>>>wrote:
>>>>
>>>>>On Tue, 11 Nov 2014 19:47:00 -0600, Old Geek
>>>>><eldergeekenator@gmail.com> wrote:
>>>>>
>>>>>>On Mon, 10 Nov 2014 23:42:52 -0600, BigC <BigC@rochester.rr.com>
>>>>>>wrote:
>>>>>>
>>>>>>>On Mon, 10 Nov 2014 19:41:37 -0600, Old Geek
>>>>>>><eldergeekenator@gmail.com> wrote:
>>>>>>>
>>>>>>>>On Mon, 10 Nov 2014 12:35:18 GMT, Ennui <none@none.net> wrote:
>>>>>>>>
>>>>>>>>>Old Geek <eldergeekenator@gmail.com> wrote in
>>>>>>>>>news:pmuv5a5mkli3rocpqeion2f6s11cnm1q81@4ax.com:
>>>>>>>>>
>>>>>>>>>> On Sun, 09 Nov 2014 12:19:15 -0500, nobody@noone.com wrote:
>>>>>>>>>>
>>>>
>>>>>>>The JPG showed up in the single header of your last post. Thank you.
>>>>>>>
>>>>>>>I checked my filters and the only ones even remotely close to
>>>>>>>@fx07.iad are these:
>>>>>>>
>>>>>>>Message-ID: newsfe\d\d\.iad
>>>>>>>Message-ID: {<.*@newsfe*.iad}
>>>>>>>Message-ID: {<.*@*.fr7>}
>>>>>>>
>>>>>>>I don't see how any of those could filter @fx07.iad.
>>>>>>>
>>>>>>>Thanks for the help.
>>>>>>>
>>>>>>>FWIW, I see JPGs from JHO but not from Yoyo.
>>>>>>
>>>>>>You're welcome, but I am confused as to why that worked.
>>>>>>I know YoYo is posting the same way I was before last night. JHO I
>>>>>>*think* is to though we haven't communicated about it directly.
>>>>>>There is a common thread there though, YoYo and I both post through
>>>>>>easynews and JHO is using giganews. Perhaps one of those filters is
>>>>>>getting the jpg. If you are game to suspend them for a time I can post
>>>>>>using the previous method to help you nail it down.
>>>>>>
>>>>>>EG.
>>>>>
>>>>>The new way you are posting does show the JPG in the single header
>>>>>along with the rest of the parts to the main file.
>>>>>
>>>>>JHOs JPGs come in as a seperate header from the main header that
>>>>>contains the vid.
>>>>>
>>>>>YOYOs posts are a single line with no JPG.
>>>>>
>>>>>CERVANTEs post are totally fractured with JPG as a seperate header,
>>>>>RARs as another header, PAR2s as a third header and if I remember
>>>>>correctly NZB and NFO in a fourth header. With the exception of the
>>>>>JPG the other headers are tagged as incomplete even though the
>>>>>individual parts in the header are complete.
>>>>>
>>>>>The way Cervantes post come in are not unique. Another group I
>>>>>frequent has the same fractured headers. Except all those seperate
>>>>>headers show to be complete.
>>>>>
>>>>>I had sent agent some NZBs that did not work correctly with Megajoin
>>>>>and was told that all files were there and just work around it.
>>>>>
>>>>>So, if you will not revert to your old way and I will try to figure it
>>>>>out from this end first I would appreciate it. I will start with
>>>>>disabeling Megajoin and reload headers and go from there.
>>>>
>>>>The reason Cervante's posts (many others too) show as fractured is
>>>>because of the $Kk variable in the header. Thas puts in the file size.
>>>>The headers don't match so megajoin doesn't combine them.
>>>>I removed that in mine for that very reason.
>>>>
>>>>Starting tomorow I will post the jpg first as a 1/1 file then the rest
>>>>as 1/?. The nzb will not include the jpg.
>>>>If you like I can create a 2nd nzb to include the jpg after thepost is
>>>>up and send that as well.
>>>>
>>>>Still confused as to why the preview doesn't come through for you when
>>>>I post it as a 1/1 but does with JHO's. YoYo and I talked about it
>>>>earlier and are doing the same thing. That and the fact that we both
>>>>post through easy is the only common thread I can find...
>>>>
>>>>EG.
>>>
>>>Don't do anything special for me. Just post the way you want. I'll
>>>figure it out. It has to be a filter i've added in the last month or
>>>so.
>>
>>It isn't an issue for me. Hopefully it will help you nail down the
>>issue.
>>
>>EG.
>
>Thanks EG.
No problem. Let me know when you figure it out and what it was,
please.
EG.
|
| Follow-ups: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 |
|