Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/BR54HK57OX5SHGRXEWPJA2O4OP7CXTNO/?format=api
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/BR54HK57OX5SHGRXEWPJA2O4OP7CXTNO/?format=api", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api", "message_id": "[email protected]", "message_id_hash": "BR54HK57OX5SHGRXEWPJA2O4OP7CXTNO", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/KNKFUNJGO6CH6K6BLA7AXN6MBUNIWYRH/?format=api", "sender": { "address": "wb3jfs (a) cox.net", "mailman_id": "bdfc678d05af4f3f96c14d823fd3fbcf", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/bdfc678d05af4f3f96c14d823fd3fbcf/emails/?format=api" }, "sender_name": "Jeff Yanko", "subject": "[AMSAT-BB] Re: LOTW VUCC Satellite entries", "date": "2022-09-08T08:13:15Z", "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/OLJGDSZFVPYXAHFY4L6DEC5HIWQU2T73/?format=api", "children": [], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "Mark,\r\n\r\nIn my first post I stated \"There is no way I could have those grid QSO's \r\nfrom stateside using a LEO bird and \"_I know that was not on the entry \r\nsheet.\"_\r\n\r\nWhat I submitted on my entry sheet was correct as I was, and still am, \r\nfamiliar with how the grid system works. It was entered incorrectly at \r\nthe VUCC desk. How is that \"on me\"? LoTW can't be corrected from the \r\noutside (the user), me, in this case, only authorized personnel (the \r\nadministrator) can make such changes. I had contacted the VUCC desk \r\ntwice after seeing their mistake and the response was high volume and we \r\ndon't have your submission forms.\r\n\r\nThe only \"mistake\" I made was not making a copy of my submission forms \r\nsince I figured it was so easy nobody could mess it up. I've submitted \r\nover 20 submissions without a problem, but I guess there is always a \r\nfirst time.\r\n\r\nThis was quite a few years ago, maybe 8 or 9, and hopefully things have \r\nimproved.\r\n\r\n\r\n73,\r\n\r\nJeff WB3JFS\r\n\r\n\r\n\r\n\r\nOn 9/7/2022 2:25 PM, Mark Johns, K0JM wrote:\r\n> Of course they've never been corrected. LoTW won't correct your \r\n> mistakes -- that's on you. You will have to re-load them with the \r\n> correct grid location.\r\n> --\r\n> Mark D. Johns, KØJM\r\n> AMSAT Ambassador & News Service Editor\r\n> Brooklyn Park, MN USA EN35hd\r\n> -----------------------------------------------\r\n> \"Heaven goes by favor; if it went by merit,\r\n> you would stay out and your dog would go in.\"\r\n> ---Mark Twain\r\n>\r\n>\r\n> On Tue, Sep 6, 2022 at 5:13 PM Jeff Yanko <[email protected]> wrote:\r\n>\r\n> Hi Mike,\r\n>\r\n> I think there are some issues with the entries at HQ. Quite a while\r\n> back, I submitted Satellite VUCC and have about 50 QSO's entered with\r\n> the grid area \"OM\", which I believe is in or around China. There\r\n> is no\r\n> way I could have those grid QSO's from stateside using a LEO bird\r\n> and I\r\n> know that was not on the entry sheet. BTW, they've never been\r\n> corrected.\r\n>\r\n>\r\n> 73,\r\n>\r\n> Jeff WB3JFS\r\n>\r\n>\r\n>\r\n> On 9/6/2022 8:28 AM, Mike Swiatkowski wrote:\r\n> > I'm having trouble getting my satellite log to show up in the LOTW\r\n> > VUCC Satellite section. I have over a hundred grids and not one\r\n> shows\r\n> > up confirmed in LOTW. I looked at the .adi log in TSQL and\r\n> indeed the\r\n> > mode of satellite, satellite name, and bands are populated. Does\r\n> > anyone have an idea why nothing would show up in VUCC Satellite? I\r\n> > only see my 6m contacts. I even tried to set a filter as my grid\r\n> > square from the example online\r\n> > (https://lotw.arrl.org/lotw-help/vucc-setup/?lang=en). That didn't\r\n> > help. Your assistance is appreciated.\r\n> >\r\n> > Thanks,\r\n> > Mike, AA9VI\r\n> >\r\n> > -----------------------------------------------------------\r\n> >\r\n> > Sent via AMSAT-BB(a)amsat.org <http://amsat.org>. AMSAT-NA makes\r\n> this open forum available\r\n> > to all interested persons worldwide without requiring\r\n> membership. Opinions expressed\r\n> > are solely those of the author, and do not reflect the official\r\n> views of AMSAT-NA.\r\n> > Acceptable Use and Privacy Policies available at\r\n> https://www.amsat.org/about-amsat/\r\n> >\r\n> > View archives of this mailing list at\r\n> > https://mailman.amsat.org/hyperkitty/list/[email protected]\r\n> > To unsubscribe send an email to amsat-bb-leave(a)amsat.org\r\n> <http://amsat.org>\r\n> > Manage all of your AMSAT-NA mailing list preferences at\r\n> https://mailman.amsat.org\r\n>\r\n> -----------------------------------------------------------\r\n>\r\n> Sent via AMSAT-BB(a)amsat.org <http://amsat.org>. AMSAT-NA makes\r\n> this open forum available\r\n> to all interested persons worldwide without requiring membership.\r\n> Opinions expressed\r\n> are solely those of the author, and do not reflect the official\r\n> views of AMSAT-NA.\r\n> Acceptable Use and Privacy Policies available at\r\n> https://www.amsat.org/about-amsat/\r\n>\r\n> View archives of this mailing list at\r\n> https://mailman.amsat.org/hyperkitty/list/[email protected]\r\n> To unsubscribe send an email to amsat-bb-leave(a)amsat.org\r\n> <http://amsat.org>\r\n> Manage all of your AMSAT-NA mailing list preferences at\r\n> https://mailman.amsat.org\r\n>\n\n\n", "attachments": [ { "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/BR54HK57OX5SHGRXEWPJA2O4OP7CXTNO/?format=api", "counter": 2, "name": "attachment.html", "content_type": "text/html", "encoding": "utf-8", "size": 8375, "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/BR54HK57OX5SHGRXEWPJA2O4OP7CXTNO/attachment/2/attachment.html" } ] }