On 2007-09-03 09:58:14 -0400, abhilash s wrote: > we are using qpsmptd 0.32. Now the mail from cbsig.net is blocked > by require_resolvable_fromhost plugin . As this domain's mail is coming from > more than a server I can't set the whitelist for a particualr IP address. > These are some of the logs of my qpsmtpd: > > > logterse plugin: ` 64.30.237.62 proxy1068-fe.tm.cbsig.net > proxy1068.tm.cbsig.net require_resolvable_fromhost > 902 Could not resolve proxy1068.tm.cbsig.net (#4.4.3) > > logterse plugin: ` 64.30.237.85 proxy1052-fe.tm.cbsig.net > proxy1052.tm.cbsig.net require_resolvable_fromhost > 902 Could not resolve proxy1052.tm.cbsig.net (#4.4.3) > > logterse plugin: ` 64.30.237.177 proxy1053-fe.tm.cbsig.net > proxy1053.tm.cbsig.net require_resolvable_fromhost > 902 Could not resolve proxy1053.tm.cbsig.net (#4.4.3) > > logterse plugin: ` 64.30.237.2 proxy1061-fe.tm.cbsig.net > proxy1061.tm.cbsig.net require_resolvable_fromhost > 902 Could not resolve proxy1061.tm.cbsig.net (#4.4.3) > > logterse plugin: ` 64.30.237.178 proxy1055-fe.tm.cbsig.net > proxy1055.tm.cbsig.net require_resolvable_fromhost > 902 Could not resolve proxy1055.tm.cbsig.net (#4.4.3) > > > You can see that everytime it is sending mail from different servers, so I > am not able to whitelist a particular IP.
It looks like all of them come from the same /24, so you should be able
to whitelist that (I assume you are using whitelist_soft).
> I tried the dig command of each proxy* servers the IP was resolving.
> Also I tried the dnsmx command and got the result as follows :
>
>
> # dnsmx proxy1055.tm.cbsig.net
> 0 proxy1055.tm.cbsig.net
Strange. Dig tells me there is no MX record (but maybe dnsmx reports
"0 domainname" when it can't find an MX record). But that's ok, an MX
record doesn't have to exist as long as there is an A record:
% digs proxy1055.tm.cbsig.net a
;proxy1055.tm.cbsig.net. IN A
proxy1055.tm.cbsig.net. 3600 IN A 10.180.27.15
There is one, but it is in a private network! That mail server is not
reachable from the public internet, and hence
<[EMAIL PROTECTED]> is not a valid email address. It
should obviously be proxy1055-fe.tm.cbsig.net instead, which correctly
resolves to 64.30.237.178.
You should try to contact the sender and tell them about the problem.
They probably have difficulties sending to other domains, too. Checking
the sender domain is pretty common although few check for bogons there.
hp
--
_ | Peter J. Holzer | I know I'd be respectful of a pirate
|_|_) | Sysadmin WSR | with an emu on his shoulder.
| | | [EMAIL PROTECTED] |
__/ | http://www.hjp.at/ | -- Sam in "Freefall"
signature.asc
Description: Digital signature
