Topic: Two easy (?) questions re. ezmlm

[Jesper Holck]

I've installed ezmlm (ezmlm-idx-0.40-2.src.rpm) and and ezmlm-web in order to run a number of mailing lists and it works fine. I just have two questions to more experienced users:

When you run ezmlm on the e-smith server, are the ezmlm options under "template control"; i.e. are they to be changed in template files or just in the files used by ezmlm?

For one of the mailing list recipients, an error occurs every time a mail should be sent to him. In the qmail/current log I can see the following message:

Sender was rejected. Remote host said: 553 Requested action not taken: mailbox name not allowed or chunk too large.

I've checked and double checked the email address of this recipient;  it's OK, and works if I just send him an ordinary mail. Even very small ezmlm mailing list mails are rejected by his server.

Any suggestions?

Jesper, Denmark

[Ray Mitchell]

Dear Jesper
If you instal the web interface from Gordon Rowells contrib ftp site, then you change configuration in Server manager- Mailing lists panel.
http://yourdomain/server-manager
I'm not sure that installing the src rpm is the correct thing to do.
There are 4 rpms you need to instal and Gordon has recently updated 2 of them so check the ftp site for the latest ones.

Copy these to a folder
e-smith-ezmlm-web-1.1.1-05.noarch.rpm
ezmlm-idx-std-0.40-2.i386.rpm
ezmlm-web-2.1-06.i386.rpm
perl-Ezmlm-0.03.1-1.i386.rpm
then do
rpm -ivh *

If your problem is to do with attachment sizes, the default size is quite small.
You can edit msgsize to change this, but if you have a large list of subscribers and send a big attachment to the list, it may slow down your server for a while as the attachment is sent to all subscribers.

cd ~ezmlm/lists/listname
pico msgsize

Regards
Ray Mitchell

[Nate]

Also, some servers may not allow mailing lists(spam prevention).  I have ran into a few of these.  My current spam filter can be configured to reject mailing list email.

[Ray Mitchell]

To be totally correct re the installation:

Copy these to a folder
e-smith-ezmlm-web-1.1.1-05.noarch.rpm
ezmlm-idx-std-0.40-2.i386.rpm
ezmlm-web-2.1-06.i386.rpm
perl-Ezmlm-0.03.1-1.i386.rpm
then do
rpm -ivh *
then do
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot

Regards
Ray Mitchell

[Jesper Holck]

Thanks, Ray. It seems that ezmlm is running quite happily, and a lot of the configuration can be changed with the web interface. I was just afraid that if I changed configuration parameters, e.g. msgsize, directly in an editor, that these changes would later be overwritten when the machine eventually is restarted. But, as I understand you, this will not be the case.

Jesper

[Rod Tinberg]

The version that I'm running DOES overwrite the msgsize file whenever you update the list through server-manager.  I was having a problem sending attachments throught the list, regardless of the msgsize setting.  I was able to solve it by removing a file named "mimeremove".  I believe that file was put in place because I origianlly used the "x" parameter in the setup.  However, taking the x out of the setup does not remove the mimeremove file.

[Gordon Rowell]

Rod Tinberg wrote:
>
> The version that I'm running DOES overwrite the msgsize file
> whenever you update the list through server-manager.

Ray brought this to my attention today. I find it very curious - my panel
and scripts don't touch "msgsize" and on quick inspection of the underlying
code (ezmlm-idx and ezmlm-web), I can't actually see what does
Investigations continue...when I have time.

> I was
> having a problem sending attachments throught the list,
> regardless of the msgsize setting.  I was able to solve it by
> removing a file named "mimeremove".  I believe that file was
> put in place because I origianlly used the "x" parameter in
> the setup.  However, taking the x out of the setup does not
> remove the mimeremove file.

The 'x' flag controls whether that file (and "mimereject"/"mimeallow") is
actually used. "mimeremove" is a feature of ezmlm-idx, and the relationship
is interesting...more digging required.

Thanks for the details.

Gordon

[rswennen]

I'm having the same problem, the msgsize gets overwritten.

Tried to solve it by manualy making the msgsize file read-only, but at that moment the SME web interface doesn't seem to work any more.

I have another problem.
According to the EZMLM manual, you use the -C option in the |/usr/bin/ezmlm-send line of the file editor, in order not to send the mail to the original sender of message (so a mail send to the list is sent to everybody except the sender).
I tried this but it didn't work.  Even with the -C option, senders are still receiving their mails.

Has anyone had the same problem ?? And if so how can you fix it

Regards,

Rohnny