Beau Barnhart wrote:
>
>We have been asked by mail-abuse.org to make changes to the configuration
>to one of our servers. The following this their request...
Actually, the request understates the problem. See below.
>-- message from mail-abuse.org --
>
>Currently, when messages arrive
Hello,
We have been asked by mail-abuse.org to make changes to the configuration
to one of our servers. The following this their request...
-- message from mail-abuse.org --
Currently, when messages arrive at your mail server it runs them through
SpamAssassin, which checks for spam and
On 12-Jun-2009, at 14:32, Brad Rogers wrote:
In my case, it was that the people attempting to (un)subscribe were
sending their requests with a plain text *and* an HTML part. The
combination of the two parts added up to far more than the allowed
number of lines for a message to be treated as admi
Brad Rogers wrote:
>
>On Fri, 12 Jun 2009 14:12:17 -0600
>LuKreme wrote:
>
>Hello LuKreme,
>
>> The help says" Administrivia tests will check postings to see whether =20
>> it's really meant as an administrative request (like subscribe, =20
>> unsubscribe, etc), and will add it to the the administ
On Fri, 12 Jun 2009 14:12:17 -0600
LuKreme wrote:
Hello LuKreme,
> The help says" Administrivia tests will check postings to see whether
> it's really meant as an administrative request (like subscribe,
> unsubscribe, etc), and will add it to the the administrative requests
> queue, notify
I have Administrivia turned on for a list, but people keep sending
subscribe requests to the list address (because they are morons, I
guess, I send them the subscribe address). Anyway, the administrivia
setting does not pick up these messages and I end up with them in the
admin queue and en
Brad Rogers wrote:
>
>I run a small mailing list which under version 2.1.11 of Mailman. A
>while ago, an unsubscribe message came to the list rather than be
>intercepted and acted upon. I thought nothing of it at the time, but
>a similar occurrence on another list (to which I subscribe but do not
Hello All,
I run a small mailing list which under version 2.1.11 of Mailman. A
while ago, an unsubscribe message came to the list rather than be
intercepted and acted upon. I thought nothing of it at the time, but
a similar occurrence on another list (to which I subscribe but do not
have admin pr
Barry Finkel wrote:
>I am converting most of our Majordomo lists to Mailman. After I
>converted one list, the list administrator sent the command
>
> who LISTNAME
>
>to the converted list. It was not caught as administrivia. In the
>2.1.9 source Utils.py, I see
>
>ADMINDATA = {
># admi
I am converting most of our Majordomo lists to Mailman. After I
converted one list, the list administrator sent the command
who LISTNAME
to the converted list. It was not caught as administrivia. In the
2.1.9 source Utils.py, I see
ADMINDATA = {
# admin keyword: (minimum #args, maxi
Does anyone have some good boilerplate to use in a welcome message or a
periodic reminder to cover some of the common newbie mistakes?
I'm thinking of issues like hijacking threads, which a lot of new list
users don't understand, and use of the List-Id header for filtering. (Esp.
for Outlook Ex
Help,
Our unsubscribe and and remove requests are going to the entire list and
into the archives.
I have checked the appropriate box under "General Options" to engage the
administrivia filter.
Am I out of sync with another group of settings. I noticed a warning, but
do not know which
Hi,
I have checked the appropriate box under General
Options for the administrivia filter.
Is there a trigger word list somewhere to edit?
Am I out of sync with another group of settings.
perhaps?
Thank you in advance.
Jane
version 2.1.2
__
Do you Yahoo
I've been running mailman on my servers for a while, and letting other
people run the mailing lists, but just recently I ended up starting a
list which I need to run. I've seen this "administrivia" option quite a
few times, and thought "oh, that's cool, I don't have to worry about
silly people se
14 matches
Mail list logo
