Mac OS X 10.5.5 Seed Thread (9F17(a) - 8/19/08)

By Cara
in Apple (macOS)

 Share

Recommended Posts

Grand Master

Cara Veteran

Posted
  • Author
  • Veteran
Posted
Riddle me this: when you create a MobileMe account in Mail after 10.5.4 and the MobileMe update, it sets up the outgoing server as port 25. Previously, when the service was .Mac, this port number was 587. Why does it do this?

Ironically enough, using the default configuration for that only works half the time (the other half of the time, I will get outgoing server errors), whereas when I change the outgoing port number to 587, everything suddenly works. I've ruled out the possibility of it being an ISP issue.

Actually it is a ISP issue. 25 is SMTP which is blocked by most ISP's to prevent SPAM. :)

It is just the proper port to use so it is the default.

Link to comment
Share on other sites
Proficient

Cadium

Posted
Posted
Actually it is a ISP issue. 25 is SMTP which is blocked by most ISP's to prevent SPAM. :)

It is just the proper port to use so it is the default.

But when the ISP doesn't block port, then what? I guess the bigger question here is why did it get switched from 587 (.Mac) to 25?

Link to comment
Share on other sites
Grand Master

Cara Veteran

Posted
  • Author
  • Veteran
Posted
But when the ISP doesn't block port, then what? I guess the bigger question here is why did it get switched from 587 (.Mac) to 25?

I think almost every (responsible) ISP is blocking 25 lately... According to documentation, it's always defaulted to 25...however....if you look through the old .Mac support and now MobileMe you will find it suggests that change for people with problems. Perhaps it is something you changed a while ago and didn't remember changing?

Link to comment
Share on other sites
Proficient

Cadium

Posted
Posted
I think almost every (responsible) ISP is blocking 25 lately... According to documentation, it's always defaulted to 25...however....if you look through the old .Mac support and now MobileMe you will find it suggests that change for people with problems. Perhaps it is something you changed a while ago and didn't remember changing?

Could be... I'm somewhat brain dead when it comes to my memory. :no:

Link to comment
Share on other sites
Grand Master

Cara Veteran

Posted
  • Author
  • Veteran
Posted
Could be... I'm somewhat brain dead when it comes to my memory. :no:

Just verified a freshly reloaded MBP that it defaulted to 25.

Link to comment
Share on other sites
Grand Master

offroadaaron

Posted
Posted
I will most likely do a clean install once this comes out.

meh its an update for a reason, so you don't need to reinstall... I don't see the point in why people do this, seems like they have to much time on their hands.

Link to comment
Share on other sites
Experienced

kaiwai

Posted
Posted

10.5.5 9F9 released, here are the notes:

Alot of fixes here, especially in mail and addressbook and finally fixing those IMAP and sync issues.

Mac OS X 10.5.5 build 9F9 Seed Note

1) The Mac OS X 10.5.5 Update (Delta) updates

- Mac OS X 10.5.5

- Any earlier seed of Mac OS X v10.5.5 ONLY AFTER installing the included reversioner. If you installed a previous seed of Mac OS X v10.5.5, please use the enclosed Reversioner.pkg.

2) The Mac OS X 10.5.5 Update (Combo) updates

- Mac OS X 10.5, 10.5.1, 10.5.2, 10.5.3, 10.5.4

- Any earlier seed of Mac OS X v10.5.3 ONLY AFTER installing the included reversioner. If you installed a previous seed of Mac OS X v10.5.5, please use the enclosed Reversioner.pkg.

Please be aware that you will not be able to revert back to your previous system after updating. Please install this update on a system you are prepared to erase if necessary.

As this is a pre-release build, it is not advisable to use this software on a production system with information on it that you depend on for your business.

Known Issues

- Aperture can unexpectedly quit with some images

Focus Areas

- AirPort

- Address Book

- AppKit

- Directory Services

- FileSync and Portable Home Directories

- Finder

- Fonts

- GraphicsDrivers

- Help Viewer

- iCal

- iChat

- ImageIO

- Kerberos

- mDNSResponder

- Networking

- Printing

- Screen Sharing

- SMB

- Spotlight

- Text Services

- Time Machine

- Traditional Chinese Input Method

- USB & Express Card Modems

- X11

Areas of Change

New issues fixed in this seed:

- Fixed issue with WaitNextEvent API

- Fix to Mail Message Storage

- Fixed issue with SAN connectivity

- Fixed issue with connecting to numerous TCP connections

- Syncing issue with newly created contacts and Address Book resolved

- Fixed issue with Address Book Framework and Smart Groups

- Issue with linking and CFURLProxies fixed

- Fixed sidebar displaying problem with Mail RSS

- Dropping a file on the Mail.app Dock icon now works correctly

