Issue 23273 - EZMLM drops users for no reason
Summary: EZMLM drops users for no reason
Status: CLOSED DUPLICATE of issue 23274
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: issues@www
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-07 22:55 UTC by grsingleton
Modified: 2004-09-19 18:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description grsingleton 2003-12-07 22:55:43 UTC
EZMLM drops users for no reason. Sometimes silently and other times because it
cannot or won't deal with the fact that some sites protect themselves against
virii. For example, today my system rejected a message from ezml because it
contained a virus. Ezmlm then sent a message to the effect that my name would be
dropped because of the fact I will not allow virii to be propagated to my system.

Here's is the message I received from exmlm/qmail:

Return-Path:
       
<users-return-warn-1070812837.homigdnfkdobionmmlph-gerry=pathtech.org@groupware.openoffice.org>
Received: from openoffice.org (s002.sfo.collab.net [64.125.133.202]) by
        pathtech.org (8.12.9/8.12.9) with SMTP id hB7G0cJc011974 for
        <gerry@pathtech.org>; Sun, 7 Dec 2003 11:00:39 -0500
Received: (qmail 10333 invoked by uid 5302); 7 Dec 2003 16:00:37 -0000
Mailing-List: contact users-help@groupware.openoffice.org; run by ezmlm
Date: 7 Dec 2003 16:00:37 -0000
Message-ID: <1070812837.10328.ezmlm-warn@groupware.openoffice.org>
From: users-help@groupware.openoffice.org
To: gerry@pathtech.org
Content-type: text/plain; charset=us-ascii
Subject: ezmlm warning
X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang)
Status:   
X-Evolution-Source: pop://gerry@mail.pathtech.org
Mime-Version: 1.0

Hi! This is the ezmlm program. I'm managing the
users@groupware.openoffice.org mailing list.


Messages to you from the users mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the users mailing list,
without further notice.


I've kept a list of which messages from the users mailing list have 
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
   <users-get.123_145@groupware.openoffice.org>

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
   <users-index@groupware.openoffice.org>

Here are the message numbers:

   891

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 5135 invoked for bounce); 24 Nov 2003 16:36:51 -0000
Date: 24 Nov 2003 16:36:51 -0000
From: MAILER-DAEMON@openoffice.org
To: users-return-891-@groupware.openoffice.org
Subject: failure notice

Hi. This is the qmail-send program at openoffice.org.
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.

<gerry@pathtech.org>:
205.189.41.5 failed after I sent the message.
Remote host said: 554 5.7.1 Virus found in mail - rejected

Note that neither exmlm nor qmail stripped the virus so the message bounced. If
I miss these messages or they are rejected because ezmlm/qmail does send a
stripped and/or non-html message, I lose my membership. 


NOT GOOD!!
Comment 1 flibby05 2004-02-10 15:15:43 UTC
grsingleton, does this problem still persist?

>> <gerry@pathtech.org>:
>> 205.189.41.5 failed after I sent the message.
>> Remote host said: 554 5.7.1 Virus found in mail - rejected

(i am not sure about the 554 error code from your mailhost. i am really not a
SMTP error-code guru, but maybe 554 indicates that your mailsystem is not
available "_at all_", not that it will not accept a single message because it
contains a virus.. Because then the reaction of EZMLM would be correct, as it
makes no sense to send messages to a nonexistent mail service.)
Comment 2 flibby05 2004-02-10 15:20:01 UTC
just found issue 23274, so please ignore my last comment
Comment 3 Rainer Bielefeld 2004-02-23 09:25:52 UTC
Hi grsingleton, 

pls. read my comments in issue 23274!

Rainer
Comment 4 bernd.eilers 2004-02-25 19:14:06 UTC
maxweber: The SMTP spec (rfc2821) says that return code 554 means the 
following:

554 Transaction failed  (Or, in the case of a connection-opening
          response, "No SMTP service here")

So this could be both just a single mail failing or the mailserver not 
accepting messages at all.


grsingleton: The sample bounce warning you described is pretty normal when 
your mailserver rejects a message. But there will be an additional probe 
message afterwards and this should normally go through even on very strange 
mailserver configurations and that means that finally EZMLM will see that 
mails to you can be send it will not unsubscribe you from the list. 

What I think is that in your case your mailserver configuration is 
just "overprotective" against virri attacks. Thinking that every mail 
containing a subject line like "test" or "failure notice" (as in your case) 
or "I love you" or "Hi" would contain a virus and should thus be rejected just 
because the same subject line was used by some virus someday is just not a 
good think to do as there are pretty much more "normal" messages that might 
also use those subjects without containing any virus at all. You should talk 
to your mailserver administrator about the mailserver configuration and better 
suited solutions to detect and reject virri while letting normal messages pass 
through. If you really get unsubscribed from a mailing list which i doubt than 
probably even the "probe" message that does AFAIK not contain a sample of a 
bounced message and does certainly NOT contain a virus will get pass your 
mailserver and would be rejected as a "could contain a virus" instead and you 
would be suffering from an extrem unsuitable mailserver configuration.

Most of this has already been discussed in issue #23274# which was closed as 
WORKSFORME. I will close this issue as a duplicate of #23274#.




*** This issue has been marked as a duplicate of 23274 ***
Comment 5 stx123 2004-03-22 16:12:36 UTC
For technical reasons we have to move the issue to another subcomponent tan 'www'.
Sorry for bothering you with this generated notification message. There is no
need for any action from yor side.
Thanks for your understanding, Stefan
Comment 6 Rainer Bielefeld 2004-09-19 18:08:35 UTC
.