On Tue, 2010-10-05 at 11:51 -0400, Alex wrote:
> > As the documentation [1] clearly states, the second value (a) is a
> > string matched against the relay's rDNS in the Received headers, and
> > (b) it is your MX's responsibility to perform the rDNS lookup and add it
> > to the header.
> > $ host 209.16.192.170
> > 170.192.16.209.in-addr.arpa domain name pointer Lanyon.com.
> >
> > So, fix your MX. :) With an rDNS entry in the header, you will need to
>
> I'm not it's a problem with my system. It's not that IP that has the
> problem, but with the host itself:
>
> $ host S253906HZ1EW06.usstls6-hosting.savvis.net
> Host S253906HZ1EW06.usstls6-hosting.savvis.net not found: 3(NXDOMAIN)
Err, you're doing rDNS lookup for the connecting host's IP, not the
rather arbitrary HELO as you just did.
> I suppose I could add that host to /etc/hosts, but is there another
> way to whitelist mail from this host/domain to a specific user? There
> are also no SPF records to use...
If there really is no way to use whitelist_from_rcvd, you of course
always can write custom header rules, matching against the pseudo header
X-Spam-Relays-Internal or friends, carefully constructing the RE to
match a specific Received header by constraining it with the square
brackets surrounding each relay.
However, I do not see yet why that should be necessary in your case.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
