[EMAIL PROTECTED] wrote:
>
>The comment "... and was distributed to all members" turns out to be
>incorrect. Messages from 'new' subscribers are delivered by MailMan
>to *some* existing members of the mailing list, but definitely not all
>of them.
>
>The bottom line is that for the moment, our att
A correction to the 'analysis' below:
--> --> >A message from a newly added subscriber is accepted, logged in the
--> --> >archive, and distributed to all the members of the mailing list.
-->
--> I just reconfirmed this, by adding myself again with yet another new
--> address, then sending a mess
Mark Sapiro writes:
> This can be tricky. LOG_DIR is defined in Defaults.py in terms of
> VAR_PREFIX. If VAR_PREFIX is redefined in mm_cfg.py, this will not
> redefine LOG_DIR as LOG_DIR was already defined in Defaults.py in
> terms of the Defaults.py definition of VAR_PREFIX.
2.1.9's Default
[EMAIL PROTECTED] writes:
> I do not have direct access to the list server system; I am working
> through our ISP's support service. Any suggestions for what I can
> tell them to look for
I'd suggest just giving them this address.
"Support" implies that they know what they are doing, and wil
On 4/27/07, Mark Sapiro wrote:
> Needless to say, this creates a very bad situation when we try to help
> cPanel users, since unless the issue is something we specifically
> recognize, we don't know whether it is a general Mailman issue or a
> cPanel issue, and if it's the latter we can't get
[EMAIL PROTECTED] wrote:
>
>X-Mailman-Version: 2.1.9.cp2
>
>which my ISP said was "current". I don't know the significance of
>the ".cp2", but 2.1.9 is the latest stable release according to
>http://sourceforge.net/project/showfiles.php?group_id=103
As Brad points out this is a cPanel releas
On 4/27/07, [EMAIL PROTECTED] wrote:
> Sorry, I should have been specific:
>
> X-Mailman-Version: 2.1.9.cp2
That's cPanel. See FAQ 6.11.
We have no way of verifying what they may have done to the stock
Mailman code once they took it and modified it to their purposes. At
best, we can try
--> BTW, what do you consider the 'current release' of Mailman?
Sorry, I should have been specific:
X-Mailman-Version: 2.1.9.cp2
which my ISP said was "current". I don't know the significance of
the ".cp2", but 2.1.9 is the latest stable release according to
http://sourceforge.net/project/s
[EMAIL PROTECTED] wrote:
>
>Thanks for the suggestion, but I don't believe it applies in our case.
>There are several hundred subscribers on each list, with over 200
>different mail domains (hence many different servers).
>
>A message from a newly added subscriber is accepted, logged in the
>archiv
--> On Thursday 26 April 2007 22:49:21 [EMAIL PROTECTED] wrote:
--> > Did you ever find a solution to this issue?
--> >
--> > I realize that this is a really old posting:
--> >
--> > I send an eMail to one of the lists, I can see in my /var/log/maillog;
--> >
--> >Jun 10 11:27:03 osiris s
Rolf E. Sonneveld wrote:
>
>Mark Sapiro wrote:
>>
>> One minor point here. The post log entry is not written until the
>> message is delivered by SMTPDirect.
>>
>
>OK, thus only after the message has been delivered to at least one
>subscriber (or the first MTA in the chain of delivery to at lea
Hello, Mark,
Mark Sapiro wrote:
> Stephen J. Turnbull wrote:
>
>> Fairly early in message processing, Mailman logs to either logs/post
>> (showing that the post was accepted) or to logs/vette (indicating that
>> the post was held or rejected, and why).
>>
>
>
> One minor point here. The po
Mark Sapiro writes:
> Stephen J. Turnbull wrote:
> >When the post is delivered,
> >there will be an entry in logs/smtp for each batch of deliveries
> >(usually one per remote host, or one per user if personalization or
> >VERP is being used).
>
> Actually, if nothing goes wrong, there will
Stephen J. Turnbull wrote:
>
>Fairly early in message processing, Mailman logs to either logs/post
>(showing that the post was accepted) or to logs/vette (indicating that
>the post was held or rejected, and why).
One minor point here. The post log entry is not written until the
message is deliver
Rolf E. Sonneveld writes:
> today I have a similar (or the same?) problem. Running Mailman V2.1.9.
> Symptoms in my case: a new member (added with the command line utility
> add_members) is subscribed properly, the associated mail address gets a
> welcome message (so far so good), but mail
[EMAIL PROTECTED] wrote:
> Did you ever find a solution to this issue?
>
> I realize that this is a really old posting:
>
> I send an eMail to one of the lists, I can see in my /var/log/maillog;
>
>Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756:
>from=
On Thursday 26 April 2007 22:49:21 [EMAIL PROTECTED] wrote:
> Did you ever find a solution to this issue?
>
> I realize that this is a really old posting:
>
> I send an eMail to one of the lists, I can see in my /var/log/maillog;
>
>Jun 10 11:27:03 osiris sendmail[2756]: h5A9R3920
Did you ever find a solution to this issue?
I realize that this is a really old posting:
I send an eMail to one of the lists, I can see in my /var/log/maillog;
Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756:
from=http://mail.python.org/mailman/listinfo/ma
Chad Leigh -- Shire.Net LLC wrote:
>Jul 12 16:51:50 2006 qrunner(5860): File "/usr/local/mailman/
>Mailman/Bouncer.py", line 131, in registerBounce
>Jul 12 16:51:50 2006 qrunner(5860): time.strftime('%d-%b-%Y',
>day + (0,)*6))
>Jul 12 16:51:50 2006 qrunner(5860): ValueError : day of yea
On Jul 14, 2006, at 9:20 PM, Mark Sapiro wrote:
> Chad Leigh -- Shire.Net LLC wrote:
>
>> I have a small mailman (2.1.x) installation with a few lists. They
>> just stopped working the other day. I did a mailmanctl restart and
>> that did not fix it but a stop and then a start did. I saw nothi
Chad Leigh -- Shire.Net LLC wrote:
>I have a small mailman (2.1.x) installation with a few lists. They
>just stopped working the other day. I did a mailmanctl restart and
>that did not fix it but a stop and then a start did. I saw nothing
>in the logs to indicate why the lists stopped wor
I have a small mailman (2.1.x) installation with a few lists. They
just stopped working the other day. I did a mailmanctl restart and
that did not fix it but a stop and then a start did. I saw nothing
in the logs to indicate why the lists stopped working.
How does one go about debugging t
Hi,
I have some problems with my Mailman server. I am running Mailman 2.1.2
(installed from source) on a RedHat 8.0 Linux server (using Sendmail
version 8.12.8-5.80). The problem is the following:
I send an eMail to one of the lists, I can see in my /var/log/maillog;
Jun 10 11:27:03 osiris
23 matches
Mail list logo
