Dave Bevis wrote:
>Is there a script out there or a mailman command that will let me
>change the domain part of all email addresses to a different domain
>in all lists? i.e. pers...@companya.com changes to
>pers...@companyb.com, pers...@companya.com changes to
>pers...@companyb.com, etc. i
Yeray Gutiérrez Cedrés wrote:
>I'm new to Mailman and I wonder if there is a proper way to
>automatically add the addresses created in the virtual-mailman file
>(when a new list is created) to a list for the check_sender_access
>postfix restriction. For example, if I create the list "mailmantest",
Mark Sapiro wrote:
>Ulf Hofemeier wrote:
>>
>>PS. if you email me, I can provide you with the URL to my MM installation.
>
>
>If you send it to me, I'll check it out.
After a little off list back and forth, Ulf wrote:
>I had no site admin password set. Setting one with mmsitepass did the
>tri
Mark,
Logout won't remove the cookie if there is one, but I doubt there is.
ALLOW_SITE_ADMIN_COOKIES is set to NO. I compiled MM 2.1.12 from the
source.
Ulf
--
Ulf Hofemeier
Programmer / Analyst II
Latin American and Iberian Institute
u...@ladb.unm.edu
On Aug 26, 2009, at 5:15 PM, Mark
an...@iguanait.com wrote:
>
>we have installed mailman-2.1.9-4.el5 on Centos 5.
>
>What i notice is that when i subscribe or when i receive a message from
>the mailing list all messages are send from
>listname-bou...@myhostname.tld.
>
>Why this happen? Should it send messages using aliases defined
Ulf Hofemeier wrote:
>
>I'm using MM 2.1.12 and am running into a problem that is rather nasty.
>In my case the MM admin interface is wide open, which means that I don't
>need a site admin pwd to access http://mydomain/mailman/admin/mylist. I
>can click on logout and it will take me to the logout p
Is there a script out there or a mailman command that will let me
change the domain part of all email addresses to a different domain
in all lists? i.e. pers...@companya.com changes to
pers...@companyb.com, pers...@companya.com changes to
pers...@companyb.com, etc. in all lists and makes th
I'm new to Mailman and I wonder if there is a proper way to
automatically add the addresses created in the virtual-mailman file
(when a new list is created) to a list for the check_sender_access
postfix restriction. For example, if I create the list "mailmantest",
the following is added to the virt
>
> That is the user based solution. The list admin based solution is to
> add per...@example.com or ^person(\+.*)?...@example\.com to
> accept_these_nonmembers.
Thanks Mark. However, as others will probably chime in, this is still a
per-user setting. IE I'd need to set a accept_these_nonmember
Hi,
we have installed mailman-2.1.9-4.el5 on Centos 5.
What i notice is that when i subscribe or when i receive a message from
the mailing list all messages are send from
listname-bou...@myhostname.tld.
Why this happen? Should it send messages using aliases defined
in /etc/mailman/aliases?
When
Hi,
I'm using MM 2.1.12 and am running into a problem that is rather nasty.
In my case the MM admin interface is wide open, which means that I don't
need a site admin pwd to access http://mydomain/mailman/admin/mylist. I
can click on logout and it will take me to the logout page, but simply
removi
David Walker wrote:
>
>Thanks Mark. However, as others will probably chime in, this is still a
>per-user setting. IE I'd need to set a accept_these_nonmembers for everyone
>who uses the +tag email option. I was thinking that there should be some
>config option that would (and if i knew python a
On 08/26/09 09:40, Mark Sapiro wrote:
The OP says "the +tag format described in RFC3696
(http://tools.ietf.org/html/rfc3696) allows for this format." I don't
know if RFC 3696 is the intended reference, but I see nothing in that
RFC regarding the semantics of a local part containing a '+' (or a
Grant Taylor wrote:
>On 08/25/09 22:57, Mark Sapiro wrote:
>
>> The list admin based solution is to add per...@example.com or
>> ^person(\+.*)?...@example\.com to accept_these_nonmembers.
>
>I don't know if I would call that a "solution" so much as I would a (per
>user) "work around".
Yes, it
On 08/25/09 22:57, Mark Sapiro wrote:
That is the user based solution.
Agreed.
The list admin based solution is to add per...@example.com or
^person(\+.*)?...@example\.com to accept_these_nonmembers.
I don't know if I would call that a "solution" so much as I would a (per
user) "work aroun
15 matches
Mail list logo
