enchanced whitelist_from_rcvd ?

2008-11-07 Thread Per Jessen
Occasionally I'd like to do something like this: whitelist_from_rcvd [EMAIL PROTECTED] /^smtp[0-9]+\.orange\.fr$/ The situation is that domain.fr is relaying mail through their provider, which has a number of smtp servers named smtpNN.orange.fr. If I were to stick to the current

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread mouss
Per Jessen wrote: Occasionally I'd like to do something like this: whitelist_from_rcvd [EMAIL PROTECTED] /^smtp[0-9]+\.orange\.fr$/ The situation is that domain.fr is relaying mail through their provider, which has a number of smtp servers named smtpNN.orange.fr. If I were to stick to the

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Matt Kettler
Per Jessen wrote: Occasionally I'd like to do something like this: whitelist_from_rcvd [EMAIL PROTECTED] /^smtp[0-9]+\.orange\.fr$/ One problem.. That involves a regex, but whitelist_from is a regular user config option. In general, regular expressions are intentionally not used in

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Henrik K
On Fri, Nov 07, 2008 at 02:38:22PM +0100, Per Jessen wrote: Henrik K wrote: On Fri, Nov 07, 2008 at 02:22:08PM +0100, Per Jessen wrote: Yes, I saw that in the code - still, having a whitelist_from_rcvdregex would be very useful, people relay via their providers quite a lot. I guess

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread mouss
Henrik K wrote: On Fri, Nov 07, 2008 at 02:38:22PM +0100, Per Jessen wrote: Henrik K wrote: On Fri, Nov 07, 2008 at 02:22:08PM +0100, Per Jessen wrote: Yes, I saw that in the code - still, having a whitelist_from_rcvdregex would be very useful, people relay via their providers quite a lot.

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Per Jessen
Henrik K wrote: Then instead of asking for a lacking addition to a poor whitelisting method (in this case), we should enhance whitelist_from_rcvd to process received paths: whitelist_from_rcvd [EMAIL PROTECTED] 1.2.3.4 2.3.4.5 Should this be read to mean whitelist from foobar if it came

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Henrik K
On Fri, Nov 07, 2008 at 03:07:59PM +0100, mouss wrote: Then instead of asking for a lacking addition to a poor whitelisting method (in this case), we should enhance whitelist_from_rcvd to process received paths: whitelist_from_rcvd [EMAIL PROTECTED] 1.2.3.4 2.3.4.5 why? I wouldn't put 30

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Henrik K
On Fri, Nov 07, 2008 at 03:09:29PM +0100, Per Jessen wrote: Henrik K wrote: Then instead of asking for a lacking addition to a poor whitelisting method (in this case), we should enhance whitelist_from_rcvd to process received paths: whitelist_from_rcvd [EMAIL PROTECTED] 1.2.3.4

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Henrik K
On Fri, Nov 07, 2008 at 04:20:17PM +0200, Henrik K wrote: On Fri, Nov 07, 2008 at 03:09:29PM +0100, Per Jessen wrote: I'm not sure I like the ideas of whitelisting based on IP-addresses, it's too inflexible. Why would you not use hostnames? Hmm.. ok I think you both (mouss) are

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Per Jessen
Henrik K wrote: On Fri, Nov 07, 2008 at 02:22:08PM +0100, Per Jessen wrote: Yes, I saw that in the code - still, having a whitelist_from_rcvdregex would be very useful, people relay via their providers quite a lot. I guess I'll have to write something up. If the originator is static IP,

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Per Jessen
Per Jessen wrote: Matt Kettler wrote: Per Jessen wrote: Occasionally I'd like to do something like this: whitelist_from_rcvd [EMAIL PROTECTED] /^smtp[0-9]+\.orange\.fr$/ One problem.. That involves a regex, but whitelist_from is a regular user config option. In general, regular

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread mouss
Henrik K wrote: why link that to trusted_networks? Obviously the whole IP path must be trusted (excluding the last one). You can use hostnames as well. But then you have to have trust path right, to trust later hostnames. maybe I misunderstood your could even work And perhaps it

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread mouss
Henrik K wrote: On Fri, Nov 07, 2008 at 04:20:17PM +0200, Henrik K wrote: On Fri, Nov 07, 2008 at 03:09:29PM +0100, Per Jessen wrote: I'm not sure I like the ideas of whitelisting based on IP-addresses, it's too inflexible. Why would you not use hostnames? Hmm.. ok I think you both (mouss)

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Per Jessen
Matt Kettler wrote: Per Jessen wrote: Occasionally I'd like to do something like this: whitelist_from_rcvd [EMAIL PROTECTED] /^smtp[0-9]+\.orange\.fr$/ One problem.. That involves a regex, but whitelist_from is a regular user config option. In general, regular expressions are

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Henrik K
On Fri, Nov 07, 2008 at 04:45:57PM +0100, mouss wrote: With hostnames there is a bigger change of failure (by just using a domain instead of exact hostname, letting f.e. dialup users from the domain forge the path). not sure I understand. people can't easily forge their rdns (in the What

Re: enchanced whitelist_from_rcvd ?

2008-11-07 Thread Henrik K
On Fri, Nov 07, 2008 at 02:22:08PM +0100, Per Jessen wrote: Matt Kettler wrote: Per Jessen wrote: Occasionally I'd like to do something like this: whitelist_from_rcvd [EMAIL PROTECTED] /^smtp[0-9]+\.orange\.fr$/ One problem.. That involves a regex, but whitelist_from is a