How to do unsecure moderator posting?

Porting mailing lists from ezmlm-idx 0.53 to 7.0.2, I am
stuck on this:

Some lists are set up with posting moderation. At the
same time, the moderator (cron bot) needs to post without
having to confirm. How is that done with 7.0.2?

I am aware of the security issues.

With 0.53 it was accomplished by adding a line 2 in editor, after
ezmlm-reject, like this:
|/usr/bin/ezmlm-issubn -n '/var/qmail/alias/lists/LIST/mod' || { /usr/bin/ezmlm-send
'/var/qmail/alias/lists/LIST' ; exit 99 ; } 

The config flags were -ABCDeFGHIJKlmNOpQrSTUVWXYZ

torben

Announcing ezmlm-idx version 7.1.1

Greetings.

I have just uploaded the 7.1.1 release of ezmlm-idx to:
	http://www.ezmlm.org/archive/7.1.1/

ezmlm-idx-7.1.1, 2010-11-18
===========================

- Fixed bug in getln2 function that prevented error handling.

- Fixed bug in ezmlm-cron that prevented parsing of spaces.

- Fixed unclosed file descriptor on error path in ezmlm-cgi.

Translation statistics:

Translation ch_GB is out of date: 6 old texts 168 old messages
Translation cs is out of date: 6 old texts 166 old messages
Translation da is out of date: 6 old texts 166 old messages
Translation de is out of date: 1 old text
Translation es is out of date: 5 old texts 168 old messages
Translation fr is out of date: 5 old texts 165 old messages
Translation hu is out of date: 5 old texts 166 old messages
Translation id is out of date: 3 old texts 3 old messages
Translation it appears up to date
Translation ja is out of date: 5 old texts 168 old messages
Translation nl is out of date: 3 old messages
Translation pl is out of date: 12 old texts 166 old messages
Translation pt is out of date: 6 old texts 165 old messages
Translation pt_BR is out of date: 6 old texts 165 old messages

Announcing ezmlm-idx version 7.1.0

Greetings.

I have just uploaded the 7.1.0 release of ezmlm-idx to:
	http://www.ezmlm.org/archive/7.1.0/

ezmlm-idx-7.1.0, 2010-11-03
===========================

- Added support for SQLite3 subscriber databases.
  Thanks to Mike Tedder.

- Added support for wildcard addresses in all address databases.

- Added support for qmqpservers to all ezmlm-idx programs.

- Added support for decoding sender addresses mangled with a BATV "btv1" tag.

- Added support for custom subject lines to ezmlm-get (for digests).

- Added a new "omitbottom" control file, equivalent to the -B option for
  both ezmlm-get and ezmlm-manage.

- Modified the (un)subscribe procedure to not require confirmation
  before telling the sender they were already on (or off) the list.

- Renamed to "setup" makefile target to the more standard "install".

- Modified ezmlm-split to exit silently if there is not "split" file,
  and added it back into the "manager" file to properly handle subscribe
  and unsubscribe requests destined for sublists.

using remote administration to create/manage sublists

old patch to fix Outlook handling of digest attachments

I'm preparing to switch to Ezmlm-Idx 7.0.2 and am reviewing patches I've 
been running for years.

In this thread, some discussion about the Outlook patch:
http://blog.gmane.org/gmane.mail.ezmlm/month=20040701

...that attaches the digested messages with extension '.eml' instead of '.ezm'

Outlook is supposed to understand the former, and treat it as a separate
rfc822 message

I see in 7.0.2 that the code has reverted to using .ezm (or just doesn't 
use the patch I use)

In ezmlm-get.c, change 2 instances of

qmail_puts(&qq,".ezm\"\n\n");

to

qmail_puts(&qq,".eml\"\n\n");

I'd like to propose this be rolled into the next release, as I'm not 
aware of any harm it does, and it did seem to relieve the problem of 
useless digests for my subscribers.

--

-- 
Associate.com - THE Place to Associate!                  http://freegroups.net
Is Your E-mail Group Here?  See http://freegroups.net/faq/your-group-here.html

PROMOÇÃO WEB-SITES

Qmail-Specific?

What parts of ezmlm are qmail specific, apart from the QMQP?  Why can only qmail use it?

Cheers,
Sabahattin

details of the *-subscribe function

Hi people,	(first post to this list)

I have a few email lists and none of them seem to honor the address:

<list-name>-subscribe <at> host.domain.tld

And I can't figure out why.  My first question is how do I go about
diagnosing this problem in an efficient manner.  Currently I send an
email and wait a week for qmail to give up.  The more specific question
is what is wrong?  I get this back:

        Hi. This is the qmail-send program at host.domain.tld.
        I'm afraid I wasn't able to deliver your message to the following addresses.
        This is a permanent error; I've given up. Sorry it didn't work out.

        <list-name>-subscribe <at> host.domain.tld
        /bin/sh: 060: command not found
        I'm not going to try again; this message has been in the queue too long.

        --- Below this line is a copy of the message.
        ...

I do not have a shell in /bin/sh but I have a shell in /bin/bash and a
symbolic pointer from /bin/sh -> /bin/bash so it should work shouldn't
it?  Although it looks like bash is looking for the command "060" and
that makes even less sense.  How can I check for this?

Is the command that is failing qmail-local?  

How do I trace a message through the system?  I really don't need
baby-sitting, just a pointer to a good tutorial please.  

Should there be a .qmail-<list-name>-subscribe file?

Thanks in advance,
Tres
--

-- 
RiverRat  a/k/a  Tres Melton,
Believer in Freedom, Crusader for Liberty, Supporter of Dr. Ron Paul
System Administrator of https://PikesPeakEconomicsClub.com
System Administrator of https://GreenDragonTavern.com

[ezmlm ipv6?]

hello, it looks

$ echo "2001:41d0:1:819c::b:a" > /home/alias/list/qmqpservers/0

gives

ezmlm-send: fatal: temporary qmail-queue error: qq unable to read
configuration (#4.3.0)

of course qmail knows how to deliver it, but not ezmlm. is someone
working on ipv6 patches?

thanks,
s.

per list message body limit

Hi,

 How can I put a message body limit for the messages sent to a specific
mailing list?

                   Doruk

--
FISEK INSTITUTE - http://www.fisek.org.tr

upgrading from ezmlm-idx 0.40 to 7.0.2: 'key' not found

Hi everyone,

After upgrading to 7.0.2; ezmlm-list started to complain that:

[perlmail <at> x18 ~]$ ezmlm-list testlist/mod/
ezmlm-list: fatal: testlist/mod//key does not exist
[perlmail <at> x18 ~]$ ezmlm-list testlist/digest
ezmlm-list: fatal: testlist/digest/key does not exist

Glancing at the code it seems that the code that reads the key was  
moved into a common library; but ezmlm-list didn't use to (and  
shouldn't need to) read the key file ...

  - ask

--

-- 
http://log.perl.org/ - http://askask.com/  - http://develooper.com/