mouss wrote:
>
> reject_unknown_helo_hostname is known to block "legitimate" mail, mostly
> from misconfigured sites (but it will defer mail in case of DNS problems
> even if the other side is well configured).
>
>>>snip<<<<
>
> No reason to remove all the checks. you can use:
>
> smtpd_helo_restrictions =
> reject_invalid_helo_hostname
> reject_non_fqdn_helo_hostname
>>>snip<<<<
>
>> Questions:
>>
>> 1) Is the problem really on my end with that config?
>
> it's on the other end, but since many servers accept mail from them, the
> problem is passed to you (the common "but we have no problem with other
> servers". sigh).
>
>> 2) If it is, how can I do better?
>
> see above.
>
>> 3) If it isn't, any suggestions for what to tell the exchange sys admins
>> to fix on their end?
>
> if you have the courage, motivation and resources to educate the
> universe, then good luck.
>
>> [snip]
Thanks to all that answered on and off list...
I have a few things to try now, but I'm definitely more comfortable with
what's going on. I feel I can at least respond (somewhat) intelligently
if I need to chat with one of those exchange sys admins. The harder
part is telling my users why they aren't getting mail that used to get
thru... curiously they don't seem to notice all the spam that quit
getting thru at the same time, oh well 8^\
--
Steve Lindemann __
Network Administrator //\\ ASCII Ribbon Campaign
Marmot Library Network, Inc. \\// against HTML/RTF email,
http://www.marmot.org //\\ vCards & M$ attachments
+1.970.242.3331 x116
