Mail.app in 10.4.7: SOCKS proxy issues again...

Hi,
Today I've updated my PowerBook to MacOS X 10.4.7. All the process was fine, but Mail didn't connect to any server. After reading some posts in this forum I've unmarked the SOCKS proxy settings in the Network pref. pane, and I've recovered the 10.4.6 functionallity. So at least I can work.
When I'm at office, we have an Exchange server with direct access in the network ( is because this that proxy is not needed ). Also a proxy server controls the Internet access.
What is not working in Mail ( or I don't know how to use it ) now is the following:
- Local access to Exchange server is only possible using a POP account. An Exchange account doesn't work because is always asking the password.
- I need to disable the SOCKS proxy to be able to access the local mail server. So the 'Bypass proxy settings' in the Network preference pane seems to not work ( I've tried all kind of syntaxs: *.domain, server.domain, IP address, etc. )
- With the SOCKS proxy settings active in my corporate network, I cannot access external mail accounts in external servers. I've tried IMAP and POP accounts with the same result: nothing. This is the same issue than in previous version of Mail.app.
So waiting again for a Mail patch...
Regards,
Joan B. Altadill
PowerBook 17 Mac OS X (10.4.6) 10.4.7 !!!!!
PowerBook 17 Mac OS X (10.4.6) 10.4.7 !!!!!

Similar Messages

When trying to send photo or web link my email ends up in gmail outbox and I have to go into mail app open outbox and email and press send again and it will send without any trouble

Hello
I would be very grateful for any help with this problem. It is really annoying as I think the email has gone only finding it after days in the outbox. It sends fine from the outbox when I open mail and resend. It also works fine if I initiate email in the mail app but not when using link in photos or safari.

Taking the accounts offline was just the easiest way to reproduce the issue. I discovered the issue when a serverside configuration was preventing me from making a connection to the SMTP server, but the effect was the same -
I attempted to send multiple emails
The connection error prevented them from being sent so they were placed in the Outbox mailbox
I changed a configuration setting thinking it would fix the issue
Selected all messages in Outbox
Right-clicked and selected "Send"
Confirmed "Send"
Messages were removed from Outbox but not delivered and I cannot find where or if they were moved
I have been able to reproduce this by both taking the accont offline and misconfiguring my smtp settings. I did not anticipate the possibility that sending emails would be a destructive act.

Mail.app won't work properly after installing Yosemite

My "new viewer window" in Mail.app won't work after installing Yosemite. I can not access the viewer window and thus none of my email.
How can I fix this?
Mail.app v 8.0

some updates on this issue, Mail application uses the same proxy that has been set on your system (system preferences==>Network==>Advanced==>proxies). People usually use HTTP/HTTPS proxy for surfing the web. You should make sure to set SOCKS proxy as well. Mail application works with SOCKS proxy. Note that port number for SOCKS proxy is usually different from the port number for HTTP and HTTPS but the IP address of your server (apparently) is the same.
Hope this helps

Mail.app and Netscape Messaging Server v3.6

We are trying to track down performance issues with Mail.app in both Tiger and Panther. Issues include how long it takes to download large attachments (PDFs upwards of 10MB), how long it takes to synchronize and cache, and other things that appear in Mail's activity window and never go away. Downloading large attachments puts a large CPU load on our mail server. We are looking at all variables -- switches, network configs, local client settings, etc. We are on a switched network with a mix of Gig and 100BT to the desktops. But my question here is: What might be the advantage of upgrading to a newer mail server? Our Netscape 3.6 software is very old, but the Sun hardware it lives on had a CPU upgrade last year. Even though the IMAP protocol itself has been pretty stable for years, would we find newer platforms more efficient with modern needs such as large attachments and inboxes that receive dozens of messages a day?

Wow, this is dusting off the cobwebs. NS 3.X has a different format for mail message, the IMAP data is contained in the first 400 bytes (or so) of the message file. So sending them through the deliver program is not an option, unless you strip the bytes off.
When you ran upgrade on an individual user, did you first remove the 4.15 mailbox with mboxutil -d?

Mail.app keeps multiple copies in Draft and does not delete after send

I have just recently noticed this problem and it seems to be getting worse. I am on Mountain Lion 10.8.1 and I'm using an exchange server (2010) email account.
I do not recall this problem being this bad in Lion. When I save a draft go back into it, make changes, it saves a bunch of copies. I just deleted about 30 emails from one draft.
The 2nd issue is it does not leave the draft folder when I actually send, so it appears I never sent it, but I did. This is extremely frustrating and not efficient. I use Mail for my business email and all my personal emails as well, but mainly business.
I don't like Outlook for Mac (too slow), and I really don't like Mail for Mac either since my contacts and calendar are all in different apps.
Does anyone have a solution for the DRAFTS folder issues and/or can you recommend another e-mail client that is better. Outlook 2011 for Mac is just too slow, the beach ball is always showing when I try to use Outlook. And I really prefer not to have to go back to Windows Outlook through Parallels. I can manage with Mail.app if I could resolve this Drafts issue. I save emails all day long so to double check each one to see if I actually sent it is too time consuming.
I'm running on a Macbook Pro, 2.2 Ghz Intel Core i7, 8 GB memory.
Thanks in advance.

I am too having the same issue. While working on Snow Leopard Mail app was working fine, bue te moment I upgraded to Lion OS, I began to see some mail laying around my draft folder. I thought they never left, but make a few call I found everyone was receiving my email, but for some strage reason, a copy stayed in drafts. I submitted this bug to Apple, and they actually told me they were aware of this issue and they were working on that. A year went by and we received Mountalion OS, and my iMac with Lion OS still has this issue. They never solved that. Now I am with this new iMac at home and and I am fighting myself not to use Mail app because, as far as I can see, the problme persist on Mountain Lion. So now, at this very moment I will give a try to PostBox (http://www.postbox-inc.com/)
My bussiness mail is mounted on Google apps, so I hope this works

Images in Yosemite mail app won't load?

I recently upgraded from mountain lion to Yosemite on my 2012 21.5 iMac, everything seems to work except the images in my emails won't load. I have checked of the settings within the mail app and nothing seems to fix the issue. Could this be a Java issue? Any help or suggestions would be greatly appreciated.

Back up all data, then disable, or preferably get rid of, your third-party "firewall" or "security" software as directed by the developer. If you don't know which such software is installed, ask for further instructions.

Snooze email messages in Mail.app

What I am missing is a Mail.app plugin that allows me to snooze messages (just like it is possible with the Mailbox app for iPhone).
Functionality:
- I would like to be able to define a snooze period for a message. There should be user-definable presets and the option to exactly specify date and time).
- Snoozed messages should be moved to a folder "Later".
- They should be moved back from the "Later" folder to the Inbox when they are due.
- The extension should work with all email accounts.

Thanks for the replies. But that link does not solve the problem: it just provides workarounds.
I would like to know if there is any way to edit a message that has been received in my mail.app program.
As for any legal issues, I find them to be not very compelling. Although it is true that courts now admit emails into evidence as if they were any other document, that does not suggest that they should not be modifiable. That courts admit such electronic documents into evidence certainly imposes no burden on me, the email receiver, to maintain the email's original format. Moreover, there is nothing improper about making programs or add-ons that facilitate the making of such changes in emails unless and until Congress decides to take up the issue and make it a crime to modify received emails.
Since that has not happened, and is unlikely to in the near future, I would still love it if someone could provide either instructions or some mail.app extension that allows one to edit received emails.
Thanks for any help! - M.

Edit Email Messages in Mail.app

Does anyone know a way to edit an email message already received in mail.app? I found this to be a useful feature of Eudora and even Outlook, but it doesn't seem to be in Mail.app.
Thanks for any help. - M.

Thanks for the replies. But that link does not solve the problem: it just provides workarounds.
I would like to know if there is any way to edit a message that has been received in my mail.app program.
As for any legal issues, I find them to be not very compelling. Although it is true that courts now admit emails into evidence as if they were any other document, that does not suggest that they should not be modifiable. That courts admit such electronic documents into evidence certainly imposes no burden on me, the email receiver, to maintain the email's original format. Moreover, there is nothing improper about making programs or add-ons that facilitate the making of such changes in emails unless and until Congress decides to take up the issue and make it a crime to modify received emails.
Since that has not happened, and is unlikely to in the near future, I would still love it if someone could provide either instructions or some mail.app extension that allows one to edit received emails.
Thanks for any help! - M.

Mail.app not restoring properly - keeps asking to import mailboxes, crashes

I noticed in the last few days that searching for email messages, either from within Mail.app or directly from spotlight, fails to find emails that I recently received and haven't deleted. (At the very least they should have shown up in the trash mailbox).
After trying to delete the Envelope* files and rebuilding the mailboxes, it started crashing completely.
I then restored both the entire ~/Library/Mail folder as well as the ~/Library/Preferences/com.apple.mail.plist file from my 1 day old Time Machine backup.
Launching Mail after this restore brings up the "Welcome to Mail" window, as if upgrading from Tiger and it then starts importing mailboxes.
After a few hundred (out of ~30,000) messages Mail.app just crashes, and trying to launch it again repeats the precise same thing again and again.
I've also tried launching it after having uninstalled all bundles by the way, and the crashes are pretty much the same.
I did note, however, that the Envelope files that are normally in the ~/Library/Mail folder, are non-existant in any of the Time Machine restore points - this seems like the reason Mail.app absolutely must start by importing the mailboxes, to create an Envelope Index etc.
Any advice for solutions/workarounds etc. would be most appreciated - I'm currently Mail-less!
Thanks!
Thanks.

I'm also having this exact problem. Mail tells me "Mail needs to import your messages. This might take a few minutes, and you won't be able to use Mail until the import is finished. Click continue to import your messages now, or click Cancel if you'd rather do it later."
Clicking continue starts the import process -- of my 170,000 -- emails. Mail reliably gets to 88868 messages, then the number stops counting upwards and the progress bar no longer progresses.
Watching Mail in Activity Monitor I can see that Mail starts rapidly consuming more and more memory until it fills the system memory entirely (on my MBP with 4GB RAM) and then crashes out.
Like the previous poster, I suspect there is a particular message causing Mail to crash or go into a memory leak loop, however, it's very difficult to identify because the crash report Mail generates (along with log info in Console) doesn't mention any specific messages it is importing.
It's clearly a memory leak problem of some sort because Mail consistently sits at 212.94 MB of active RAM usage while importing the mail up until the point it crashes, after which time it uses about 40MB a second until it fill system memory.
I tried using the LSOF command to monitor what files Mail was opening each second, however when it goes into its "rapid memory consumption about to crash" mode, I can see that it is continuing to open different mail messages, so it is not clear which one I'd have to delete to fix the problem.
So I am a bit stumped. I can work around the problem by hitting cancel when Mail says it needs to reimport the mail, but then I can only receive new mail, as none of my existing mail is listed in Mail. Very annoying.

Socks5 Proxy in Mail.app

So this is some background. I'm a Peace Corps volunteer living in Samoa. I have a powerbook, and my roommate just purchased a Macbook Pro --- a very nice machine. We work at the National University and get our internet access through a connection in American Samoa. Our university filters traffic as well as at least one person upstream of us.
When I got here, I realized that pop requests were being dropped. For me this wasn't a problem. I came from a unix world, and I'm still using fetchmail to get my email. I have shell accounts on several computers in the states, so I filter all my email fetchings through a socks 5 proxy. Now my roommate just got his computer, and he's coming from the other end of the computing world. He's used windows a bit, but doesnt know much about computers.
So he'd like to use the Mail.app to check his yahoo mail. The delima is that pop access is being blocked. So I thought, hey I can set up a socks 5 proxy and all I should have to do is make some changes in his network settings. I tried to test it out on my powerbook, but I'm having no luck. I can route safari traffic through the proxy just fine, but Mail.app doesn't seem to respect these settings. I've read on the internet that other people have had similar problems. So these are my questions: is there a way to get mail.app to use proxy settings of some sort? If not is there an alternative mail client someone can suggest which will respect these settings?
Powerbook Mac OS X (10.4.6) Mail.app 2.0.7 (746.2/749.3)

Mozilla Thunderbird will do what you ask.
However, I'd much rather use Apple Mail, so am anxious for any possible workarounds.

Configuring Proxy servers for Mail.app

Hello, and sorry if this question has been answered b4, but I couldn't find an answer... basically, I have to go thru proxy server at work to connect to the internet on my MBP, which I configured with Network Preferences (I enabled ftp, http, https, socks, and ITMS proxies.. Safari works fine, but can't get Mail to retrieve any mail from either of my mailboxes (.Mac and Gmail POP). the same prob. doesn't happen when i'm home trying to access my Mail from home (where i don't have to go thru proxy servers) using my macbook pro. the question is, how can i "tell" Mail that i'm using a proxy server?? thanks

No, actually i tried it first with socks proxy disabled, and then with it enabled, but nothing appears to be working.. it sounds a little strange to me that Mail.app doesn't contain specific settings that allow users behind company proxies to still access their mail servers, b/c for whatever reason Mail.app doesn't appear to be using the default system-wide proxy settings specfied in network preferences, which by the way Safari picked up right away and started using. well, any further help on this would be much appreciated, thanks .....

SOCKS + SSL = trouble (Safari crashes, Mail.app doesn't connect)

I use a SOCKS (v4) proxy over an SSH tunnel to connect to applications at work, as do many of my co-workers.
Safari will often (even usually) crash hard when using SOCKS if you try to connect to an SSL (i.e. https://) site.
We recently migrated to IMAP over SSL for Mail, and Mail.app cannot connect successfully to the IMAP server; it gets a generic "SSL error" (NOT a certificate error).
Both work fine over a plain SSH tunnel, and both work fine without SOCKS. Firefox and Thunderbird work fine over SOCKS for such sites (note that they don't use the system-wide settings/libraries). Other users at my workplace are seeing the same behaviour.
It seems to me that there might be a bug in the SOCKS implementation, or SSL libraries, or combination thereof, provided by OSX.
Can anyone else confirm this?
15" PowerBook G4 Mac OS X (10.4.8)

I know nothing about your problem, but wonder if this older article on 10.4.7 "fixing" the problem, mighn't give you a clue or two...
http://docs.info.apple.com/article.html?artnum=303771

Mail.app Proxy Issues

Hello Everybody,
I cannot get the Mail app to use the systemwide proxy settings for some strange reason. I am at college adn I need to use a proxy to access the internet. Now, this proxy works fine for every other program (As far as I know) except for Mail. I am trying to connect my Gmail account, and I just keep getting the response that Mail cannot establish a connection. The college uses an automatic pac file to configure the proxy, which I will add below. It doe snot seem to be using a SOCKS server, although I am not sure what that is, and that option is not checked. It does not make a difference if it is checked or not.
Thanks
Here's the text of the .pac file with some information starred out. (They probably don't want everybody to know their server settings)
function FindProxyForURL(url, host){
          pacver = "************";
// Convert the host expression to lower case and set host variable
          var lhost = host.toLowerCase();
          host = lhost;
// Set the default variables
          myip = myIpAddress();
          caproxy = "PROXY ";
          noproxy = "PROXY ";
// Localhost and loopback handling
          if ((host == "localhost") ||
          (host == "************") ||
          (shExpMatch(host, "localhost.*")))
          {return "DIRECT";}
// Exclude plain host names
          if (isPlainHostName(host))
          {return "DIRECT";}
// Exclude all FTP traffic
          if (url.substring(0, 4) == "ftp:")
          {return "DIRECT";}
// Exclusion of special domain host names
          if (dnsDomainIs(host, "************") &&
          !(host == "************") &&
          !(host == "************") &&
          !(host == "************"))
          {return "DIRECT"};
          if (dnsDomainIs(host, ".************") &&
          !(host == "************") &&
          !(host == "************"))
          {return "DIRECT"};
          if (dnsDomainIs(host, ".************") &&
          !(host == "************") &&
          !(host == "************") &&
          !(host == "************") &&
          !(host == "************") &&
          !(host == "************"))
          {return "DIRECT"};
// Exclude special non-domain host names
          if (host == "************")
          {return "DIRECT";}
// Resolve the host and set the host IP address variable
          var resolved_ip = dnsResolve(host);
          host = resolved_ip;
// Exclude IP Address of all hosts within the same subnet
          if (isInNet(host, "************"))
          {return "DIRECT";}
          if (isInNet(host, "************"))
          {return "DIRECT";}
// Exclude special IP addresses/clients:
          if ((host == "************") ||
          (host == "************") ||
          (host == "************") ||
          (host == "************") ||
          (host == "************") ||
          (host == "************") ||
          (host == "************") ||
          (host == "************"))
          {return "DIRECT";}
// Return the default action (direct to proxy server)
          return caproxy;}

You really should take your questions to the specific forum for your issue. In this case, it would be Mac OS X v10.7 Lion.
However, it is really easy to choose email send accounts on the Mail app. As you are aware, the email goes through your default account which you can choose that in Mail>Preferences>Compose. There should be a dropdown menu to choose which account you send from.
To override that whenever you want, when you create a new message (including replying or forwarding), right under the subject line is a drop-down menu to change the send account.
I wish that Mail could read my mind as to which one to use, but you have to remember to do that. I actually keep all of my business mail on a Outlook (since my business server uses Exchange, so it's easier to use) just to keep everything separate. I had a friend who didn't keep his accounts straight on Mail, and sent out a rather improper photo and joke through the corporate email rather than his personal one.

Mail.app 3.6 won't connect to my POP3 server over a proxy

I updated to 10.5.7 the other day, and now Mail.app will not connect to my POP3/SMTP server via my proxy. This is a big problem for me as I work remotely a lot.
My setup - I use Proxifier (www.proxifier.com) and an SSH proxy so I point my Mail.app at the 192.168.* local address of my POP3 server on my home network. Whether I'm physically on the 192.168.* network, or remote but running Proxifier, Mail.app 3.5/10.5.6 would work flawlessly, as would any other application that addressed my local network (e.g., RDC).
Since upgrading to Mail.app 3.6/10.5.7, however, Mail.app will not connect when I'm using the proxy, but works fine when I'm physically connected to that network; it thinks that the servers is offline (even when using the Connection Doctor). All other TCP/IP applications including RDC continue to work fine via proxy. In particular, I can still use "telnet 192.168.x.y 110" and connect correctly to my POP3 server (and interact with it using the POP3 command set), so the issue would appear to be in Mail.app rather than in the connection itselof.
Since Proxifier only proxifies TCP and not UDP connections, is it possible that Mail.app 3.6 now attempts a UDP connection to a mail server to check if it's alive before trying TCP? If that's the case, can it be disabled? I don't know of any requirement that POP3 servers must be able to respond to UDP. Or is there a way I can drop back to 3.5 which DID work?
Thanks. Jim.

OK, I understand this now (thanks to DHJ for help with experimentation).
1) Mail.app 3.6 appears to ignore /etc/hosts completely. Mail.app 3.5 honored definitions in /etc/hosts.
I tested this by putting the known IP address of pop.gmail.com into /etc/hosts and calling it foo - I could not receive mail by pointing Mail.app at the server foo.
If this is so, it needs to be documented. This is extremely unusual behavior for a network application. I can see why Apple may be trying to protect us from hosts-hijacking, but this non-standard behavior has eaten up a lot of our time trying to figure it out.
2) Mail.app 3.6 appears to use a system proxy if one is defined. Mail.app 3.5 did not.
I tested this by verifying that Mail.app 3.6 could receive my mail (modulo the problem in 1) above) when any system proxy was defined, regardless of whether Profixier was running.
Every other application I know that uses the system proxy gives you the option of doing this (e.g., Firefox, Adium, and so on). This is why my Proxifier application was seeing nothing - Mail.app was going right to the system proxy. (FYI, Proxifier is designed to support proxies for applications that have not already been written to support proxies explicitly.)
The combination of 1) and 2) presented as a totally wacky complex problem. Viewed separately they don't seem so difficult to diagnose. Either way, they are both surprising, unusual and, to my knowledge, undocumented.

Socks proxy not honoured in mail

While using a ssh tunnel with a setting (DynamicForward 1456)
Then in the system preferences i've set the socks proxy to localhost on port 1456
Mail doesn't seem to honor the system wide socks proxy while, Entourage works perfectly without missing a beat (Setup with the exact same account as Mail).
Has anyone had success with this everything else on the system goes through the local socks proxy (e.g. Safari , entourage)

Ok i've made a work around that will use local forwards instead of dynamic forwards and i've made an apple script that will switch all the settings for me.
set buttonTunnel to "Tunnel"
set buttonNormal to "Normal"
set result to display dialog "hey" buttons {buttonTunnel, buttonNormal}
set theButton to button returned of result
if theButton is equal to buttonTunnel then
tell application "Mail"
tell account "MainAccount"
set server name to "localhost"
set port to 1110
set uses ssl to false
end tell
set smtp server of account "MainAccount" to smtp server "localhost:UserNAME"
tell account "SecondAccount"
set port to 1111
set server name to "localhost"
end tell
set smtp server of account "SecondAccount" to smtp server "localhost:UserNAME"
end tell
else
tell application "Mail"
tell account "MainAccount"
set server name to "mail.MainAccount.com"
set port to 995
set uses ssl to true
end tell
set smtp server of account "MainAccount" to smtp server "mail.MainAccount.com.au:UserNAME"
tell account "SecondAccount"
set port to 110
set server name to "mail.SecondAccount.net"
end tell
set smtp server of account "SecondAccount" to smtp server "mail.MainAccount.com.au:UserNAME"
end tell
end if

Mail.app in 10.4.7: SOCKS proxy issues again...

Similar Messages

Maybe you are looking for