[prev in list] [next in list] [prev in thread] [next in thread]
List: majordomo-users
Subject: [majordomo-users] The daily digest for Majordomo-Users V10 #12
From: majordomo-users-owner () greatcircle ! com
Date: 2010-05-24 10:20:03
Message-ID: 20100524102029.A251D690356 () mycroft ! greatcircle ! com
[Download RAW message or body]
The daily digest for Majordomo-Users
Volume 10 : Issue 12 : "text" Format
Messages in this Issue:
Re: Approval process not working
----------------------------------------------------------------------
Date: Sun, 23 May 2010 06:50:39 -0700
From: Sean Casey <mj@scaseyllc.com>
To: majordomo-users@greatcircle.com
Subject: Re: Approval process not working
Message-ID: <4BF932AF.9010408@scaseyllc.com>
Frank Collette IV said on 5/22/2010 7:13 PM:
> Sean,
>
> Thanks for your reply! After some testing with your reply, things still
> were not working, so I decided to try using Squirrelmail instead of
> Gmail to send the original email and it worked!
>
> Any idea if there have been complains from admins about their emails not
> working properly when sending the original email from Gmail?
>
> --Frank
I've not had any issues with gmail, but I wouldn't expect any
foreign-hosted, web-based email client to allow sufficient control of
message headers and/or content to facilitate the approval process. It's
even a struggle to send Approved: mail with most windows clients,
although I've had good luck with the second option in the instructions:
...If your mailer does not allow you to add additional headers, you can
add the line:
Approved: sekrit
as the first line of the message, followed by a blank line (which is
required for your message to be sent properly) followed by the text of
your message. The Approved: line and one following blank line will be
deleted and the message will be passed without being checked. The blank
line is important...
Sean
BTW, replies to this list are directed to the sender by default. It's a
good idea to send replies to the list so that others may benefit (or
not) from the discussions.
>
> On Sat, May 22, 2010 at 7:01 PM, Sean Casey <mj@scaseyllc.com
> <mailto:mj@scaseyllc.com>> wrote:
>
> Frank Collette said on 5/22/2010 7:51 AM:
>
> Hey guys/gals,
>
> I'm new to the list so please be gentle!
>
> I'm using Directadmin, exim, and majordomo. I've setup my first
> mailing
> list and have set it to be moderated. I've setup a 2nd mailing
> list and
> subscribed the addresses that I want to be administrators of my
> first
> list and set the restrict_post option to the 2nd mailing list.
>
> When I send an email from one of the admin emails to
> newsletter@domain.com <mailto:newsletter@domain.com>
> <mailto:newsletter@domain.com <mailto:newsletter@domain.com>>,
> it gets flagged as
>
> needing approval. This to me, doesn't make sense but I play
> along. I
> get an email to the moderator account, which happens to be the same
> email I sent the email from in the beginning. Email subject from
> owner-newsletter reads "BOUNCE newsletter@domain.com
> <mailto:newsletter@domain.com>
> <mailto:newsletter@domain.com <mailto:newsletter@domain.com>>:
> Approval required:".
>
>
> I have tried replying with approved: password, I've tried forwarding
> with approved: password, I've sent the approved message to
> newsletter@domain.com <mailto:newsletter@domain.com>
> <mailto:newsletter@domain.com <mailto:newsletter@domain.com>>,
> owner-newsletter@domains.com
> <mailto:owner-newsletter@domains.com>
> <mailto:owner-newsletter@domains.com
> <mailto:owner-newsletter@domains.com>>, and
> newsletter-approve@domain.com
> <mailto:newsletter-approve@domain.com>
> <mailto:newsletter-approve@domain.com
> <mailto:newsletter-approve@domain.com>> and
>
> the newsletter@ just sends me another approval request for the
> approved:
> email.
>
> To me, it seems as though the approve script isn't working
> properly, but
> I have no idea where to start to find the issue. Maybe I'm just not
> doing something right.
>
> Any advice is appreciated!
>
> Thanks, Frank
>
> I'm not finding the "default" instructions for approving messages,
> but I did find this explanation (which I think is a copy of the
> "default" instructions):
>
> ====================================
> Approving Bounced Messages via Email
> =======================================
> To approve a message via email, follow these directions _exactly_:
>
> 1) Save the original message (the body of the message you received
> from Majordomo) in a file. The portion you need will consist of
> the headers of the original message, followed by a single blank
> line, followed by the text of the original message. You do not
> need to include any of the headers of the Majordomo message
> which
> contained the original message. Here's a quick example:
>
> From: majordomo@list.server |
> To: your-list-approval@list.server | Don't want these headers
> Subject: BOUNCE: taboo_header found |
> - Blank line
>
> >From list-member@her.site date |
>
> Received: some long routing info | Headers of original message;
> From: list-member@her.site | You want these. It's OK if you
> To: your-list@list.server | don't have the first line.
> Subject: Just a message |
> - Blank line, you _must_ have
> this!
> Hello. I'm just writing to |
> consume some bandwidth and | Message body; include all of
> take up space in your mail | this.
> spool! |
>
> Basically you want everything after (and not including) the
> first
> blank line of the full message you received from Majordomo.
>
> 2) Edit the file to insert a line that says "Approved:
> password" (where
> "password" is the password for your list) at the top, before the
> original message, with absolutely no intervening space.
> Note the
> capitalization of the word "Approved", the colon after it,
> and the
> space after the colon:
>
> Approved: sekrit
>
> >From list-member@her.site date
>
> Received: some long routing info
> From: list-member@her.site
> To: your-list@list.server
> Subject: Just a message
>
> Hello. I'm just writing to
> consume some bandwidth and
> take up space in your mail
> spool!
>
> 3) Send this edited file back to the posting address for your
> list (NOT
> to Majordomo). You should make sure that your mailer
> doesn't try
> to do anything like include your prepared mail as an attachment,
> encode it somehow, indent every line, or add anything extra
> to the
> beginning or end of the message. There are mailers that will do
> pretty horrible things to messages before they are sent; you
> should
> take care that you aren't using one - or, if you are, that
> you have it
> configured to pass your text on unadulterated.
>
> This time around, Majordomo will notice the "Approved:" line and
> check it
> against your list password. If it matches, Majordomo will strip off the
> header of your message and the "Approved:" line (leaving just the
> original
> message), and send the original message on through.
>
> Even your own messages may be bounced to you for approval. To send
> out your
> own message without server checks (perhaps you know it contains
> something
> the list server will complain about) you can pre-approve the message
> in one of
> two ways:
>
> If you're using a mailer that can add additional headers, add one
> like the
> following:
>
> Approved: sekrit
>
> Its precise location within the headers is not important.
>
> If your mailer does not allow you to add additional headers, you can add
> the line:
>
> Approved: sekrit
>
> as the first line of the message, followed by a blank line (which is
> required for your message to be sent properly) followed by the text
> of your
> message. The Approved: line and one following blank line will be
> deleted
> and the message will be passed without being checked. The blank line is
> important because it is used to differentiate between a pre-approval
> and the
> approval of a bounced message, outlined above.
>
>
------------------------------
End of [majordomo-users] The daily digest for Majordomo-Users V10 #12
**********
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic