Re: [Mailman-Developers] dkim-signature headers

On 2/8/07 10:27 AM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > Me too. Here's my discussion on the topic, including a concrete > proposal for Mailman 2.1.10 and 2.2/3.0. Feel free to comment on the > wiki on in this thread. > > http://wiki.list.org/x/OgM > Looks good to me. " IOW, a valid s

Re: [Mailman-Developers] dkim-signature headers

On 2/7/07 9:19 AM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > OTOH, how many people would smell something fishy if this > message had this header: > > From: Barry Warsaw <[EMAIL PROTECTED]> With many MUAs (including the vast majority of different MUA programs and versions) that would pass total

Re: [Mailman-Developers] dkim-signature headers

On 2/7/07 8:46 AM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > Should we strip DKIM by default or not? Not strip by default. Even though that changes the default vs the most recent Mailman, it leaves the default alone for everyone who jumps to 2.1.10 from earlier versions. --John __

Re: [Mailman-Developers] dkim-signature headers

On 2/7/07 7:32 AM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > Either they have a milter that refuses to > resign or they have a working milter. If their milter doesn't > resign, then less harm is done by stripping the header. If their > milter does resign, then less harm is done by allowing it

Re: [Mailman-Developers] dkim-signature headers

On 2/6/07 5:51 PM, "Bob Puff" <[EMAIL PROTECTED]> wrote: > If a bad DK isn't bad, then how is this supposed to help spam? I mean, if the > mere presence of some signature in the headers will increase the likelihood of > an email being delivered (or at least help it NOT be tagged as spam), surely

Re: [Mailman-Developers] dkim-signature headers

On 2/1/07 5:46 PM, "Bob Puff" <[EMAIL PROTECTED]> wrote: > I have demime in front of most of my larger lists, and I can tell you from > casual peeks at the incoming copy that I keep, there are far too many people > who send html email. Anyone using Windows machine, or a Mac starting with Tiger wh

Re: [Mailman-Developers] Pickles begone

On 12/29/06 2:17 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > I'm about to merge my SQLAlchemy branch to the trunk. I'm happy > enough with where this is going to commit to this approach going > forward. [Loud cheering from the sidelines!!] (An upcoming rewrite of our mail handling system w

Re: [Mailman-Developers] Crypto-sign to post

On 11/9/06 2:54 AM, "Stefan Schlott" <[EMAIL PROTECTED]> wrote: > Another possible problem: And yet another problem: the proliferation of different ways to create signed messages, and recognizing them successfully. I could sign messages at least three ways just using Apple's Mail.app: GPG wi

Re: [Mailman-Developers] [Mailman-Users] OS X & Mailman & Python

On 9/28/06 7:16 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > If you look at the source, you'll see that the #! line is actually > @PYTHON@ which gets substituted by configure at build time. I forget > exactly why, but the standard #! /usr/bin/env python invocation > caused problems for people,

Re: [Mailman-Developers] [Mailman-Users] OS X & Mailman & Python

On 9/27/06 6:29 PM, "Carson Gaspar" <[EMAIL PROTECTED]> wrote: > --On Wednesday, September 27, 2006 11:54 AM -0400 Barry Warsaw > <[EMAIL PROTECTED]> wrote: > >> Then there is the question of what versions we support for Mailman >> 2.2, which is currently under development. Previously we've said

Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8041] trunk/mailman/Mailman

On 9/28/06 1:11 AM, "Nigel Metheringham" <[EMAIL PROTECTED]> wrote: > On Wed, 2006-09-27 at 23:25 -0500, Brad Knowles wrote: >> LMTP is probably the best and most native method for both sendmail >> and postfix. I can't speak for other MTAs. > > Exim can do LMTP, over a pipe (ie fork/exec program

Re: [Mailman-Developers] Patches in mandriva package

On 9/17/06 8:01 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > BTW, what do you think about changing the way we hold messages for > digests? E.g. instead of putting them in an mbox file, where it's > more difficult to skip bad messages, stick them in a queue-like > directory and pull them from t

Re: [Mailman-Developers] Fwd: suggested improvement for Mailman's bounce processing

On 8/14/06 5:42 AM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > Today, held messages still have to be approved by the moderator. > What I propose is to allow posters to self-moderate, simply by > verifying that their address is real. This probably means a > clickable link and (maybe) a header coo

Re: [Mailman-Developers] Turning off dynamic JavaScript

