Performance

[Ed Bruce]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Glenn Steen wrote:
> On 05/02/07, Ed Bruce <edwardbruce at sbcglobal.net> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Glenn Steen wrote:
>>
>> >
>> > So, there is litle to no risk with this. The sender _will_ get a
>> > somewhat informative reject code, and should be able to find the
>> > problem at their end... Forcing _them_ to comply to the RFC;-).
>> >
>>
>> One would hope. A major software vendor whose accounting software my
>> company uses has a misconfigured MTA. I've told them and told them. I've
>> whitelisted them and then volunteered to help configure it correctly.
>> There response is please keep whitelisting us. This is a company that
>> develops software and they can't configure their Exchange Server.
> 
> Yes? Did you explain to them that this is loosing them money,
> potentially? And they still persist? I'm assuming you mean they
> HELO/EHLO with something strange, like your IP address or domain name
> ... Else it's a bit non-relevant to this subthread:-):-)
> Then again... I suppose there are fools all over the world (and
> sometimes even we could be seen as such:-), but... "Helping" them
> remain fools isn't really helping anyone, now is it?;)
> 

They had a malformed HELO/EHLO. I just searched through our mail logs
and I couldn't find anything. Started to get worried then found out they
changed their company name. With the change they seem to have gotten a clue.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFx3ippdNaP9x3McgRAkEvAKCylN4bUJwNYyQxpcAzCRdx4914TgCeO48J
BGUUYeDhC2gUiu8bmJvhF30=
=H84O
-----END PGP SIGNATURE-----