Le 11/06/2014 18:01, Larry Kuenning a écrit :
Thus _this is important_ will be underlined in Thunderbird, _but this
is also important_ will not (at least if the line break falls within
the markers, as it did when I tested this by sending it to myself).
Yep it doesn't work. Is a ticket opened
Thanks to Mark and Steven, but it seems that the paths are consistent
between servers. I just inherited the server and need to get it on a
supported OS. Here is the old server info:
Fedora release 13 (Goddard)
mailman-2.1.12-17.fc13.i686
New server info:
Red Hat Enterprise Linux Server release
Hi,
I've upgraded our Mailman installation to 2.1.18-1 recently and noticed
that the dmarc_moderation_action is not working.
We've setup a test list, and set the list to Munge From for
dmarc_moderation_action. Upon sending a test message in from either one
of our Yahoo or AOL accounts the From
On 06/12/2014 07:29 AM, Peter Knowles wrote:
We've setup a test list, and set the list to Munge From for
dmarc_moderation_action. Upon sending a test message in from either one
of our Yahoo or AOL accounts the From field is being maintained as
usern...@yahoo.com or usern...@aol.com
On 06/12/2014 05:51 AM, Jimmy wrote:
Thanks to Mark and Steven, but it seems that the paths are consistent
between servers. I just inherited the server and need to get it on a
supported OS. Here is the old server info:
So you manually run '/some/path/to/bin/mailmanctl start' and it works,
but
Yep, done that too. Here is a little demo of what I'm seeing:
=
[root@mailman-server ~]$/usr/lib/mailman/bin/mailmanctl start
Starting Mailman's master qrunner.
[root@mailman-server ~]$/usr/lib/mailman/bin/mailmanctl status
mailman (pid 8337) is running...
Mark,
When I set the option to reject it rejects properly as expected. But when
it's set to munge from it sends it out as if Accept was chosen.
Best Regards,
Peter Knowles
TPN Solutions
Email: pknow...@tpnsolutions.com
Phone: 604-229-0715
Skype: tpnsupport
Website: http://www.tpnsolutions.com
On 06/12/2014 01:41 PM, Peter Knowles wrote:
When I set the option to reject it rejects properly as expected. But
when it's set to munge from it sends it out as if Accept was chosen.
Then the problem almost certainly has to be the pipeline. There is a new
WrapMessage handler that must be in
Mark,
Inside mm_cfg.py, GLOBAL_PIPELINE has the following:
SpamDetect
Approve
Replybot
Moderate
Hold
MimeDel
Scrubber
Emergency
Tagger
CalcRecips
AvoidDuplicates
Cleanse
CleanseDKIM
CookieHeaders
ToDigest
ToArchive
AfterDelivery
Acknowledge
ToOutgoing
Best Regards,
Peter Knowles
TPN Solutions
Mark,
In Defaults.py GLOBAL_PIPELINE has the following:
SpamDetect
Approve
Replybot
Moderate
Hold
MimeDel
Scrubber
Emergency
Tagger
CalcRecips
AvoidDuplicates
CleanseDKIM
CookieHeaders
ToDigest
ToArchive
ToUsenet
AfterDelivery
Acknowledge
WrapMessage
ToOutgoing
Best Regards,
Peter Knowles
TPN
On June 12, 2014 2:34:50 PM PDT, Peter Knowles pknow...@tpnsolutions.com
wrote:
Mark,
In Defaults.py GLOBAL_PIPELINE has the following:
SpamDetect
Approve
Replybot
Moderate
Hold
MimeDel
Scrubber
Emergency
Tagger
CalcRecips
AvoidDuplicates
Cleanse is missing here. I am guessing this is a typo.
On 06/12/2014 12:38 PM, Jimmy wrote:
The relevant portions of the mailman init script:
=
MAILMANHOME=/usr/lib/mailman
MAILMANCTL=$MAILMANHOME/bin/mailmanctl
Does this file perhaps contain anything like
if [ -f /etc/sysconfig/mailman ] ; then
.
12 matches
Mail list logo
