Its odd, I could have sworn the slicing used to be done per recipient,
not per message. I've had to check logs for a client to confirm her
messages went out, and generally had check all three machines to verify
every user received the message.
The rest of the process works as I expected it to
With great sadness, I'm trying to deal with the DMARC problem certain
providers have decided to create for everyone else, and for some reason,
even after turning the mung option on in the web interface, there's no
munging going on. (wrap doesn't wrap either)
I have ALLOW_FROM_IS_LIST = Yes in mm_c
On 5/24/14, 6:26 PM, Stephen J. Turnbull wrote:
> Richard Damon writes:
>
> > From what I have seen, any version of Mailman before 2.1.16 (and
> > preferably 2.1.18) just isn't compatible with DMARC
>
> Please, it's the other way around! ;-) DMARC is the interloper, and
> some insiders fear that
> > I just realized that setting the digest option could be a temporary
> > solution for my Yahoo and AOL subscribers
>
>Just make sure you set it for *all* users, not just those using Yahoo!
>and AOL.
You only need to implement it for subscribers using mail systems that
implement DMARC rejections
On 05/24/2014 03:05 PM, Jeff Taylor wrote:
> After stopping mailman, machine #1 shows:
> May 24 15:23:34 2014 (11512) Master qrunner detected subprocess exit
> (pid: 11516, sig: None, sts: 15, class: IncomingRunner, slice: 1/3)
>
> Machine #2:
> May 24 15:21:56 2014 (12767) Master qrunner detected
Well, never mind. I would have to do this for all users, not just these. A
pain this is.
Sorry.
Allan
I just realized that setting the digest option could be a temporary solution
for my Yahoo and AOL subscribers until things get sorted (hopefully by Yahoo
and AOL stopping this nonsense). My M
Richard Damon writes:
> From what I have seen, any version of Mailman before 2.1.16 (and
> preferably 2.1.18) just isn't compatible with DMARC
Please, it's the other way around! ;-) DMARC is the interloper, and
some insiders fear that this mess will derail progress to RFC status
of the useful
Allan Hansen writes:
> I just realized that setting the digest option could be a temporary
> solution for my Yahoo and AOL subscribers
Just make sure you set it for *all* users, not just those using Yahoo!
and AOL. The important thing is that non-AOL/Yahoo! subscribers be
protected from the de
After stopping mailman, machine #1 shows:
May 24 15:23:34 2014 (11512) Master qrunner detected subprocess exit
(pid: 11516, sig: None, sts: 15, class: IncomingRunner, slice: 1/3)
Machine #2:
May 24 15:21:56 2014 (12767) Master qrunner detected subprocess exit
(pid: 12769, sig: None, sts: 15, clas
On 5/24/14, 4:24 PM, Allan Hansen wrote:
> I just realized that setting the digest option could be a temporary solution
> for my Yahoo and AOL subscribers until things get sorted (hopefully by Yahoo
> and AOL stopping this nonsense). My Mailman installation comes with the
> system (Mac OS X). Ma
I just realized that setting the digest option could be a temporary solution
for my Yahoo and AOL subscribers until things get sorted (hopefully by Yahoo
and AOL stopping this nonsense). My Mailman installation comes with the system
(Mac OS X). Maiman is 2.1.14 and the OS is 10.5.8. I have no pl
On 05/24/2014 12:14 PM, Jeff Taylor wrote:
> The entire QRUNNERS section on the machines looks like this:
>
> QRUNNERS = [
> ('ArchRunner', 3,0,3), # messages for the archiver
...
OK. That's as it should be.
> Per your ps command, on this machine I get:
>
> list 11516 11512 0 08:
The entire QRUNNERS section on the machines looks like this:
QRUNNERS = [
('ArchRunner', 3,0,3), # messages for the archiver
('BounceRunner', 3,0,3), # for processing the qfile/bounces directory
('CommandRunner', 3,0,3), # commands and bounces from the outside
world
('Inc
On 05/24/2014 07:52 AM, Jeff Taylor wrote:
> After doing some upgrades, I noticed yesterday that my multi-machine
> setup is no longer properly slicing the queue between machines. I
> probably missed something, but after going through all my notes on the
> setup I cannot figure out what the proble
After doing some upgrades, I noticed yesterday that my multi-machine
setup is no longer properly slicing the queue between machines. I
probably missed something, but after going through all my notes on the
setup I cannot figure out what the problem in. Hopefully someone else
can spot the issu
15 matches
Mail list logo
