[Mailman-Users] [SOLVED] Re: message held for moderation "no member", adding address: "already member"
kardan at riseup.net
Wed Jul 31 22:38:28 CEST 2013
On Sat, 27 Jul 2013 16:18:03 -0700 Mark Sapiro <mark at msapiro.net> wrote:
> >> 4. rejection = _('''Blind carbon copies or other implicit
> >> destinations are not allowed. Try reposting your message by
> >> explicitly including the list address in the To: or Cc: fields.''')
> >> 4.
> >> "Blindkopien ('BCC:'), oder weitere enthaltene Zieladressen,
> >> sind nicht erlaubt. Tragen Sie die Adresse der Mailinmgliste in das
> >> 'An:'- oder 'Cc:'-Adressfeld ein und senden Sie Ihre Nachricht
> >> bitte noch einmal."
> > This message is perfect and should have been shown instead of 1
> > ("the sender is not part of the list"). I don't know why this went
> > wrong.
> I don't know why you saw the wrong message. Two possibilities occur
> two me. This could be verified only by looking at the various held
> message entries in Mailman's 'vette' log.
The log said: "Reason: Blind carbon copies or other implicit
destinations are not allowed. Try reposting your message by explicitly
including the list address in the To: or Cc: fields."
> The first, and I think more likely possibility is the an initial post
> was held as a non-member post and the poster got a notice and
> subscribed (You could also check Mailman's 'subscribe' log) before
> you tried to subscribe him.
Unfortunately this is not the reason as the poster is a member since
the list was created and even is one of the moderators.
(Sorry, I didn't tell before.)
> The only other possibility I can think of is the German message
> catalog in the Mailman installation that supports your list has been
> modified or corrupted somehow and is displaying the wrong translation
> for strings 3 and 4.
Makes sense but seems unlikely. Which file is the right one to check?
> I just thought of a third possibility which seems more likely that the
> two above. See below.
> >> The 'reasons' are what appear in the admindb summary and the
> >> notices to the admin and user. the 'rejections' appear only in the
> >> admindb detail as the default rejection message and in rejection
> >> messages if the default is not overridden.
> > If I would have read the first moderation message properly -
> > ("Mailadresse der Liste steht nicht im Mailheader (vielleicht wegen
> > einer Weiterleitung?)") - I just had overlooked the misleading
> > reason in the admindb ("the sender is not part of the list").
> That message can be seen in the admindb even though the user is a list
> member in the following way.
> I explained before how SENDER_HEADERS are consulted to deterrmine if a
> post is from a list member. However, once a post is held and displayed
> in the admindb interface, admindb uses a different method to determine
> the sender. If USE_ENVELOPE_SENDER is set to Yes in mm_cfg.py (or
> changed to Yes in Defaults.py), admindb will take the contents of a
> Sender: header if any in preference to From:.
USE_ENVELOPE_SENDER = No
there is no Sender defined in the header.
> In this case, the message could be From: a member but have a Sender:
> which is not a member, and the message could be held for some other
> reason like 'too big' or 'implicit destination' and the left hand side
> of the admindb summary will say the sender is not a list member.
Thanks a lot for the explanations and sorry for my delay. The sender
agreed to send messages to the list separatedly instead of BCCing in
the future. Though I like to help to track this down to see if it is a
Mailman bug or misconfiguration.
I send you the original mail and the mailman reminder so you can
inspect the headers.
Kardan <kardan at riseup.net>
Encrypt your email: http://gnupg.org/documentation
Public GPG key 9D6108AE58C06558 at hkp://pool.sks-keyservers.net
fpr: F72F C4D9 6A52 16A1 E7C9 AE94 9D61 08AE 58C0 6558
More information about the Mailman-Users