ality, it is rare to turn Javascript off. > > David Andrews > > At 01:54 PM 7/5/2006, John W. Baxter wrote: >> On 7/5/06 11:26 AM, "emf" <[EMAIL PROTECTED]> wrote: >> >>> The problem I face is not when JavaScript is not active, the problem is &

Re: [Mailman-Developers] Parsing and Rendering rfc8222

On 7/5/06 4:30 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > I'm thinking something along the lines of sha1 hashing Message-ID and > perhaps Date. RFC 2822 $3.6 says that the only required headers are > the origination date (Date:) and originator address fields (From: and > possibly Sender: and

Re: [Mailman-Developers] Turning off dynamic JavaScript

On 7/5/06 11:26 AM, "emf" <[EMAIL PROTECTED]> wrote: > The problem I face is not when JavaScript is not active, the problem is > when JavaScript *is* active *and* behaves correctly - i.e. performs the > dom modification I've told it to - but the browser/screen reader doesn't > bother to tell the u

Re: [Mailman-Developers] 2.1.8 documentation mismatch

On 6/6/06 9:23 AM, "David Lee" <[EMAIL PROTECTED]> wrote: > This mixture of terminology seems to occur in other places also. You might > want to consider rationalising these to the same thing for the sake of > moderators who might be (say) secretarial staff. Secretarial staff should have no probl

Re: [Mailman-Developers] Topic regexps

On 5/25/06 8:29 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote: > I've thought about this some more and what I'm currently thinking is if > the topic regexp is multiline, leave it as is in topics, but before > compiling it for use, split the lines and then rejoin them with "|", > and compile not in V

Re: [Mailman-Developers] [Mailman-Users] Sender field

On 4/29/06 8:00 AM, "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: > Sender doesn't instruct *conformant* MTAs at all, does it? AFAIK the > only thing that a RFC 2821-conforming MTA looks at is the Return-Path > header, and it's supposed to remove that. There is no Return-Path: header during t

Re: [Mailman-Developers] [Mailman-Users] Sender field

On 4/28/06 6:06 AM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > On Thu, 2006-04-27 at 22:46 -0500, Brad Knowles wrote: > >> If the previous value of the "Sender:" field is being lost, then >> that should be corrected. At the very least, the value should be >> saved in an "Old-Sender:" or "Previo

Re: [Mailman-Developers] Advice wanted on option to not include original post in notices

On 3/27/06 3:48 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote: > First, should these be site wide mm_cfg.py options or should they be > per-list options with a default from mm_cfg.py? In either case, the > Defaults.py setting would match current behavior. > [Other good thoughts deleted, as Mark kno

Re: [Mailman-Developers] Inactivity deletion of maillist users ?

On 1/12/06 5:51 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote: > Joshua Ginsberg wrote: >> >> Perhaps an interesting compromise might be to add to config.pck a key >> "last_post" whose value is a dictionary of email:time 9-tuple pairs. >> That way, folks like Erling could write a script to go ahead

Re: [Mailman-Developers] RELEASED Mailman 2.1.7

On 1/1/06 1:22 AM, "Tokio Kikuchi" <[EMAIL PROTECTED]> wrote: > John W. Baxter wrote: >> >> Shouldn't Mark Shapiro be recognized in the ACKNOWLEDGEMENTS file now? >> > > Yes. Mark Sapiro _is_ in the ACKNOWLEDEMENTS. I've just added his nam

Re: [Mailman-Developers] RELEASED Mailman 2.1.7

On 12/31/05 5:02 AM, "Tokio Kikuchi" <[EMAIL PROTECTED]> wrote: > I'm pleased to announce the release of GNU Mailman 2.1.7. This > is a significant release, which includes security enhancement > fixes, a new language (ia: Interlingua) support, a couple of new > features, and many bug fixes. Well

Re: [Mailman-Developers] Spam/Scam button

On 12/14/05 3:32 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > I do think mailman-developers > is a reasonable place to discuss this. We can talk about whether it's > even reasonable to have anti-spam defenses in Mailman, and if so whether > we want to pick one such product to support, or have

Re: [Mailman-Developers] Make web_page_url visible in the admin GUI?

On 11/26/05 1:25 AM, "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: >> "Max" == Max Bowsher <[EMAIL PROTECTED]> writes: > > Max> Is there any reason not to add web_page_url to the > Max> configurable options in the admin GUI? Right below host_name > Max> in the general category

Re: [Mailman-Developers] MysqlMemberships.py

On 11/23/05 3:38 AM, "Fil" <[EMAIL PROTECTED]> wrote: >> Unfortunately this still doesn't succeed reconnecting to the server: I get >> this traceback: >> >> File "/var/local/mailman/Mailman/MysqlMemberships.py", line 141, in >> _prodServerConnection >> if self.connection.ping() == 0: Operat

Re: [Mailman-Developers] PHP Wrappers?

On 11/22/05 12:18 AM, "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: > Speaking for myself, I see nothing wrong with asking the bleeding edge > adopters to change MTAs, and I see nothing wrong with restricting > Mailman-supplied MTA code to a couple of MTAs that we "like". Of > course we help o

Re: [Mailman-Developers] Informal "MEP" process, anyone? [was: PHP Wrappers?]

On 11/17/05 11:24 AM, "Joshua Ginsberg" <[EMAIL PROTECTED]> wrote: > 2) Ability to switch MemberAdaptors through the web interface as well as > configure SQL queries through the web interface. This comment led me to think "ah, most people working on the development will be running Mailman on serv

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

