ISP Blocks port 25, server rejects 587

I have a client who's home ISP blocks outgoing mail on port 25, when I switch his client to 587 to circumvent this, I get an error that the server rejected the connection on that port. I have double checked the firewall that 587 is open for traffic, but the rejected connection continues. Is there something I am missing?

If your client trying to send mail from his home via his office mail server, then a VPN can be an option. That'll solve various problems here, including the firewall blocks (often found on inbound and outbound port 25 from dynamic IP addresses) and it'll provide secure connectivity and ease-of-use benefits. It'll operate like the client is "on" the office LAN, if established at the external firewall.
But yes, configuring the office external firewall and the mail server to enable and allow the SMTP submission ports is normal practice, particularly if the mail server connections are comparatively fleeting as can be the case with remote and mobile clients. Both unencrypted and SSL connections are possible. And the submission ports isn't generally considered "circumvention", it's basically the normal path into a mail server for authenticated users. (Connections into the mail servers from dynamic ports are usually spam engines.)

Similar Messages

How can I use Back to my Mac when my ISP blocks port 1900?

I was just forced to switch ISPs (don't ask...) and it turns out that my new ISP (Astound) lied to me and actually does block port 1900, which means that Back to my Mac (on which I rely) does not work.
Has anyone seen this and found a viable workaround? Preferably one that is easy for my non-technical family to use also, but all suggestions are welcome.
Thank you!

So, I convinced my ISP to open port 1900 and they did, but it's still not working.
I get two messages that make no sense to me, but I hope indicated something that someone here can help me undertstand...
When I open the iCloud preference pane in System Preferences, It says just below the Back to my Mac setting "Configure Router for better performance" - My Airport Extreme is configured with Back to my Mac and it looks like my account shows a green indicator.
Second, next to the Back to my Mac setting in the iCloud preference pane, there is a button labeled "Details..." When I click that it tells me that "Back to my Mac is not working properly because the DNS server isnt' responding" and suggests I contact my ISP for a different DNS server.
All other internet services - including iCloud services - are working fine. I even tried changing my DNS servers to Google's public DNS servers and nothing changed.
Any suggestions are very much appreciated! Thank you!

Blocked Port? Mailboxes?

hey all, I'm trying to setup my website email in Mail. It downloads all the mail just fine, but I cannot send email out. I realize after combing these forums that it's quite likely that my ISP (Comcast) has blocked Port 25. BUT, I use Entourage to download my Yahoo email and it sends/receives mail just fine. So I'm wondering what the deal is, cause if the Port 25 was blocked, wouldn't I have the same troubles with my Yahoo account in Entourage sending mail?
Also, is it possible to have each individual account you have setup in Mail (i.e. .Mac, Yahoo, etc) to have the incoming messages come into it's own mailbox? Instead of it being a free-for-all in the inbox?
Any and all help is greatly appreciated. Thanks!
Powerbook G4 Mac OS X (10.4.5)

This drove us CRAZY around here for several months. I knew it was the port 587 thing but couldn't come up with the info to fix it. We ended up adding port 587 to the mail server along with port 25. This info was in a response to my posting back on Nov 3. Here's the info member William Lloyd sent me. It worked perfectly.
Michael,
First, this is the Xserve forum -- there is a separate forum under OS X Server for the Mail Server -- I'd suggest you post in the appropriate location.
Second, if you have enterprise support from AppleCare, they can probably help with this. The AppleCare Select agreement starts at $7999/year, I think. If you call the consumer line, it's unlikely you'll get assistance with this.
Finally, you can enable Postfix to accept mail on a port other than 25, to get around the "ISP blocks port 25 due to spam concerns" issue. It's a simple modification to the master.cf file.
Here's what it would look like, if you wanted to also enable port 587:
To add a second listening port on 587, edit master.cf like this:
You should be able to just add another port that postfix listens on. Leave the port 25 stuff in there, and add a second port for smtpd.
So as root, edit the file /private/etc/postfix/master.cf, so it looks something like the following, assuming port 587 for the purposes here. You'd want to pick a port that didn't have a conflict with another service, and it should be above 1000 (below 1000 is only accessible to root).
# =====================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# =====================================================================
smtp inet n - n - - smtpd
587 inet n - n - - smtpd
Do a little Google digging for more info.

Need to relay to ISP through port 587

Hello,
We need to set up relay through ISP smart host, but use the 587 port.
What Postfix file needs to be changed for that?
Regards
Kostas

Do I need to regenerate sasl_maps?
I can't imagine sasl_maps has any connection/bearing on relayhost
What to do with Server Admin GUI? Do I set it there, too?
For the most part all Server Admin does is view the current config file (in this case main.cf) and writes certain parameters (ones it knows about), so in this case when you open Server Admin and look at the mail settings for 'relay all messages through:' it just reads the relayhost setting from main.cf. If you change the setting in Server Admin, it just writes the value back to main.cf... in other words, Server Admin is just a GUI front end to the same file.
Therefore I'd expect whatever value you set manually in main.cf to appear when you look at the settings in Server Admin (and vice versa)

Web Server Blocks Port 80 - What am I to Do?

I have a WebSite that will load up locally, but not remotely. I think it's because the web server is blocking port 80. How do I get around this (port forwarding - how do you do it)?

There are a few ways to do this... This is what I do, personally... This is sketchy, but you can figure it out with some research and lots of googling!
1. Set the machine that will be the server to use a static internal network address. I use 192.168.2.100. This is the internal, non-routable IP address of the machine on your network. This is not the IP that your modem/router receives from your internet provider.
2. Open an external port on the router that is not blocked by your ISP. I use port 5100. Then configure the router to listen on external port 5100, and pass all "port 5100" traffic to 192.168.2.100 and port 80. By doing it this way, I avoid having to edit the apache configuration. Apache listens to port 80 by default. Apache does not realize that the traffic originally entered the network on port 5100.
3. If your external IP address is dynamic, you will want to start googling "dyndns". It is a free service that will let you "register" a domain name. In my case, my router notifies DynDns automatically whenever it gets a new IP from the provider. This way, I don't have to remember my IP address, which changes anyway... I just remember my domain name. I can use any network service, such as SSH, Apache, ftp, etc....
Good luck!

Mail Server when Comcast blocks port 25

I want to host a mail server, and am able to get mail to send, but am unable to receive mail. I tried sending an email from my gmail, and it gets delayed because it can't connect to xxx.xxx.xxx.xxx:25. I then found out that Comcast blocks port 25. Is there a way to change what port the server app uses so it can receive mail?

This is a common question; you're not the first person to have considered resetting the SMTP TCP port.
As Strontium90 indicates, you can most certainly set up your own global mail infrastructure on a variant port (possibly even by using DNS SRV records to find the port de jour), but by the time that's all coded and debugged and generally accepted and standardized and in widespread use around the planet, Comcast and the other ISPs will probably just detect and block the new port or the new service on their residential service tiers. Which means you'll need to add TLS encryption and potentially random ports, and down the proverbial rabbit hole we go.
But seriously, the usual and preferred and best approach is a business class service, as that has port access and you can get correct DNS. Without correct forward and reverse DNS translations, many other SMTP mail servers will detect a dynamic IP service as a spam engine, and drop outbound mail as it arrives. Some mail servers will detect this and will also drop inbound mail, as well.
As an alternative to a business-class service, you can set up a mail relay through your ISP, or potentially a relay via a commercial mail relay service — if either of these approaches is permitted by your ISP terms of service. There are various folks that offer these mail hop services by subscription, but then all your mail is routed through that service and that may or may not be desirable.
Hosting your own virtual private server or dedicated host just for mail can be pretty cheap these days, if you're willing to run your mail server in a data center. That avoids all entanglements with your ISP. (But again, if you're willing to host your mail elsewhere.)

