Special headers


  1. Introduction about special headers
  2. Distribution: local
  3. Distribution: usenet
  4. X-Server-Commands: noerrorlog
  5. X-Server-Commands: forcerejection
  6. X-Server-Commands: nowebcancel

 

1. Introduction about special headers

This service supports some special, non-standard headers that allow clients to customize server behavior when receiving a message that includes them. These headers can only be inserted within articles posted through this site. If they are included inside messages posted through other services, they have no effect on the behavior of this news server. All users should keep in mind that the server does not delete any special headers after receiving and before making public a message that includes them and so other users may realize that they have been inserted simply by reading the headers of each post. All headers are case insensitive and therefore they can be written in uppercase or lowercase characters.

 

2. Distribution: local

Usually, all messages sent by users of this service are transferred  to all other servers that are part of the usenet network and so they can be read by all users regardless of the service they use. However, local clients are allowed to configure this server in such a way as to avoid propagating an article to other usenet sites but to make it still visible to users of this service. This can be done by adding the following header to the message:

Distribution: local

Any message that includes this header will only be visible to local users.

 

3. Distribution: usenet

If an user replies to a local message that includes the "Distribution: local" header, by default his answer will be made available only to the local clients unless the author explicitly configures the server to trasfer it anyway to the other usenet sites. In other words, this server adds the "Distribution: local" header to all articles that reply to every post that includes it in order to avoid missing articles inside threads of messages. If a local user still wants that the server propagates to other usenet sites his answer to a message that includes  "Distribution: local" must add to his article the following header:

Distribution: usenet

Each message that includes the "Distribution: usenet" header will be propagated to other servers that are part of the usenet network even if it is an answer to a message that is available only to local users. This header has no effect on messages that would have been propagated anyway.

 

4. X-Server-Commands: noerrorlog

In order to help customers to understand why the server has rejected their messages, this service provides a web page that allows users to see all messages sent from an IP address and rejected by the server in the last 24 hours. On one hand this service is needed because many newsreaders noradays do not show to their users the error string returned by the server that describes why each message was rejected. This behavior makes almost impossible for many users to find out why a message was rejected. On the the other hand, this service could be dangerous to the users' privacy because anyone could be able to discover the IP address of any client that has sent in the last 24 hours a message that was rejected by the server simply by doing an huge number of searches, one for each ip address. Those who do not want their messages to be displayed on that page should only include in their messages the following header:

X-Server-Commands: noerrorlog

All messages that contain the "X-Server-Commands: noerrorlog" header will not be displayed on the page that allows users to see which messages sent by an ip address have been rejected in the last 24 hours.

 

5. X-Server-Commands: forcerejection

This header allows the sender of the message to ask the server to reject it. This feature is useful for developers to test the behavior of their programs when the server rejects a message. It can also be used to verify if the server is working properly. If a client includes this header in a message, the server performs all the usual checks before rejecting that post with a custom error message. So if the message has to be rejected for another reason, the server refuses it as it would do anyway and the string returned by the server to the sender shows the real rejection reason found by the script.

 

6. X-Server-Commands: nowebcancel

This news server provides a web page that allows the author of each message to delete it. Only articles posted within the last 24 hours through this server can be deleted in this way and their cancellation can only be requested by the same IP address that sent each post. The header "X-Server-Commands: nowebcancel" prevents a message from being deleted through this web page.