very helpful for
multi-server setups.
Cheers,
Hans-Martin
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.
ontainer communication really
internal.
We're currently working on moving our mail system over to a "mailu" dockerized
implementation, so I will gather some
experience in connecting Mailman3 with a dockerized postfix.
Cheers,
Hans-Martin
___
hen I have time.
Cheers,
Hans-Martin
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman
a socketmap service to Mailman that Postfix can
query to get map information. Since this
idea is probably not totally original I'd like to ask on this list whether
someone already tried such a thing, and what
their experiences were.
Cheers,
Hans-Martin
__
- Original Message -
> From: "Stephen J. Turnbull"
> To: "Franck Martin"
> Cc: "Barry Warsaw" , "mailman-developers"
>
> Sent: Monday, August 22, 2016 9:06:31 PM
> Subject: Re: [Mailman-Developers] Remediation for fake member
- Original Message -
> From: "Barry Warsaw"
> To: "mailman-developers"
> Sent: Monday, August 22, 2016 2:43:06 PM
> Subject: Re: [Mailman-Developers] Remediation for fake member creation
> On Aug 22, 2016, at 01:03 PM, Franck Martin wrote:
>
&
I'm not sure if you have seen the following blog posts:
https://wordtothewise.com/2016/08/subscription-bombing-esps-spamhaus/
https://wordtothewise.com/2016/08/spamhaus-comments-on-subscription-attack/
https://wordtothewise.com/2016/08/ongoing-subscription-attack/
While mailman does double op
You can also apply this patch:
http://bazaar.launchpad.net/~mlm-author/mailman/2.1-author/revision/1341?remember=1338&compare_revid=1338
Rather than injecting an invalid domain in the From: and weakening more the
security of email...
___
Mailman-Deve
You are really mixing everything...
Toute connaissance est une réponse à une question.
> On May 16, 2014, at 20:09, "John Levine" wrote:
>
> In article <1856298671.144791.1400292991012.javamail.zim...@peachymango.org>
> you write:
>> The trouble with .invalid is that it is a domain that do not
Upgrade to 2.1.18
Toute connaissance est une réponse à une question.
> On May 16, 2014, at 20:43, "Bob Puff" wrote:
>
> So guys... Is there a simple little hack we can do within MM 2.1 to try to
> mitigate this issue, by adding .invalid or some other extension? I've got a
> few lists that are
The trouble with .invalid is that it is a domain that do not accept emails.
Therefore why should you accept emails from a domain that does not allow you to
reply to it?
It is bound in the future to create issues when people move to more
serious/ubiquitous domain reputation schemes.
- Original Message -
> From: "Jim Popovitch"
> To: "Franck Martin"
> Cc: Mailman-Developers@python.org
> Sent: Thursday, November 7, 2013 4:59:38 PM
> Subject: Re: [Mailman-Developers] Mailman DMARC Support (it's not what you
> think!)
- Original Message -
> From: "Jim Popovitch"
> To: Mailman-Developers@python.org
> Sent: Thursday, November 7, 2013 11:49:30 AM
> Subject: Re: [Mailman-Developers] Mailman DMARC Support (it's not what you
> think!)
>
> On Thu, Nov 7, 2013 at 1:27
Yes this is one of the other options to do. The last one is to do Original
Authentication Header, but transitive trust on email is complicated.
To be noted, the procedure, in this patch, to find the policy record in the
DNS, is not in line with the best current practice specified in the DMARC sp
- Original Message -
> From: "Andreas Schulze"
> To: mailman-developers@python.org
> Sent: Wednesday, November 6, 2013 11:28:42 PM
> Subject: Re: [Mailman-Developers] Mailman DMARC Support (it's not what you
> think!)
>
>
> Zitat von Jim Popovitch :
>
> > ... that mailing lists, li
On Sep 17, 2013, at 10:36 PM, Mark Sapiro wrote:
> On 09/17/2013 10:04 PM, Franck Martin wrote:
>>
>> 1) If you keep the From: header as it is then, we will still have the same
>> problems
>
>
> Perhaps I wasn't clear. The From: of the outer message wo
On Sep 17, 2013, at 6:21 PM, Mark Sapiro wrote:
> On 09/17/2013 05:28 PM, Barry Warsaw wrote:
>> On Sep 15, 2013, at 08:24 AM, Mark Sapiro wrote:
>>
>>> Because the issue remains controversial, I will soon release 2.1.16
>>> final with the feature disabled by default, and will consider the
>>>
in a mime rfc822. This
seems an interesting and good alternative. I'd like to see it in practice so we
can compare data.
On Sep 14, 2013, at 1:27 AM, Stephen J. Turnbull wrote:
> Franck Martin writes:
>
>> One may argue that since the list is modifying the message, it is
>
On Sep 14, 2013, at 5:16 PM, Stephen J. Turnbull wrote:
> Franck Martin writes:
>
>> Unfortunately z= and especially l= are not used practically by
>> senders because they create a risk. One could add an attachment
>> containing malware to the message for instance.
On Sep 13, 2013, at 7:48 PM, Mark Sapiro wrote:
> On 09/13/2013 12:18 PM, Franck Martin wrote:
>>
>> Mailman breaks DKIM as soon as you add a footer or tag in the subject line,
>> which a lot of lists do (including this one).
>
>
> Not necessarily. It depends
admin consent and action.
On Sep 13, 2013, at 12:13 PM, Stephen J. Turnbull wrote:
> Franck Martin writes:
>
>> In the upcoming mailman 2.1.16 there has been the introduction of
>> the optional feature author_is_list
>>
>> "Replace the sender
>
> Bef
- Original Message -
> From: "Mark Sapiro"
> To: mailman-developers@python.org
> Sent: Friday, September 13, 2013 11:31:44 AM
> Subject: Re: [Mailman-Developers] Author_is_list option in upcoming mailman
> 2.1.16
>
> On 09/13/2013 08:06 AM, Barry Warsaw wrote:
> >
> > I will leave it t
On Sep 12, 2013, at 11:30 PM, SM wrote:
> Hi Franck,
> At 22:44 12-09-2013, Franck Martin wrote:
>> In the upcoming mailman 2.1.16 there has been the introduction of the
>> optional feature author_is_list
>>
>> "Replace the sender with the list address
In the upcoming mailman 2.1.16 there has been the introduction of the optional
feature author_is_list
"Replace the sender with the list address to conform with policies like ADSP
and DMARC. It replaces the poster's address in the From: header with the list
address and adds the poster to the Rep
We are not asking mailman to do the work of DMARC here. There is openDMARC for
that.
On Jul 10, 2013, at 11:23 AM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
>> For #1 you would have a rule that can answer the question of DMARC
>> disposition. Rules output binary results,
>
> This i
On Jul 9, 2013, at 8:19 PM, Barry Warsaw wrote:
> On Jul 06, 2013, at 11:02 PM, Murray S. Kucherawy wrote:
>
>>
>> (a) the second bullet above is a significant departure from current use (as
>> I understand it), and fails the test of least surprise if we were going to
>> suddenly see that MM3
On Jul 9, 2013, at 8:15 PM, Barry Warsaw wrote:
> On Jul 02, 2013, at 12:44 AM, Patrick Ben Koetter wrote:
>
>> Before we take out to write code, I would like to ask mailman-developers how
>> it should be done to fit best into Mailman's architecture. Here are the DMARC
>> features that should g
- Original Message -
> From: "Mark Sapiro"
> To: "Franck Martin"
> Sent: Monday, July 8, 2013 10:37:01 AM
> Subject: Re: [Mailman-Developers] Adding DMARC support for Mailman 3
>
> On 07/08/2013 08:34 AM, Franck Martin wrote:
> >
> &g
- Original Message -
> From: "Murray S. Kucherawy"
> To: "Franck Martin"
> Cc: "Stephen J. Turnbull" , "Mailman Developers"
>
> Sent: Monday, July 8, 2013 6:57:03 AM
> Subject: Re: [Mailman-Developers] Adding DMARC support for M
- Original Message -
> From: "Stephen J. Turnbull"
> To: "Franck Martin"
> Cc: "Mailman Developers"
> Sent: Monday, July 8, 2013 2:01:43 AM
> Subject: Re: [Mailman-Developers] Adding DMARC support for Mailman 3
>
> Franck Marti
Yes, these are options and they should be off. It is important when you
introduce options, you do not change past behavior automatically.
1) may not be necessary, if mailman recognizes the bounce message as in section
http://tools.ietf.org/html/draft-kucherawy-dmarc-base-00#section-15.8
eg "550
much excitement in email for a long time.
Franck Martin
https://www.linkedin.com/in/franckmartin
- Original Message -
From: "Patrick Ben Koetter"
To: "Mailman Developers"
Sent: Monday, July 1, 2013 3:44:15 PM
Subject: [Mailman-Developers] Adding DMARC support for Mai
Unfortunately, I did not have time to look at porting the optional authorship
settings from the branch I did on mailman 2.1 to 3.0. I suppose this is too
late to make the 3.0 deadline, but from what I saw of the 3.0 code, this does
not seem a complicated change.
How can I register a bug, so tha
> * Franck Martin :
>> As I have not received feedback.. then no feedback is good feedback right?
>>
>> I submitted the code to be merged into main branch (using launchpad
>> interface). It is 2.1.x branch and I know the development happens on 3.x,
>> but let me
base in a view to
submit a similar patch.
Thanks.
- Original Message -
From: "Franck Martin"
To: "mailman-developers"
Sent: Tuesday, July 10, 2012 9:45:28 PM
Subject: [Mailman-Developers] mailing list to work with ADSP and DMARC
I did a branch on the 2.1 series to tes
I did a branch on the 2.1 series to test rewriting the From: header to be able
to make emails to comply with DMARC and ADSP
You can find the branch here:
https://code.launchpad.net/~mlm-author/mailman/2.1-author
and the diff with mailman main branch here:
http://bazaar.launchpad.net/~mlm-au
It's great to see this happening.
Do you have a clear idea and/or wireframes for the layouts of the pages?
If not, I'd be happy to help mock-up a default "skin" that looks nice
and easy to use.
--
Martin
___
Mailman-Develope
too negative. I am always in
favour of better and more user friendly spam filters. But there are
quite a lot of spam-related patches already and any new approach should
be clearly better than the already existing hooks and functions.
Otherwise it is just a waste of time which should
> "st" == Stephen J Turnbull
> "Re: [Mailman-Developers] Improving the archives"
> Tue, 24 Jul 2007 15:56:35 +0900
st> Jeff Breidenbach writes:
>> > Notice that of 325146 total messages, 624 of them had no
>> > message-id header. Even if you aggregate dup+col, you're
> "st" == Stephen J Turnbull
> "Re: [Mailman-Developers] Improving the archives"
> Wed, 04 Jul 2007 16:49:58 +0900
st> The main drawback to using Message IDs that I can see is that
st> broken MUAs may supply no Message-ID, or the same one
st> repeatedly. In the former cas
name on subscription is optional.
Thus IMHO showing real names does not disclose significant information,
but makes things more convenient for legitimate users.
I have attached a three-line patch against Mailman/HTMLFormatter.py
--
Martin Schütte
96a97,99
> realname = Utils.uncanon
> "baw" == Barry Warsaw
> "Re: [Mailman-Developers] LTMP for incoming mail"
> Thu, 28 Sep 2006 14:40:51 -0400
baw> I think John was asking about using virtual_mailbox_maps with
baw> delivery to mbox, but I think that's worse, because mbox
baw> delivery forces you to implem
> "Brad" == Brad Knowles
> "Re: [Mailman-Developers] LTMP for incoming mail"
> Thu, 28 Sep 2006 11:06:29 -0500
Brad> Maildir was not designed as an efficient queue-on-disk
Brad> strategy.
Is in not possible to do Postfix virtual mailbox domains _without_
maildir style delive
ctionality being requested on the 'wishlist', so I assume that it has yet
>to be implemented.
>
>
It's already mostly there: The command "list_owners -m" prints all
owners and moderators of all mailing lists on your machine.
Gett
ll cause in double work maintaining two areas of MM and
as I am not that much into coding, but I think this would be pretty.
Upgrading should mean to install the "Technology Preview for MM3" ;-)
bis dahin/kind regards
Martin Mewes
--
You are receiving this automatic
"MitgliedsbestÃtigung" in the second
place?
Sorry if not all english readers can follow this ;-)
bis dahin/kind regards
Martin Mewes
--
I am on holiday. Your e-mail has been deleted.
___
Mailman-Developers mailing list
Mailman
things easier for me to read and understand the
background here instead of browsing the searchable archive online.
Sorry for any inconvinience if any ...
bis dahin/kind regards
Martin Mewes
--
Hi. I'm thinking about what you've just sent me. Please wait by your
PC for m
ds logical from a performance point of view.
Hm, I tried to find some design documention/overview on the list.org
site, but I couldn't find anything, could somebody give me a hint
about this?
Thanks again,
cu Martin
--
dont.wanna.tell
[ot]coder - hehe
___
d sounded like not every mail (to a user) is processed on its own
but instead many of them are built and send as one mail?
That would go aginst my understanding, but hey... :)
cu Martin
--
dont.wanna.tell
[ot]coder - hehe
___
Mailman-Develo
At 13:13 Uhr -0400 08.05.2004, Terri Oda wrote:
On May 8, 2004, at 9:23 AM, Martin Häcker wrote:
I want to create an option that allows my users
to have the mailinglist set a reply-to header
to itself in their e-mails.
Could you please give me some advice about where to start implement this
I will need to add the
preference in MemberAdoptor.py and some of it's subclasses (which?)
and then change Decorator.py to write the Reply-To if the user
whiches for it.
Would this be the right way to do it? And is there any other place I
need to change to make this work?
Thanks a lot
cu Martin
-
> "Brad" == Brad Knowles
> "Re: (Fwd) Re: [Mailman-Users] Re: How to rem"
> Mon, 5 Apr 2004 00:08:34 +0200
Brad> Okay, so a Keep-These-Headers option being restricted
Brad> to just the following:
Brad> From:
Brad> Subject:
two whitelists for sender and receiver for
each list, which cause approval without moderation checks.
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
invalid/expired pgp subkeys? use
Hi,
I found quite annoying and bad to generate full URL's in the generated
webpages. For example, https://some.host/mailman/listinfo has a link to
http://some.host/mailman/listinfo/admin . That's bad! I want to use
only relative URL's of course!!! Could someone tell me where to edit the
scripts o
> "baw" == Barry Warsaw
> "RE: [Mailman-Developers] Adding headers to mailman generated mails"
> Thu, 22 Jan 2004 17:50:33 -0500
baw> I don't think Postfix has the same embedding capabilities,
baw> although I haven't looked at what Postfix 2.1 may provide.
Hmm... dunno, but p
non-standard maybe:
Web server ("hubble") is Redhat9
Mail server ("hypatia") is Solaris 8 -- mailman installed on both
Many thanks for mailman,
and for your consideration of this report.
Martin Maechler <[EMAIL PROTECTED]> http://stat.ethz.ch/~maechler/
Seminar fuer St
place (web server).
Thanks a lot for your help, and for mailman in general
(and do apologize for having disturbed you!)
BTW: It seems 2.1.4 did catch much more bounce messages than 2.1.3:
In about 10 hours, I didn't have one of the "Uncaught bounce notification"
messages
8;
Web server (apache) on Linux Redhat 9.
This had worked fine with Mailman 2.1.3.
to which we had to revert ASAP.
We got the following in a browser window.
Do you have any ideas what could have gone wrong?
Regards,
Martin Maechler <[EMAIL PROTECTED]> http://stat.ethz.ch/~ma
el free to contact me in
private.
Cheers,
Martin.
--
[EMAIL PROTECTED] - +1 416 832 7759
Melbourne Business School FT 2004 MBA Exchange Participant to Rotman
=-Original Message-
=From: J. Nick Koston [mailto:[EMAIL PROTECTED]
=Sent: November 15, 2003 10:47 PM
=To: [EMAIL PROTECTED]
=
Nick,
Has Cpanel documented the changes they have made to Mailman? If not, can
Cpanel supply the Mailman dev team with the scripts they use to mould it to
fit?
Cheers,
Martin.
--
[EMAIL PROTECTED] - +1 416 832 7759
Melbourne Business School FT 2004 MBA Exchange Participant to Rotman
>>>>> "J" == J C Lawrence <[EMAIL PROTECTED]>
>>>>> on Tue, 11 Nov 2003 09:05:45 -0500 writes:
J> On Tue, 11 Nov 2003 10:52:07 +0100
J> Martin Maechler <[EMAIL PROTECTED]> wrote:
>> My problem is that I get abou
Nick / Barry
Can you please at least acknowledge whether this is a known problem?
Many Thanks,
Martin.
--
[EMAIL PROTECTED] - +1 416 832 7759
Melbourne Business School FT 2004 MBA Exchange Participant to Rotman
=-Original Message-
=From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED
many (like the following) very it seems very easy to do
both (recognize bounce format and extract member address; in the
attached example, [EMAIL PROTECTED] is clearly
subscribed to the mailing list "r-help").
Regards,
Martin Maechler <[EMAIL PROTECTED]> http://stat.ethz.ch/~maec
e's my postings to the cpanel site:
* http://forums.cpanel.net/showthread.php?s=&threadid=15928
And I am not alone:
* http://forums.cpanel.net/showthread.php?s=&threadid=13383
Can you please advise?
Thanks,
Martin.
--
[EMAIL PROTECTED] - +1 416 832 7759
Melbourne Business
ld address if we had the correct
communication in place.
Thanks,
Martin
--
[EMAIL PROTECTED] - +1 416 832 7759
Melbourne Business School FT 2004 MBA Exchange Participant to Rotman
=-Original Message-
=From:
[EMAIL PROTECTED]
=[mailto:[EMAIL PROTECTED]
=org] On Behalf Of Jon Ca
> "claw" == J C Lawrence
> "Re: [Mailman-Developers] Requirements for a new archiver "
> Wed, 29 Oct 2003 21:22:32 -0500
claw> I may be unusual in this regard, but I generally consider
claw> list archives as one-way systems: messages go in and never
claw> come out.
Out of
Brad Knowles <[EMAIL PROTECTED]> writes:
> At 3:06 PM -0500 2003/10/27, Kevin McCann wrote:
>
>> I was thinking about using MHonarc to enhance the archive experience but
>> it doesn't work with MySQL directly so Mail::Box just might be what the
>> doctor ordered.
>
> No database handles "
> "Iain" == Iain Bapty
> "[Mailman-Developers] Requirements for a new archiver"
> Mon, 27 Oct 2003 12:00:57 +
Iain> Functional Requirements The archive component should
Iain> 1. store email discussions.
Iain> 2. integrate with Mailman.
Iain> 3. provide a web-based
> "claw" == J C Lawrence
> "Re: [Mailman-Developers] Requirements for a new archiver "
> Tue, 28 Oct 2003 13:30:23 -0500
claw> 1) We guarantee uniqueness of all Message IDs. The only way
claw> to do this is to rewrite all IDs. This will piss off some
claw> people.
L
> "Harald" == Harald Meland
> "Re: [Mailman-Developers] "@" in mail **text** gets replaced inarchives"
> Sun, 28 Sep 2003 22:09:09 +0200
>>> "baw" == Barry Warsaw "Re: [Mailman-Developers] "@" in
>>> mail **text** gets replaced inarchives" Sun, 28 Sep 2003
>>>
> "baw" == Barry Warsaw
> "Re: [Mailman-Developers] "@" in mail **text** gets replaced inarchives"
> Sun, 28 Sep 2003 09:45:32 -0400
baw> On Sun, 2003-09-28 at 05:13, Harald Meland wrote:
>> [Barry Warsaw]
>>
>> > I really really want to use something like message-ids
t MHonarc's
multiple-encoding techniques are much behind pipermail's.
Regards,
Martin
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
> "Greg" == Greg Stark
> "Re: [Mailman-Developers] Re: Bounce removal parameters default values"
> 26 Sep 2003 12:45:46 -0400
Greg> Barry Warsaw <[EMAIL PROTECTED]> writes:
Greg> Causing valid bounces to be sent to the envelope sender
Is required by the standards.
G
ch back to keep e-mail addresses unaltered.
which caters to the spammers address-collection robots...
Of course that's a bug in mailman/pipermail
===> forwarding to the developers.
Martin Maechler <[EMAIL PROTECTED]> http://stat.ethz.ch/~maechler/
Seminar fuer Statist
> "baw" == Barry Warsaw
> "Re: [Mailman-Developers] Mailman 2.1.2 doesn't work with postfix-style virtual
> domains + patch"
> 13 Sep 2003 18:43:42 -0400
baw> On Mon, 2003-09-08 at 05:46, Steve Alexander wrote:
>> Mailman 2.1.2 writes out a "sendmail-style" virtual-mailma
Mail to a list with a hyphen in its name languishes forever in
qfiles/maildir. The culprit might be in MaildirRunner.py
,[ MaildirRunner.py lines 65-74 ]
# We only care about the listname and the subq as in listname@ or
# listname-request@
lre = re.compile(r"""
^# s
> "baw" == Barry Warsaw
> "Re: [Mailman-Developers] Problem with MM after power outage"
> 12 Sep 2003 12:35:32 -0400
baw> On Fri, 2003-09-12 at 12:28, Brad Knowles wrote:
>> I would suggest making this flag visible on certain OSes. For
>> example, turned off by default bu
gaard BSA)
5. Re: potentially nasty interaction between R 1.8.0 and tetex
(A.J. Rossini)
6. rank(*) with NAs -- new option "keep" desired (Martin Maechler)
7. Re: potentially nasty interaction between R 1.8.0 and tetex
([EMAIL PROTECTED])
8. Re: potentially nas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> "baw" == Barry Warsaw
> "Re: [Mailman-Developers] script"
> 05 Sep 2003 08:08:41 -0400
baw> Take a look in cvs. There's a script called bin/discard
baw> which takes a list of file names and does proper discards on
baw> all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What defenses does Mailman have against suicide mail-bomber attacks?
The suicide mail-bomber has a number of list-owner addresses for which
the receiving MTAs take delivery and subsequently send a "Mail
Delivery Warning" mail message back to the list
Log entries like the following appear with some regularity.
,[ Excerpt from /var/log/apache-ssl ]
[Fri Aug 1 15:54:12 2003] [error] [client 128.242.232.130] attempt to
invoke directory as script: /usr/lib/cgi-bin/mailman
`
I've poked around a bit but haven't seen how to tickle the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have submitted a bug asking for the Invitation and subscription
Confirmation messages to contain information indicating when they
expire. Folks seem to be confused when they return a stale response.
jam
-BEGIN PGP SIGNATURE-
iD8DB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>>>>> "Tom" == Tom Neff
>>>>> "[Mailman-Developers] Re: Cutting "Received:" headers (John A. Martin)"
>>>>> Wed, 11 Jun 2003 12:57:09 -0400
Tom> [EMAIL PROTECTED] (J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> "Roman" == Roman Sinelnikov
> "[Mailman-Developers] Cutting "Received:" headers"
> Wed, 11 Jun 2003 14:50:22 +0400
Roman> Dear colleagues, one more idea, it would be very convenient
Roman> to have an optional cutting of "Receive
{Mailman 2.1.1}
I hope this continues to help improving the already good mailman
software!
Martin
--- Begin Message ---
The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it. This mailing list has been
Dear developers,
thank you very much for an already fantastic product!
I hope the following is helpful for improving this part of
mailman...
Martin Maechler <[EMAIL PROTECTED]> http://stat.ethz.ch/~maechler/
Seminar fuer Statistik, ETH-Zentrum LEO C16Leonhardstr. 27
ETH (Federa
follows -
... while talking to akasolvr.vub.ac.be.:
>>> RCPT To:<[EMAIL PROTECTED]>
<<< 553 <[EMAIL PROTECTED]>... User mathie.roelants unknown at vub.ac.be
550 <[EMAIL PROTECTED]>... User unknown
- Message header follows -
Thanks a lot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> "BryanW" == Bryan Fullerton
> "[Mailman-Developers] list.org DNS fubar?"
> Fri, 14 Mar 2003 06:19:40 -0500
BryanW> I tried direct queries to all the listed name servers,
BryanW> none are returning A records for list.org.
Useful
/1.5.3i ...)
Mutt is compliant.
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
___
blem reports about the mailing list to %s"
Ideally this text might be a per-site customization, rather than
hardcoded in Mailman/Cgi/listinfo.py. I have fixed it there for the
time being.
--
Martin
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
terface.
Cheers
--
Martin
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
terface.
Cheers
--
Martin
please cc me on replies
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message
Please consider an option suppressing the advertisement of Mailman
version. In spite of the possibility that the advertisement may ease
troubleshooting there are those who believe that the running
email addresses or distinguished names
as attributes.
It is available at http://webserver.offal.homelinux.org/
If you're running mailman and have an LDAP service, please try this and
tell me what you think. Or how it broke.
Martin Whinnery
[EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> "BAW" == Barry A Warsaw
> "Re: [Mailman-Developers] Sourceforge notifications considered harmful"
> Thu, 16 Jan 2003 00:12:07 -0500
BAW> So vote by the -1/0/+1 rules against these options:
BAW> 1. Do nothing, everything's fine
Folks,
I'm quietly beavering away at LDAP support using the extend.py /
MemberAdaptor route.
It's going ok, but I'm unsure as to where I ought to be putting things.
As Greg has pointed out, It's not a good idea to mess with the
distribution code. So where ought stuff to go?
I illustrate:
I hav
ant to handle the interface between LDAP and mailman lists, or
on my coding. I am using this in a purely test environment at the
moment. As soon as MM 2.1 gets to be stable, I'll be using this or
something better at work, for real.
So I suppose this is a call for help. Either help me get my code
0.html
I would suggest that pipermail looks for a text-plain part in the
message, and tries to render that into HTML, ignoring all other parts.
Regards,
Martin
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/lis
On Wed, 30 Oct 2002, Greg Ward wrote:
> On 30 October 2002, Martin Whinnery said:
> > Please indulge a python virgin. Barry has advised someone to 'overload
> > the Load & Save function' in extend.py . Would someone help me with a
> > little sample? It doesn
er|discard] thing. And
archives. And it deals with 'real' mailing lists (which we would die
rather than lose).
Martin Whinnery
*Assistant* Network Manager
South Birmingham College
'Just the assistant'
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
1 - 100 of 105 matches
Mail list logo
