Balls of string aren't long enough, and although voice traffic can be transmitted textual data is more tricky. Particularly if the string gets wet.

Another good thought!!!

In reply to a post by Andrew_W:

Right, I know that XP and OE6 are unsupported, old etc etc but generally they work OK and are ideal for our undemanding requirements as we are old too!

My wife and I both have a PC, both running the same version of XP and OE6 but when my wife sends an email with a photo attachment or image inserted into the body of the text, IDNet�s servers bounce it back as �unsolicited bulk email. UBE�. Normal email without attachments works fine. I have no problem at all with my PC.

Webmail works OK with attachments but is not the most convenient method of sending emails. I contacted IDNet and they offered no solution pointing out that both XP and OE6 are no longer supported which was not a great help as I knew that already and as my ISP I hoped they would have an answer!!!

So, I fired up another old PC, same spec as above, copied across all OE6 emails etc from my wife�s PC and would you believe, back comes �unsolicited bulk email. UBE� when sending images.

I then created another email address on the old PC changed the POP3 server settings from mail.idnet.com to securemail.idnet.com and, same problem. I even tried my own email address on this PC and that threw up the same error.

It would appear that whatever is causing this error has been imported with the email transfer from one PC to another.

Anybody any idea what it might be, please!

I would suggest you CALL IDNET - they're actually pretty good in my experience. Bearing in mind that this is not an official support resource, or you can e-mail IDNet support. Either would be fine and would be far better than just moaning here nobody helped you from the supplier on someone else's web site.

Believe me, mon fruit, I have indeed contacted IDNet and they don't want to know as I am using "old software"..... So I sought help from this forum, generally populated with helpful individuals!

Oh, and by the way, I grew out of moaning when I was five years old

Unfortunately, there's not enough information provided for me to be able to help. I would have to examine the mail headers to see a more detailed explanation of why the mail is being rejected and this would probably result in a disclosure of personal information if you were to post the mail headers here.

Sorry

As has already been mentioned, using the ISP's mail addresses and servers isn't recommended any more than the use of old software.

Although my PC is running Windows 7, my email is still OE6 using a Windows XP 'virtual window'. This was a feature of Win7 but is now unsupported. I have lots of active email addresses and a personal domain name. The only time I get issues is when the ISP (Virgin in my case) email gets blocked because it's been used for sending spam by someone, not me.

As you've discovered, using the webmail option often works as the ISP tend to swap the server for that first, before telling clients there is any problem.

What I've been able to do is swap the outgoing mail to my own domain name server but it can be fiddly to set up and is frowned upon by using the outgoing server for mail it's not supposed to be handling.

There is something to look at. In the OE6 settings.
Tools - Accounts - (select the email address) - Properties - (click Advanced tab)
Is the outgoing mail (SMTP) set to 25 ? Try 465

It seems that IDNet have several different email systems, each with their own settings and servers. By you swapping to the 'securemail' option you may well have invalidated your own email address. More about that at https://www.idnet.net/support/guides/email/settings.php

Thank you for all that!

Now, how about this!! I changed SMTP settings from 25 to 465 as you suggested and it didn't work at all, so, I changed it back to 25.

All now works as hoped with photo attachments not causing any problem at all. I wonder why???

I already have tried the various email settings offered by IDNet so again thank you for whatever you did!

As Paul Daniels used to say 'Now that's magic!'

Sounds like something was perhaps corrupt and you've reset it by changing and changing back. Port 465 is often used as a secondary send option, Google especially. My own email provider uses port 2500 to send. Many ISP's trap port 25 and only allow their own messages to be sent.

I don't know if that's any explanation but at least it's working now.

I was never very impressed with Mr. Daniels but perhaps I should consider his magic next time!