mailman-2.1.29_6, FreeBSD 12.0-RELEASE-p10
After an unscheduled power cut by our hosting provider, one of the
mailing lists hosted on this server came back up with a config.pck file
containing 0 bytes. The file's timestamp corresponded to the time of the
power loss.
As a result, bin commands
On 1/4/19 5:10 PM, Mark Sapiro wrote:
> On 1/4/19 4:40 PM, David Newman wrote:
>>
>> Actually, the localhost issue began _after_ I ran "bin/withlist -l -a -r
>> fix_url" from the /usr/local/mailman directory and restarted the Mailman
>> service.
>
>
On 1/4/19 4:40 PM, David Newman wrote:
>
>
> On 1/4/19 12:19 PM, Mark Sapiro wrote:
>> On 1/3/19 2:18 PM, David Newman wrote:
>>> FreeBSD 12.0-RELEASE-p1, mailman-2.1.29_5, postfix-3.3.2_1,1,
>>> nginx-1.14.2_3,2
>>>
>>> Greetings. Could use
On 1/4/19 12:19 PM, Mark Sapiro wrote:
> On 1/3/19 2:18 PM, David Newman wrote:
>> FreeBSD 12.0-RELEASE-p1, mailman-2.1.29_5, postfix-3.3.2_1,1,
>> nginx-1.14.2_3,2
>>
>> Greetings. Could use help understanding two issues after migrating from
>> Apache to ngin
FreeBSD 12.0-RELEASE-p1, mailman-2.1.29_5, postfix-3.3.2_1,1,
nginx-1.14.2_3,2
Greetings. Could use help understanding two issues after migrating from
Apache to nginx:
1. All Mailman web pages load as expect except links from the admindb
page (for pending moderator request), which redirect to
On 8/16/16 1:19 PM, The Mailing List Server Admin wrote:
> Dear Mailman Cognoscenti,
>
> We have Mailman (and ListProc) running on a physical machine which
> needs to be decommissioned. Cloning the system to a virtual machine
> (VM) shouldn't be a problem, but I am unsure about the tasks needed
Greetings. How to get the data/virtual-mailman file to include all
virtual domains after running bin/genaliases?
This is on a FreeBSD 10.3 system running mailman 2.1.22 from ports.
The system has mailing lists defined from 3 domains -- let's call them
domain1.tld, domain2.tld, and domain3.tld.
Had to reinstall the Mailman port (not pkg) on a FreeBSD 10.3-RELEASE
system after updating some ports due to security vulnerabilities.
Several other packages also required rebuild to point to new shared objects.
The Mailman build failed, saying 'dnspython not found' even though that
port is
How to configure Mailman to handle https redirects to public archives
for virtual domains?
This is for a server with a canonical name of mail.domain1.tld, and
virtual names of lists.domain2.tld, lists.domain3.tld, etc.
With the mm.cfg config pasted below, clicking the archives link on a
list
On 2/19/11 6:57 AM, Mark Sapiro wrote:
David Newman wrote:
With the mm.cfg config pasted below, clicking the archives link on a
list page for lists.domain2.tld redirects to
https://mail.domain1.tld/pipermail/listname
which fails because the list name is associated with domain2.tld
On 11/2/10 8:13 AM, Mark Sapiro wrote:
David Newman wrote:
On 10/31/10 10:22 PM, Mark Sapiro wrote:
On 10/31/10 4:56 PM, David Newman wrote:
On 10/31/10 9:09 AM, Mark Sapiro wrote:
[...]
Here's a log snapshot of a message sent to s...@domain1.tld, a Mailman list
with subscribers 'dnew
On 10/31/10 10:22 PM, Mark Sapiro wrote:
On 10/31/10 4:56 PM, David Newman wrote:
On 10/31/10 9:09 AM, Mark Sapiro wrote:
What exactly does the Postfix log (maillog) say about the delivery to
one of these addresses?
maillog says status is sent to all list subscribers. The test list
(Apologies for re-raising a topic I asked about here a couple of years
ago. The instructions on Sourceforge have changed a bit since then.)
New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual
domains. Mail sent to/from virtual domains works fine.
Different story with Mailman.
On 10/31/10 9:09 AM, Mark Sapiro wrote:
David Newman wrote:
(Apologies for re-raising a topic I asked about here a couple of years
ago. The instructions on Sourceforge have changed a bit since then.)
New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual
domains. Mail sent
For a read-only announcement list, I'm looking for a way to set up
one-click subscription where a user enters an email in a form on a web
page and gets subscribed right away, with no confirmation needed.
Thanks in advance for clues on setting this up with MM, Apache and postfix.
Apologies in
On 3/1/10 10:34 AM, Mark Sapiro wrote:
David Newman wrote:
For a read-only announcement list, I'm looking for a way to set up
one-click subscription where a user enters an email in a form on a web
page and gets subscribed right away, with no confirmation needed.
This is not a good idea
On 1/26/10 5:07 PM, Mark Sapiro wrote:
David Newman wrote:
I am looking to obscure any reference to the sender's address from list
postings.
Per the guidelines, this includes (all done via the Web UI):
anonymous_list: Yes
first_strip_reply_to: Yes
reply_goes_to_list: Explicit address
I've set up a read-only announcement mailing list following these
guidelines:
http://wiki.list.org/pages/viewpage.action?pageId=4030685
I am looking to obscure any reference to the sender's address from list
postings.
Per the guidelines, this includes (all done via the Web UI):
anonymous_list:
On 1/16/10 7:55 AM, Mark Sapiro wrote:
David Newman wrote:
On 1/15/10 7:33 PM, Mark Sapiro wrote:
My guess is that on the old server, domain.tld was in Postfix's
mydestination so that addr...@domain.tld was a local address and only
referred to alias_maps and not virtual_alias_maps, whereas
On 1/16/10 11:11 AM, Mark Sapiro wrote:
David Newman wrote:
For clarification, which form do I want in mydestination?
localh...@local_domain (as you wrote)
or
localhost.$mydomain (as formerly in main.cf)
I think you mean the latter, but just checking.
What I actually suggest
Mailman 2.1.13, postfix 2.5.6, MySQL 5.0.77, OpenBSD 4.5
After migrating to new hardware, Mailman lists are working OK using the
form listname@mail.domain.tld, but mail sent to listname@domain.tld
bounces with an User unknown in virtual mailbox table error.
This is a problem since some users
On 1/15/10 7:33 PM, Mark Sapiro wrote:
David Newman wrote:
After migrating to new hardware, Mailman lists are working OK using the
form listname@mail.domain.tld, but mail sent to listname@domain.tld
bounces with an User unknown in virtual mailbox table error.
This is a problem since some
I'm sure this is a standard problem, but I haven't found the answer in
any of the FAQs or by searching the mailing list archives.
A customer asked that we change archives of an existing list from
private to public. That's done, but Mailman still requests a password,
even from a new browser with
Mailman 2.1.12 on OpenBSD 4.5
Don't know if this is a coincidence, but ever since rebuilding a Mailman
server that crashed last week and restoring the lists from archives, the
site admin address has received a few dozen bogus subscription requests
to lists on that server.
This is odd, in that
Mailman 2.1.12
Had a server crash. Built a new server, compiled MM 2.1.12 from source
and restored the lists, data, and archives from a backup.
Messages are going to the list but most aren't getting archived, with
errors like the one pasted below.
This has come up before:
On 5/13/09 10:06 PM, David Newman wrote:
Mailman 2.1.12
Had a server crash. Built a new server, compiled MM 2.1.12 from source
and restored the lists, data, and archives from a backup.
Messages are going to the list but most aren't getting archived, with
errors like the one pasted below
On 5/17/09 5:49 PM, Mark Sapiro wrote:
David Newman wrote:
On 5/13/09 10:06 PM, David Newman wrote:
Mailman 2.1.12
Had a server crash. Built a new server, compiled MM 2.1.12 from source
and restored the lists, data, and archives from a backup.
Messages are going to the list but most
On 3/27/09 9:07 AM, Mark Sapiro wrote:
David Newman wrote:
On 3/26/09 2:49 PM, Mark Sapiro wrote:
You can also see if this
post in in archives/private/LISTNAME.mbox/LISTNAME.mbox which will
tell you that Mailman tried to archive it. Note that two different
messages should never have
Mailman 2.1.10 on OpenBSD 4.4 with Postfix 2.5.3
Checked the FAQ and searched Google but didn't see anything that
directly addressed this:
Most messages make it into the archives but a few do not. I've pasted
below a sample of a message that didn't make it to the archive. I
suspect that it might
On 3/26/09 8:05 AM, Mark Sapiro wrote:
David Newman wrote:
Most messages make it into the archives but a few do not. I've pasted
below a sample of a message that didn't make it to the archive. I
suspect that it might be related to Postfix's message handling but am
not sure what's missing from
On 3/26/09 2:49 PM, Mark Sapiro wrote:
There are only a few reasons why a
particular post would not be archived, assuming archiving is working
in general.
Archiving is working in general.
1) There could be something in this particular post that throws an
exception in ArchRunner. This is
On 3/22/09 4:30 PM, Mark Sapiro wrote:
David Newman wrote:
This evening I tried creating a new list but posts from a subscriber to
the new list bounce with the message User unknown in virtual mailbox
table.
AFAICT Mailman is set up to work with Postfix virtual domains as
described
On 3/23/09 7:44 AM, Mark Sapiro wrote:
David Newman wrote:
I didn't have these two lines:
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
but adding them and restarting apache and mailman, deleting and
recreating the list didn't resolve the original error
Greetings. I have a mailserver running OpenBSD 4.4, Postfix 2.5.3 and
Mailman 2.1.0. The machine hosts multiple virtual domains and Mailman
already hosts several mailing lists in one of these domains.
This evening I tried creating a new list but posts from a subscriber to
the new list bounce with
On 6/2/08 4:34 AM, Bill Honneus (honneus) wrote:
Hi,
Anyone know how I can disable the monthly membership reminder email that
gets sent out to all members of a mailing list?
It's send_reminders on the general options page, under notifications.
dn
Thanks,
Bill
On 5/30/08 4:35 AM, Larry Stone wrote:
On 5/29/08 11:37 PM, Jim Popovitch at [EMAIL PROTECTED] wrote:
On Fri, May 30, 2008 at 12:18 AM, David Newman [EMAIL PROTECTED]
wrote:
Hmmm. I must be missing something, as the system is still associating each
Message-ID with all 250 list subscribers
On 5/30/08 8:40 AM, Larry Stone wrote:
On Fri, 30 May 2008, David Newman wrote:
When you then get the AOL TOS e-mail, you can figure out who the list
recipient was as while AOL redacts the AOL recipient, they don't touch the
Return-Path.
I wish this were true, but it appears AOL gets
On 5/30/08 3:28 PM, Brad Knowles wrote:
Stephen J. Turnbull wrote:
Yeah, somebody actually said that, but they really meant the
Return-Path. Changing Message-ID on regular posts would violate RFC
2822. Message-ID ids the content, not the medium, and is an author
header: intermediate senders
On 5/28/08 8:43 PM, Larry Stone wrote:
On 5/28/08 9:26 PM, David Newman at [EMAIL PROTECTED] wrote:
Another is to enable VERP for your outgoing messages, this allows
you to track the message ID to the individual user.
That sounds very promising, thanks. Trying it now...
I have all my lists
On 5/29/08 11:40 AM, Brad Knowles wrote:
David Newman wrote:
OK, I've enabled VERP but I'm no closer to isolating who's complaining
in AOL-land.
Possibly this is some VERP config error on my part. I added the
following to mm_cfg.py and rebooted:
VERP_PASSWORD_REMINDERS = Yes
On 5/29/08 12:09 PM, David Andrews wrote:
Did you go back to the list configuration and turn on personalization?
Er, no, I haven't. Where do I set that in the Web UI?
thanks
dn
DA: It is under Nondigest Options.
Sorry for being dense, but where?
These are the only choices I see under
On 5/29/08 1:46 PM, Larry Stone wrote:
On Thu, 29 May 2008, David Newman wrote:
Possibly this is some VERP config error on my part. I added the
following to mm_cfg.py and rebooted:
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS
One or more AOL subscribers is reporting posts to one of our mailing
lists as spam. Every time there's a post to this list, both we and our
upstream provider get a feedback report from AOL. This report provides
the message-ID for the offending email, but not the recipient's address.
AOL
On 5/28/08 7:09 PM, Dave Dewey wrote:
Quoting David Newman ([EMAIL PROTECTED]):
One or more AOL subscribers is reporting posts to one of our mailing
lists as spam. Every time there's a post to this list, both we and our
upstream provider get a feedback report from AOL. This report provides
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Congratulations!
I presume the usual upgrade instructions apply?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp
dn
--
Mailman-Users mailing list
Mark Sapiro wrote:
I suspect a permissions problem. Mailman would not serve up pages when
all files were owned by group mailman, so I did 'chgrp -R www
/var/www/mailman'. But after trying to create a list, the
aliases file is mode 660, owned by root:www.
This is probably a mistake.
Greetings. Apologies if this has been answered before but I didn't find
a direct answer in the archives or FAQ.
Is there a howto for installing Mailman from source inside the Apache
chroot on OpenBSD?
I'm struggling with this, using Mailman 2.1.19, Postfix 2.4.3, and
OpenBSD 4.2. There's a list
On Monday, January 29, 2007, at 04:18PM, Mark Sapiro [EMAIL PROTECTED]
wrote:
Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens
after that.
Presumably, that's because Postfix is delivering the mail to a local
mailbox 'pctest' instead of piping it to Mailman's mail
MM 2.1.9, Postfix 2.3.5, cyrus-imap 2.3.7, all on FreeBSD 6.1 installed from
ports
Postfix already handles mail for multiple virtual domains defined in a MySQL
database. I believe virtual domain setup is OK, as individual users have been
sending and receiving mail for some time.
Having
49 matches
Mail list logo
