| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
(first non-whitespace is a #).
|
| | |
|
| |
|
|
| |
decide whether to use msg.GetEnvelopeSender() or not.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(option_descs, option_info): Provide much more detailed descriptions
of the options. Also changed `norcv' to `notmetoo' although the
former is still acceptable as an alias.
(options): New global to preserve the order that we want to display
the options in response messages. These options are in the same order
as shown on the membership management admin page. The user option
page still needs to be changed to support this order.
MailCommandHandler.__init__(): All private variables are fixed to
start with double underscore (e.g. __dispatch). Added an __errors
ivar to count the number of AddError() calls made. A different error
message format is now used, which should be much more concise, and
more informative information is provided at the head of error
messages.
AddToResponse(), AddError(): Both methods now take a final argument
`trunc' which says what column to truncate the text to. With trunc=0
no truncation (this is useful for when we use Utils.wrap() to wrap the
text). AddError() also now takes a prefix argument, increments
self.__error, and essentially calls AddToResponse().
ParseMailCommands(): Some stylistic changes. The line being processed
is not placed in the response buffer unless we know it is a valid
command. If it's an invalid command, we print the error message more
concisely.
When `end' is found, include in the response all the following lines
that are ignored.
If the number of errors exceeds 5, then stop processing the message
immediately (don't keep processing more lines).
If an unexpected error occurs with a valid command (one that is
dispatched), we catch this and include the traceback in the response
message. We also send the traceback to the list administrator -- I
wonder if this should be the mailman-owner??? We also log the
exception.
In the error preamble, include human contact information.
Several of the Process*Cmd()'s have been modified to work with this
new framework, and to provide much more meaningful response messages.
|
| |
|
|
| |
script which does a much better job of reporting the error.
|
| |
|
|
|
|
| |
made, we now change the `norcv' option to be `notmetoo'. This is
still backwards, but changing the sense of this option is to much work
right now. `norcv' is accepted as an alias for `notmetoo'.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
user's address, which jumps you to their member info page.
Second, reorder the items in the table so that digest comes just
before plain. Didn't make sense to separate these two digest related
items.
|
| | |
|
| |
|
|
| |
instead of Makefile (which now needs to be removed)
|
| | |
|
| |
|
|
|
|
|
| |
file containing Vivek's comments. Second, in the Makefile.in, allow
the installer to override the chmod command on the directories.
-Barry
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
letters.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
bottom" => "button at the bottom". Sounds somehow obscene the other
way, but nonetheless we'd like it to make sense.
While i was here i did a few *more* trivial things...
Using "not metoo" instead of "norcv" for member's status column
headings (and legend), to disambiguate from "nomail"! (I think i
recall "metoo" from things like /bin/mail, in any case, it's a lot
more descriptive of the intention.)
While i'm here i centered all the checkbuttons, which i think looks a
lot tidier.
|
| |
|
|
|
| |
changed the message so it only says it's at the bottom of the page
when it really is.
|
| |
|
|
| |
1.0b9
|
| |
|
|
| |
getting sent once again to the mailing list!
|
| |
|
|
| |
members table [and testing the emailing of this checkin message, as well].
|
| |
|
|
| |
(check in by baw not klm)
|
| |
|
|
|
|
| |
on the page. (It should be available on the top, even more, but i
don't see how to do so without cluttering at the moment, and my
connection is so low band that i can't scope it out right now.)
|
| |
|
|
|
|
|
|
| |
posting is being rejected. (This enables them to explain the right
place to send administrivia, for example.)
((Barry - i know these are niggly little things - it's all i have time
for. I just want to mention that i'm really greatful that you've been
taking care of as much of the substantial stuff as you've been doing!))
|
| |
|
|
|
|
|
|
|
| |
occur for transient things, like procmail errors or "can't create
output".
In general i'm dubious about the immediate-removal class, and would
lean towards treating all bounces the same, with action on a
cumulative incidence, so any transient problems get time to be
fixed...
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1 by default. This instructs the MailList.Post() method to use first
the envelope sender (i.e. Unix "From " line) and then the From:
header. However, this breaks member_only_posting on some systems (for
reasons unknown). Set this variable to 0 in mm_cfg.py to use only the
From: header, although this can open the list up to spam.
(MailList.py): in Post(), check USE_ENVELOPE_SENDER to see if
GetEnvelopeSender() should be called.
(FAQ): Add a question refering to USE_ENVELOPE_SENDER.
|
| | |
|
| |
|
|
| |
it's a string.
|
| |
|
|
| |
`general' category page. The others are just too noisy.
|
| |
|
|
|
|
| |
- member management page should display case-preserved email addresses
(but still sort case-insensitively). Also, addresses should be
links to member options page.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
moved to NEWS and removed.
|
| |
|
|
| |
process.
|
| |
|
|
|
|
|
|
|
|
|
| |
digest_members onto one_last_digest attribute. This attribute is
checked in SendDigest().
SendDigest(): Add the members in one_last_digest attribute to the
digest recipients. This means that folks who turn digests off at
least don't lose messages. This is a kludge but it was much harder to
send the digest to the user when they undigest, so this is a workable
compromise.
|
| |
|
|
| |
user may get one last digest.
|
| |
|
|
| |
whole message as <MM_Case-Preserved-User> replacement).
|
| |
|
|
|
|
|
|
|
|
| |
will contain the entire case-preserved message, if one exists.
Also, added some text explaining that if digests are turned off, one
last digest will be sent to the user.
Yeah, this means site admins will have to copy options.html into each
lists/<listname> during the upgrade.
|