Re: [Mailman-Users] Mailman list sends but doesn't receive mail.

[JRC Groups]

Larry,


Thank you for your helpful reply.

Although not enthusiastic about it I have decided to follow your advice as
well as Mark's and just install a new version of Mailman. I was trying to
save myself sometime but considering the explanations both of you have
provided I believe it is better to just face the extra work and avoid
Apple's version.

Now that I now I can simply install it on a new directory that will not
conflict with the existing version things should be much simpler.

Thank you again for your reply and help with this issue.

Best regards,


Joe


On 4/18/11 4:28 AM, "Larry Stone"  wrote:

> On 4/18/11 1:53 AM, JRC Groups at joemailgro...@gmail.com wrote:
> 
> 
>> I have read the page and also contacted Larry Stone. His instructions are
>> for installation on OS X client and not OS X Server. I haven't found
>> instructions on how to remove the Mailman version bundled by Apple with OS X
>> Server. One of my concerns is that Apple's version and the downloaded
>> version would both have several (if not all) files installed as default in
>> the same location and this could lead to potential conflicts.
> 
> With some more thought than my quick private reply to you last night, I
> don't think this is an issue. IIRC, you choose where to install Mailman and
> I believe it is self-contained in that directory. My latest instructions
> (for Snow Leopard) suggest /usr/local/mailman but previous versions
> suggested /Applications/mailman (and if you wanted to, you could call it
> something like 
> /usr/local/my_private_copy_of_mailman_which_does_not_conflict_with_Apples
> which is inelegant but would work and I'm pretty sure really does not
> conflict :-) ). So long as the directory you pick does not exist, then you
> will not be at risk of a conflict. You would, of course, have to change that
> name throughout my instructions but that is trivial.
> 
> The instructions do call for modifying some configuration files of other
> software (Postfix and Apache) but those files are intended to be
> user-modifiable and Apple provided updates should not be overriding your
> mofications.


--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Upgrading and converting mailman to postfix

[Mark Sapiro]

On 4/20/11 7:59 PM, Steven Jones wrote:
> Hi,
> 
> I have to upgrade a old mailman setup on RHEl3 and sendmail to RHEL6
> which comes with postfix by default...
> 
> So,
> 
> a) Docs or how easy is it to straight migrate from RHEL3 (2.1.5) to
> RHEL6  (2.1.12) ?


This is a RedHat packaging question. See the FAQ at
. If your RedHat package is 2.1.5-21 or
later, it should be no problem. If it is 2.1.5-20 or earlier, many files
and directories move as discussed in the FAQ, but the FAQ also tells you
where to find a migration script and RedHat's documentation.


> b) How easy is it to convert a sendmail setup with /etc/aliases to
> postfix?  any automated scripts?


No conversion is required. Postfix can use the same Mailman aliases as
Sendmail in /etc/aliases except that the path to the wrapper may change
from /var/mailman/mail/mailman to /usr/lib/mailman/mail/mailman because
of the file changes above.

On the other hand, the new package may make various changes in both
postfix and Mailman to enable Mailman/Postfix integration, in which case
all you'd need to do after migration is to remove Mailman's aliases from
/etc/aliases and run Mailman's bin/genaliases to generate the new aliases.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, CaliforniaBetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Upgrading and converting mailman to postfix

[Brad Knowles]

On Apr 20, 2011, at 9:59 PM, Steven Jones wrote:

> a) Docs or how easy is it to straight migrate from RHEL3 (2.1.5) to RHEL6  
> (2.1.12) ?

What does Red Hat tell you about migrating from sendmail to postfix with RHEL3 
-> RHEL6?  In my experience, postfix goes pretty far out of its way to be as 
much of a drop-in replacement for sendmail as can reasonably be done.

But that's in a more typical Unix type of environment where you're building 
tools from source, or using a BSD-style "ports" system.  I can't speak for how 
that would work in a more regimented binary-only RPM package environment.

> b) How easy is it to convert a sendmail setup with /etc/aliases to postfix?  
> any automated scripts?

My experience has been that postfix is the most natural MTA to pair with 
Mailman, and I've been involved in the postfix community since the very 
earliest days back when Wietse was still calling it VMailer.  We've been using 
postfix with Mailman on python.org at least as long as I've been involved in 
the Mailman project -- and we're talking multiple years in both cases.

By default, postfix includes some standard tools for taking the same sorts of 
source files and turning them into a postfix-native binary format (by replacing 
the "newaliases" command, among other things).

However, I don't know how Red Hat chooses to modify that situation when they 
build a postfix package for their platform.  You'd have to ask them where their 
tools are and how those tools change from one version of RHEL to another.

--
Brad Knowles 
LinkedIn Profile: 

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Upgrading and converting mailman to postfix

[Steven Jones]

Hi,

I have to upgrade a old mailman setup on RHEl3 and sendmail to RHEL6 which 
comes with postfix by default...

So,  

a) Docs or how easy is it to straight migrate from RHEL3 (2.1.5) to RHEL6  
(2.1.12) ?

b) How easy is it to convert a sendmail setup with /etc/aliases to postfix?  
any automated scripts?

regards

Steven

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Approved header, mailman password and security

[Mark Sapiro]

Dag Wieers wrote:

>On Thu, 14 Apr 2011, Dag Wieers wrote:
>
>> We have been using the Approved header as a way to automatically approve 
>> commit logs to a read-only mailinglist. We recently moved our infrastructure 
>> to github and I wrote a patch to the github Email service hook to add an 
>> Approved header.
>>
>>https://github.com/github/github-services/pull/84
>>
>> Now the problem of course is that this secret currently is either the list 
>> admin or the list moderator password, which is far from secure. Especially 
>> if 
>> the mails are not created on the mailman list server.
>>
>> So I would propose to allow to set a separate secret used for approved 
>> messages. If compromised, it's easy to change that secret on both sides.
>>
>> Is this acceptable ?
>
>I received no feedback on this. Shall I open a ticket for this, or is this 
>not considered valuable ?


Sorry for not responding sooner. I do think it is a good idea. Although
many lists do not need separate admins and moderators and could thus
use the moderator password in this way, I think a separate 'posters'
password would be a valuable change.

The problem is Mailman 2.1 is supposed to be feature frozen, and this
is a rather extensive change involving the web GUI to set the
password, and list migration changes to ensure that list objects have
the poster password attribute. We can certainly consider this for MM3.

Please open a tracker item at
, and I'll see what I can
do.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Approved header, mailman password and security

[Dag Wieers]

On Thu, 14 Apr 2011, Dag Wieers wrote:

We have been using the Approved header as a way to automatically approve 
commit logs to a read-only mailinglist. We recently moved our infrastructure 
to github and I wrote a patch to the github Email service hook to add an 
Approved header.


   https://github.com/github/github-services/pull/84

Now the problem of course is that this secret currently is either the list 
admin or the list moderator password, which is far from secure. Especially if 
the mails are not created on the mailman list server.


So I would propose to allow to set a separate secret used for approved 
messages. If compromised, it's easy to change that secret on both sides.


Is this acceptable ?


I received no feedback on this. Shall I open a ticket for this, or is this 
not considered valuable ?


--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, i...@dagit.net, http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org