- Fixed login issue with Active Directory

- Fixed issue with Mail and displaying IMAP messages

- Resolved Sync Services issue with Address Book and iCal

- Fixed duplicate syncing issue with iCal Synchronization

- Resolved issue with PDFKit and Safari PDF documents

- Issue with VPN menu UI fixed

- Fixed issue with set wake up times and Power Management

- Fixed problem with ACLs and NFS access permissions

- Fixed issue with Mail IMAP and out-of-order replies

- Issue with DSADPlugin and preferred server option fixed

- Resolved problem with Active Directory Map UID/GID

- Resolved issue with Address Book Printing

- Fixed issue with NoteComposeBackEnd and Mail Notes

- Fixed issue with "Show GL Layer Setup" in OpenGL

Issues fixed in previous seeds:

- Fix to DesktopServices and Full Restore from Time Machine

- Fixed issue with FileSync and incomplete syncing

- Fixed issue with TextEdit and color palette

- Fixed Networking download load issue with NAT host

- Fix to Text Services Manager

- Issue with CoreText Layout and neutral character runs resolved

- Fix to SearchKit

- Fix to CUPS admin.cgi

- Issue with non-unicode clients and SMB File Server resolved

- Fixed issue with SpotlightIndex

- Recursive GIF interface issue with Networking fixed

- Fixed kernel panic issue problem with Dashboard

- Fixed kernel panic issue with smbfs.kext

- Issue with BootCache resolved

- Fixed issue with Spotlight and Time Capsule backups

- Issue with LaunchServices and GuardMalloc resolved

- Issue with server-side agent and rPFS fixed

- Issue with copying to FileVault user's desktop resolved

- MLTE crash after applying URL attribute fixed

- SMB panic when doing directory listing ACLS resolved

- Resolved issue with reset sync and Sync Services

- PPDs with cupsPortMonitor keywords issue fixed

- Fixed Mac OS Kernel random crashes with physical addresses >4GB

- Issue with iCal AppleScript and due date resolved

- SSHD and BSD Kernel hanging issue resolved

- DO-over-TCP problem with multiple connections to same address issue fixed

- Fixed issue with inconsistent iCal syncing

- Fixed application launch crash in _CFURLCacheCopyCacheDirectory

- NSSocketPort no longer crashes when used in GC enabled application

- Fix to HLTB Appearance and ThemeTextColor CoreUI

- Fix to HICocoaView and HIWindowToolbarView

- Drag and Drop problem with HLTB DataBrowser issue resolved

- Fixed menu corner issue with HLTB Menus

- HIViewGetOptimalBounds now returns correct baseline for HIRadioButton

- HLTB DataBrowser type selection in choose from list dialog now enables default button

- HLTB DataBrowser type-select in 'choose from list' issue fixed

- Fixed ImageIO sips issue

- Fixed NSNavigationServices stripping suffix from file name issue

- Issue with libresolv fixed

- Fixed issue with iCal HI and invited events

- BaseWritingDirection and CoreText Layout now works correctly

- HLTB Windows: Resizing a window with a drawer now draws correctly

- Space activation feature now works correctly in HLTB Windows

- Fix to HLTB Menus and iTunes Help Menu

- Fix to CFURLConnection

- Fix to Text Services Manager and CGEventKeyboardSetUnicodeString

- Issue with CUPS and identical USB printers resolved

- Resolved issue with ImageKit and GC

- HLTB Control Manager and file-based image content resolved

- Fixed issue with Accessibility API and HLTB Menus

- Issue with Fast User Switching and input method resolved

- Fixed issue with Page Setup/Print Dialogs and 64-bit applications

- kThemeAdornmentDefault now works correctly

- FindControl now returns correct value for control at negative vertical coordinate

- Issue with HIShrinkToFit and window width fixed

- Fixed preference syncing issue with Sync Services Engine

- Issue with SpotlightIndex and finder comments resolved

- Problem with Proxy Authentication and CFURLAuthentication fixed

- Fixed freezing issue with Accounts pref pane

- Fixed filtering issue with Sync Services Engine

- NSImageBitmapRep now returns correct bytesPerRow

- Fixed issue where Cocoa apps may crash if carbon events handled prior to NSApplication instance

- Issue with iCal Invitations and email invitations

- CoreImage: CILinearGradient now works correctly

- Fixed hanging issue with Preview application and QuickDraw Manager

- Resize volume issue with Disk Utility during install resolved

- Implementation of recurrence rules in VEVENTs now works correctly

- Issue with RTF Handling and certain file types fixed

- Fix to CreateLocalIsochPort

- Issue with migrating backup.backupdb fixed

- Read Only flag issue fixed with iCal Synchronization

