Hi Richard Haas
On 2011-11-22 15:14, Richard Haas wrote:
< ... >
>
> The original address that led to the bounce was accepted outbound for
> delivery, and then came back about 17 seconds later, after remote
> translation of
>
> @someresearch.com to @telecdyne.com
>
> ... but cam back only once
On Tue, Nov 22, 2011 at 2:54 AM, Mark Sapiro wrote:
> Richard Haas wrote:
> >
> >Last week, we ran into a rather odd event (first time we've seen it in a
> >decade or so of Mailman ops), where a bounced message kept writing to its
> >/var/mailman/data/bounce-events-PID.pck file, until it filled t
Richard Haas wrote:
>
>Last week, we ran into a rather odd event (first time we've seen it in a
>decade or so of Mailman ops), where a bounced message kept writing to its
>/var/mailman/data/bounce-events-PID.pck file, until it filled the disk [...]
>The first bounce seemed normal:
>
>Delivery faile
Greetings.
Last week, we ran into a rather odd event (first time we've seen it in a
decade or so of Mailman ops), where a bounced message kept writing to its
/var/mailman/data/bounce-events-PID.pck file, until it filled the disk --
it wasn't a series of bounces (same delivery times on every receiv
