Dear Submitter: The e-mail message you submitted to the GCN Circular service (appended below) was NOT distributed to the GCN Circular List. This could be due to one of the following reasons (the Subject-line of this e-mail contains your specific reason-number): Reason 1) It came from an account (account_name and/or account_domain) which is not recoginized by the GCN system. This could be due to several reasons: a) You are submitting from an account or machine which is (i) not your normal account_name, or (ii) from a machine outside your normal domain. b) You have recently changed your account name/domain and have not notified the GCN_List operator to update the database. (Send email to scott@lheamail.gsfc.nasa.gov to have your new account information updated in the list database.) c) You were requesting to be added to the distribution list (instead of submitting an actual GCN Circular message). If this is the case, you should send the request to scott@lheamail.gsfc.nasa.gov. Reason 2) You did not include one of the following strings in the Subject-line: "GRB", "grb", "SGR", "XRF", FXT", "XTR", "XRT", "XRB", "AXP", "Swift", "SWIFT", "INTEGRAL", "IBAS", "KONUS", "AGILE", "Fermi", "MAXI", "IPN", "IceCube", "ICECUBE", "ANTARES", "HAWC", "Chandra", "HST", "SDSS", "RATIR", "VLA", or "VLBI". Reason 3) On very very rare occasions, it is possible to receive more than 3 incoming submissions within 100 seconds. When this happens the 4th submission is not distributed. Reason 4) There are too many lines in the body of the email submission. Reason 5) There was an "RE: " in the Subject-line. Reason 6) There was some 'vacation-program' strings in the Subject-line. Reason 7) There are HTML-commands in the body of the email. Reason 8) Unknown error condition. Reason *) You are sending an administrative email to this account instead of sending it to the "scott@lheamail.gsfc.nasa.gov" account. If you are sending an administrative request about the Circulars (or the Notices), then you should be sending your email to "scott@lheamail.gsfc.nasa.gov" account and not to this "gcncirc" Circulars account. Solution 1) If you have access to your normal account, then please resubmit the message from that account. If this is not possible, then your current submission has been forwarded to the "pending file" and will be processed by a human within a short amount of time (1-24 hours depending on the time-of-day, the day-of-week, and any special circumstances: holidays, vacations, etc), and it helps to send an email to scott@lheamail.gsfc.nasa.gov. The human operator has more latitude in determining a valid submission than the automated GCN List processing program. [If you are not currently a member of the GCN Circulars list, then you should visit the new-members (invitation) web page: http://gcn.gsfc.nasa.gov/gcn/invitation.html to determine what information is needed to be added to the list.] Solution 2) If the problem was the no "GRB"/etc in the Subject-line, then please resubmit the message with one of the following strings: "GRB", "grb", "SGR", "HETE", "XRF", "FXT", "XTR", "XRT", "AXP", "IPN", "Swift", "SWIFT", "INTEGRAL", "IBAS", "KONUS", "AGILE", "Fermi", "MAXI", "IPN", "IceCube", "ICECUBE", "ANTARES", "HAWC", "Chandra", "HST", "SDSS", "RATIR", "VLA", or "VLBI". in the Subject-line. Traditionally, everyone should have a string like "GRByymmdd" in the Subject-line anyway so as to identify which burst you are discussing, or for the transients, then the other strings identify which type of transient it is (and then a 'telephone_number' location designation will likely be included too, eg. VLA J1744+1717. The reason for this test on the GRB string in the Subject-line is to eliminate the problem of people who use a 'vacation' program to respond to received e-mail. Since these vacation responses are sent back to the originator (gcncirc@capella.gsfc.nasa.gov in this case) and also have a valid submitter's identity, an infinite loop of messages is created. This string-test is one of the ways to protect against the infinite loop. Solution 3) If you believe your submission passed items 1 and 2, then you might try submitting your message again (after 100sec has elapsed). This rate-limit is a safeguard against an infinite loop situation of e-mail ping-ponging back-n-forth. People using the "vacation" program (or similar programs) plus some scenarios of bounced e-mail would cause infinite loops, but protections within the processing have been constructed to break these loops. However, there can be a yet undiscovered and therefore unprotected scenario which would produce an infinite loop. To stop this unknown scenario, a "<4 within 100sec" rate limit has been imposed. Solution 4) If you the body of the email message you submitted has more than 500 lines, then it is rejected. Check to make sure that your mailer program did not append an html-lized version of your submission. or that your editor did not append many blank lines at the end -- remove either of these and re-submit. (This is yet another protection mechnism against various infinite-loop scenarios.) If you feel that you need to distribute a Circular longer than 500 lines, then please contact the GCN editor (he can override this limit). Solution 5) The Subject-line contained one of the following "RE: " or "Re: " substrings. The test for these substrings is one of the ways the Circulars demon protects against people accidentally hitting the 'reply' command within their email reader programs. The progression of email reader programs has neccessitated this new protection/filtering mechanism. If you feel you have a valid submission, then please remove the 're' string from your subject-line and resubmit your circular. Solution 6) The Subject-line contained one of the following (case insensitive): "this is an automatic reply", "vacation", "out of the office", "out of office", "out of town", "away from my mail", "away from his e-mail", "away from the office", "away from his office", "away from her office", "no longer receiving email", and "re: " substrings. The test for these substrings is one of the ways to protect against the various forms of the 'vacation program' that people use when they are away from their office (vacation, business travel, etc). Solution 7) Turn off the HTML-copy-inclusion function in your mail program and resubmit. Some mailer programs append a duplicate copy of the plain-text email which has HTML-formatting commands embedded. Some mailer programs only have the HTML-ised version of the message. Either way, these HTML-versions of the message should not be distributed. So it is reqested that you resubmit your Circular with plain-text only in the body of the email -- disable the option in your mailer program that includes the HTML-version. Solution 8) There is no suggested remedy for a type 8 problem. These is no previously known/suspected way this can happen. Your submission has been placed in the pending file and will be investigated by a human at a later time. (And sending email to scott@lheamail.gsfc.nasa.gov will speed up this process.) For more information about the GCN Circulars (content, procedures, formats, etc) please check the web page: http://gcn.gsfc.nasa.gov/gcn/gcn_circulars.html. If you require further (more urgent) consideration, please use one of the following communication methods listed below. Try calling my office first. Then e-mail to my normal e-mail account. If you require urgent assistance, then try a short e-mail message to my pager account (I'll respond to my pager all hours but midnight to ~8am). Scott Barthelmy NASA-GSFC, Code 661, Greenbelt, MD 20771 PHONE: 301-286-3106 (work) FAX: 301-286-1684 (1st choice, -1682 2nd choice) EMAIL: scott@lheamail.gsfc.nasa.gov PAGER: 3013463733@mmode.com WEB: http://gcn.gsfc.nasa.gov/gcn MARKER: DKJSDSD6S75AXPSNO234H54YUAS98FXNXIZQ0PAPQ8238J1J3N3L0ZPQ8X7F63UW ///////////////////////////////////////////////////////////////////////////////