On Thu, 17 Jan 2008, Mark Sapiro wrote:
Joakim Nömell wrote:
Hi all. I have just upgraded my system to MM 2.1.9 and wonder if it is
possible to change the -owner-addresses to something else?
It may or may not be easy. At a minimum, you'd need to change
def GetOwnerEmail(self):
On Thu, 17 Jan 2008, Brad Knowles wrote:
On 1/17/08, Joakim Nömell wrote:
Hi all. I have just upgraded my system to MM 2.1.9 and wonder if it is
possible to change the -owner-addresses to something else? The reason is
that we receive a lot of spam after 3 years use. We already have
On Wed, 23 Jan 2008, Joakim Nömell wrote:
On Thu, 17 Jan 2008, Mark Sapiro wrote:
Joakim Nömell wrote:
Hi all. I have just upgraded my system to MM 2.1.9 and wonder if it is
possible to change the -owner-addresses to something else?
It may or may not be easy. At a minimum, you'd need to
Hi everybody.
Since a couple of months I have started having some problems with
mailman. Sometimes it stops sending out e-mail: outgoing messages get
stuck in ~/qfiles/out.
The qrunner for outgoing mail is up and running, but it simply does not
process the messages in the queue. Restarting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joyce Dowling wrote:
I sympathize. The variations are endless. I had to find a new one just
because my most favorite doesn't use Mailman and I needed it for a
couple of clients.
| We just purchased this service in Nov. I don't know how I'd get my
SP writes:
I checked the mailman logs, but I can't find any error or any message
that can help debugging the problem...
Find the last few logs from Mailman and the MTA before the stoppage.
This may give experts some clue. (If I knew what to tell you to look
for, I would, but experts often
Brandon Sussman writes:
I have had good luck so far with Dreamhost's Mailman support - they have
some folks who seem to care and know Mailman fairly well.
That's interesting, considering that there was some hair-pulling over
on mailman-devel about possible problems with Dreamhost. (Totally
Stephen J. Turnbull ha scritto:
Find the last few logs from Mailman and the MTA before the stoppage.
This may give experts some clue. (If I knew what to tell you to look
for, I would, but experts often can see things that we can't. :)
Good suggestion: I have to wait for the problem to appear
At 9:52 AM -0500 1/23/08, Brandon Sussman wrote:
Were the recommendations specific regarding Mailman support?
Who knew that Mailman support would be an issue?! Besides listservs,
I need cpanel, message boards, drupal, and who knows what else! I
help several non-profits small businesses with
Actually bad support for mailman is a common problem among web hosts. Since
mailman comes package along with cpanel and other popular hosting control
panels, many web hosts freely advertise it with their services without
having the knowledge of runnning a reliable mailman server. Even large hosts
SP wrote:
Good suggestion: I have to wait for the problem to appear again, but as
soon as it jumps out I will post here the logs... the only problem is
that in fact I don't know exactly when the runner stops working: I
can only check the oldest message in the outgoing queue and conclude
that
Dear mailman guys..
I have a cent-os dedicated server with godaddy and is hosting my daily
newsletter list on it .. my subscrier list has grown to over 77,000 and is
growing rapidly that I will have to purchase another server in order to deliver
the newsletter in the same day.. because
Jon Slater wrote:
DEFAULT_URL_HOST = www.myserver.com
DEFAULT_EMAIL_HOST = myserver.com
You also want
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
if you don't have it and then
add_virtulahost('www.firstdomain.con', 'firstdomain.com')
add_virtulahost('www.seconddomain.con',
Joakim Nömell wrote:
Hi again. I changed it to own instead of owner. I also changed
-owner to -own in the mailman-router in my exim4.conf-file. But after
restarting exim4 and mailman I got:
[EMAIL PROTECTED]
local delivery failed
I don't know why. If you have something like the
On Thu, Jan 24, 2008 at 02:14:02AM +0900, Stephen J. Turnbull wrote:
Brandon Sussman writes:
I have had good luck so far with Dreamhost's Mailman support - they
have some folks who seem to care and know Mailman fairly well.
That's interesting, considering that there was some hair-pulling
Mark Sapiro wrote:
Then restart mailman, and finally run fix_url to fix your lists. E.g.
cd ~mailman
bin/withlist -l -r fix_url members -u firstdomain.com
bin/withlist -l -r fix_url board -u seconddomain.com
etc.
Actually, the fix_url -u option is the url host, not the email host, so
Matthew Farr wrote:
I tried to set up a new list today, here:
http://tlca.org/mailman/listinfo/risingsun
However, no one can send mail to the list. It bounces back with:
This is an automatically generated Delivery Status Notification
Delivery to the following recipient failed permanently:
At 06:10 PM 1/21/2008, you wrote:
Somewhere, there is another test/backup/incompletely deleted/whatever
Mailman installation that is sending these. Check the Received: headers
of the message to see at which server it originates and then
I'm not sure what you mean by at which server it
On 1/23/08, Khalil Abbas wrote:
the question is, is there a way to prevent duplicate subscriptions?
because people subscribe to my newsletter by email sent to me, then
I collect all the emails and use the mass-subscribe option in the
web interface.. and some subscribers may exist in the
19 matches
Mail list logo
