Messages won't send files via AIM anymore

Question

Level 1

0 points

Messages won't send files via AIM anymore

I've been using Messages via AIM and iMessage and had no problems sending files or images for years until recently. Now AIM won't send files. There's no error message and I can see the image in the conversation window but the recipient doesn't get the file/image. Also when they try to send to me, I don't get the file/image either. This problem has started just this week.

We have had our broadband upgraded and a new router installed but it's in Modem mode and hooked up to our Airport Time Capsule that runs the wifi.

I've read some posts about port changes, but not sure if this would be the case.

Any help much appreciated.

Martin

MacBook Pro, OS X Yosemite (10.10.3)

Posted on Apr 9, 2015 4:33 AM

Reply

Answer 1

etresoft

Level 9

57,554 points

Apr 10, 2015 5:05 AM in response to f23creative

I have heard that AIM may not be supported anymore. Does anything in this sound familiar?

http://appleinsider.com/articles/14/07/02/apple-requirement-ends-aim-logins-with -legacy-maccom-and-mecom-ids-for-os-x-1071-and-below-found-affecting-later-os-x- versions-as-well

Reply

Answer 2

Apr 9, 2015 1:06 PM in response to f23creative

Hi,

An AIM Login to the servers happens on port 443.

A File Transfer which includes Pics-in-Chats moves to port 5190 on the UDP protocol.

Several posts refer to issues with sending Pics.

It seems that Zipping or Stuffing the files first gets around this.

At times in the past AIM have "restricted" various things for Security issues.

One was to stop Hyperlinked words so that code could not be hidden. Links had to be sent in plain text.

One attack on Macs involved iChat and a malicious jpeg.

(it only went on to "infect" via Bonjour connection in iChat)

See http://en.wikipedia.org/wiki/Leap_%28computer_worm%29

I would not be surprised to find AIM think that there is something new to be tackled.

9:06 pm Thursday; April 9, 2015

 iMac 2.5Ghz i5 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

Reply

Answer 3

f23creative Author

Level 1

0 points

Apr 10, 2015 5:07 AM in response to etresoft

Thanks for that link - seems like that could deb part of the cause - I'm not a fan of apple creating the new domains and still prefer mac.com but will see if switching the icloud.com fixes the problem.

Reply

Answer 4

Apr 10, 2015 11:28 AM in response to f23creative

Hi,

See also AIM Screen Names using @Mac.com or @me.com IDs to end (it is in Mountain Lion's area)

The @mac.com and @me.com name should still work as AIM valid Screen Names.

It is only in iChat up to and including the base version of iChat 6 in Lion.

The Later updated version of iChat 6 should work.

It is because during Lion Apple introduced the double Login to AIM and Apple that allows the app to confirm you can login in with the Apple ID.

Basically unless the app has logged in to Apple with the ID then the AIM server cannot see it.

To certain extent this already was the case in AIM and iChat for @me.com ID once there was no MobileMe server.

All @me.com names that became linked to iCloud IDs get around that by being iCloud IDs.

So... Later versions of iChat 6, Messages 7 in Mountain Lion, Messages 8 in Mavericks and the version in Yosemite (also called version 8) all allow Logins with Apple Issued IDs to the AIM servers.

It does help that you may have "updated" the account yourself along the way - such as Linking an @mac.com to MobileMe when MobileMe came out and again for iCloud.

This may mean that actually you have an Apple ID that has @mac.com@me.com and @icloud.com emails and all those "IDs" works as login names with the same password.

7:28 pm Friday; April 10, 2015

 iMac 2.5Ghz i5 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

Reply