[BRLTTY] PLEASE ......................... explain ?
Labrador
labrad0r at edpnet.be
Thu Dec 16 11:48:44 EST 2010
Hi!
I sincerely regret but had never received any answer. Note that there is no
any filter on my procmail or so: I only use Mutt+Fetchmail+Exim4 on a Debian
system, and I'm surprised that only this Mailman machine doesn't reacts as
the others I had submitted my address change.
Seeing this that's why I decided to mail privately to prevent too much
noise on the ML. If there is a similar problem shoudn't that explain why I
don't receive then any machineanswer ? I'm honestly not filtering!
Can't explain. Sorry!
Thanks for having shown the logs with my trials, so this means the request
itself was received,
but then I didn't receive any confirmation request! Bizarre :)
Greetings,
On Mon, Dec 13, 2010 at 01:52:47PM -0500, Dave Mielke wrote:
> Aside from the fact that you really ought to apologize for what amounts to
> incredible rudeness, I decided to go have a look.
>
> It turns out that another user (I forget who) already told you a few days ago
> what the problem must be.
>
> You yourself observed that every other Mailman server has been working
> correctly. Why, then, would you simply assume that mine isn't working properly?
>
> Would it surprise you to learn that my Mailman server is working just as
> reliably as all the others? I count no less than thirteen attempts made by it
> to send messages to your new address (see below).
>
> What the other user suggested to you was that some server, if not your own spam
> filtering, must be discarding those messages. It sure looks like that must be
> the case.
>
> Note that, if this is so, then any attempt by me to personally reply to your
> new address would likely also get dsicarded. Now what do you think about all
> your claims that I haven't been responding to your private requests for help?
>
> Now, from my server's mail log, here are those 13 log entries. Notice that,
> from my end, every attempt to send your new address a message was successful.
>
> Dec 2 07:31:36 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 2 11:07:14 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 5 04:42:54 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 5 05:02:33 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 5 06:30:44 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 5 06:30:44 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 5 14:09:49 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 5 14:28:23 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 6 14:33:42 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 6 15:11:29 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 12 09:54:21 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 12 12:28:39 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
> Dec 12 12:31:30 ... to=<osvaldo.larosa at .....> ... status=sent (250 OK , completed)
More information about the BRLTTY
mailing list