summaryrefslogtreecommitdiff
path: root/modules (follow)
Commit message (Collapse)AuthorAgeFilesLines
* .DeliverToList(): Append a sender field pointing to the list admin.klm1998-05-241-1/+2
|
* Use more of the available space in the basic description for 'info'klm1998-05-241-2/+5
| | | | field to better explain where it is used.
* .RegisterBounce(): I think this corrects the bounce log reporting ofklm1998-05-211-3/+4
| | | | | | | | the remaining number of bounces a member is allowed (within the stipulated time frame) before exceeding the limit. If this is right, with the other bounce-handling refinements i feel a lot more confident about predicatable, well-mannered behavior from the bounce management stuff...
* Prevent bounce loops when admin-action recipient is itself theklm1998-05-211-30/+65
| | | | | | | | | | | | | | | bouncing address - before sending the notice, check whether the bouncing address is among the list owner addresses. And otherwise, include (attach) a copy of the actual bounce notice in the admin-action message. Otherwise there is no record the administrator can examine. Finally, send both failed and successful admin-action notifications to the list administrator. Before, failed action (e.g. inability to locate the specific user) were sent to the mailman site admin - this was while i was debugging the bounce handling, but it looks a lot better now.
* Neglected to mention on last checkin:mailman1998-05-201-10/+10
| | | | | | | | | | | | | ScanMessage(): added final-step massage of all candidates to remove encompassing <, > angle brackets, if any, and check against already processed candidates. (In order to change something to enable a checkin i made a spelling change of something trivial that i resisted for a while - substituted "message_grokked" for "message_groked". I'm pretty sure the double k is right, but don't have a copy of stranger in a strange land happy to check. Anyway, i keep reading "groked" like it would rhyme with "stoked", which just can't be right...-)
* Do not send "user disabled" notices to admin when user is alreadymailman1998-05-201-17/+35
| | | | | | | | | | | disabled. The idea is that numerous outstanding bounces do not each require renotification of the admin. DisableBouncingAddress(), RemoveBouncingAddress(): changed return signatures to indicate whether email notification is necessary for this action, and in Disable version, indicate not necessary when user is already disabled. In all other cases, notification is indicated, whatever the status.
* .FormatDisabledNotice(): Text to put at top of user options pages tomailman1998-05-201-26/+46
| | | | | | | | | prominently point out when the user's delivery is disabled. (When a user's email is disabled due to bounces, they probably would not notice the checked button way down the page.) Using "from htmlformat import *" to simplify references to formatting objects.
* .DeleteMember(): Delete the option settings for the user (if any), asmailman1998-05-181-1/+3
| | | | well as the rest of the stuff.
* Really cosmetic change to the rule (dashes became underscores) in themailman1998-05-122-4/+4
| | | | default message footer.
* Essential cosmetic changes - one typo, and one missing comma (whichmailman1998-05-121-3/+3
| | | | | separates a detail elaboration from the brief description, so its lack made the two into a long brief description).
* Incremented version to 1.0b3.klm1998-05-042-6/+10
| | | | | Changed mailman URL to point to john's site, and included a comment explaining what it is for.
* Removed change_boundary() - not necessary, now that the Digest classklm1998-05-041-17/+1
| | | | is doing the right thing right off the bat.
* Removed constant i added but didn't use (SUBJ_REGARDS_PREFIX).klm1998-05-032-7/+2
|
* .SaveForDigest():klm1998-05-021-18/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Digest messages now keep all headers except 'received', 'errors-to', and all 'x-*' ones (and any continuations of these). - Mime digest messages now properly (i believe) contain mime attachments. (The key was preserving the original content-type header.) - It may be that some more headers should be trimmed, ie for the sake of the non-mime recipients - but actually, it doesn't look cluttered, for the few sample messages i tried. - The entries in the table-of-contents have the redundant subject-prefix string removed. Digest: Redundant "Vol" in masthead string removed. I took a look at rfc 934 (thanks, barry), which is the pre-Mime standard for encapsulating (nesting) messages in other messages, and it looks like the key is to have an "encapsulation boundary" that starts with a "-" dash - looks like mime extended from this. However, the old rule for nesting an encapsulated message within another encapsulated message is to insert a "- " space in front of the original encapsulation boundary. Unfortunately, this would break mime encapsulation, so i'm not implementing this part of the old burstable-digests standard. The rest of it *may* be ok, though, in case anyone has the old-style bursting readers... Anyway, i've done about as much as i was hoping to do with the digests format - i don't forsee devoting much more attention to features, just to ironing out bugs.
* .SendDigest(): digest_text wasn't defined - had to read the file.klm1998-05-011-2/+2
|
* On further thought, emphasize that case-changes only are acceptableklm1998-05-011-2/+2
| | | | for the real_name setting - in the brief description.
* Whoops, a trivial after-checkin phrasing refinement.klm1998-05-011-2/+2
|
* .GetConfigInfo(): Reenable web-based setting of web_page_url. Thisklm1998-05-011-15/+42
| | | | | | | | | | | | | | (together with the 'host_name' setting) is crucial for lists that use some alternate address of a host that has multiple identities. (I have to go through everything to make sure these addresses are utilized everwhere they ought to be, but this capability will be crucial for, eg, clients of ISP's that have their own client domains, and of course want to have their mailman setup reflect that domain!) .GetConfigInfo(): Added long descriptions for several variables that needed them, including particularly the real_name - have to make sure that people know they can change the case, but not anything else about it, and why.
* Strengthen admonition against setting reply_goes_to_list.klm1998-05-011-6/+10
|
* Digest(): new class which represents a digest in a presentation-klm1998-05-011-79/+134
| | | | | | | | | | | | | neutral format, and then can present as either plain or mime format. Much cleaner than when the digest structure and layout was combined with the other logic in .SendDigest(). .SendDigest(): Use new Digest() class to compose the digest and then present it in either (or both) formats. Much simplified as the digest structure and layout logic is now in the digest class. Added DIGEST_MASTHEAD, removed DIGEST_HEADER_TEMPLATE and DIGEST_CLOSE_TEMPLATE.
* Digest class moved to mm_digest, because that is the only place itklm1998-05-011-19/+1
| | | | | will be used, and it uses maillist-specific digest stuff (e.g. DIGEST_MASTHEAD).
* .DeliverToList(): header and footer are now optional. (Digests nowklm1998-05-011-3/+3
| | | | | take care of incorporating the header and footer, and shouldn't have to specify null ones...)
* On john's urging, MIME is *not* default digest format, asklm1998-04-292-4/+4
| | | | | distributed. (I'm sticking with it as default here at python.org, until i get complaints.)
* Beginning of Digest class. (Premature checkin forced by need toklm1998-04-281-1/+19
| | | | relocate the repository.)
* Include a few more likely prospects among invalid request senders.klm1998-04-281-2/+2
|
* 1.0b2, not 1.0b1.2!klm1998-04-282-4/+4
|
* For mime digests, substitute the result of mimetools.chooseboundary()klm1998-04-271-67/+82
| | | | | | | | | instead of the ad-hoc one. This should be more robust and more likely to not break sendmails out there... (There actually has been lots of restructuring, in preparation for using a digest object that will provide for better mixed multipart mime presentation...)
* New routine change_boundary, for substituting one mime boundary forklm1998-04-271-1/+17
| | | | another.
* New LOOPING_POST error message, for wide-loop detection disposition.klm1998-04-271-1/+2
|
* Using new X-beenthere message header for loop-detection, particularlyklm1998-04-271-1/+7
| | | | for reflection loops.
* Using new OutgoingMessage.__delitem__ method.klm1998-04-271-6/+6
|
* OutgoingMessage: Add a __delitem__, extracting .CacheHeaders() methodklm1998-04-271-7/+23
| | | | from .SetHeaders() so the __delitem__ can use it.
* Discard "mail commands" from postmaster accounts (nobody,klm1998-04-271-5/+15
| | | | | | | | mailer-daemon, postmaster, orphanage, postoffic) - they're almost certainly delivery-failure notices. I'm going to poll the mailman-developers list for suggestions about refinements to this approach.
* .SaveForDigest(): When reply_goes_to_list is set, add a reply-to:klm1998-04-231-6/+11
| | | | list to each digest entry. (From janne sinkkonen, more or less.)
* Ignore any mailcommands coming from postmaster-type accounts -klm1998-04-231-1/+7
| | | | | | | | | mailer-daemon, postmaster, orphanage, and postoffice - on the presumption that they're failed subscribe instructions, bouncing back to the -request addr. I think this'll take care of that sticky problem fairly safely. Nobody should be sending commands from those accounts, anyway...
* .ScanMessage(): Further robustification of the bounced-message addressmailman1998-04-231-4/+10
| | | | | | | | | extraction, with testing. We now avoid all the silly elipses cases... (Unfortunately i could not test the bounce handling on glyph due to some subtleties in the sendmail setup. Fortunately, bounce handling is a sufficiently uncommon event that i could work on the production system without much fear of disruption.)
* Added missing "</dl>" to MESSAGE_DECORATION_NOTE.mailman1998-04-231-1/+2
|
* Repaired minor typo in option description.mailman1998-04-231-2/+2
|
* ValidEmail(): Elide the constraint that addresses have their top-levelklm1998-04-231-11/+11
| | | | | | domain among those iterated among valid_toplevels. Depending on ensuing discussion on the mailman-developers list, i'll probably cut this out completely.
* These changes should reduce, if not eliminate, the duplicate handlingklm1998-04-231-14/+13
| | | | | | | | | | | | | | | of bounce violators, and also reduce if not eliminate the number of invalid address targets. .ScanMessage(): Instead of handling each email addr as it's encountered, collect together all the candidates and go through them all at the end, rejecting duplicates. This way, candidates found repeatedly in different cases won't be processed multiple times. .ExtractBouncingAddr(): Prevent a commonly recurrent aberrant address gleaning, eg: "<klm@python.org>..." - many error notice lines have that elipsis after the address, and it was not being adequately filtered. Now it is.
* Added "su" to valid top levels.klm1998-04-231-2/+2
|
* Add the number of messages to the digest subject lines.klm1998-04-221-12/+21
| | | | Regularize the digest header list info section slightly.
* .SendTextToUser(): Removed debugging log message.klm1998-04-151-3/+1
|
* .DeliverToList(): Was missing a newline between message headers andklm1998-04-141-7/+5
| | | | | body, so initial body lines that looked like header would be incorporated in header.
* (First checkin after release tagged mailman-1_0b2.)klm1998-04-141-29/+34
| | | | | | | | | Changed digest header format slightly, but changed the code more to use keyword format strings instead of order-dependent ones, to make reorganizing the text a lot less fragile. (I'm coming to think that having a footer is mostly undesirable, so mm_cfg.DEFAULT_DIGEST_FOOTER should be the empty string.)
* Whoops - i broke the subscribe acknowledgement on checkin. Fixedklm1998-04-131-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | thanks to janne sinkkonen. Date: 14 Apr 1998 01:22:26 +0300 From: Janne Sinkkonen <janne@avocado.pc.helsinki.fi> To: klm@python.org Subject: Re: [Mailman-developers] late on new mailman release - soon I guess this patch is necessary to get sensible welcome messages: *** mm_deliver.py Tue Apr 14 01:21:27 1998 --- mm_deliver.py~ Sun Apr 12 04:37:30 1998 *************** *** 168,175 **** header = '' welcome = '' ! body = (SUBSCRIBEACKTEXT % (self.real_name, self.host_name, ! header, welcome, self.GetScriptURL('listinfo'), self.GetOptionsURL(name), self.real_name, self.host_name, --- 168,175 ---- header = '' welcome = '' ! body = (SUBSCRIBEACKTEXT % (header, welcome, ! self.real_name, self.host_name, self.GetScriptURL('listinfo'), self.GetOptionsURL(name), self.real_name, self.host_name, -- Janne Sinkkonen <janne@iki.fi> <URL: http://www.iki.fi/~janne/ >
* Send messages by connecting directly to port 25 and talking SMTP toklm1998-04-135-16/+141
| | | | whatever mail delivery agent is there.
* Use new mm_message __delitem__ discipline.klm1998-04-131-2/+2
|
* Use __delitem__ discipline for deleting headers by name. (Guidoklm1998-04-131-13/+22
| | | | | provided a refinement of the code that's not naive about continuation lines.)
* Move the unconfigurable vars to the unconfigurable's section.klm1998-04-121-10/+10
|
generated by cgit v1.2.3-70-g09d2 (git 2.52.0) at 2025-12-25 13:24:16 +0000