Mail app 4.5: bugs, ehancement reqs?

I'd like to submit an enhancement idea
Mail 4.5 (1084) on Leopard
when creating and sending new mail
the user may enter either an incorrect email address / badly formed email address in the to: field, including zero or more good email addresses
in this case, I end up doing support of "I can't send email. It's popping up this window about mail servers"
the app should collect the 'good' email addresses
then pop up a useful dialog that says "You have entered the following addresses that don't work because they are either badly formed, or unknown by the server"
[ list here ]
"Would you like to remove them and then re-send your message?" Y/N
if Y, do it.
if N, behave as usual.
Would vastly improve the user and support experience, is my bet.
hope someone can direct me how to get this to Apple development

Use "product feedback", here -
Apple - Feedback
I didn't see a separate link for Mail, so use the one for "Mac OS X".

Similar Messages

My Mail.app had a Bug

Hello Apple,
my Mail has an Bug. It works with one Exchange-Mailbox... but it dosn't work with more Exchange-Mailboxes... It does not synchronize the mailboxes...
I work with my Mac's and it really is very very annoying, this problem...
I'm really upset, especially with Lion everything worked.
My MacBook Pro runs with OS X 10.8.2 (12C60) with Mail 6.2 (1499)

Have you tried removing the email account from the app through settings? I would try removing it, rebooting, opening the email app to see if it still crashes, & then adding it back your email account.
If you're leary about causing more issues while you're not home, you could always try using a third party mail app (there are many), accessing your email through it...not a fix for your problem but a way to deal with the situation until you can get it worked out.
Resetting all settings on the iPad (not deleting content) is a good way to clear many errors as it can remove leftover cache files & files that have become corrupt.
Sorry I couldn't be of more help. Good luck & let us know if you get it working.

Mail.app "From:" default bug

When I want to compose an email, my email is address shown in the "From:" field. It is automatically filled in. I have a few email accounts and I can change it if I need to.
The email address I want to use as the default has been the one there most often in the past. However, from time to time in the past Mail.app has changed the default. I haven't noticed, of course, until many messages have been sent to people who don't recognise the sender. I haven't found a way to stop Mail.app doing this.
After system upgrades, the behaviour has gone into remittance. Today it has resurfaced and, despite relaunching the app and tweaking preferences, I can't get it to stop. I have to make sure I check the "From:" field every time I compose a message. It's rather frustrating.
Has anyone else had this problem? Is there a workaround?

