gmane.mail.ezmlm

Re: How to do unsecure moderator posting?

Andy Bradford — 2010-12-11T18:02:37

Thus said torben fjerdingstad on Fri, 10 Dec 2010 12:03:47 +0100:


I have no idea how it is down with 7.0.2, however, you can easily create
a  secret alias  that bypasses  subscriber checking  that your  cron job
sends to  (instead of  the mailing  list address). As  long as  ezmlm is
configured to replace the To header  with the mailing list address, this
should work.

Andy

Re: How to do unsecure moderator posting?

David I. Bell — 2010-12-10T16:47:53

Hello Torben,


I have not moved to 7.0.2.  I still use 6.0.1 and I do it this way:

|/usr//bin/ezmlm-gate '/var/qmail/alias/lists/LIST'  mod

- David Bell

How to do unsecure moderator posting?

torben fjerdingstad — 2010-12-10T11:03:47

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

Bruce Guenter — 2010-11-19T02:48:44

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 1

Announcing ezmlm-idx version 7.1.0

Bruce Guenter — 2010-11-04T01:37:20

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

Jake Jones — 2010-11-01T23:41:41

I'm new to ezmlm and having a difficult time understanding how to use remote
administration to create and manage sublists. I don't have direct access to
the server or root configuration files since I'm running on a hosted
service. is there any way to do this by sending special instructions to my
list through an email?  where can I find how to accomplish this?

Thanks

Re: old patch to fix Outlook handling of digest attachments

Bruce Guenter — 2010-08-19T15:51:22

That would help.  Too bad the content type isn't enough of a clue bat.


It has been that way since I first started tracking the sources.


Done.

old patch to fix Outlook handling of digest attachments

Glen Stewart — 2010-08-08T02:22:12

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.

PROMOÇÃO WEB-SITES

AC6 Design — 2010-05-03T21:56:36

Re: Qmail-Specific?

Bruce Guenter — 2010-02-19T00:51:31

The issues are: Performance -- with one message per recipient, the MTA
has to separately queue up potentially thousands of messages.  Disks are
getting faster, but that's still an expensive proposition, and can
seriously impact other users of the disk on the same system.
Reliability -- does the message get to all the recipients exactly once?
If the sending process is interrupted (due to taking a long time to
queue up all the messages), there is the address list could easily
change before the next run.  With the introduction of non-file address
list databases, this can mean not just duplicated delivery occasionally
but actually reordering the list for some kinds of storage.

So, to make this work reliably, ignoring the performance issues, it
needs to store the message to be delivered plus a snapshot of the
address list.  In order to handle interruptions, it also has to store an
indication of which addresses have been delivered, and some mechanism
needs to be set up to restart delivery if needed.


This does

Re: Qmail-Specific?

Sabahattin Gucukoglu — 2010-02-15T22:53:48

If I were still on Sendmail, I'd solve the first with the DeliveryMode=Q kludge.  It isn't perfect, but it's the established way to get high-throughput Sendmail.  Otherwise you'd have to change the submission protocol like SMTP to recognise multiple-message transactions as a single transaction, and that's not something *any* MTA is designed to do, by design, seeing as how transactions for multiple recipients are normally addressed per message.  The closest to such a thing in an existing MTA might be ETRN, with automatic queue processing switched entirely off.

I'm still not clear why you need special handling in the case of interruptions: if your submissions to the MTA are interrupted, start where you left off; if the queue run is interrupted, the MTA will simply begin where it left off.  Why do you want to ensure an entire VERP-style delivery is transactional?  I must be missing something.

Oh, well, if it's so unimportant a consequence of a failure to have a retry occasionally send duplicates in exchange f

Re: Qmail-Specific?

Bruce Guenter — 2010-02-15T15:58:42

I don't see there doing much point is such a proxy.  Since ezmlm doesn't
itself do QMQP, it would be necessary at some point to add a protocol
sender into ezmlm itself to interoperate with non-qmail systems (unless
installing mini-qmail is considered acceptable of course).  At that
point, basically any protocol is possible.

However, given that the MTA under discussion accepts QMQP and that QMQP
provides *exactly* the semantics currently required by ezmlm (VERP for
posts, and envelope follows the message) with the minimum amount of
overhead, that is certainly the path of least resistance in the case of
adding a protocol, and would be my first target if I go down that route.


Unsubscription already uses the sender's return address.  The problem
comes when the subscriber is receiving messages forwarded to them from
some other address, and can't (for whatever reason) determine from the
headers what address is actually subscribed.  With customized outgoing
messages, the sender could put an unsubscribe link int

Re: Qmail-Specific?

Sabahattin Gucukoglu — 2010-02-15T00:36:34

Ignore Reply-To, one-time avoidance of autoresponders on DJB's lists.

On 11 Feb 2010, at 20:36, Bruce Guenter wrote:
On Thu, Feb 11, 2010 at 01:13:08PM +0000, Sabahattin Gucukoglu wrote:

I'll take a closer look later on, but I thought it'd be much harder than it looks.


Yes, QMQP or ESMTP with PIPELINING would do it best for Postfix since that only requires starting up the server process once to queue the delivery, and not much overhead to fork an already initialised instance.


I'm still evaluating all the other MTAs to find "The right one for me".  So far I've found two (Courier and XMail) which have built-in list distribution features: Courier is closest to Qmail and probably needs not very much change to get ezmlm going ... and indeed Google shows this to be the case, at least for inbound delivery.  Courier supports a facsimile of the .qmail-* support, and indeed can be compiled and configured for this.  It has subscriber management using its mail processor, maildrop, called courier-mlm, which does si