Outgoing port scan to find blocked (by ISP)/open ports

Hi,
How can I do a port scan (network ports, where web pages/applications use port number 80 for example)? I would like to find out if my ISP are blocking ports -- get some hard data/facts. I've tried using an online port scanner (one that operates from a web page/server) and according to it, all my ports are blocked -- but I now realise that's incoming (to me) where I didn't initialise the communication. So I suppose to find out what I want I need to initialise the communication -- outgoing (from me) communication. How can I do this? Any software / utilities available anywhere? I tried the "port scan" in Network Utility but this never reported anything. Maybe that will do what I want but I didn't have it set up properly possibly?
Any suggestions / ideas much apprecaited.
Cheers,
John.

Hi,
I'm not sure what you're asking.
What I'm asking about is in connection with the action that some ISP's take described as "traffic shaping". I know they are filtering/blocking because all P2P applications stop working for a period of time each day while email and web pages continue to work fine for example. I'm thinking of complaining to varous organisations because I have it in writing from the ISP they don't do this. They do, but I just want a bit more factual data first, before spending time and money making official complaints.
ISP's rarely block outbound packets
Well there's traffic shaping of some sort happening. I've found out that all incoming initialted outside packets are blocked but things still work fine so I assumed it must be outgoing which are being blocked.
If you can't make an outbound connection, it's usually the return (ACK) packet that gets blocked.
Right, I see. In that case another cooperating machine is needed to find out what I'm after I suppose.
However, most firewalls have a rule that allows packets through that are part of existing connections. That allows you to browse the internet no matter what source port your browser uses.
This isn't about a protection, it's about an ISP stopping/filtering certain uses (ports) via their connections because they don't like it -- too much band width use probably.
By far the best packet sniffer is Wireshark (formally Ethereal) for display of the capture.
From what's said above, a packet sniffer isn't going to be enough right? There needs to be two machines, me sending to another on various ports and it replying on the same port and both machines keeping a log of what's been sent and received, then a comparison made to see what made it and what didn't --- I guess. I wonder if there is such a service, piece of software, whatever, out there?
Is your computer behind a router in your home? Of course that would include Airport. If so, that is more likely the culprit than your ISP.
Yes an AirPort base station. Say "that is more likely the culprit than your ISP" again after visiting http://www.reviewcentre.com/review210703.html and searching the text for "traffic shaping" a few times! I'm pretty sure I've got the base station set up fine. And I think it's more likely my ISP (the one reviewed at that link) is the culpret. P2P software stops working, well it varies, but it reliably stops during "peak hours". It's the ISP for sure.
I don't know any ISP that blocks all ports.
Well, for incoming, according to the http://www.websecurity.mobi/network-security-audit/178-no-open-ports-my-machine- obviously-rediculous.html (which is me expressing surprise about all incoming ports being blocked) my ISP does. Apparently there is quite a difference between incoming and outgoing. Stops people using their machine as any kind of server (according to that link). One thing I do notice is that doing:
sudo tcpdump -v -x -s 128
on the command line while I'm not doing anything on the internet results in nothing -- complete silence as it were. On the dial up connection I've just left doing that command there was stuff coming in all the time -- who knows what, but the complete silence on my new broadband connection would back up the idea that all incoming ports are blocked. I could be wrong of course.
"nmap" is probably the best portscanner available but as you discovered, OS X has one builtin that you can access through the Network Utility.
Oh right I didn't know they were the same thing. I found that the port scan in NU didn't do anything. I left it for hours. There was an IP address which I left as it had filled it in itself. Maybe I should have changed that? How can I get the right address, or does it usually fill it in correctly itself?
What actually does a port scanner like that one do? Send something out? To what? And how does it know if it got there?
It seems to me to get what I need there needs to be first a suitable piece of software, second another computer running the software ready for my computer to talk to and to communicate multiple times and see what happens. My point is it's not just a piece of software that's needed it's also another cooperating computer elsewhere that needed? Otherwise what's the testing software going to talk to to see if the channel is working?
I'll look into the Port Scan in NU again, see if I can get some actual results from it this time. On a broadband connection I left it for about, I don't know, 3 hours maybe, got nothing.
Cheers,
John

