Mark Sapiro | 1 Aug 04:18 2008
Picon

Re: How many domain in one list of mailing list?

Maickel Pandie wrote:
>
>I have some question. in average, How many domain in one list of
>mailing list in your server? because refer to RFC 2821 message always
>be sent once for one domain

I'm not sure what you think RFC 2821 says, but in the case of Mailman,
messages are delivered to the MTA in SMTP transactions with as few as
1 and as many as SMTP_MAX_RCPTS (default 500) recipients per
transaction depending on things like VERP and personalization. Each of
these transactions will be considered a separate message by the MTA,
even if the contents are identical. Further, in the case of large
lists, even with large numbers of recipients per transaction, it is
not guaranteed that all recipients in a given domain will be in the
same transaction.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

David Andrews | 1 Aug 04:42 2008

Mailman and C-Panel

I currently run my own server, a SUN Cobalt RAQ550.  Mailman is 
installed on it and I have full access to everything.

Because of aging hardware, etc. I will be replacing everything.  I am 
considering going to c-panel as we also host web sites for parts of a 
national nonprofit for which we also provide the lists.

I have read here over the years about limitations to Mailman on 
c-Panel?  What are they?  Are they imposed by the hosting 
company.  Since I will have full access to c-Panel, will I have a 
fully functional Mailman available to me.

Are the limitations mentioned here imposed by hosting companies?

Dave

Mark Sapiro | 1 Aug 06:23 2008
Picon

Re: Mailman and C-Panel

David Andrews wrote:
>
>I have read here over the years about limitations to Mailman on 
>c-Panel?  What are they?  Are they imposed by the hosting 
>company.  Since I will have full access to c-Panel, will I have a 
>fully functional Mailman available to me.
>
>Are the limitations mentioned here imposed by hosting companies?

I'm not sure what limitations you're referring to, but if you mean
things like limits on the number of messages per hour, those are all
imposed by the hosting provider.

If you haven't seen our FAQ on cPanel Mailman, it's at
<http://wiki.list.org/x/sYA9>.

The main issue is cPanel has their own patches. The most well known of
these is a patch to allow the same list name in two different virtual
domains, but this works by just appending the domain to the listname
for everything except the list email addresses which means the
listname for purposes of the web interface is listname_domain, and it
would be the same for command line tools if the command line tools
even work.

They have other patches as well which may be buggy, and we can't help
with these bugs. There has been at least one such issue in the past
<http://mail.python.org/pipermail/mailman-users/2007-February/055639.html>.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
(Continue reading)

Andrew Hodgson | 1 Aug 10:24 2008

Re: Mailman and C-Panel

David Andrews wrote:

>I currently run my own server, a SUN Cobalt RAQ550.  Mailman is 
>installed on it and I have full access to everything.

>Because of aging hardware, etc. I will be replacing everything.  I am 
>considering going to c-panel as we also host web sites for parts of a 
>national nonprofit for which we also provide the lists.

I have done both the C-pannel thing and using my own server with config files etc, and in my experience,
unless you are hosting lots of websites like in a hosting environment, there is not much point in using
C-pannel.  When I was using it, I got very fustrated with what it was trying to do, which was fab in a hosting
environment, but not for me, having different requirements for different sites etc.

Hope this helps.
Andrew.

Rachel Mawhood | 1 Aug 10:49 2008
Picon

Passwords

We have set up Mailman as a closed, private list for an international 
society.  Members are subscribed by the Secretary, via the Admin 
control panel.  (Anyone who wants to join the list has to e-mail the 
Secretary, and only the society members are eligible to be joined to the list.)

As far as I can see, that means that members won't ever be asked for 
a password/don't need a password to send messages to the list.  But 
they still would need a password to be able to view the Archives 
which we have set to "private".  When I tested accessing the 
archives, I got in with my own e-mail address and the Admin password 
(my own e-mail address is on the subscriber list and is difference 
from the list-owner e-mail address).

Obviously, we can't give 400-plus people the Admin or Moderator 
passwords so that they can view the Archives.  Is there a way of 
having a third password, which we can give to the membership (and 
reset from time to time), to enable members to view the Archives?

TVMIA
Rachel