Re: Qmail-Specific?

Bruce Guenter — 2010-02-11T20:36:20

If the wrapper script could figure out the right variables, sure.  You'd
have to adjust the ezmlmrc as well to build the right links and such.


If I'm reading that right, this would seem to require that ezmlm send to
Postfix via QMQP (or SMTP).  I don't know that the sendmail interface is
adequate to the needs of ezmlm.  What happens if there are more
recipients than can be passed on the command line, for example?


That would have to be sick, yeah.


I am willing to help.  I would love to be able to say that ezmlm-idx
works with more than just qmail.


This presumes that connection caching is a net benefit for a MTA.


DSNs can't inject the sender's email address into the header or footer,
giving customized unsubscribe instructions (among other things).


Actually, the biggest problem with doing message personalization in
ezmlm is not connection caching or other delivery issues.  How do you
reliably queue up large numbers of messages without starving other users
of the disk and/or the queue (depending on

Re: Qmail-Specific?

Sabahattin Gucukoglu — 2010-02-11T13:13:08

Okay, I found the spec, but it's by DJB and apparently just for DJB, seeing as how ESMTP PIPELINING seems to be better suited to this for all but the smallest deliveries ...

However, I find that Postfix has the ability to accept qmqp requests, which means sending from ezmlm to postfix direct is possible (google "ezmlm postfix").  Tangentially, I also found alternative mailing list managers, Enemies of Carlotta (no longer maintained) and mlmmj, both of which remove this requirement, behave quite like ezmlm, and work with any mailer using local-part additional data, something+other or something-other.

Can a wrapper script do this to pass the necessary environment to ezmlm programs, given that it can parse out the extension part?


http://www.postfix.org/VERP_README.html

And some sick bastard has even got it going with Sendmail's rewriting rules:
http://mlmmj.org/man/sendmail

Ezmlm-idx's database and MIME support are attractive features.  I'd love it if (ever I find the time, and) it worked with other MTAs

Re: details of the *-subscribe function

Bruce Guenter — 2010-02-10T02:25:06

The 6 doesn't need escaping, however as you discovered the & did.
Since the file is being interpreted by the shell (via qmail), here's
what it effectively saw:

/usr/bin/ezmlm-get '/var/qmail/alias/Austrian' *Q3[%\,25B &
0\60

After backslash (quote) removal, you get:

/usr/bin/ezmlm-get '/var/qmail/alias/Austrian' *Q3[%,25B &
060

That's why it was trying to run "060" and not finding it.

Re: Qmail-Specific?

Bruce Guenter — 2010-02-10T02:09:42

Technically, QMQP isn't qmail specific, though currently all QMQP
servers that I am aware of deliver to qmail.

The mechanism for ezmlm accepting messages is currently keyed to how
qmail handles things -- the dot-qmail mechanism, and specifically
wildcard handling through .qmail-something-default.  I understand
Postfix at least has a similar but not quite identical mechanism, but it
would require adapting ezmlm.

The mechanism for delivering messages requires qmail-queue.  This too
could be adapted to any MTA that accepts a raw envelope in some form,
except for one detail: VERP.  ezmlm depends on all list posts having a
unique envelope sender in order to most efficiently handle bounces.  I
have no idea how easy it would be to adapt that to another MTA.

So that's pretty much three issues that are specific to qmail (wildcards
for incoming messages, qmail-queue for delivery, and VERP), the first
two of which should be easy to adapt to a different MDA or MTA.  If
there are other other MTAs that do something eq

Re: [ezmlm ipv6?]

Bruce Guenter — 2010-02-10T02:18:35

There should be no patching required for ezmlm -- it does not actually
make any sockets or connections itself, IP or otherwise.  When it has
qmqpservers, it simply invokes qmail-qmqpc with the listed servers on
the command line.  It would be qmail-qmqpc that needs patching.

Re: Qmail-Specific?

Sergiusz Pawlowicz — 2010-02-10T01:25:41

QMQP is definitely not needed for ezmlm, but of course it may be an
advantage if you have a really big amount of subscribers.

what is specific? of course dot-qmail :)

s.

Qmail-Specific?

Sabahattin Gucukoglu — 2010-02-09T21:23:15

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

Cheers,
Sabahattin

Re: details of the *-subscribe function

Tres Melton — 2010-02-01T03:17:07

Problem solved.  See below for details and thank-you.

On Sat, 2010-01-30 at 11:19 -0700, Andy Bradford wrote:

net-mail/ezmlm-idx-6.0.0    (in Gentoo)


As best as I can figure it defaults to:

/var/qmail/alias/Austrian/.qmail-austrian-default

as there is no 

.qmail-austrian-subscribe 

entry.  That is a pointer to:

/var/qmail/alias/Austrian/manager

and I've looked in there and can't see a "060" file.  It looks pretty
standard to me.  However there is a line like this:

|/usr/bin/ezmlm-get '/var/qmail/alias/Austrian' *Q3[%\,25B&0\60

For some reason the '&' wasn't escaped upon creation of the list.
Changing that to '*Q3[%\,25B\&0\60' fixed everything.  I'm still not
sure why the '6' needs to be escaped and figure that the escaping script
simply missed the right character needing escaping.


Thanks again for your reply.  It pointed me in the right direction.