On 10/26/05 6:06 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote: > Actually, it is not really doing the right thing because it is not > supposed to be aware of what's in the _BounceInfo class. The info that > is passed to it is a string representation of the _BounceInfo > instance, and it should real

Re: [Mailman-Developers] Issues with archiving directory and OS limitations

On 10/24/05 5:28 PM, "Brad Knowles" <[EMAIL PROTECTED]> wrote: > Base-64 would let you get two characters creating no more than > 4096 hash subdirectories, and you can see the numbers above for the > likely reduction in the number of grandchild subdirectories/files. Base 64 isn't a good idea for

Re: [Mailman-Developers] Mailman 2.X CVS MAIN is back

On 8/31/05 8:11 AM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > At the very least, we must drop Python 2.1 and 2.2. Neither of those > versions are being supported any longer and I will definitely not claim > to have tested the current code base on either version in a very long > time. If we mus

Re: [Mailman-Developers] Patch for Mail Archive mirroring

On 5/12/05 5:57 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: >> I would see it that way, in the "Archiving" section of admin : >> >> Archiving on a foreign system : >> --- >> >> prevent archiving on foreign systems yes [] no [x] >>

Re: [Mailman-Developers] EOL handling in Mailman

On 3/19/2005 23:43, "Sylvain Beucler" <[EMAIL PROTECTED]> wrote: > Savane uses the PHP "mail()" function, that executes the local > sendmail-compatible command. > > At both GNU Savannah (savannah.gnu.org) and Gna! (gna.org), we use the > Exim version packaged by Debian. In both cases, the mail we

Re: [Mailman-Developers] EOL handling in Mailman

On 3/19/2005 9:59, "Mark Sapiro" <[EMAIL PROTECTED]> wrote: > Sylvain Beucler wrote: >> >> I'm a Savane (gna.org/p/savane) developer, and we noticed that when we >> send mail with newlines in the \r\n format, Mailman converts them to >> \n\n. >> >> I would like to get your point on what we shoul

Re: [Mailman-Developers] Mailman 2.1.6b4

On 3/4/2005 9:37, "Nigel Metheringham" <[EMAIL PROTECTED]> wrote: > On Fri, 2005-03-04 at 12:11 -0500, Bryan Fullerton wrote: >> Is there an updated timeline for the final 2.1.6 release? It won't be >> in February... :) > > Is there a booking form for Guido's time machine? Of course it will be i

Re: [Mailman-Developers] High Availability

On 2/27/2005 17:46, "Preston Wade" <[EMAIL PROTECTED]> wrote: > Hello, > > I read some old post back in 2002 on this list about Load balancing. In my > scenario I don't have near the volume to warrant load balancing but I am > interested in fail over capabilities. Would it cause Mailman any hea

Re: [Mailman-Developers] Hashing member passwords in config.pck

On 2/12/2005 6:02, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > On Sat, 2005-02-12 at 02:07, Bob Puff wrote: > >> So let me ask this: if we drop passwords for everything but the private >> archives, do we really need to do anything differently than the format >> currently in place? Do they really

Re: [Mailman-Developers] Compatibility with Opera

On 2/11/2005 12:13, "Brad Knowles" <[EMAIL PROTECTED]> wrote: > At 6:05 PM +0200 2005-02-11, <[EMAIL PROTECTED]> wrote: > >> When I open http://mailman.greennet.org.uk/mailman/listinfo/plenary using >> Opera, the last block just above the 'subscribe' button gets spread out in >> one long strin

