At 10:24 PM 12/12/99 -0800, you wrote:
>Most of the messages don't return a reason why
That's your first problem! Here's part of the help file I wrote
for "configset access_rules", which I believe to be correct but
which caused Jason some concern:
There are some interactions between your choice of replyfile or mailfile
and the subscriber's setting of ack/noack (via the "set" or "configset
default_flags" commands). Error messages can vanish (for noack with
replyfile, unless ack_denials_always is enabled for the list in question)
or lacking information because variables are not always evaluated (for
mailfile). Refer to "help set" for more details.
Check your default_flags, make sure "ack" is set!
>but a few return:
>Duplicate Message Checksum (Fri Dec 10 00:12:28 1999)
>Duplicate Partial Message Checksum (Fri Dec 10 00:12:28 1999)
>Can anyone tell me how to fix this?
I've been using Mj2 for a long time now, and I've never seen this
message EXCEPT WHEN THERE REALLY WAS A DUPLICATE POST. Some mailers
go bonkers every so often and hose out 50 copies of the same thing.
Mj2 saves you. Some people lose their connection while sending and
don't know if it went out before. Mj2 saves you.
On the OTHER hand, if you get a bounce for ANY reason and the post
does not go out, fixing the reason for the bounce does NOT allow
you to re-post the message. Duplicate message checksums are done
before the post is sent out. This is good and bad. Good because a
spammer who bounces once can't keep trying. Bad because a person
who gets "you can't post because you're not subscribed" and then
subscribes STILL can't post... until they change the first line
or two of the message. It always works to add "I tried to post
this but I wasn't yet subscribed" as the first line.
When debugging this sort of thing, just set up the list-address
aliases to fork you a copy at the same time a copy is delivered
to Mj2 - then watch for a while, comparing what you see with
what the subscribers say they sent.
References:
|
|