Mail, returned mail, blacklisted ISPS and port selection

I live in Spain and my e-mail, especially to US friends and colleagues, is increasingly being returned to me, even though I have been e-mailing them for years, because it is now being identified as spam. E-mail to family, friends and colleagues in Spain and other countries is rarely treated this way, I suspect because US ISPs are more pro-active in blacklisting spammers.
Error 526, listed on the returned e-mails, is identified by AT&T as being a spam problem. The site at spamhaus.org identifies a whole IP range, within which the IP assigned to me (I'm not sure whether it is assigned to my computer or router or my ISP's outgoing mail server(s)) as a spam source, even though I send no spam at all.
I use Mail 2.1.3 as part of OS 10.4.11.
I have spoken to my ISP at huge length, and expense, about this and they say they can do nothing to get their IP range removed from the blacklist, although various websites make it clear that ISPs can do this, if they want to. The real problem is that there is very little choice of ISPs in Spain, and the ISPs are all as badly run as each other and not one of them is remotely service-oriented. So changing my ISP will not achieve anything. The secondary problem is that I appear to know more about ports, and mail programs than the 'technical' staff I am talking to at my ISP, so they just say they do not know how to or cannot help me.
Two possible solutions occur to me.
1) I could ask for a fixed IP address, paying a little more each month. Would such an address apply to my computer, my router or all 4 or 5 computers, wired or wireless, on my LAN? Would a fixed IP address normally fall outside the range of dynamic IP (address) numbers).
2) The standard smtp port used by Mail for outgoing e-mail is port 25. Authentication, by my ISP, is by username and password. However, I have read that port 25 is filtered by receiving ISPs for spam, in other words port 25 does not do a 'full' authentication job. In contrast, port 587 is supposed to do a 'full' authentication job, and e-mail proceeding from that to other ISPs is supposedly not filtered. So I have tried sending mail out through port 587, but this doesn't work. Do I have to turn SSL on? Do I need to open port 587 in my router's firewall? And does my ISP have to make some adjustment at their end? They say they cannot and do not have to, and that I can send e-mail through any port I choose to???????
I have looked to see where port 25 is currently open, but there is no mention of Mail or port 25 in any of my router settings, so other than specifying in Mail preferences that the smtp server port number is 25, or 587, I don't know where else to look.
All help would be deeply appreciated.