Re: [Mailman-Developers] Hashing member passwords in config.pck

I used to be careful about saving my passwords for all the lists [Mailman*] I am subscribed to. I no longer bother...I request the mail out of the password if I need it (very rare). If the situation becomes a choice of 1. mail out the password becomes generate a new time-limited password and mai

Re: [Mailman-Developers] [Fwd: Re: [Mailman-Announce] Mailman 2.1.6 beta 1]

On 1/21/2005 13:31, "Tokio Kikuchi" <[EMAIL PROTECTED]> wrote: > >>> think I can add some code before the 2.1.6 final release to exchage >>> Re: and prefix order for the subject prefix without numbering. (Yes, we >>> now have a nice feature to add numbering in the subject prefix.) >> >> >> Can

Re: [Mailman-Developers] What would send to bare administrator

On 1/21/2005 14:06, "Mark Sapiro" <[EMAIL PROTECTED]> wrote: > John W. Baxter wrote: >> >> A quick grep in the source didn't reveal a case where Mailman attempts to >> send mail to the unqualified recipient . Does anyone happen >> to know where i

[Mailman-Developers] What would send to bare administrator

OK, that subject might hit a filter somewhere. ;-) Mark Shapiro wrote in another thread, in mailman-users: If you haven't changed SMTP_LOG_EACH_FAILURE in mm_cfg.py, the 3 failures should be logged in Mailman's smtp-failure log. Which prompted me to look there, and find Jan 18 14:47:56 2005 (2

Re: [Mailman-Developers] [Fwd: Re: [Mailman-Announce] Mailman 2.1.6 beta 1]

On 1/21/2005 5:54, "Tokio Kikuchi" <[EMAIL PROTECTED]> wrote: > think I can add some code before the 2.1.6 final release to exchage > Re: and prefix order for the subject prefix without numbering. (Yes, we > now have a nice feature to add numbering in the subject prefix.) Can you do the same for

Re: [Mailman-Developers] [Fwd: [vendor-sec] Weak auto-generated passwords in Mailman]

On 12/21/2004 15:47, "Terri Oda" <[EMAIL PROTECTED]> wrote: > On Dec 15, 2004, at 11:37 AM, John Dennis wrote: > >> This was forwarded to me by our security officer. I believe the >> original >> author, Florian Weimer, intended to reach this list but did not know >> how >> to and instead went thr

Re: [Mailman-Developers] Maybe it's time to release 2.1.6

On 12/1/2004 6:05, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > I have no problems requiring Python 2.4 for Mailman 2.2, although I > would like to get some feedback from the community before we decide for > sure. I wouldn't be opposed to requiring at least Python 2.3, but I > definitely think we

Re: [Mailman-Developers] Dates again

On 11/24/2004 12:25, "Terri Oda" <[EMAIL PROTECTED]> wrote: > 3. Helping users sort the email in their inboxes. This can be > important to some people, since I know when we had one user posting > from 1980, many other list members weren't noticing her posts because > their mail clients put those

Re: [Mailman-Developers] Dates again

On 11/20/2004 13:26, "Kenneth Porter" <[EMAIL PROTECTED]> wrote: > --On Saturday, November 20, 2004 6:22 AM -0500 Steven Kuck <[EMAIL PROTECTED]> > wrote: > >> As I said, I can guarantee messages from the future are wrong. Disagree? >> >> Perhaps messages from more than a day (or N days) in the

Re: [Mailman-Developers] Can we remove nimda.txt ?

On 10/16/2004 14:13, "David Relson" <[EMAIL PROTECTED]> wrote: > On Sat, 16 Oct 2004 08:52:15 -0700 > John W. Baxter wrote: > > ...[snip]... > >> You might want to refer folks who want to run test "virus" messages >> through their Mai

Re: [Mailman-Developers] Can we remove nimda.txt ?

On 10/15/2004 22:52, "Tokio Kikuchi" <[EMAIL PROTECTED]> wrote: > Also, I want to ask 'nimda.txt' in the tests/msgs directory is of > any use in the mailman source code. None of the test scripts refer > to this file. I even did "find . | xargs grep nimda" only to get > "Binary file ./tests/msgs ma

Re: [Mailman-Developers] 8bit and NNTP gateway

On 9/21/2004 1:14, "Brad Knowles" <[EMAIL PROTECTED]> wrote: > At 11:24 PM -0400 2004-09-20, J C Lawrence wrote: > >> Are there any extant tools to detect 8bit mail (identified by a >> Content-Transfer-Encoding: 8bit or not) and to suitably transform the >> affected MIME parts (or base message

Re: [Mailman-Developers] Timestamps in archive are +1 hr

Version of Mailman? System on which you're running? Assuming Linux, what is the third (last) line of cat /etc/adjtime I expect either LOCAL or UTC...our Mailman machine has UTC, and--which I had never noticed--is an hour ahead on the From lines in the archive. Hmmm. Mailman 2.1.2; RedHat 9

Re: [Mailman-Developers] [Greg Stark ] Re: Bounceremoval parameters default values

On 7/1/2004 9:57, "J C Lawrence" <[EMAIL PROTECTED]> wrote: > On Thu, 1 Jul 2004 09:46:47 -0700 > somuchfun <[EMAIL PROTECTED]> wrote: > >> J.C., I agree with you that there is never a right time. BUT, when >> introducing a new feature (like mailman did with the VERP bounce >> probes) it is wise

Re: [Mailman-Developers] message filters - how to define regex string which allowes any mail address

On 3/30/2004 8:01, "lp" <[EMAIL PROTECTED]> wrote: > If anyone knows the regex string that defines "any" mail address > reagrdless of what stands before and after "@", please give me an exact > example of the string. Well, the first edition of "Mastering Regular Expressions" by Jeffrey E. F. Frie

Re: [Mailman-Developers] Virus sent to lists "from" my domain - add password for moderated users

On 3/15/2004 11:11, "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote: > and I don't have a good answer for that, not at all. not sure how to > close that hole offhand. we made it easy to figure out it IS a list, we > show an address that the virus can tell has posting privs -- and we do > no validatio

Re: [Mailman-Developers] SF.net March 2004 POTM

On 3/5/2004 19:50, "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > Hey folks, quick note. Mailman's the March 2004 SourceForge.net project > of the month. > > http://sourceforge.net/potm/potm-2004-03.php > Well done, Barry. So many deserving projects...so few months! --John ___

[Mailman-Developers] Text for the mass subscribe upload a file option.

In Mailman 2.1.1, the mass subscription page has this text under the textbox, introducing the "Choose File" button or specify a file to upload: I just talked with a not-dumb list owner who selected an Excel file, producing a wonderful list of 22 non-deletable, non-modifiable entries, which ha

Re: [Mailman-Developers] Subscriber list

On 9/13/2003 18:45, "Phil Barnett" <[EMAIL PROTECTED]> wrote: > On Saturday 06 September 2003 6:15 pm, [EMAIL PROTECTED] wrote: > >> I would like to retrieve my complete list of subscriber (i'm using mailman) >> in a text file but i don't know how to do it, can someone help me please ? >> (i've m

Re: [Mailman-Developers] Non-member post confirmation

At 22:42 +0200 8/28/2003, Brad Knowles wrote: > There is already the option "Should the list moderators get >immediate notice of new requests, as well as daily notices about >collected ones?", which I was very grateful to be able to turn off. Perhaps more useful the list admin could set peri

Re: [Mailman-Developers] Non-member post confirmation

At 10:21 -0400 8/28/2003, Barry Warsaw wrote: >> In additon to the full subscription option there could perhaps be a thread >> subscription which would subscribe the sender to only receive mails from the >> thread started by him/her. This might become somewhat heavy though. > >It's a great idea tha

Re: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders

At 11:49 +0100 1/3/2003, Fil wrote: >> SB> I've recently discovered that vacation autoresponders will >> SB> subscribe recipients to Mailman lists when they get "invited". >> >> Dang. This is because the From address contains the confirmation >> cookie encoded in the address. This might k

Re: [Mailman-Developers] more on that password crash.

At 1:05 -0500 1/2/2003, Barry A. Warsaw wrote: >(Aside: Chuq, how can we better help Apple with their Python stuff?) Sending the info along to Jack Jansen (email address widely known, but still I'd rather not stick it in here--will send privately if needed). --John -- John Baxter [EMAIL PRO

Re: [Mailman-Developers] email comparison bug?

At 23:28 -0500 1/1/2003, Barry A. Warsaw wrote: >>>>>> "JWB" == John W Baxter <[EMAIL PROTECTED]> writes: > >JWB> Since *can* be a different account than is >JWB> , I think we're stuck, even though it almost never >JWB> is.

Re: [Mailman-Developers] email comparison bug?

At 12:12 -0500 1/1/2003, Stonewall Ballard wrote: >One of my users got two notices for her two lists at one domain, instead of >one notice with two password/URLs. > >One of the lists has her address all lower case, and the other is capped >like this: [EMAIL PROTECTED] > >They're exactly the same ot

Re: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman2.1 beta5

At 1:02 -0500 11/20/2002, Phil Barnett wrote: >Sending passwords as plaintext in 2002 is downright negligent considering the >current state of sniffing, monitoring and penetration. So...we stop calling them passwords. --John -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA __

Re: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pagesHTML does not set TEXT color

At 9:37 -0500 11/8/2002, Dale Newfield wrote: >On Fri, 8 Nov 2002 [EMAIL PROTECTED] wrote: >> Admin pages HTML does not set TEXT color > >Why is it mailman's job to protect stupid users from their own browser >settings? This one sounded like it was posted not from a stupid user but from a careful

Re: [Mailman-Developers] another traceback

At 21:49 +0200 10/20/2002, Fil wrote: >(current CVS) This one is weird, I must admit -- what's the difference >betwenn re.search and re.match by the way? re.search searches the target string for a match to the regular expression. It's what one coming from Perl (and others) is used to. re.match s

Re: [Mailman-Developers] more 2.1b3++ MIME funnies.

At 17:25 -0400 10/14/2002, Barry A. Warsaw wrote: >CVR> What I'd like to be able to do (but can't) is allow M/A, >CVR> t/plain and t/html, and use the lynx to defang HTML going >CVR> into the text (but not MIME) digests. That seems the most >CVR> reasonable set of compromises to al

Re: [Mailman-Developers] Anti-spam "killer app"?

At 13:10 -0700 8/16/2002, Chuq Von Rospach wrote: >Take a look at this -- > > > >It's a new technique for identifying spam. The more I look into the details, >the more I think we have the "anti-spam killer app", becaues it tunes itself >to the individual (or si

[Mailman-Developers] Re: Opening up a few can o' worms here...

At 19:53 -0700 7/29/2002, Ka-Ping Yee wrote: >If you generate an image containing the entire e-mail address, it >can be made extremely hard to read, even with state-of-the-art OCR. It also becomes hard to read for those who don't have their browser download images. Plus you have to avoid typical

[Mailman-Developers] Re: Integrating TMDA (was Re: Cute TMDA use)

At 21:02 -0600 7/29/2002, Jason R. Mastaler wrote: >In a perfect universe, you'd have a global >whitelist containing the address of every non-spammer on the planet. In a perfect universe, there would be no spammers on the planet. ;-) --John -- John W. Baxter Port Ludlow,

Re: [Mailman-Developers] Opening up a few can o' worms here...

"Bob Puff@NLE" <[EMAIL PROTECTED]> >Not to get too far OT here but... > >I've seen the next generation of spammer software at work recently. >Spammer's machine makes direct SMTP connection to my box, gives MY address >as the FROM:, TO:, and >REPLY-TO:. This bypasses all the open relay testing, a

Re: [Mailman-Developers] Opening up a few can o' worms here...

At 17:28 -0700 7/16/2002, Chuq Von Rospach wrote: >On 7/16/02 5:35 PM, "Bob Puff@NLE" <[EMAIL PROTECTED]> wrote: > >> I've seen the next generation of spammer software at work recently. >>Spammer's >> machine makes direct SMTP connection to my box > > >Actually, the REAL state of the art is that t

Re: [Mailman-Developers] Opening up a few can o' worms here...

At 20:49 -0400 7/16/2002, Jay R. Ashworth wrote: >But *why isn't this the recipients' problem*? Because the recipient gives up, and takes her ISP payments elsewhere, or really gives up and takes them nowhere (which I'm tempted to do myself when I retire). --John -- John Baxter [EMAIL PROTEC

Re: [Mailman-Developers] Opening up a few can o' worms here...

At 17:46 -0400 7/16/2002, Barry A. Warsaw wrote: >> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: > >CVR> Problem is, many users don't know how. And one could argue >CVR> who ought to solve this problem. Should users be forced to >CVR> jump through hoops to use a mail list

Re: [Mailman-Developers] Opening up a few can o' worms here...

At 10:58 -0700 7/16/2002, Chuq Von Rospach wrote: >Are we hitting a point where mail list servers have to act as blind front >ends for all of the subscribers, where replies are processed by those >servers, and the server then takes on the job of acting as a >troll-exterminator and spam blocker? An

Re: [Mailman-Developers] OSX installation problem - no "mailman"user

At 12:37 +0100 7/12/2002, Robert Crosbie wrote: >John W Baxter hath declared on Thursday the 11 day of July 2002 :-: >> Greg Westin <[EMAIL PROTECTED]> wrote: >> >> >I sent this question to the mailman-users list and got no response, so I >> >thought ma

Re: [Mailman-Developers] OSX installation problem - no "mailman"user

Greg Westin <[EMAIL PROTECTED]> wrote: >I sent this question to the mailman-users list and got no response, so I >thought maybe I should try here. I don't know if this is a problem >because I'm a novice at these UNIX installations, or if there's >something wrong with the Darwin installer: I hav

Re: [Mailman-Developers] Another stupid question

At 23:21 -0400 5/22/2002, Jay R. Ashworth wrote: >On Wed, May 22, 2002 at 10:27:58PM -0400, Barry A. Warsaw wrote: ... >> So, you need to fix host_name (and probably web_page_url). Only the >> former can be changed on the General admin page. Both of course can >> be changed via withlist. > >Or I

Re: [Mailman-Developers] Replybot change proposed

> >> I propose that the Replybot not send responses to any message marked >> "Precedence: bulk" unless there is a corresponding "X-Ack: yes" >> header. Should that be expanded by adding "Precedence: junk" ? --John -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA

Re: [Mailman-Developers] patch for using Bouncers/Catchall.py with Python 2.2.1

At 1:00 -0400 5/10/2002, Barry A. Warsaw wrote: >>>>>> "JWB" == John W Baxter <[EMAIL PROTECTED]> writes: > >JWB> Interesting...my Python 2.2.1 on Mac OS X does include those >JWB> modules (and issues a deprecation warning upon import at t

Re: [Mailman-Developers] Another broken message

At 13:38 -0400 5/9/2002, Ron Jarrell wrote: >Ok, I got another instance (that makes 5 I've seen now) of mailman >sticking the headers into the body of the note.. > >There were extremely abbreviated headers, a blank line, a mangled header, >and then the rest of the headers in the body of the note.

Re: [Mailman-Developers] Re: [Mailman-Users] Re: Editability of messages

At 0:46 -0400 5/6/2002, Barry A. Warsaw wrote: >[about occasionally exhausting file descriptors...] > >>>>>> "JWB" == John W Baxter <[EMAIL PROTECTED]> writes: > >JWB> We haven't moved to either Mailman 2.1 or Exim 4 (on the >JWB

Re: [Mailman-Developers] Warning: nasty variant of this new virus.

At 14:35 -0700 4/23/2002, Chuq Von Rospach wrote: >I just got sent a new copy of the Klez.E virus. The text it sends to the >user is this: > >-- >Klez.E is the most common world-wide spreading worm.It's very dangerous by >corrupting your files. Ah...there's one now. It came in a text/html part,

Re: [Mailman-Developers] Re: [Mailman-Users] Re: Editability ofmessages

At 18:04 -0400 4/19/2002, Barry A. Warsaw wrote: >... >specifically, we seem to exhaust our open file limit about every 3rd >or 4th day. >... >It's disturbing and >we'll have to do something about it, although hopefully not as drastic >as reverting to Exim3. I'm just wondering if any other Exim4

Re: [Mailman-Developers] message posting in a loop with mailman2.1b1

At 16:28 -0700 4/16/2002, Marc MERLIN wrote: >I'm not saying that mailman is incorrect on the interpretation of the RFC, >I'm saying that if mailman feeds an incorrect Email address or something >that causes the MTA to reject the mail, it will endlessly spam all the >subscribers that a

Re: [Mailman-Developers] Yet another weird-a$$ potential attack problem...

At 0:37 -0500 4/5/2002, Dale Newfield wrote: >So instead of sending the token in the Subject: line of the message, >it's sent in the subject line in a mailto link. >(like so: ) > >I still use pine, and even it is able to "do the right thing"(tm) with >that..

Re: [Mailman-Developers] bin/qrunner picking up changes

At 8:19 -0500 3/29/2002, Mentor Cana wrote: >With the latest CVS, whenever list's configuration changes (i.e. new headers >or footers) a bin/mailmanctl restart is needed. > >This could confuse lists owners who expect (rightfully so) to see the >changed footers or headers on their lists as soon as

Re: [Mailman-Developers] "search for member with RE" box at topinstead of bottom

At 0:33 -0500 3/27/2002, Barry A. Warsaw wrote: >> "DM" == Dan Mick <[EMAIL PROTECTED]> writes: > >DM> I don't know why the first time I tried this, it seemed hard, >DM> but it's easy, and I like this a *lot* better: > >Hmm. Sorry, I'm not crazy about it, so I'll give it a -0 (which m

Re: [Mailman-Developers] Modifications to msg

At 18:56 -0800 3/18/2002, Dan Mick wrote: >> RFC 2822 rules on the number of specific headers a message can have. >> E.g. it can have many Received: headers, but only one Reply-To: header >> (although the latter allows for multiple addresses... go figure). > >Ease of parsing. No one but humans ty

Re: [Mailman-Developers] Headers and footers not appearing

At 10:59 + 3/10/2002, Colin Mackinlay wrote: >In news:local.mailman-d> on Sun 10 Mar, Ben Gertzfield wrote: >> > "Colin" == Colin Mackinlay <[EMAIL PROTECTED]> writes: >> >> Colin> Hi, I seem to have lost the ability to add a customised >> Colin> footer and header to messages. The

Re: [Mailman-Developers] Please Allow Me To Introduce Myself...

At 15:01 -0800 3/8/2002, James J. Besemer wrote: >However you characterize them, don't you agree they "are the future" >(which was >the main point of my sentence)? For better or worse, I detect an inexorable >trend. Trend, yes. Perhaps it's wishful thinking, but I don't think "inexorable." Cou

Re: [Mailman-Developers] big list

At 23:31 +0100 3/8/2002, Fil wrote: >Sometimes you want to try and stress things, just to give beta feedback to >Barry. I've shown a problem with computing all VERPed messages before >sending (as opposed to *while sending*), I'm quite happy with that being in >a beta (or alpha) moment before the m

Re: [Mailman-Developers] big list

At 12:15 -0500 3/8/2002, Barry A. Warsaw wrote: >It would be really cool if we could get a bunch of MTA authors >together (I only care about the open source ones ) to define a >protocol for letting the MTA doing the stitching. I think Postfix, >and probably Exim support a way to do this for the e

Re: [Mailman-Developers] Please Allow Me To Introduce Myself...

At 16:14 -0800 3/6/2002, James J. Besemer wrote: >Another faction doesn't object to HTML per se except that the text in such >messages (for them) >appear in too small a font and they can't figure out how to change it. Happens to me a lot since I read mail on my Macs, and a sensible size on a Wind

Re: [Mailman-Developers] Please Allow Me To Introduce Myself...

t;[EMAIL PROTECTED]> X-Mailer: Apple Mail (2.481) X-olympus-virus-scan: Encoding found - scanned Testing style (or misuse thereof) -- John W. BaxterPort Ludlow, WA, USA The primary cause of problems is solutions. -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA

Re: [Mailman-Developers] Protecting email addresses from spamharvesters

At 10:55 -0800 2/27/2002, Dan Mick wrote: >"wrong" was misstated; what I meant to say was "the user is not >part of Mailman". But the user is part of the mailing list system. Usually the most troublesome part. --John -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA ___

Re: [Mailman-Developers] Protecting email addresses from spam harvesters

>I find it very rare that anybody actually responds to postmaster@ >addressed email. I suspect that for most sites, nobody reads them. Hmmm...could that be why other admins seem surprised when I answer? ;-) --John -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA ___

Re: [Mailman-Developers] Protecting email addresses from spamharvesters

At 12:36 -0500 2/26/2002, Jay R. Ashworth wrote: >*I* think that postmaster@ the mailing list machine (or domain) is a >good enough answer, but I think Chuq will accuse me of geeking out >again, and on this one, I'm afraid I'd agree with him. > >The number of people on the net with *no* indoctrina

RE: [Mailman-Developers] Interesting study -- spam on postedaddresses...

At 12:15 -0500 2/21/2002, Dale Newfield wrote: >The two I marked with () above are not obfuscation schemes. >They involve not the obfuscation of information, but rather it's removal. Oh, good...another debating point. Is removal the limiting case of obfuscation, or something different in kin

  1   2   >