From: Gene3 on
I've resent it, to your 'Reply to' address '@msn.aosake.net' ... -- Gene3


From: N. Miller on
On Tue, 22 Sep 2009 06:39:47 -0500, Gene3 wrote:

> I've resent it, to your 'Reply to' address '@msn.aosake.net' ... -- Gene3

I am looking for a log entry like this:

| T 20090921 163429 4ab5bf63 RCPT TO:<2006MS10-28.spam(a)msn.aosake.net>

I am only seeing the test I sent myself by using my "Reply" button in my
client, which automatically goes to the "Reply-To:" email address configured
in my client posting parameters.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
From: N. Miller on
On Tue, 22 Sep 2009 06:23:05 -0500, Gene3 wrote:

> Ooops...
> Nope, it went to your @msnews.aosake.net address, which is what shows in
> your message headers here.

:) This is what will happen when Google mail tries:

| 09/22/09 11:45:29 dns msnews.aosake.net
| Canonical name: msnews.aosake.net
| Addresses:
| 127.0.0.1

That address which you see is intended as a spam foil.

> I don't have a '@msn.aosake.net' address for you,
> so you'll have to clarify then I'll resend.

I've configured a working email address in the "Reply-To:" field of my
posting client. If you just use your client "Reply" button, and do not
modify the resulting email address in any way, shape, or form, it should
work. See my response to your later post, with the log entry of my test.

P.S. If the spammers pick this up, I'll just have to change it. No big deal
for me. But it is designed so that using the "Reply" button will do the job.
It seems to work nicely for posters who manage to inadvertently hit the
"Reply" button instead of the "Reply to Group" button.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
From: o;; on

"Gene3" <Gene3(a)not.valid> wrote in message
news:eOThVHcNKHA.4692(a)TK2MSFTNGP06.phx.gbl...
>I thought this was a forum interested in such facts. It looks like I was
>wrong. Good bye.
> --Gene3
>
> "PA Bear [MS MVP]" <PABearMVP(a)gmail.com> wrote in message
> news:uXNO0z3MKHA.220(a)TK2MSFTNGP02.phx.gbl...
>> [And another hoople-head joins the fray...]
>>
>> Gene3 wrote:
>>> The bug occurs with Windows Live Mail and Vista. It has nothing to do
>>> with
>>> Outlook, Outlook Express, or other mail/newsreader clients except that
>>> they
>>> (all of them) find such URLs dead, inactive because of the spurious
>>> x-usc:
>>> prefix. You can google for yourself and read about it, searchstring:
>>> "x-usc
>>> windows mail vista".
>>>
>>> "N. Miller" <anonymous(a)msnews.aosake.net> wrote in message
>>> news:1r0ad3m996dhn.dlg(a)msnews.aosake.net...
>>>> On Tue, 8 Sep 2009 05:10:47 -0500, Gene3 wrote:
>>>>
>>>>> To answer my own question: I did quite a bit of googling, and
>>>>> discovered
>>>>> that reports of this bug started over 2 years ago. So MS has ample
>>>>> time
>>>>> to
>>>>> become aware of it, and their response is apparently to ignore it and
>>>>> hope
>>>>> it will go away. :) Or maybe they just don't care. The evolution of
>>>>> windows
>>>>> software has perhaps become too top heavy...
>>>>
>>>> Does this bug exist in Windows Live Mail, or MS Outlook 2007? Even if
>>>> the
>>>> bug were discovered two years ago, it will never be addressed in MS
>>>> Outlook
>>>> Express because development stopped well over two years ago. Even
>>>> Windows
>>>> Mail (the Vista client, and different from Windows Live Mail) is older
>>>> than
>>>> that discovery date for the bug; as is MS Outlook 2003.
>>>>
>>>> --
>>>> Norman
>>>> ~Oh Lord, why have you come
>>>> ~To Konnyu, with the Lion and the Drum
>>
>
>


First  |  Prev  | 
Pages: 1 2 3 4 5 6 7
Prev: still problems
Next: MSOE.DLL help needed