- Issue with NSMenu resolved

- Fixed issue where Cal UI wouldn't update with API changes after window is closed

- Fixed issue with CoreFoundation and uppercase letters in urls

- CoreGraphics: Issue with clipping to scaled images resolved

- Issue with Time Machine Preferences and stated available space fixed

- Fixed issue with SMB and Kerberos reconnects

- CoreText Layout: CTRunDelegate advance width now applied correctly

- Issue with Expose/dashboard invoke keys and HLTB Menus fixed

- Fixed issue with CFURLCookies

- Fixed problem with iCal To Do List and Preferences

- RRULE now interpreted correctly in .ics import

Link to comment
Share on other sites
Proficient

Cadium

Posted
Posted
I see a few SMB fixes there, but really, the SMB in leopard really sucks. It's way way worse than Tiger. For instance, a lot of times copying files over to a new empty share just results in the data being removed after the copy has completed.

You can read more about it here: http://discussions.apple.com/thread.jspa?messageID=7821900

I have never encountered that issue with Leopard from 10.5.1 (when I first purchased my MacBook Pro) right up until now (10.5.4), and I work with SMB shares frequently every day.

Link to comment
Share on other sites
Experienced

kaiwai

Posted
Posted
I see a few SMB fixes there, but really, the SMB in leopard really sucks. It's way way worse than Tiger. For instance, a lot of times copying files over to a new empty share just results in the data being removed after the copy has completed.

You can read more about it here: http://discussions.apple.com/thread.jspa?messageID=7821900

And if you see their signature, none of them are running 10.5.4. Why should help those who can't even be bothered doing the basic thing of updating their software?

Link to comment
Share on other sites
Collaborator

dyn

Posted
Posted
:(

Go into network utility and check, it'll probably be 130MBPS, not 300MBPS.

That would be because the router is running in 802.11n and 802.11g mode with one or more 802.11n devices and one or more 802.11g devices connected to it. It's normal behaviour to do so it seems. If there are only 802.11n devices connected it will be an 802.11n only network providing the theoretical speed of 300Mbps. However, if one or more 802.11g devices connect to it, the network will become a 802.11n network supporting 802.11g which will drop the theoretical speed of 300 Mbps for the 802.11n clients to 130 Mbps.

There is a solution to fix this: setup 2 seperate networks: one 802.11n only network and one 802.11g only network. You might need more then one device to do this.

In short: this is not a bug, it's a feature (and not the Microsoft kind of feature in this case but a real one) ;)

It also has got nothing to do with Apple, MacOS X, etc.

Riddle me this: when you create a MobileMe account in Mail after 10.5.4 and the MobileMe update, it sets up the outgoing server as port 25. Previously, when the service was .Mac, this port number was 587. Why does it do this?

Ironically enough, using the default configuration for that only works half the time (the other half of the time, I will get outgoing server errors), whereas when I change the outgoing port number to 587, everything suddenly works. I've ruled out the possibility of it being an ISP issue.

The setup wizard in Mail will autodetect the correct mailsettings. I'm guessing it will try to connect to the server or it does a simple port check, checking what port is being used (that probably will be just the common ports used for mail). If port 25 is not available (due to something that some ISP's like to call "antispam/virus measures" (which it's really not, there are far better methods for that) as Cara already said) it will try the submission port (port 587). Mail also tries if it can connect using things like SSL. In my case it managed to detect that the Gmail IMAP and SMTP server both use SSL. Mail did setup my Gmail account using SSL and not the submission port as port 25 can not be used since it's blocked by my ISP.

Blocking port 25 is one of the most stupid things an ISP can do because it really has no effect on spam and virus stuff. It puts the ISP in a position where it's mailservers end up on several blacklists and a lot of unhappy customers because mail they send never got to the recipient. There are better solutions for this which unfortunately aren't used by ISP's on their mailsetup (e.g. sender/recipient verification, greylisting, other forms of scanning/detecting virusses/spam). Not a customerfriendly setup.

Link to comment
Share on other sites
Grand Master

Cara Veteran

Posted
  • Author
  • Veteran
Posted

959 Bump

--

Officially updated to the main thread. I was holding out till I got back to my desk, however it seems the next build was delayed, not sure why...

Link to comment
Share on other sites
Grand Master

rajputwarrior

Posted
Posted

hopefully apple will actually fix the wireless issues the macbooks are having. You know, cause having a N card and not being able to use it with N routers is so sweet and all...

Link to comment
Share on other sites
Grand Master

giga Veteran

Posted
  • Veteran
Posted
hopefully apple will actually fix the wireless issues the macbooks are having. You know, cause having a N card and not being able to use it with N routers is so sweet and all...

What router?

Link to comment
Share on other sites
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.