[vsnet-grb 99596] Request For Comment on GCN Notice To-line change proposal
Bacodine
vxw at capella.gsfc.nasa.gov
Wed May 27 08:37:55 JST 2009
TO: All email-based GCN Notice recipients
RE: Change in the To-line of the email Notices
DT: 26-May-09
If you are NOT a full-format email GCN customer, IGNORE this email.
INTRO:
I am considering changing the content of the To-line
in the header of some of the emails you receive.
Currently, the To-line looks something like:
To: youraccount at astro.institution.edu
The new way would look like:
To: nl_061_email_none at capella.gsfc.nasa.gov
(where the "061" is the notice type number, and
the "email" is the full-format method, and
the "none" says no attachment (or "fits", "gif", etc)).
WHY THE CHANGE:
The new method would utilize 'procmail' to manage
the distribution lists for each notice type. This should make
GCN faster and more efficient for emailings.
(The lists would still be based on all your site-specific filtering rules.
You would still continue to receive only those notices you have requested.)
QUESTION TO YOU:
Would this change cause any problems at your end?
a) Some spam-filters check to see if the recipient's identity
is also in the To-line field. This would not be true
for this new method. Usually this discrepancy is not
a make-or-break effect. Rather, it only contributes an additional amount
to the total "score" to determine if the email is spam or not.
[Surely GCN Notices do not come anywhere close to being considered spam. ;-) ]
b) It is possible that some people use the To-line
in post-processing (eg procmail filtering rules).
Do you test/use the To-line in some special processing?
If either of these is a problem for your operations,
then I need to know. (There is a work-around.)
Sincerely,
Scott
Scott Barthelmy NASA-GSFC, Code 661, Greenbelt, MD 20771
PHONE: 301-286-3106 (office)
PHONE: 301-346-3733 (cell)
FAX: 301-286-1684 (1st choice, -1682 2nd choice)
EMAIL: scott at lheamail.gsfc.nasa.gov
PAGER: 3013463733 at cingularme.com
WEB: http://gcn.gsfc.nasa.gov/gcn
PS Of course, you can always take this opportunity to request a change in your configuration.
//////////////////////////////////////////////////////////////////////////////////////
Site_name: VSNET
Lon,Lat= 135.75 35.00
Distribution_method: EMAIL Attachment_format: NONE
Address: vsnet-grb at ooruri.kusastro.kyoto-u.ac.jp
Filter: ALL
Error_limit= 360.100 [deg, diameter]
Delta_T_limit= 999.900 [hr]
Swift_Trigger_ID_filter: Disabled
Sources & Notice Types/Subtypes:
RXTE-PCA_Alert_wont: Disabled
RXTE-PCA_Alert_will: Disabled
RXTE-PCA_nosaw: Enabled
RXTE-PCA_saw: Enabled
RXTE-ASM: Enabled
IPN_RAW: Disabled
IPN_POS: Enabled
RXTE-ASM_TRANS: Enabled
HETE_TEST: Disabled
TYPE2_TEST: Disabled
INTEGRAL_Test_notices: Disabled
SWIFT_BAT_GRB_TEST: Disabled
AGILE_GRB_TEST: Disabled
FERMI_GBM_TEST: Disabled
FERMI_LAT_TEST: Disabled
INTEGRAL_POINTDIR: Disabled
INTEGRAL_SPIACS: Enabled
INTEGRAL_WAKEUP: Enabled
INTEGRAL_REFINED: Enabled
INTEGRAL_OFFLINE: Enabled
GRB_CNTRPART: Disabled
SWIFT_BAT_GRB_ALERT: enabled
SWIFT_BAT_GRB_POS: enabled
SWIFT_BAT_GRB_POS_NACK: enabled
SWIFT_BAT_SUBTHRESH_POS: Disabled
SWIFT_BAT_GRB_LIGHTCURVE: enabled
SWIFT_FOM_2OBS: enabled
SWIFT_SC_2SLEW: enabled
SWIFT_XRT_POS: enabled
SWIFT_XRT_POS_NACK: enabled
SWIFT_XRT_SPECTRUM: enabled
SWIFT_XRT_IMAGE: enabled
SWIFT_XRT_LIGHTCURVE: enabled
SWIFT_UVOT_IMAGE: enabled
SWIFT_UVOT_SRCLIST: enabled
SWIFT_UVOT_POS: enabled
SWIFT_UVOT_POS_NACK: Disabled
SWIFT_BAT_GRB_LC_PROC: enabled
SWIFT_XRT_SPECTRUM_PROC: enabled
SWIFT_XRT_IMAGE_PROC: enabled
SWIFT_UVOT_IMAGE_PROC: enabled
SWIFT_UVOT_SRCLIST_PROC: enabled
SWIFT_POINTDIR: enabled
SWIFT_BAT_TRANS: Disabled
SWIFT_BAT_SLEW_POS: Disabled
SWIFT_TOO_FOM: enabled
SWIFT_TOO_SLEW: enabled
AGILE_GRB_WAKEUP_POS: Disabled
AGILE_GRB_GROUND_POS: Disabled
AGILE_GRB_REFINED_POS: Disabled
AGILE_POINTDIR: Disabled
FERMI_GBM_ALERT: Disabled
FERMI_GBM_FLT_POS: Disabled
FERMI_GBM_GND_POS: Disabled
FERMI_LAT_POS_UPD: Disabled
FERMI_POINTDIR: Disabled
SIMBAD-NED: Disabled
General Adminastrivia Comments/Suggestions:
1) When requesting changes to your configuration,
it helps if you refer to your site_name.
2) If your site has more than one recipient (ie a list),
please review the list to see if anybody should be deleted;
(the volume of bounce-back-to-gcn emails gets large after a while).
3) If a new contact_person has taken over for the project, please inform me.
4) If your site is no longer active, please inform me.
More information about the vsnet-grb
mailing list