I'd forward some samples of the complete headers to your ISP, which it
appears is comporium.net/comporium.com and which has a registered technical
contact address of: contactdomains@xxxxxxxxxxxxx and a registered
postmaster address of postmaster@xxxxxxxxxxxxx. Address it to one and cc
the other. Ask that they check things out and reply to you.
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"
On Mon, May 5, 2014 at 6:42 PM, Tina Manley <images@xxxxxxxxxxxxx> wrote:
> An update - my e-mail seems to have sorted itself out with no actions from
> me other than a negative virus check. HOWEVER! Our internet cable is strung
> above ground since we are doing lots of plumbing and wiring excavations.
> Tom was mowing the yard on Saturday and he ran over the cable, nicking it
> enough to lose the connection. The ISP came out today to re-attach it. I've
> been in withdrawal since Saturday but have gotten an awful lot done around
> the house. Spring cleaning - sigh :-(
>
> Tina
>
> On Sunday, May 4, 2014, David Thatcher <davidt@xxxxxxxxxxxxxxxxxxx> wrote:
> > On Sun, May 04, 2014 at 08:28:32AM +1000, Andrew Fildes wrote:
> >> I'm in OZ - it was incomprehensible here as well.
> >>
> >> Andrew Fildes
> >> afildes@xxxxxxxxxxxxx
> >> www.soultheft.com
> >
> >
> > OK, fair enough! :)
> >
> > I did try to explain it in laymans terms (and keep it brief) but
> > internet communications protocols are heavily technical. The middle
> > paragraph tied directly into the failure message - and a guess at a
> > reason. If someone wants a more detailed explanation, feel free to
> > contact me off-list.
> >
> > As Phillipe said, the important bit was the last line. :)
> >
> > davidt
> >
> >
> > --
> > _________________________________________________________________
> > Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
> > Archives: http://lists.thomasclausen.net/mailman/private/olympus/
> > Themed Olympus Photo Exhibition: http://www.tope.nl/
> >
> >
> >
>
> --
> Tina Manley
> http:// <http://tina-manley.artistwebsites.com/>www.tinamanley.com
> --
> _________________________________________________________________
> Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
> Archives: http://lists.thomasclausen.net/mailman/private/olympus/
> Themed Olympus Photo Exhibition: http://www.tope.nl/
>
>
--
_________________________________________________________________
Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
Archives: http://lists.thomasclausen.net/mailman/private/olympus/
Themed Olympus Photo Exhibition: http://www.tope.nl/
|