Actually, this forum has just shown me other threads that answer my question. Thanks to varjak paw (https://discussions.apple.com/message/19054087#19054087).
I did try hard to search for this on the forum before posting, but the site would not allow me. Very strange behaviour.

Possible Bug in Mail.app

I am running a server and clients -- all at 10.4.4. The mail app on the clients Version 2.0.5 (746/746.2).
I have been tracking down errors in my imapd log file. The errors are:
Feb 5 00:18:05 EaseServer imap[23046]: IOERROR: reading message: unexpected end of file
You can find various people asking for help on this but no help. I believe I tracked this down. It is not an imapd problem but a Mail client problem.
When the client wants to add a file to an existing mail box on the server, it does an APPEND command. The "literal" at the end of the command can take on two forms: { number } or { number + }. The second is called the "non-sychronizing" form.
By default, this is supprted by imapd (and advertised) and used by the client. In this case, the client is suppose to not wait for the server to reply with the "go ahead" response but just blast the message across the wire. Well... it does not. Instead, you get a pregnant pause and eventually imapd times out and rejects the request. The client, eventually, may even crash from all this but, for sure, it will provide a very poor user experience.
The work around I did was to download CyrusIMAP from the OpenDarwin.org. In cyrus_imap/imap/version.h, the CAPABILITY_STRING advertises LITERAL+. If that is removed, then imapd does not claim to support it (even though the bug is in the client). This prompts the client not to use it. And things appear to work much better.
I know virtually zilch about IMAP protocol, cyrus, Mail.app, or imapd -- so, someone needs to verify all this.
The thing that is curious to me is why I hit the problem and others seem to be working fine. There are a few people that have noticed the problem but, they seem to be the exception and not the rule...

I have tracked down my problems to a call to sasl_decode in prot_fill (in imapd).
To recap: I am getting IOERROR: unexpected end of file in my imapd log file. The client interface is also slow and sometimes crashes.
It turns out that if the client has Kerberos GSSAI authentication and the client tries to do an "APPEND" command (which is what the imap protocol uses to add a message to an existing mailbox), the APPEND frequently fails (but not always). The rest of my Kerberos stuff appears to be fine.
The APPEND is sent across to the server. The client can be set up to do LITERAL+ or not. The client sends all of the message in either case. The server reads all of the packets. Usually the first packets go through the sasl_decode and result in valid text. But after the first block (4096) or so of data, the remaining data is lost and sasl_decode reports back that there is only two valid characters. No errors are reported back (that I am aware of).
I ended my quest at this point last night and I probably will not pick it up again. For now, I can work around the problem by switching to plain authentication and just set up a VPN before using mail.
I hope this helps whoever follows in my footsteps...
Perry

Font size bug in iOS 7.0.4 mail app?

Hi,
I experience a strange behaviour with iOS 7 mail app. When I try to read a plaintext mail with the iPhone in portrait orientation the font size is oddly big. I can "zoom" in with a two finger pinch but I cannot zoom out to decrease the font size.
Is this a bug, a setting I activated somewhere, a silly feature?
Thanks for advice,

Yes, the time and date is correct. It just started happening a few days ago and has bene like this since. I cant even open the mail, because theirs no content in them. Nor can i delete it.

Bug in decoding of From-addresses in Mail.app

Dear all,
since quite some time there is a bug in Mail.app, which leads to problems in replying to certain mails. The bug is similar (or the same) as in thunderbird 2 (see https://bugzilla.mozilla.org/show_bug.cgi?id=254519), which was fixed in Thunderbird 3.
If a "From:" line encoded with RFC 2047 contains characters which should, per RFC (2)822, be quoted (because it contains commas (",") or similar) Mail.app does not decode it properly but treats (in the case of a comma ",") this as two different addresses. A reply to such a message usually results in a bounce or error (since the first part is usually not a valid address).
An example for such a "From:" line is:
From: =?iso-8859-1?Q?M=FCller=2C_Henry?= <[email protected]>
This is correctly encoded and thunderbird 3 and (I hate to say this) outlook treats this correct.
Maybe someone from apple reads this and there is a chance to get this fixed soon, since it is rather annoying and causes a lot of user questions to our helpdesk. Or is there another easy fix (without changing the "From:" address.
Best regards,
Damian

Apple doesn't work here (except to moderate posts for terms of use). We're all just users like you.
If you want to file a bug report, sign up for a free Developer account and file one here: http://developer.apple.com/bugreporter/
Or, use the Provide Mail Feedback menu item in the Mail menu.

Bug in Mail App in LION

Just the other day, my hard drive depleted to the point of 54MB and I got a warning that my start up disk is full and I need to delete files. I found that strange since I have about 200+Gig available, the last I checked and did not do any new downloads. But I deleted a bunch of stuff anyway, and restored my size to 9 Gig.
Next day, same message. I knew something is wrong, called Apple and discovered that there is a bug in the Mail app. For some reason it created a Recovered folder in the Mail folder that just kept copying over and over again. The tech told me it's a bug but no clear direction on how to solve it and/or when. The only thing we did was delete that file and my space was restored. I was told that is all I would need to do for now and I should be fine. Well, today, again my HD is depleting and sure enough, there is that recovered folder again.
Anyone else with this problem? Specifically, it appears to be doing it with my Yahoo mail. I'm thinking I should delete the account, start over. If anyone has other ideas or if it's a settings thing in Mail or Yahoo pop settings, please let me know.
Thanks

It's not related to a third party app. I don't have any. The tech was able to pinpoint the folder in the Library/Mail/V2/Mailboxes
He said they have had reports of this bug and he went directly there. So they must be aware of it.

Is anyone experiencing a bug in mail app in iOS 7 ?

I'm experiencing a bug in mail app in iPhone as well as in my iPad... This bug makes all my mails unread whenever I refresh for mails and whenever I read a new mail it stays unread even if a close the app. Please help me if possible...

I've not heard of or experience any such issue.
Have you tried removing and readding the accounts in question?

OSX Lion Mail.app bug in signatures containing a URL

This is highly reproducable: try adding an image followed by text in a signature in Mail.app. Now select the image and add a url (CMD+K) e.g. to your company website. So far this should look the way you expect. Now click on some other preference, so Mail saves the signature. I have multiple signatures, so I just click any other signature. Click back on the signature you have just created, and notice how all text that came after the image now is underlined.
Why?
There's a bug in the way Mail saves the webarchive file for the signature (~/Library/Mail/V2/MailData/Signatures/<blabla>.webarchive. When you open this file, you will find a bunch of binary bla, followed by invalid (see missing quotes in attributes below) HTML, that will contain your image similar to this:
<a href="http://www.mywebsite.com/">
<SPAN class="Apple-string-attachment"><OBJECT height=53 width=157 type=application/x-apple-msg-attachment data="cid:[email protected]"></OBJECT></SPAN>
Don't ask me why Mail capitalizes just these tags and not any other tags, but the most important bit is that Mail forgets to add the closing tag </a>, so now everything trailing the image is linked too.
I cannot reproduce this in Safari, so apparently Mail and Safari do not share code here. I have tried what happens when copy/paste a valid rendered HTML file with the appropriate signature text from Safari into Mail, but the result is the same.

also via applescript same beahviour, composing a message and including an attachment after setting the signature make underlined all the text after the first email adress inside the signature.

Bug in Mail.app preventing from retrieving mail

Found a bug today when using Mail.app:
What happened:
- I setup my IMAP account onto Mail
- Synchronized Mail with my IMAP account by clicking 'Get Mail'
-> I could get all my mails, but any other click on 'Get Mail' ended up with doing nothing. Even the 'Check for new mail every x minute' checked, I was never getting new mails. The only way to retrieve my mails was to quit Mail.app and run it again or Go offline in the App and then click 'Get Mail'
Did some investigations and here's what I found:
- Displayed the Activity Viewer at startup
- I saw that the app was connecting to the server, then getting mail, then doing some caching over my attachments in existing mails. While the task running on attachment was not finished I was able to click 'Get Mail' and see a task for it.
- Once the task for attachment was finished, 'Get Mail' stopped working and no new task appeared in the activity viewer each time I clicked the button
- Quit Mail.app and ran it through terminal.
- When caching the attachments, I saw an exception about an absurd size in one of the attachments and some lock issues (sorry didn't copy the exception at that time)
- Sorted my mail by attachment and looked for a mail for an attachment with a strange size.
- While I did not saw anything weird in the sizes, when I went over one of the mails, got again the exception in the terminal.
- Deleted the mail, restarted Mail.app
-> And everything started working fine
Conclusion:
- Either a bug in the Mail.app code or a faulty attachment can create a lock between threads, preventing then a normal functioning of the application... (sorry I did not kept the attachment)

It's not related to a third party app. I don't have any. The tech was able to pinpoint the folder in the Library/Mail/V2/Mailboxes
He said they have had reports of this bug and he went directly there. So they must be aware of it.

Mail attachment assertion failure Yosemite - Mail app bug

Hi,
I am facing a very annoying issue with Mail app. Since the upgrade to Yosemite, I am unable to save attachments with the "save all" button and the drag and drop is not working properly (sometime freezing the mail app for a minute). I am using Yosemite 10.10.2
I tried every fix I have read online, such as :
- rebuild mailboxes
- repair permissions
- remove 3 enveloppe index files in .../V2/MailData
- reindex spotlight
- run the command to repair permissions & reset home directory permissions and ACL (from this post : Mavericks Mail "Save Attachement..." doesn't work)
- onyx automations...
Nothing presented above fixed the problem.
Here are the console logs related to the issue :
20/02/2015 03:38:49,690 mdwrite[4655]: -[MDKeyRing initWithService:label:comment:] (/SourceCache/Spotlight/Spotlight-917.1/xpc-services/mdwrite/MDKeyRing.m:294) failed assertion -- Couldn't add Spotlight Metadata Privacy password to keychain! [osErr:-25295]
20/02/2015 03:38:49,973 Mail[4088]: Metadata.framework [Error]: error Connection interrupted
20/02/2015 03:38:49,973 Mail[4088]: *** Assertion failure in -[MailWebAttachment _addPrivateAttributes:], /SourceCache/Mail/Mail-2070.6/Mail/MessageDisplay/MessageView/DocumentModel/Mai lWebAttachment.m:331
20/02/2015 03:38:49,973 Mail[4088]: [QL] Exception raised while try to get launch url for preview item: Failure in _MDItemSetPrivateAttributes: 3
There is apparently a problem with the privacy attributes. Any idea of how to solve it?
Thanks for your help,
Best,
Laurent

Hi,
I am facing a very annoying issue with Mail app. Since the upgrade to Yosemite, I am unable to save attachments with the "save all" button and the drag and drop is not working properly (sometime freezing the mail app for a minute). I am using Yosemite 10.10.2
I tried every fix I have read online, such as :
- rebuild mailboxes
- repair permissions
- remove 3 enveloppe index files in .../V2/MailData
- reindex spotlight
- run the command to repair permissions & reset home directory permissions and ACL (from this post : Mavericks Mail "Save Attachement..." doesn't work)
- onyx automations...
Nothing presented above fixed the problem.
Here are the console logs related to the issue :
20/02/2015 03:38:49,690 mdwrite[4655]: -[MDKeyRing initWithService:label:comment:] (/SourceCache/Spotlight/Spotlight-917.1/xpc-services/mdwrite/MDKeyRing.m:294) failed assertion -- Couldn't add Spotlight Metadata Privacy password to keychain! [osErr:-25295]
20/02/2015 03:38:49,973 Mail[4088]: Metadata.framework [Error]: error Connection interrupted
20/02/2015 03:38:49,973 Mail[4088]: *** Assertion failure in -[MailWebAttachment _addPrivateAttributes:], /SourceCache/Mail/Mail-2070.6/Mail/MessageDisplay/MessageView/DocumentModel/Mai lWebAttachment.m:331
20/02/2015 03:38:49,973 Mail[4088]: [QL] Exception raised while try to get launch url for preview item: Failure in _MDItemSetPrivateAttributes: 3
There is apparently a problem with the privacy attributes. Any idea of how to solve it?
Thanks for your help,
Best,
Laurent

Possible bug with HTML emails and attachments from Mail.app

I'm trying to send an attachment with an HTML email from Mail.app and getting unexpected results. I've been messing around with the order that things get added to the new e-mail and it seems that I can have either an attachment or I can have HTML email, not both.
The code... (of course simplified)
tell application "Mail"
set new_message to make new outgoing message with properties {subject:"A subject", sender:"[email protected]"}
tell new_message
set visible to true
make new to recipient at end of to recipients with properties {address:"[email protected]"}
tell content to make new attachment with properties {file name:alias "Path to your file as string"} at after the last paragraph
set html content to "<head><body>Some HTML here...</body></head>"
end tell
send new_message
end tell

etresoft wrote:
The problem is that there is no such thing as HTML email.
Well, I wonder what I have been generating for over three years now. RTF ? Because it sure looks like HTML. I must agree that HTML is not documented or even mentionned in the Mail AS dictionnary, but it does work, though you must specify visible to false so that it does. Here's my sub:
tell application "Mail"
set DMF to default message format
set default message format to plain text
set newMessage to make new outgoing message with properties {subject:theSubject}
tell newMessage
set visible to false
set sender to theSender
make new to recipient at end of to recipients with properties {name:Photographer, address:theAddress}
set html content to "<html><head><title>" & theSubject & "</title></head><body>" & "This is an automated response." & theSource & "Find your personnal planning on the web: " & thelink & "
</body></html>"
end tell
send newMessage
set default message format to DMF
end tell

Mail.app Subject: context menu on highlight word bug

Hello
I have problem on Mail.app Version 5.0 (1244.2/1244.3)
The shortcut menu on the selected word in Subject letters does not work
Expected:
Current:
Please confirm.

Aha! after entering this post a link to this :
http://forums.adobe.com/message/3663140#3663140
appeared. It seems you have to create a custom skin for the Panel with mouseEnabled=true. Yuck.

Mail.app bug?

Hi there,
Im using mail.app to a IMAP server (not dotmac).
I just noticed a wird number at the top of the mail.app window. I guess there is supposed to be the number of mail in my inbox, but there has never been that many messages in there. Not even close even if you cumulate
Look here:
http://usenet.ducktrucks.dk/mailappbug.jpg
(Just above the "Reply all" button".)
Can I fix it?

Hmm.... I found a way to remove the problem.
Standing on the inbox. Ctrl + click and "Erase deleted messages".
Then this crazy number dissappeared. I have no idea why because this number where infinitly high...

What is the best mail app for MacBook Pro that is not the req mail app

i am having nothing but issues with the mail app. i use office 365 but cannot sync my contacts to it. so what is a better app to replace it

Go to OWC and purchase a drive and an enclosure. Put it together yourself. Takes about five minutes and a screwdriver. Or you can purchase one already complete from them if you prefer.

Mail app 4.5: bugs, ehancement reqs?

Similar Messages

Maybe you are looking for