Platforms

All


Abstract

Specifies non-POSTMASTER users who are allowed to post to the ALL-REQUEST alias.


Example

z/VM:

ALL_REQUEST_ALLOWED_USERS = 'joe@example.com pete@abc.unix.example.org'

Unix:

ALL_REQUEST_ALLOWED_USERS=joe@example.com pete@abc.unix.example.org

export ALL_REQUEST_ALLOWED_USERS

Windows:

ALL_REQUEST_ALLOWED_USERS=joe@example.com pete@abc.unix.example.org


Details

The ability to post to the ALL-REQUEST alias, which expands to all non-quiet list owners, is restricted as follows:

      1. The site configuration variable, ALL_REQUEST_ALLOWED_USERS, can be used to specify who can mail to ALL-REQUEST. This variable uses the same syntax as POSTMASTER=, in other words, a space-separated list of userid@host specifications.
      2. Postmasters are always allowed to mail to ALL-REQUEST, even when not listed in ALL_REQUEST_ALLOWED_USERS.
      3. The determination is made conclusively on the RFC821 MAIL FROM because:
        • This avoids dealing with header errors. Header error = don't know who sent this = discard silently = unhappy admin who had to send an urgent notice to all his owners.
        • The main point of this change is to block spammers, and spammers typically have non-working or null MAIL FROM: addresses. Needless to say, null doesn't pass the test.
      1. When the MAIL FROM is not null, the REQNAK1 mail template form is sent when the message is rejected.


Default Value

Null string.


Wildcards

Not allowed.