hi all.
after moving a mailinglist from one domain to another, i was wondering
how i can keep the old List-ID (according to RFC2919 the List-ID (or the
address-part therein) should not change, even if the list-address changes)
i have found an open bug-report regarding this:
IEM - network operating center (IOhannes m zmoelnig) wrote:
after moving a mailinglist from one domain to another, i was wondering
how i can keep the old List-ID (according to RFC2919 the List-ID (or the
address-part therein) should not change, even if the list-address changes)
Correct. It
Mark Sapiro wrote:
The only solution that doesn't involve hacking code is to not change
the host_name of the list, but since the host_name is the domain that
is exposed in all list email addresses, that is clearly not a
practical solution.
are there any plans to allow an administrator to set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2009, at 11:17 AM, IEM - network operating center (IOhannes
m zmoelnig) wrote:
are there any plans to allow an administrator to set the List-ID in
future versions of Mailman?
It's not out of the realm of possibility for MM3. It
Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my
error log is filling up with messages like this and virtually no
messages are moving through my mailing lists. Based on a search of
the archives, I removed ALL digest.mbox files and ran unshunt. No
messages moved and the
rp...@kinfolk.org wrote:
Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my
error log is filling up with messages like this and virtually no
messages are moving through my mailing lists. Based on a search of
the archives, I removed ALL digest.mbox files and ran unshunt. No
Hi Mark,
What Mailman version is this...
Not sure as it is supplied by my host at hostgo.com
You aren't by chance seeing only the 152 As (or whatever's first) ...
AHH! That was exactly the problem. So there really was no problem, just cockpit
error.
Thanks a bunch.
Ed Corcoran
Mailman is currently not sending email and not posting to the archives. We
moved the server, that hosts the mailman application, to a new network.
This required that our email relay server also be changed. I am wondering
if there is something in the mailman config that needs to be updated.
I
Mark Sapiro wrote at 05:49 PM 2/28/2009:
What is supposed to happen when a non-listmember tries to get a password
reminder from the member options page?
I tried it myself after trying to figure out if a member was using the wrong
email address, and the web page said, A reminder of your
Barry Warsaw writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2009, at 11:17 AM, IEM - network operating center (IOhannes
m zmoelnig) wrote:
are there any plans to allow an administrator to set the List-ID in
future versions of Mailman?
It's not out of
Michael Welch wrote:
Mark Sapiro wrote at 05:49 PM 2/28/2009:
The issue is your list's membership is not public, so we can't reveal
that the person requesting the reminder is not a member or this could
be used to fish for list membership. Granted the message should be
better (i.e. more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2009, at 12:28 PM, Stephen J. Turnbull wrote:
It's not out of the realm of possibility for MM3. It seems to me on
the order of browser ID hacking.
? Isn't it as simple as adding a rfc2919-list-id attribute to the
list object, and
Patricia A Moss wrote:
Mailman is currently not sending email and not posting to the archives. We
moved the server, that hosts the mailman application, to a new network.
This required that our email relay server also be changed. I am wondering
if there is something in the mailman config that
On 2 Mar 2009 at 9:10, Mark Sapiro wrote:
rp...@kinfolk.org wrote:
Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my
error log is filling up with messages like this and virtually no
messages are moving through my mailing lists. Based on a search of
the archives, I
I have a system that I just set up and mail, such as subscribe notifications
and list creations are going out but mail isn't making it in. I get a server
is down error reply. Although postfix is up, where might the catch be?
Thanks for any ideas or suggestions,
Tim
Tim Ferguson
rp...@kinfolk.org wrote:
# python
Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21)
[GCC 4.2.4] on linux2
Type help, copyright, credits or license for more
information.
I re-ran the configure and install of mailman, ran unshunt and the
errors still show using python 2.5:
What does
Tim Ferguson wrote:
I have a system that I just set up and mail, such as subscribe notifications
and list creations are going out but mail isn't making it in. I get a
server is down error reply. Although postfix is up, where might the catch
be?
Where do you see this? Is this in a DSN
On 2 Mar 2009 at 10:24, Mark Sapiro wrote:
rp...@kinfolk.org wrote:
# python
Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21)
[GCC 4.2.4] on linux2
Type help, copyright, credits or license for more
information.
I re-ran the configure and install of mailman, ran unshunt and the
rp...@kinfolk.org wrote:
On 2 Mar 2009 at 10:24, Mark Sapiro wrote:
Are you also getting many errors like the following?
Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file:
/var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c3518
5 46e179e37b02.bak
Yes:
Mar
Jim Savoy wrote:
Reading this reminded me that I have a similar problem. All of our
lists
are set by default to be admin_immed_notify=yes, but the list owners
only
get a message when something new arrives (that is put on hold). They
never get a daily reminder about the queued-up stuff. Is
Jim Savoy wrote:
I am not all that familiar with cron. Is that crontab -u mailman
crontab.in something you need to run every time you reboot the system?
Or does it add something to /etc/cron.d or /etc/cron.daily or
/etc/crontab?
(I don't see anything new in those).
Jim Savoy answers himself:
I think I have my phantom requests (eg the -1 request(s) pending)
question
answered. Googling it I see that Mark provided a fix, but also said that
by
going to that admin page once should clear it. That may save me from
manually
having to fix hundreds of lists.
Savoy, Jim wrote:
The answers to your questions are: yes, yes yes. But I don't think
the person
who installed Mailman many years ago ever did the crontab -u mailman
crontab.in
bit, so I just did it now. First I commented out everything in that
crontab.in file
except the checkdbs line, and set
Barry Warsaw writes:
On Mar 2, 2009, at 12:28 PM, Stephen J. Turnbull wrote:
It's not out of the realm of possibility for MM3. It seems to me on
the order of browser ID hacking.
? Isn't it as simple as adding a rfc2919-list-id attribute to the
list object, and defaulting it to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2009, at 9:23 PM, Stephen J. Turnbull wrote:
I disagree. The identity of a list is what it is, and shouldn't
change because the server changes. The issue here arises because in
Mailman 2.1, lists have no sense of their own identitywink,
25 matches
Mail list logo
