Dodgy solutions are fairly common even in enterprise-grade e-mail
deployments, usually with bizarre results like these.
Firewall/networking people like me end up having to figure out what the
bizarre results mean, with:
a) less & less information from equipment as the user interfaces are
dumbed down for administrators who can only do GUI; and
b) more and more stupid problems as the largest software providers
ignore - or more likely the majority of the current generation of
software architects no longer understand - the ratified standards.
That said, Internet name-service (DNS) performance has been generally
poor lately.
davidt
On Mon, May 05, 2014 at 08:45:23PM -0700, Scott Gomez wrote:
> Another possibility is a misconfiguration of the Barracuda device or
> service.. It's widely purchased by organizations looking for a "quick and
> easy fix" for problems of spam and viruses, especially by organizations
> running Microsoft's Exchange Server, and not having someone adequately
> trained about smtp and other email arcana. I'll spare everyone the in-depth
> technical reasons and say this:
>
> 1. Some organization runs Exchange Server, registered as exchange.some.org
> 2. Said organization believes Microsoft when told they "really don't need a
> person well versed in mail protocols" because, after all, Exchange will do
> it all for you
> 3. Said organization suffers many attacks and plagues of spam, not handled
> by the default Exchange installation configuration
> 4. Barracuda tell them they have a whizzy fix that will solve all their
> mail problems
> 5. Some.org buys the Barracuda device
> 6. Many mail rejections or delays occur until the configuration is "tuned"
--
_________________________________________________________________
Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
Archives: http://lists.thomasclausen.net/mailman/private/olympus/
Themed Olympus Photo Exhibition: http://www.tope.nl/
|