Mail problems to the PLUG list

[Art Wagner]

This is a multi-part message in MIME format.
--------------F806AC12485AD2D680BA5F17
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> David Demland wrote:
> 
> I got Cox@home and I signed up for plug again
> from home. This way I can get mail both at work
> and at home. But every time I have posted from
> home the mail never makes it to the mail list
> here. I got the signup e-mail from the list, but
> I get nothing else. Any ideas?

David;
What software are you running on your home system?
What sort of error are you getting when attempting 
to post to the list? There have been some problems
using Netscape 4.6 - 4.72 with Linux. The problem
shows up as a error in the Mailman program which
causes the posted message to hang up in the
Mailman
program and fail to post to the list. I am
attaching
a README.NETSCAPE file from the Mailman folks
which
might help.
Art Wagner
--------------F806AC12485AD2D680BA5F17
Content-Type: text/plain; charset=us-ascii;
 name="README.NETSCAPE"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="README.NETSCAPE"

Mailman - The GNU Mailing List Management System
Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA

Some of your users may experience problems sending mail to a
members-only list, if they are using Netscape Communicator as their
MUA.  Communicator 4.6 on Linux has been observed to insert bogus
unqualified Sender: headers -- i.e. Sender: headers with only the
username part of the email address.  Other version of Netscape may
also have the same bug.

Members-only lists use Sender: as the first field to authenticate
against, so if Sender: exists in the email message, but it is
unqualified, it will never match a mailing list member's address, and
their post will always be held for approval.

In the future, Mailman will improve its algorithm for finding a
matching address, but in the meantime, M. A. Lemburg <mal@lemburg.com> 
provides the following advice.  You can send this snippet to any user
whose posts are being held for seemingly no reason.

    Edit the two .js files in your .netscape directory (liprefs.js and
    preferences.js) to include the function call:

    user_pref("mail.suppress_sender_header", true);

    BTW, the binary includes a comment which says that this is only
    necessary on Unix.

    Since Communicator regenerates this file upon exit, the change
    must be done when Communicator is not currently running.  With the
    next start, it will stop adding the Sender: header and things
    start to work like a charm again.

The reason things start to work again, is that Mailman falls back to
authenticating the From: header if the Sender: header is missing.



Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:

--------------F806AC12485AD2D680BA5F17--