On Tue, 2002-01-15 at 23:22, Barry A. Warsaw wrote:
> A special place in hell is reserved for the authors of MSExchange who
> not only decided to roll their own, but also made the brilliant
> decision to include absolutely nothing in the bounce message which
> even hints at the remotest morsel of
> "aw" == alex wetmore <[EMAIL PROTECTED]> writes:
aw> Huh? Microsoft Exchange 2000 (you didn't specify a version,
aw> assuming you are talking about the latest version) sends RFC
aw> 1894 complaint NDRs.
Dunno, but I'll have to look more closely when [EMAIL PROTECTED] gets
an
On Tue, 15 Jan 2002 [EMAIL PROTECTED] wrote:
> A special place in hell is reserved for the authors of MSExchange who
> not only decided to roll their own, but also made the brilliant
> decision to include absolutely nothing in the bounce message which
> even hints at the remotest morsel of a clue
> "JCL" == J C Lawrence <[EMAIL PROTECTED]> writes:
JCL> I knew I should have added an "in practice" there, but by the
JCL> time I thought of that I got distracted by a phone call, hit
JCL> send, and, well...
Yeah, I knew you knew, JC. :)
JCL> auto-bounce all Exchange conn
On Tue, 15 Jan 2002 18:22:19 -0500
Barry A Warsaw <[EMAIL PROTECTED]> wrote:
>> "JCL" == J C Lawrence <[EMAIL PROTECTED]> writes:
>> The problem is that Mailman attempts the parse the body of a
>> bounce to determine subscriber address. As the message body
>> format is not standardised thi
> "JCL" == J C Lawrence <[EMAIL PROTECTED]> writes:
JCL> The problem is that Mailman attempts the parse the body of a
JCL> bounce to determine subscriber address. As the message body
JCL> format is not standardised this is an error prone process
JCL> (which also explains the
On Tue, 15 Jan 2002 15:18:36 -0500
Jon Carnes <[EMAIL PROTECTED]> wrote:
> Some email systems send "bounces" from some weird addresses (as
> apposed to Mailer-Daemon, or some such address).
A bounce is sole identified by having a null return address in the
envelope, and by nothing else. None
>
> > Other bounces (that come back in a non-standard format that Mailman
can't
> > interpret), will be posted to the admin for handling (assuming you have
the
> > list set so that only members or admin's can post). These messages are
> > stored in ~mailman/data/..
>
> How do you define "other bo
Hi Jon,
* Jon Carnes <[EMAIL PROTECTED]> [2002-01-14 19:00:41]:
> So the problem is that you want a list of the email addresses that are
> undeliverable, so they can be removed from the database (either manually or
> via a script).
Right.
> Mailman does some of this. You can read the ~mailman/
en Brix Pedersen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 14, 2002 9:20 AM
Subject: [Mailman-Users] Using mailman to take care of mailer-demons
> Hi,
>
> At my company, we have a rather big amount of websites where users can
> subscribe to newslette
Hi,
At my company, we have a rather big amount of websites where users can
subscribe to newsletters and more. Now we are having the problem that
more than 3000 messages are coming back as mailer demons, and a person
has to delete these e-mails automatically.
All the e-mail addresses lies in an O
11 matches
Mail list logo
