On Tue, 13 Sep 2005 20:10:52 -0400, Benjamin Scott <[EMAIL PROTECTED]>
wrote:
Hello,
I just got another day-late-dollar-short message from Rob for SLUG
again (hi Rob!). I decided to examine the headers and noticed that the
message appears to have spent about 12 hours bouncing around inside
<rogue.codemeta.com>. I just wanted to make sure that is expected.
It shouldn't be approval delays, since Rob's address is on the
approved senders list.
I can't remember if this particular issue has been raised before. My
apologies in advance if it has.
Actually, Ben, it was an approval delay. Looking back, there were two
problems present.
1) The announcement was from an unapproved address.
2) The announcement was sent the day of the meeting.
The first is because mailman only does exact matching on sender addresses.
The sender domain for this message was example.com, but the approved sender
domain is q.example.com. No match, so it needed approval.
The second is all too common. Depending on how often the approvers check
the queue, a message can wait a while. And in this case, the delay was
made worse by the fact that Rob's sending address was also not the
subscribed address for the discuss list (announce feeds into discuss).
So a SECOND approval was needed before it got to everybody.
The solution? Be consistent in your posting address (register multiple
addresses if you must), and have longer lead times on your announcements.
Mark
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
_______________________________________________
gnhlug-org mailing list
[email protected]
http://mail.gnhlug.org/mailman/listinfo/gnhlug-org
