How to accept mail from a single IP / DNS name only for a given list

1st, forgive me if this has been answered before. I have searched high
and low and can not find an answer to my question.
How can I setup a list so that mail can be accepted ONLY from 1 IP
address? As an example I have a list named abc@123.com and it is setup
as an announce list only accepting mail from 1 user with an address of bob@123.com
. How can I set this list up so that even if the mail appears to come
from bob@123.com the email will post to the list ONLY if bob@123.com's
email came from bobspc.123.com which has an an IP address of
123.456.789.246
Thanks!

on 12/30/08 1:10 PM, Emmett Perdue said:
That's really something that you need to do in your MTA. By the time the message gets to Mailman, we can no longer tell what IP address sent what.
-- Brad Knowles <brad@shub-internet.org> If you like Jazz/R&B guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at <http://tinyurl.com/y8kpxu> http://preview.tinyurl.com/bigsbytracks

On Tue, Dec 30, 2008 at 02:10:45PM -0500, Emmett Perdue wrote:
Sounds like the sort of thing to be handled by an MTA rule/ACL.
(nb: §3 of http://www.rfc-editor.org/rfc/rfc2606.txt)

Emmett Perdue wrote:
You could set up header_filter_rules (Privacy options... -> Spam filters) for this list as follows:
rule 1
regexps ^Received:.*bobspc\.123\.com ^Received:.*123\.456\.789\.246
action Accept
rule 2 regexp .
Action Discard
However, An easier and better way to do this is to moderate Bob along with everyone else and have Bob post with a header
Approved: password
where password is the list's admin or moderator password.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 12/31/08 12:00, Mark Sapiro wrote:
You could set up header_filter_rules (Privacy options... -> Spam filters) for this list as follows:
Eh...
I would think that this would be easy to fool by adding a bogus Received: header. So, IMHO this is not such a good idea.
I like this better.
Grant. . . .

Thanks everyone, the posting with a header password seemed the easiest
to do so I went with that. I will read up on trying some things with
sendmail to see what can be done there.
On Dec 31, 2008, at 3:48 PM, Grant Taylor wrote:

on 12/30/08 1:10 PM, Emmett Perdue said:
That's really something that you need to do in your MTA. By the time the message gets to Mailman, we can no longer tell what IP address sent what.
-- Brad Knowles <brad@shub-internet.org> If you like Jazz/R&B guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at <http://tinyurl.com/y8kpxu> http://preview.tinyurl.com/bigsbytracks

On Tue, Dec 30, 2008 at 02:10:45PM -0500, Emmett Perdue wrote:
Sounds like the sort of thing to be handled by an MTA rule/ACL.
(nb: §3 of http://www.rfc-editor.org/rfc/rfc2606.txt)

Emmett Perdue wrote:
You could set up header_filter_rules (Privacy options... -> Spam filters) for this list as follows:
rule 1
regexps ^Received:.*bobspc\.123\.com ^Received:.*123\.456\.789\.246
action Accept
rule 2 regexp .
Action Discard
However, An easier and better way to do this is to moderate Bob along with everyone else and have Bob post with a header
Approved: password
where password is the list's admin or moderator password.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 12/31/08 12:00, Mark Sapiro wrote:
You could set up header_filter_rules (Privacy options... -> Spam filters) for this list as follows:
Eh...
I would think that this would be easy to fool by adding a bogus Received: header. So, IMHO this is not such a good idea.
I like this better.
Grant. . . .

Thanks everyone, the posting with a header password seemed the easiest
to do so I went with that. I will read up on trying some things with
sendmail to see what can be done there.
On Dec 31, 2008, at 3:48 PM, Grant Taylor wrote:
participants (5)
-
Adam McGreggor
-
Brad Knowles
-
Emmett Perdue
-
Grant Taylor
-
Mark Sapiro