Mark Sapiro wrote:
Martin Dennett wrote:
Brad Knowles wrote:
At 7:23 AM +0100 10/4/06, Martin Dennett wrote:
There is no other information in the bounce message, so how do I
find out who the message is really trying to be delivered to?
This kind of problem is
Hi
Now I know this will sound like a didn't read the archives and/or
didn't read the FAQ but I did and no solution suggested for similar
problems worked. In particular
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp
does not fix the problem:
Mailman has been installed on a
At 2:05 PM +0100 10/6/06, Chris Puttick wrote:
However
the root/master/? (a better name escapes me but default iseems
inappropriate, given it is a correctly configured variable) domain of
the installation is stubbornly
Non-routeable as in private address behinded a NATed proxying
firewall; the problem is seen if you go to any of the generic pages
e.g. lists.my.tld/mailman/listinfo, where the server instead of
referring to itself as lists.my.tld refers to itself as ip.ad.dr.ess -
if you go to a list specific page
Mark Sapiro skrev:
Anders Norrbring wrote:
I'm having troubles finding info on this matter.. Probably because
English isn't my native language, so I guess I just don't get the search
terms right to get relevant results.
Try the threads starting at
On 10/6/06, Anders Norrbring [EMAIL PROTECTED] wrote:
Thanks Mark,
But I don't feel that fetchmail would be the right way for me...
I'm thinking that maybe I can mount the mailman executable directory
from the webserver as a NFS share, and then run as usual.
Would that work?
While this is
Chris Puttick wrote:
the problem is seen if you go to any of the generic pages
e.g. lists.my.tld/mailman/listinfo, where the server instead of
referring to itself as lists.my.tld refers to itself as ip.ad.dr.ess -
if you go to a list specific page the URLs are as expected, except the
link for the
Patrick Bogen skrev:
On 10/6/06, Anders Norrbring [EMAIL PROTECTED] wrote:
Thanks Mark,
But I don't feel that fetchmail would be the right way for me...
I'm thinking that maybe I can mount the mailman executable directory
from the webserver as a NFS share, and then run as usual.
Would that
At 3:45 PM +0100 10/6/06, Chris Puttick wrote:
URLs are also as expected in emails, as are email addresses. Like I
say, the list server functions properly, except for this insistence of
using the IP address in the base URLs.
Mark Sapiro, or one of the other core developers, may have a
At 5:01 PM +0200 10/6/06, Anders Norrbring wrote:
I'm thinking that maybe I can mount the mailman executable directory
from the webserver as a NFS share, and then run as usual.
The Mailman developers have done a lot of work to try to make Mailman
as NFS-safe as possible. In theory, you
For some reason, the gate_news cron starting giving this error every 5
minutes:
IOError: [Errno 13] Permission denied:
'/usr/local/mailman/lists/testlist/config.pck'
To the best of my knowledge, this list does not have a mail/news gateway.
Can someone let me know how I can get rid of
September 6th, I updated mailman and it quit working. The file permissions
are all group mailman, but it doesn't send out messages to the private
group. My postfix maillog looks like this:
Oct 6 10:16:00 mail postfix/local[16020]: 03AFA3F84E:
to=[EMAIL PROTECTED], relay=local, delay=0,
* Jack Gordon [EMAIL PROTECTED]:
September 6th, I updated mailman and it quit working. The file permissions
are all group mailman, but it doesn't send out messages to the private
group. My postfix maillog looks like this:
Oct 6 10:16:00 mail postfix/local[16020]: 03AFA3F84E:
On 10/6/06, Ralf Hildebrandt [EMAIL PROTECTED] wrote:
* Jack Gordon [EMAIL PROTECTED]:
Any hints on where I should look for the problem?
Is mailman's queue runner running?
Also, you want to check the mailman logs to see if anything looks bad
there. And, as Ralf said, check the qrunners are
Ok, the problem:
http://lists.openarchaeology.net/mailman/listinfo
compared with
http://lists.openarchaeology.net/mailman/listinfo/mailman
mm_cfg:
from Defaults import *
##
# Put YOUR site-specific settings below this line.
DEFAULT_URL_PATTERN
Ki Song wrote:
Scratch the last comment. Apparently, the config.pck and other pck files are
recreated every time the cron runs. The problem is that when this file is
recreated, the permissions are such that mailman cannot modify that file.
For example, my config.pck file for all the lists on my
Chris Puttick wrote:
Ok, the problem:
http://lists.openarchaeology.net/mailman/listinfo
compared with
http://lists.openarchaeology.net/mailman/listinfo/mailman
mm_cfg:
from Defaults import *
##
# Put YOUR site-specific settings below this
Patrick Bogen wrote:
On 10/6/06, Ralf Hildebrandt [EMAIL PROTECTED] wrote:
* Jack Gordon [EMAIL PROTECTED]:
Any hints on where I should look for the problem?
Is mailman's queue runner running?
Also, you want to check the mailman logs to see if anything looks bad
there. And, as Ralf said,
I'm running Mailman-2.1.8p0 on an OpenBSD 3.9 box. I
have everything set up correctly (I've installed
successfully using older versions on older versions of
OpenBSD) as far as I can see. Mail is sending through
the lists appropriately, but it's not archiving at
all. I've checked Defaults.py and
stupidmail4me wrote:
Mail is sending through
the lists appropriately, but it's not archiving at
all. I've checked Defaults.py and mm_cfg.py and the
list's configuration options and they're all set to
archive. I've checked permissions in
/var/spool/archive/* and they appear to be fine (if I
give
Ki Song wrote:
Scratch the last comment. Apparently, the config.pck and other pck files are
recreated every time the cron runs. The problem is that when this file is
recreated, the permissions are such that mailman cannot modify that file.
For example, my config.pck file for all the lists
Mark Sapiro wrote:
Is ArchiveRunner running?
That should be Is ArchRunner running?. Sorry for any confusion.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Ki Song wrote:
I ran check perms and there were no problems found.
What else do I need to check? I am still getting the
Cron [EMAIL PROTECTED] /usr/bin/python -S /usr/local/mailman/cron/gate_news
message.
What happens if you manually run
/usr/bin/python -S /usr/local/mailman/cron/gate_news
http://lists.appliedeco.org/
How to change the email address that shows up in the text:
If you are having trouble using the lists, please contact
[EMAIL PROTECTED] ?
Scott
--
Mailman-Users mailing list
Mailman-Users@python.org
Scott Chapman wrote:
http://lists.appliedeco.org/
How to change the email address that shows up in the text:
If you are having trouble using the lists, please contact
[EMAIL PROTECTED] ?
In the module Mailman/Cgi/listinfo.py in the definition of the
listinfo_overview() function you'll find the
Mark Sapiro wrote:
However, perhaps a better solution is to just leave it as is and
subscribe the intended recipient to the 'mailman' list.
I don't follow you here. You mean [EMAIL PROTECTED] being the
intended recipient?
How would this help?
Scott
Scott Chapman wrote:
Mark Sapiro wrote:
However, perhaps a better solution is to just leave it as is and
subscribe the intended recipient to the 'mailman' list.
I don't follow you here. You mean [EMAIL PROTECTED] being the
intended recipient?
I mean instead of changing the code to replace
Mark Sapiro wrote:
Scott Chapman wrote:
Mark Sapiro wrote:
However, perhaps a better solution is to just leave it as is and
subscribe the intended recipient to the 'mailman' list.
I don't follow you here. You mean [EMAIL PROTECTED] being the
intended recipient?
I mean instead of
Scott Chapman wrote:
I found it. The list is not available to non-members. How do I make a list
be available to anyone?
Set Privacy options...-Sender filters-generic_nonmember_action to
Accept.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area,
Mark Sapiro wrote:
Scott Chapman wrote:
Mark Sapiro wrote:
However, perhaps a better solution is to just leave it as is and
subscribe the intended recipient to the 'mailman' list.
I don't follow you here. You mean [EMAIL PROTECTED] being the
intended recipient?
I mean instead of
mailman-2.1.9
FreeBSD 4-11
python-2.3.5_1
python-2.4.3
Hi there,
I recently upgraded python and mailman and a bunch of other FreeBSD
ports. mailman no longer appears to be forwarding mail. I can see in
my sendmail logs that the mail is received and piped to mailman with the
post command
On 10/7/06, Noah [EMAIL PROTECTED] wrote:
I recently upgraded python and mailman and a bunch of other FreeBSD
ports. mailman no longer appears to be forwarding mail. I can see in
my sendmail logs that the mail is received and piped to mailman with the
post command like -
Patrick Bogen wrote:
On 10/7/06, Noah [EMAIL PROTECTED] wrote:
I recently upgraded python and mailman and a bunch of other FreeBSD
ports. mailman no longer appears to be forwarding mail. I can see in
my sendmail logs that the mail is received and piped to mailman with the
post command like
Noah wrote:
yeah they are/were running. something a little deeper is happening
here. Again it is only one mail list at the momment that is not working
or posting rather. I can sub and unsub and receive notifications. but
the post is an issue right now.
Where are the messages ('ls -lR
34 matches
Mail list logo
