Thanks to all contributers to this post. I have tried some of the suggestions
within replies and it leads me back to the same conclusion (as said by
others) that virgin net spam catcher is causing the problem. They however
will not admit it and don't care..........Will have to live with it or move
elsewhere. Thanks again..
"Gary VanderMolen" wrote:
| Quote: |  | |
|
> Aside from switching to a more enlightened ISP, you could send
> photo emails through a different SMTP server. One solution
> would be to use Gmail's SMTP server.
>
> --
> Gary VanderMolen, MS-MVP
>
>
> "Frustrated virgin user" <Frustrated virgin user@xxxxxx>
> wrote in message news:307FB119-6F9F-48C2-9496-0AA3682C336A@xxxxxx | Quote: | | | |
> >I have recently had a long 'support' conversation with virgin.net regarding
> > an error message I keep getting when sending a "photo email" using Windows
> > Live Mail. Virgin are my ISP for the internet and I have email addresses
> > with
> > them ending virgin.net. The error code is reproduced below:
> > An unknown error has occurred.
> >
> > Subject 'xxxxxxxxxx'
> > Server Error: 554
> > Server Response: 554 5.7.1 Requested action not taken: Message was spam or
> > contained virus
> > Server: 'mail.virgin.net'
> > Windows Live Mail Error ID: 0x800CCC6F
> > Protocol: SMTP
> > Port: 25
> > Secure(SSL): No
> >
> > In my discussion with virgin support the conclusion was reached that when
> > a
> > "photo email" is created there is a stage of "preparing photos" before the
> > email is placed in the outbox. This would appear to be where the problem
> > occurs in that some code is added to the photograph for it to be
> > identified
> > when uploaded to the WLM server (this would make sense as the email
> > recipient
> > would then click on the thumbnail image in the email to download the
> > hi-res
> > image from the server). It seems that virgin.net & maybe some other ISPs
> > see
> > this embedded code as possibly malicious and therefore reject the email
> > with
> > the error message above.
> > Some work needs to be done here. Has anyone else experienced the same
> > problem and, more importantly have they resolved the issue.
| | | | | >
> | |
| | |