Liviu Daia <Liviu(_dot_)Daia(_at_)imar(_dot_)ro> writes:
My question has remained the same from the initial post.
Can you please explain then how is your question related to messages
without "To:" headers.
I think there is a misunderstanding here, probably due to my poor
presentation of what I was after. My comments in initial post,
mention "To:" Headers in this way:
1) Messages with "To: " headers, .forwarded to reader(_at_)newsguy(_dot_)com,
from a reader(_at_)address that is not newsguy, can eaily be filtered
(at newsguy machine)
2) Messages .forwarded to reader(_at_)newsguy(_dot_)com, from a
reader(_at_)addrss
that is not newsguy, and have *NO* "To: " header are not easily
filtered (identified as messages .forwarded from a different
reader(_at_)address). This was the only context in which "To: " headers
are mentioned.
Part 2 being the reason for my post.
But I see Era has supplied the answer I was after. An easy way to
ident. messages that have been forwarded from certain accounts to
reader(_at_)newsguy(_dot_)com(_dot_)
Like I said, this only works for messages addressed to
reader(_at_)newsguy(_dot_)com(_dot_) If this was your initial question, why
didn't you
say this from the beginning?
How so? Messages addressed to reader(_at_)newsguy(_dot_)com wouln't even be
involved in any way. The way I read Era's recipe is: All messages
sent to a machine (foo.bar, not newsguy.com) will have a header added
indicating that the message is a .forward from (foo.bar) and be
forwarded to reader(_at_)hewsguy(_dot_)com(_dot_)
Thus solving the problem of inventing complicated "Received"
header scanning to do that job, and solving my problem (1+2 above)
with an easy to do recipe on the forwarding end.
Was the first part of my initial post really that unclear as to the
source and destination? My intent was to show all .forwards being to
reader(_at_)newsguy(_dot_)com(_dot_)
From initial post:
So that mail sent to :
reader(_at_)place1
reader(_at_)place2
reader(_at_)place3
Can be forwarded from those machines with a header added to make
them easily filterable when they arrive at:
reader(_at_)newsguy(_dot_)com