RW wrote:
> I think the question was getting no mail without unsubscribing and
> losing the ability to post. This is useful if you read a list by other
> means, e.g. via NNTP.
I was not aware that this mailing list requires one to be subscribed
to post to it. Does it? It's not necessary on most technical mailing
lists.
I look now at the help file for the apache.org mailing lists and do
not find any way to set a "nomail" option (which some other mailing
list management software provides). Therefore I think there is no
feature to do it. The help file only lists unsubscription. Since it
has become part of the discussion I will include the help file at the
end.
As to your specific case question I can only find this infomration on
it and it appears that primarily it requires the list owner to
manually handle things.
https://www.ezmlm.org/manual/Unsubscribing.html
1.4.1 Posting from an alternative address when post are allowed only to
subscribers.
When a list is set up to allow posts from subscribers only(*), a post
from an address ('jon...@softx.com') may be rejected since this
address is not a subscriber (even though mail to the subscriber
'j...@univ.edu' reaches you, ezmlm has no way of knowing this). The
easiest way to deal with this is to unsubscribe 'j...@univ.edu' and
subscribe 'jon...@softx.com'. If this is not possible/desirable, send
the addresses in question with a note to
'mailinglist-ow...@example.org'.
The list owner can add your sender address (in this case
'jon...@softx.com') to an extra address lists of non-subscribers
allowed to post (and access the archive). The extra addresses are
kept in a database much like subscriber addresses.
In fact, you can add the address 'jon...@softx.com' as an alias
for the list 'mailingl...@example.org' by mailing
'mailinglist-allow-subscribe-jonesj=softx....@example.org' and
replying to the confirmation request. Again, you're changing the
"target" address of the request from the default (the sender
address) by adding the target to the command with the '@' replaced
by '='. Of course, the "allow" list doesn't send out posts. It is
solely a vehicle for storing "allowed" aliases.
That last paragraph (I reformated it into these paragraphs for
readability) is not clear to me and I do not understand it. But this
next makes it clear that it can only be done by an administrator.
https://www.ezmlm.org/manual/Adding-Aliases.html
2.4 Adding subscriber aliases(*).
ezmlm lists may be set up to only allow subscribers to send
messages to the list. This is less secure than moderation, but
still keeps most "garbage" off the list. Occasionally, a user may
wish to send messages from an address other than the subscription
address. As a remote administrator, you can add the user's alias
to a special "allow" database. To add 'j...@example.net' as an
alias to the 'mailingl...@example.org', send mail to
'mailinglist-allow-subscribe-john=example....@example.org'. -unsubscribe
and other commands work the same way. The messages ezmlm sends
talk about the 'mailinglist-al...@example.org' mailing list, but
of course you know that this is just a figure of speech.
On lists that do not have subscription moderation, users can add
themselves to the "allow" database in the same way. This is
documented only briefly in the USER'S manual.
Archive access may also be restricted to subscribers. Like
subscribers of the list or the digest list, addresses in the
"allow" database are allowed to access the archive.
Therefore it seems that unsubscribing is the only action a user may
take to avoid receiving email. The above requires the mailing list
owner to take action.
Bob
Hi! This is the ezmlm program. I'm managing the
users@spamassassin.apache.org mailing list.
This is a generic help message. The message I received wasn't sent to
any of my command addresses.
--- Administrative commands for the users list ---
I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:
To subscribe to the list, send a message to:
<users-subscr...@spamassassin.apache.org>
To remove your address from the list, send a message to:
<users-unsubscr...@spamassassin.apache.org>
Send mail to the following for info and FAQ for this list:
<users-i...@spamassassin.apache.org>
<users-...@spamassassin.apache.org>
Similar addresses exist for the digest list:
<users-digest-subscr...@spamassassin.apache.org>
<users-digest-unsubscr...@spamassassin.apache.org>
To get messages 123 through 145 (a maximum of 100 per request), mail:
<users-get.123_...@spamassassin.apache.org>
To get an index with subject and author for messages 123-456 , mail:
<users-index.123_...@spamassassin.apache.org>
They are always returned as sets of 100, max 2000 per request,
so you'll actually get 100-499.
To receive all messages with the same subject as message 12345,
send a short message to:
<users-thread.12...@spamassassin.apache.org>
The messages should contain one line or word of text to avoid being
treated as sp@m, but I will ignore their content.
Only the ADDRESS you send to is important.
You can start a subscription for an alternate address,
for example "john@host.domain", just add a hyphen and your
address (with '=' instead of '@') after the command word:
<users-subscribe-john=host.dom...@spamassassin.apache.org>
To stop subscription for this address, mail:
<users-unsubscribe-john=host.dom...@spamassassin.apache.org>
In both cases, I'll send a confirmation message to that address. When
you receive it, simply reply to it to complete your subscription.
If despite following these instructions, you do not get the
desired results, please contact my owner at
users-ow...@spamassassin.apache.org. Please be patient, my owner is a
lot slower than I am ;-)