1. That likely won't make a difference at all, any IP the ISP gives you will be in the banned range.
2. None of that matters at all to the "ban", different port usage is strivkly dependant on your ISP's set up on their end.
I think your only solution is getting something like a free gMail account. After you sign up...
http://email.about.com/od/macosxmailtips/qt/et_gmailosxmail.htm

Mail: outgoing and now incoming mail server rejects password

Hello all. Hope you can help with this one.
I was using Mail as normal yesterday. I use the same incoming mail server and SMTP server (my university's Exchange server). Then sending mail suddenly failed. The error message I get is:
The SMTP server “exch.wlv.ac.uk” rejected the password for user “(null)”
Enter your password again or cancel.
The settings are port 995 for outgoing mail, using SSL and requiring password authentication.
I've verified my settings and passwords with IT support. They say they haven't altered anything, and nor have I.
I've tried Connection Doctor: it says Mail connected with the exch. server without any problems. However, under Account Information, the server says (offline).
I've changed ports (to 25 and 587): no success.
I've deleted my password from Keychain and Mail plist and reentered it. No success.
I've verified and repaired permissions.
I'm now not getting incoming mail either: the error message is
There may be a problem with the mail server or network. Verify the settings for account “Staff POP” or try again.
The server returned the error: The connection to host exch.wlv.ac.uk on port 25 failed.
I can send and receive using web-based OWA.
Is there anything else I can do, or is it a server problem?
Thanks,
Aidan

May be no help to you Aidan except comfort in numbers. Mail has started behaving erratically for me in the past week. My inbox and account mail has disappeared and my accounts keep being rejected by the webmail host similar to your problem; password rejected etc. Then Mail closes abruptly telling me there's a problem and offering to send a report to Apple. Mail is version 4.5 and the iMac is 10.6.8. Help!
Maurice

I am really upset at verizon for blocking port 25

I am very upset at verizon blocking port 25 ....
Now I can't send mail through email accounts that I have. (only support 25 for SMTP because they are normal)
!!!_)*_)*!_)*!_)*!+_(!+_+$+$(_&*_+!*#!
That is what I have to say about it.
There should be a law against a utility turning off a standard service. It is like the electric company all the sudden deciding they will only send DC. Now my appliances don't work.

Howard3 wrote:
I am very upset at verizon blocking port 25 ....
Now I can't send mail through email accounts that I have. (only support 25 for SMTP because they are normal)
!!!_)*_)*!_)*!_)*!+_(!+_+$+$(_&*_+!*#!
That is what I have to say about it.
There should be a law against a utility turning off a standard service. It is like the electric company all the sudden deciding they will only send DC. Now my appliances don't work.
All you need to do is to change the outgoing server on your non verizon accounts to
outgoing.verizon.net
Check the authentication box and enter your verizon mail userid and password under setting and in the advanced tab make the port 587
You've wasted more time in compiling the complaint than it would take you to fix the issue.

Problem: Cannot send mail unless Password is transmitted insecurely & Port is set to 587.. Can receive mail but can't send..

Problem: Cannot send mail unless Password is transmitted insecurely & Port is set to 587.. Can receive mail but can't send Code 501..
Need help with T-bird.. My OS is Win XP-64..Have been using Mozilla for about 10 years with little or no problems.. This happened when I upgraded to 3.17.. Spent hours on T-Bird diagnostics web site.. Called Comcast & talked to a net tech.. he ran some tests on his end & had me log into my Comcast e-mail account & all worked well,, so he concluded the problem was in T-Bird.. He had me change my port to 587 & disable connection security & authentication to none & I was able to send mail.. That was all he could do.. Comcast was working.. the problem is in T-Bird.. Can any one help with this problem.. I don't want to send mail with my password transmitted insecurely..
Thanks
Richard

It was not intended to be "snide". You said two separate things that at face value would be out of the ordinary.
I considered if it might be a typo for 31.7. Since 31.5 is the current formal release, I would have to thank you for volunteering to test a pre-release beta version. If it was truly 3.1.7 then it would appear that you have chosen, or have become stuck with a somewhat ancient version. In either case it's harder to reach out to you with any meaningful comments or advice. However I do watch various other sites and newsgroups and I don't see a clamour of distressed users, so it seems fair to suppose that this feature isn't actually broken in 31.7.
And you said XP 64. XP is obsolete and no longer supported and if there is a 64-bit version, then again you have set yourself apart from the mainstream.
I had a look at the comcast site and found some puzzling recommendations. Some users come here asking how to set up a secured connection in Thunderbird when it isn't offered by the server. Comcast are different, in that they mention the ports 143 and 587, and also 993 and 465. So far so good, in that security is actually on offer, but they also suggest that you enable SSL, regardless of which port is being used. It would be unusual and unconventional to offer TLS or SSL on ports 143 and 587. STARTTLS would be more credible on these ports.
Have you tried IMAP on 993 and SMTP on 465? SMTP on 587 with SSL, or TLS, is not impossible, but is improbable.

Configuring socket policy for flex apps(with blocked port 843)?

We have built several flex-based ecommerce apps for a fortune 500 customer of ours, that for various reasons, we need to use sockets to a different domain and requires a socket policy file, but were having trouble configuring our flex apps for deployment in thier enviornment where they are blocking virtually everything except port 80 . The current documentation in in regards to socket policy files and crossdomain files in a non-standard configuration not using port 843 is not providing any useful help to us.
Here is the scenario:
Flex apps are served from domain www.a.com in to users browsers via http. The apps then make socket connections to domain www.b.com:80 where there are php scripts serving json data to the flex apps via port 80 using http(we use sockets because we need to set and read back http headers). The problem is the flex apps cannot make socket connections to the www.b.com domain without errors like below(unless we setup a socket policy server on port 843 of www.b.com, in which case everything works):
Warning: Timeout on xmlsocket://www.b.com:80 (at 3 seconds) while waiting for socket policy file. This should not cause any problems, but see http://www.adobe.com/go/strict_policy_files for an explanation.
Error: Request for resource at xmlsocket://www.b.com:80 by requestor from http://www.a.com/bin-debug/DownloadManagerFlex.swf is denied due to lack of policy file permissions.
Error: Request for resource at xmlsocket://www.b.com:80 by requestor from http://www.a.com.us/bin-debug/DownloadManagerFlex.swf is denied due to lack of policy file permissions.
Since we cannot use port 843 for the socket policy file server, we setup the socket policy server on a different ip in the same domain: spf.b.com:80 (using the sample perl code Adobe provides), and per the docs(cited below), use Security.loadPolicyFile("xmlsocket://spf.b.com:80") before we invoke "socket.connect", to supposedly tell the flash player to check there for the socket policy file. The problem, as you can see from the error log, is that the loadPolicyFile("xmlsocket://spf.b.com:80") is ignored.
No matter what we do or how we set things up, we cannot get the flash player to recognize the loadPolicyFile(), it always wants to go to the port were making the socket connection on. It is unclear how to properly configure the flex app, socket policy file and crossdomain file for the above scenario. The docs allude to being able to serve the socket policy file from a different port 80 in the same domain as the socket connection were trying to make, but were having no luck with that.
->Can anyone shed some light on how to make this work or what are we missing/doing wrong? Also, if we can get this to work, are we stuck with a 3 second delay because this(very large) customer is blocking port 843?
As an aside, the documentation for all this is a bit scattered, unclear and contrdictory:
One document says:(http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security_07.html)
"This warning usually means one of two things: first, that you need to set up a
            socket policy file server on port 843, which is the first location that Flash
            Player checks by default; or second, that you need to provide more explicit
            guidance to Flash Player from ActionScript by calling loadPolicyFile to indicate the location
            of a socket policy file. When you call loadPolicyFile rather than allowing Flash Player to check
            locations by default, Flash Player will wait as long as necessary for a
            response from a socket policy file server, rather than timing out after 3
            seconds."
Another document says(http://www.adobe.com/devnet/flashplayer/articles/socket_policy_files.html):
"If an ActionScript Security.loadPolicyFile() command exists within               the SWF file, then the Flash Player runtime checks that location. Flash Player checks               the destination of the loadPolicyFile() only after it has checked the               master policy file on port 843 for permission to acknowledge other policy               files. If the developer has not specified a loadPolicyFile() command,               then Flash Player checks the destination port of the connection."

I found the reason why the Flex application was ignoring the socket policy (crossdomain.XML). I have a policy server that listens to port 843 and submits the policy to the Flex client. My policy was getting ignored by the Flex application and I was getting the sandbox security error you were getting. The solution to this problem isto write a null byte right after the policy server sends the policy. I'm using Apache Mina that is wrtten is Java and the null byte is written as follows:
public void sessionCreated (IoSession session)
        throws Exception
        session.write(_policy); -- > policy string
        session.write("\u0000"); --> null byte
         //session.close(true); ---> No need to close the session because it is closed by the Flex client after it receives the null byte.
Now my Flex application can read and accept the policy from port 843 and I'm not getting more security violations.
Thanks for your reply,
Alberto

Comcast POP Server Rejecting Password & Now Dysfunctional (Keychain?)

I'm starting a new thread because a related topic "POP server rejecting password" is marked answered, but for Charter, which solution will not work with Comcast. Comcast has advised that some problems are stemming from internal changes (commencing near the end of November 2007) mandated by the FCC to improve security. But, given that I can access the Comcast email account remotely via my Treo Smartphone (using Sprint), and via Comcast Webmail, makes me think that my Mac (OS 10.4.8) and/or Mail application may also be culpable.
I specifically am having a problem with a Comcast email POP server, but not two other POP inboxes hosted by another, unrelated ISP, also managed by Mail.
When I open Mail, the Comcast mailboxes (both inbox and sent) are grayed out with a ~ next to them--I've never seen a ~ before. The other two mailbox pairs (the non-Comcast ISP) work normally. Selecting Mail's Connection Doctor produces the results: "Connection and login to server succeeded" for the Comcast POP and "Connection to server succeeded, no login required" for the Comcast SMTP--no difference when compared with the results for the other, non-Comcast ISP mail accounts. This is notably different from posts in the other thread.
Historically, I'd occasionally (perhaps monthly or so) get the popup request "Enter Password for Account..." Comcast previously conveyed that such treatment is normal. I perhaps could have alleviated this by adding the response to the keychain, but never bothered. Problems began yesterday when typing in the correct password resulted in the same request, repeatedly without end.
Called Comcast tech support (three times now), verifying that the Mail application is set up OK. They acknowledged that they were experiencing some server outages, but that was unlikely the issue since I could access such via Comcast webmail. Of course, they referred me to Apple--my Mac "had to be the problem."
The other topic suggested, perhaps, that keychain was at fault. So, using the Keychain Access utility, deleted all items. I was motivated to do this anyway based on speculation last week by the Trash It scriptware developer that I may have keychain corruption, as regarded another, hopefully unrelated problem, now resolved, having to do with attempting to eliminate "localized.rsrc" files from the trash via the Terminal command "sudo rm -R ~/.Trash/*" returning the error "...(my formal user account name) is not in the sudors file."
Pulling my hair out on this one.

Comcast fixed the problem they were having with their server(s). No explanation, of course. Guess the problem was theirs entirely--no fault on our side.
Thanks David for your insight on what the (~) meant. Tried going online, but upon Mail checking, the affected mailbox immediately again went back offline--at least until Comcast fixed its end.
As regards the POP servers, yes I suspect there are intervening servers (PoP or otherwise) between users and the underlying database holding the email. All Comcast would acknowledge is that customer service representatives access the same customer email repository as do individual customers themselves, whether by POP or Webmail (Duh).

Can't send mail, get message: the smtp server rejected the password. I tried lock and unlock keychain. I tried unlock captcha. Gmail works okay, it is Mail that does not. Help!! :(

Can't send mail, get message: the smtp server rejected the password. I tried lock and unlock keychain. I tried unlock captcha. Gmail works okay, it is Mail that does not. Help!!

Hi
You need to check with your ISP whether or not the send mail server (SMTP) requires a password. Some do, but many do not. When you know the correct password to send mail, then you need to tell Mail as follows:
Mail menu > Preferences > Accounts > Select the account
Click on the Outgoing Mail Server (SMTP) combo box, and select Edit SMTP Server List...
In the Account Information tab put the server name
In the Advanced Tab, set up the authentication information from your ISP.
Good luck
Bob

Binghamton University Blocks Port 5060

I dropped my daughter at her new college and discovered that we are unable to make an iChat video connection between her MacBook and my Powerbook. Specifically I am getting a message that the other person did not accept the incoming call and it times out. This happens no matter which side originates the call.
I have had no trouble using iChat from home before this so I checked the Apple forums and learned that this problem is typically a result of a blocked port (5060). I contacted my daughter's school's IT department and asked them if they were blocking 5060. They said they do block 5060 and that it was not likely they would NOT block it based on my request. I sent in a formal request anyway but have not heard back.
I was able to video chat using SightSpeed and plan on testing Skype this evening.
If this is the problem then it is a kind of big problem because it means that none of the students on the State University of New York networks can use Apple iChat. There are a lot of students on many campuses all over the state.
Before I begin lobbying the Governor of New York to change this poilcy, anyone know of a workaround for making iChat video connections when an ISP is blocking 5060?

As you have probably read port 5060 is one of the ports "reserved" for SIP, the protocol that all VoIP devices and Apps use.
It is one of a range (5060-5063) that can be used.
VoIP apps and devices allow your standard Line line connection to use the Internet to make phone calls.
Now as there are 4 port to use iChat and other apps are supposed to move up to the next free one and try that.
Many large corporations and campuses are now using VoIP phone services because it is cheaper.
Now some ISPs are also trying to recoup money by blocking these ports when they offer a VoIP service.
Partly as a result of the competition these make to their standard phone services but also to stop people using equipment such as the Vonage type adapters.
However it does seem if they are challenged (rather than confronted) about changing their service and blocking an application they offer without proper warning they often change the users service back again.
At the ISP level there is also the fact that it is an International Standard and they can not be seen to be blocking it.
As whether a University is blocking it to save confusion with their phone service, or because they want to protect bandwidth, or feel it would make their phone service too un-secure would remain to be seen.
Of course what they probably mean is that they are blocking all SIP ports.
This would prevent student using SIP/VoIP phones and certain parts of Skype and other apps as well as iChat.
The Bandwidth issue would easily be dismissed as anyone (or group) can download anything in a web browser and easily swamp any service if they so tried.
I have seen a case where a student pointed out they were a paying customer and that the service for their room included "Internet Access" and had not pointed out these restrictions. They were given their own IP address to circumvent any issues.
So in summary.
iChat has three other ports to use.
These are probably blocked as well.
Unblocking or challenging the block would need to look at the size of the potential user base with problems (iChat and other apps or devices) and the reasons the University states for doing so. If, and it is a big IF, iChat is the only thing that is blocked there is always discrimination to look into.
8:45 PM Friday; August 24, 2007

ISP Blocks port 25, server rejects 587

Similar Messages

Maybe you are looking for