Fwd: ezmlm warning

Lee Sharp <[email protected]>
Newsgroups gmane.comp.security.firewalls.m0n0wall
Message-ID <[email protected]>
I got this today...  I am working with the e-mail provider, and they 
want to talk with the person running the list.  Who is that? :)

			Lee


-------- Original Message --------
Subject: ezmlm warning
Date: 9 Feb 2011 14:59:06 -0000
From: [email protected]
To: [email protected]

Hi! This is the ezmlm program. I'm managing the
[email protected] mailing list.

I'm working for my owner, who can be reached
at [email protected].


Messages to you from the m0n0wall 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 m0n0wall mailing list,
without further notice.


I've kept a list of which messages from the m0n0wall 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:
    <[email protected]>

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
    <[email protected]>

Here are the message numbers:

    36810

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

Return-Path: <>
Received: (qmail 85817 invoked for bounce); 28 Jan 2011 21:18:27 +0100
Date: 28 Jan 2011 21:18:27 +0100
From: [email protected]
To: [email protected]
Subject: failure notice

Hi. This is the qmail-send program at s0.m0n0.ch.
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.

<[email protected]>:
64.18.4.10 does not like recipient.
Remote host said: 530 5.7.0 Must issue a STARTTLS command first - on 
relay of: MAIL 
FROM:<[email protected]>
Giving up on 64.18.4.10.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.