Hi Russ,
Couldn't we install them as ${PATHETC}/motd.innd.sample and
${PATHETC}/motd.nnrpd.sample or should they be in a separate path?
In the latter case, would the ${PATHETC}/samples directory be fine?
Looking at the files, they're mostly documentation for the facility. I'm
wondering whether that's a useful thing to install. The upside of
installing some sort of sample is that it makes it clear to people
installing a new server that this is something that can be done. The
downside is that the files are not, themselves, actually useful; you
wouldn't use any part of their content when creating a real MOTD file.
They're just documentation.
Shouldn't we just add examples in /etc/news/motd.innd.sample and
/etc/news/motd.nnrpd/sample so that these files contain more information
than mere documentation?
Wouldn't then /etc/news be the right place to keep using? (Note that we
keep ".sample" at the end of the name of these files for them not to be
automatically used by INN in case the news administrator forgot to
modify them.)
For instance adding in motd.nnrpd.sample:
%%%
Here are a few suggestions of messages to display to the news reader.
Example 1
---------
Attention all users,
This server will be down for scheduled upgrades on February 1st.
It should be back up by 8:00 a.m. February 2nd.
Any questions should be e-mailed to <[email protected]>.
Apologies for the disturbance.
Example 2
---------
Dear customers,
We are pleased to announce the creation of a support newsgroup, named
"our.company.support". It was created on February 1st and is intended
to receive your questions about the use of our services. Our support
team will respond within a couple of days.
Please use this new newsgroup preferably as a means to contact us.
Example 3
---------
This news server now supports TLS connections. Please configure your
news reader to use TLS when connecting or authenticating. A tutorial is
available in the newsgroup "our.company.support" to help you do the
change. Do not hesitate to ask for help in the newsgroup if you
encounter issues during the change.
Starting from February 1st, unencrypted authentications (that is to say
not using TLS) will be rejected.
Example 4
---------
Support for a new SASL mechanism has been added: OPENID20 can now be
used to authenticate. Feel free to use it!
%%%
And in motd.innd.sample:
%%%
Here are a few suggestions of messages to display to the peer.
Example 1
---------
Attention all users,
This server will be down for scheduled upgrades on February 1st.
It should be back up by 8:00 a.m. February 2nd.
Any questions should be e-mailed to <[email protected]>.
Apologies for the disturbance.
Example 2
---------
This news server now carries the comp.* hierarchy. Feel free to add it
to the list of hierarchies you feed us.
Example 3
---------
This news server no longer accepts articles whose length exceeds 32 768
bytes. Please configure your server not to send us such articles.
Example 4
---------
Starting from February 1st, the IP of this news server will change.
Note that its host name remains the same. In case explicit rules based
on IP exist at your end (firewall, iptables, feed configuration, etc.),
please update them to use 10.0.0.1 as the IP of our news server.
%%%
Is it OK to do the suggested change and keep the samples in /etc/news?
Please tell me in case there are misspellings in the suggested texts.
Some of you may have noticed that the first example for nnrpd is taken
from RFC 6048 (specifying LIST MOTD, amongst other commands). I hope it
is fine to use it :-)
If you have ideas of other examples to add, do not hesitate to suggest.
--
Julien ÉLIE
« Il faut mettre un frein à l'immobilisme. »
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
