On 05/04/2016 11:27 AM, David Newman wrote:
> 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, sayin
On 05/04/2016 10:48 AM, Beu, Ed (DOA) wrote:
>
> DEFAULT_DEFAULT_MEMBER_MODERATION = Yes
The double DEFAULT_DEFAULT on this variable appears to be the only doubled
default in the Defaults.py file. And, using it in the same manner in the
MM_CFG.py file appears to be the only way to
Hi, I got it working...
From: Beu, Ed (DOA)
Sent: Wednesday, May 04, 2016 8:49 AM
To: 'mailman-users@python.org'
Subject: Order of operation - config files
Hello,
We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10.
Production version will be running on CentOS.
Since mo
Hello,
We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10.
Production version will be running on CentOS.
Since most of our lists are 'Announcement' type lists, I have put the following
in the mm_cfg.py file:
DEFAULT_DEFAULT_MEMBER_MODERATION = Yes
For the occasional 'di
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 insta
On 05/04/2016 09:27 AM, Curtis Villamizar wrote:
> I'm resending this with a new subject. The last email just
> disappeared (no bounce). Maybe having
> DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in the subject tripped an all
> caps in subject test. (Or the moderator is slacking?)
A moderator (me) ap
On 05/03/2016 12:26 PM, Curtis Villamizar wrote:
> By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to
> https://publicsuffix.org/list/public_suffix_list.dat
>
> I have mailman set up on an IPv6 only host and publicsuffix.org has no
> IPv6 address. A near identical configuration is set up o
I'm resending this with a new subject. The last email just
disappeared (no bounce). Maybe having
DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in the subject tripped an all
caps in subject test. (Or the moderator is slacking?)
By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to
https://publicsuffi
On 05/03/2016 02:22 PM, Danny Schmarsel wrote:
> Hello guys,
>
> I'm running a mailing list without digests to keep the replies clean.
>
> On the "Membership Management" page I can still enable digests for
> specific users even with digestable turned off.
>
> The question: Will these users still
On 05/04/2016 06:12 AM, Craig Pettersen wrote:
> However after things went back up I've received two messages from the
> list and I have no idea where they've been hiding. Since I can't have
> people upset with 20 emails from the list showing up in their inboxes I
> shut postfix and mailman down
By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to
https://publicsuffix.org/list/public_suffix_list.dat
I have mailman set up on an IPv6 only host and publicsuffix.org has no
IPv6 address. A near identical configuration is set up on a dual
stack host. Any email to the IPv6 only host fails
Hello guys,
I'm running a mailing list without digests to keep the replies clean.
On the "Membership Management" page I can still enable digests for
specific users even with digestable turned off.
The question: Will these users still receive digests or does digestable
override user-specific
Hello,
I inherited a server that has a couple mailman lists that interface with
postfix and was alerted that daily messages from the list haven't been
going out for almost 3 weeks now. I fixed the problem in postfix, and
before fixing it I checked queues and files in /var/spool/postfix and in
/h
13 matches
Mail list logo
