On Mon, 2011-03-14 at 12:15 -0400, [email protected] wrote:
> Error happened on March 12th. Notification sent to me on March 14th.
(March 2 you meant to say here, which matches the original bounce.)
Yes. This is the ezmlm default, as googling for "ezmlm bounce handling"
confirms. The list server keeps bounced messages queued up for 12 days,
then sends a warning containing the list of bounces. Probe send after
another 12 days, if the warning bounces as well.
> The only reason I noticed this is because I recently stopped blocking the
> range of messages that trigger this kind of thing.
Yeah, well -- better to start off with a properly configured MX in the
first place, eh?
The size limit of 64k (!) you used before (see a recent post of yours to
the users list) seems overly aggressive and prone to break something
eventually, if not back-fire outright.
guenther -- one of the moderators, who also can be contacted
at LIST-owner@ rather than on-list
> Hi. This is the qmail-send program at apache.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.
>
> <[email protected]>:
> 64.71.152.40 failed after I sent the message.
> Remote host said: 552 5.3.4 Error: message file too big
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