Ron Peterson | 1 Aug 15:13 2008

duplicate membership reminders

I'm running mailman 2.1.9-7 on debian etch.  I'm also subscribed to
several of the lists.  These lists have been around for a while, through
one or two mailman upgrades.

When I recieve my monthly membership reminders, I get the correct number
of reminders, but they are all for the same list.  I.e. I'm in lists A,
B, C, and D, but I recieve four reminders for list A, and none for the
other three lists.

??

--

-- 
Ron Peterson
Network & Systems Manager
Mount Holyoke College
http://www.mtholyoke.edu/~rpeterso
-
I wish my computer would do what I want it to do - not what I tell it to do.

Cris McConkey | 1 Aug 16:31 2008

Patch to allow regular_exclusion _lists to function on hosted systems?


      // Option

*regular_exclude_lists* (nondigest): Other mailing lists on this site 
whose members are excluded from the regular (non-digest) delivery if 
those list addresses appear in a To: or Cc: header.

This option for non-digest mail is so duplicate posts are not sent out 
subscribers to more than one list in a particular domain when a message 
is sent to more than one list --a very important function that as list 
owner I have been patiently waiting for.  Now, Mailman supports it, but 
still there is a nered for a patch on hosted systems.

The hosting service I use to host various lists under one domain is 
aware of the problem that the list exclusion function does not work.  
This apparently has to do with aliases used for the list name in the 
shared environment.   It seems that the common  list address is not the  
"real" list address and so  exclusions based on  what appears in the To: 
and Cc: lines do not work.

Has anyone worked on a patch?  If so, please contact me.

Thanks,

Cris

Bill Honneus (honneus | 1 Aug 16:57 2008
Picon

Mailman posting question

Hi,

I have a Mailman setup integrated with Sendmail on the same server.
When my list sends out posting updates via the bounces address, i.e.
mylist-bounces <at> mydomain.com, one of the recipients is an internal user
defined on the same local server.  So my question is, when the
mylist-bounces sends out the updates, do the messages destined for local
addresses go directly to the local address without hitting the outside
or does mailman send all the messages out to the Internet, and then
those messages get routed back to the local machine?  This is assuming
that no special routing is set up with Sendmail MTA.

Thanks,

Bill

Dragon | 1 Aug 17:14 2008

Re: Mailman posting question

Bill Honneus (honneus) wrote:
>Hi,
>
>I have a Mailman setup integrated with Sendmail on the same server.
>When my list sends out posting updates via the bounces address, i.e.
>mylist-bounces <at> mydomain.com, one of the recipients is an internal user
>defined on the same local server.  So my question is, when the
>mylist-bounces sends out the updates, do the messages destined for local
>addresses go directly to the local address without hitting the outside
>or does mailman send all the messages out to the Internet, and then
>those messages get routed back to the local machine?  This is assuming
>that no special routing is set up with Sendmail MTA.
>
---------------- End original message. ---------------------

MTAs are designed to deliver mail to the correct host based on the MX 
record for a given domain.

So if the MX record for your own domain points to the machine with 
the MTA Mailman is using, it will deliver it locally on the same 
server. There is no reason for it to ever be placed on the wire 
because it has nowhere else to go. In order for it to work as you 
suggest, another SMTP server would have to serve as an open relay to 
send it back and that is not such a good idea. It's bad because it 
wastes bandwidth and because it leaves a big hole open for abuse.

Dragon

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
(Continue reading)

Mark Sapiro | 1 Aug 17:24 2008
Picon

Re: Patch to allow regular_exclusion _lists to functionon hosted systems?

Cris McConkey wrote:
>
>The hosting service I use to host various lists under one domain is 
>aware of the problem that the list exclusion function does not work.  
>This apparently has to do with aliases used for the list name in the 
>shared environment.   It seems that the common  list address is not the  
>"real" list address and so  exclusions based on  what appears in the To: 
>and Cc: lines do not work.
>
>Has anyone worked on a patch?  If so, please contact me.

This sounds like cPanel Mailman <http://wiki.list.org/x/sYA9>. If that
is the case, this would have to be addressed by cPanel (or a cPanel
installation site) since they are the only ones who know what their
code base is.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


Gmane