Found a bug in Mail 4.4

I was checking the options at the bottom right of the screen and then a prompt to enter my account password popped up. I could only select "ok" to the prompt and could not type anything into the password query. I had to select "ok" without a password and quickly select something on the menu to relieve the ability to type in a password when it popped back up. For better illustration of this issue, please see the screen shot I made of Mail.app when this problem occurred.
[http://img508.imageshack.us/img508/7/screenshotvod.jpg]

If you want to report this issue to Apple's engineering, send a bug report or an enhancement request via its Bug Reporter system. To do this, join the Mac Developer Program—it's free and available for all Mac users and gets you a look at some development software. Since you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report or enhancement request. The nice thing with this procedure is that you get a response and a follow-up number; thus, starting a dialog with engineering.

Similar Messages

Found a bug in mail

Since updating to Mavericks, mail.app has a rather annoying bug.
If you have your email setup to check spelling on sending, when the spelling dialogue box opens up, and editing of the origional email will automatically send the message as soon as you hit the space bar.

Go to Apple BugReporter and file your bug report. You get a response and a follow-up number thus starting a dialog with engineering.

Bug in Mail: Plain-Text | Rich-Text-Mails

Hi,
just found a bug in Mail (Mac OS X 10.6.2):
I am using a faxservice-provider, which sends my PDF-files to the transmitted fax-number.
This stopped working a few weeks ago, the recipients of my faxe just get blank pages.
I talked to the provider and they told me, that I was sending "Multi-Part-HTML"-mails, so their fax-software just sends the first part of the mail (some blank lines) and not the attached PDF-file.
So I checked a few thing and found the following bug:
Mail is set up to send mails only as "plain-text"-mails.
But if i send an email via the print-dialog ("send PDF per Mail") Mail creates a Rich-Text-mail. This also happens when using the "send PDF via Mail button" in Adobe Reader.
The created Mail is NOT a plain-text-mail!
Saving a PDF-file to the desktop and dragging the file to the Mail-Icon in the dock creates a "Plain-Text-File".
So you need to check the format of the Mail in the "Format-Menu". If you change the format at this place to "Plain-Text" everything is working fine.
Something in this Automator-workflow-script is working wrong. This workflow just has the order to create a new Mail with the PDF as attachment, so I can't change anything their. But the error must be founded in this script/workflow.
Sven

And it's only a Gmail issue, not in, for example, Google Docs.

Bug in Mail when using Google Apps Gmail and sync

I found a bug in the sync process between the Mac and the phone. If you have Mail (on the computer) set to use Google Apps for Your Domain, the sync on the phone changes the user for the mail account. I assume this is because it sees "smtp.gmail.com" or something and decides to "protect" you from having an incorrect user account.
So for example, if you're using Google Apps and your e-mail is [email protected], Mail (on the computer) will also have smtp.gmail.com and pop.gmail.com as the servers. When sync'd to the phone, iTunes or the phone decide to change the user account for both servers to [email protected]@gmail.com, which is of course not what we want.
I'm kind of annoyed that they're trying to protect us like this.

Yeah unfortunately if you tried to send an e-mail
before discovering that bug, you will have an error
message show every time you access Mail saying "the
sender address [email protected]@gmail.com was
rejected by the server."
I can't get it to go away even by deleting the
account on iPhone and not setting it to sync.
Anybody know of a fix?
-AJT
Yes. Create the GMail account on your iPhone using the Other shortcut instead of the GMail shortcut. That will let you specify whatever address you want.

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.

I found a bug in iOS 4.3.3 - Long voice memos

Hello,
i found a bug in iOS 4.3.3 for my iPhone 3GS
Long voice memos can not be played
In these cases, the iPhone saves the file not in the format M4A or can not open this file.
This file is stored in the folder /var/mobile/Media/Recordings
In This cases there can be find a file in the format MOV.
During recording, the voice memo has the format MOV.
When the voice memo stopped the file must be stored in the format M4A.
For large files, there are currently problems.
I use the program iPhone Explorer and save the MOV-file on my computer.
Now i can open it with QuickTime.
Best regards from Germany!
Ruediger

Apple Feedback

I think I've found a bug... (CS 4 6.0.4, export to EPUB, w/ test case)

Hi everyone,
I think I've found a bug. I suppose I would like to see if others can reproduce it - I've managed to on 2 work machines, but the more the merrier. I suppose I'm also hoping that giving this bug more exposure will increase the likelihood of it getting resolved. I can dream
The bug shows itself when exporting an InDesign document (or book) to "Digital Editions", or as an EPUB file. The InDesign source needs to have a Table of Contents, and this TOC has to be used by the EPUB to create TOC entries (see the "contents" tab of the export window). In certain cases, using the InDesign TOC causes the EPUB export to garble certain characters; unicode-specific characters, in my experience.
Steps to reproduce:
Create a new document, add a blank text frame and fill it with placeholder text. add a heading to this text frame, styled appropriately.
Create a table of contents, using the heading style you defined and used previously.
Add some unicode characters to the end of your text frame. I've been using "bêche-de-mer — a genus", which has 2 unicode characters. My tests have shown about 1715 characters in the text frame is enough to trigger this bug.
Save the document and export to digital editions. under the "contents" tab, check the "include indesign TOC entries" option.
Open the EPUB (or unzip it and view the xhtml content). I would expect to see "bêche-de-mer — a genus" at the end. However, I see something more like "b√™che-de-mer ‚Äî a genus" instead. I do see the correct output if I don't check the "include indesign TOC entries" option when exporting to EPUB.
I've confirmed the fonts I've tried are unicode-compliant and have the relevant character codes. I'm running the latest update to InDesign CS4 (6.0.4) on OSX 10.4.11. This character encoding problem doesn't manifest itself in the PDF or IDML export, only the EPUB export. Choosing whether or not to include embedded fonts in the EPUB doesn't make a difference to the outcome. I have run this test on my machine and a workmates, which is OSX 10.5.[something]
I'll attach a test document to see if others can reproduce this bug. I'd be interested to hear if others can, or cannot reproduce it. I have submitted a bug report at https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform, but that doesn't exactly imbue me with confidence that anything will get done in a hurry...
This problem is pretty annoying; I can either have EPUB navigation, or uncorrupt text. My current (proposed) workaround is for the operator to create 2 EPUBs, one with a TOC and one without, and merge the two together... EPUB transplant if you will. A bit ugly....
thanks for listening!

Hiya Joe (and Archie)
It is indeed an annoying bug - I spent a few days looking around it before posting (wow, it must be nearly a year ago now).
Fortunately, it really is straightforward (if a bit of a hassle) to workaround:
- make 2 EPUBs, identical except one will have a TOC generated (epub-a), the other will not (epub-b)
- extract the TOC file from epub-a and insert it into epub-b
remembering that EPUB is a zip package, this is very easy indeed. On OSX you have /usr/bin/zip and /usr/bin/unzip to assist with extraction / insertion in a script (bash, applescript, etc). I don't think Windows comes with command-line zip programs, so you'd need to hunt around a bit.
Good luck. I don't know if this is resolved in the latest 6.0.5 patch - if you haven't updated to that, it might be worth a shot. And if you have and it's still a problem, please respond to this message just so there's a log stating as much.
Steve

FAQ: I found a bug. How do I write a useful bug report? Or send bug files to Adobe?

If you think you've found a bug in Photoshop CS6, please post your findings here on the forums.
Here is a list of the information we'll want for you to gather at a minimum:
Clear and concise steps so that someone who isn't in front of your comptuer can reproduce the issue you are seeing
Include information on the operating system/version you are running. (e.g. "Mac OS 10.7.3" or "Win XP Service Pack 3")
Here are some more detailed instructions for writing a useful, complete bug report for us on the forums:
Provide a descriptive title that includes your OS information:Example: "Photoshop crashes when I save a JPEG file using the File>Save For Web & Devices... command (Mac OS 10.7.3)"
Provide concise, step-by-step details on how to reproduce the issue you are seeing.
Example:
Open an 8-bit, RGB image by selecting File>Open...
Create a new layer by clicking the "Create New Layer" button on the bottom of the Layers panel
Paint on the layer created in Step #2 using the default Brush tool
Choose File>Save For Web & Devices...
Make sure the optimized format is set to "JPEG" and set the Quality setting to "80"
Click the Save button at the bottom of the Save For Web & Devices dialog, choose the desktop as the location for saving the file
Provide a description of the "Result" you are observing:
Example: "Result: Photoshop crashes"
If there is an error dialog, please include the exact wording displayed in the dialog or provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
If the error is a visual defect, either in the user interface or the image itself, provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
Provide a description of the "Expected Result":
Example: "Expected Result: Photoshop to save JPEG file to the desktop, no crash"
In some cases this may be obvious (such as in the case of a crash) but in others, what you expect to happen may be different than what the application was designed to do. Please be as specific as possible.
Provide the crash log by submitting all crash reports, including your email address, for every single crash your encounter:
You may also include the contents of your crash log in your forum posts as well, but always submit them using the above instructions as well.
Crash logs are located on Macintosh here: Users/<your user name>/Library/Logs/CrashReporter
Provide your System Info from Photoshop: What's even more useful is if you can share your System Info from Photoshop as it contains all kinds of useful information (OS/version, graphics card, driver version, 3rd party plug-ins used, etc) that will help the team track down your issue.
On occasion, the Photoshop engineers may request that you provide problematic files in order to reproduce and debug your issue.
In these cases, please post the file somewhere using your own servers or one your favorite online document/distribution services and provide a URL/instructions to download the file:
Dropbox
Adobe SendNow
YouSendIt
If the file isn't something you can post publically, you can request that someone from the engineering team contact you to figure out a secure way to get the affected files.
Thanks,
The Photoshop Development Team

First thing would be to realise the exact error. Second would be to check your logs to see what you have installed/upgraded which might be causing this error. Third, google your error and see if matches turn up. Fourth, search in Arch bugtracker to see if a match exist. Else file a report.

I've found two bugs in iOS 7. 1) declined calls does not appear as missed calls on the lock screen/notification centre. 2) when bluetooth is enabled from control center, it does not connect to an already paired bluetooth device

I've found two bugs in iOS 7:
1) declined calls does not appear as missed calls on the lock screen/notification centre - iOS 7.0.2.
2) when bluetooth is enabled from control center, it does not connect to an already paired bluetooth device automatically - iOS 7.0.

We are all users here, just like you, but you can tell Apple about it by using this link:
Apple - iPhone - Feedback

Dear Apple, unfortunately, I think I have found a bug in ios 7. During an incoming call is no call rejection or selection of the ability to send a text message. I hope it is a bug and there is a solution. Thank you very much.

Dear Apple, unfortunately, I think I have found a bug in ios 7. During an incoming call is no call rejection or selection of the ability to send a text message. I hope it is a bug and there is a solution. Thank you very much.

Please report via Apple Feedback. These are user forums. You aren't speaking to Apple here.

I Have found a bug in iOS 7.1 on iPhone 4S ? What should i do ?(i'm french)

I Have found a bug in iOS 7.1 on iPhone 4S, what shoud I Do ? (i'm french)

Use the contact us link at the bottom of the page and tell Apple.

Bug in Mail 2.1.1

there is a bug in mail, watched the screenshot:
http://img217.imageshack.us/my.php?image=screenshot159hu0.jpg

Do you have a .Mac account? Do you have .Mac synchronization of Mail data enabled either in Mail > Preferences > General or in System Preferences > .Mac? That would interfere with any attempt to get rid of potentially corrupt *.plist files...
BTW, you can make your life easier in these forums by going to System Preferences > International and moving English to the top of the list. The next time you launch Mail, it'll be all in English. You can then go back to the preferences panel and move your preferred language to the top again so that everything else is in that language.

A small but very irritating bug in Mail: after pressing the spacebar after typing an apostrophe in a word such as "we're", the cursor moves to the left i.e. backwards, and not to the right, effectively deleting a space and not creating one.

When composing an email in Mac Mail I've noticed a small but very irritating bug: pressing the spacebar after typing an apostrophe in a word, e.g. "we're", the cursor moves to the left i.e. backwards, and not to the right, effectively deleting a space and not creating one.
Any ideas?

I just recreated this problem on my iMac (wired KB, no wireless KB) by changing Mail > Preferences > Composing > Spellcheck from "as I type" to "never". Then type a contraction ending in 're and the space bar causes the cursor to jump back as others have stated, to the spot 'r|e
Next, I went into System Preferences > Keyboard > Text, and turned off "use smart quotes" and the problem went away again.
From this point (smart quotes off, spell checking never), if I turn Smart Quotes ON, the problem returns.
The problem is dependent on the state of both settings.
The spacebar in Mail "works" if I have either of the following setting combinations:
Keyboard: smart quotes OFF, Mail: check spelling ANY SETTING
Keyboard: smart quotes ON, Mail: check spelling AS I TYPE
Other combinations FAIL
Keyboard: smart quotes ON, Mail: Check spelling NEVER
Keyboard: smart quotes ON, Mail: Check Spelling WHEN I CLICK SEND
Looks to me like there's a bug in Mail > Preferences > Check spelling > NEVER and WHEN I CLICK SEND that interacts badly with Keyboard > Smart quotes ON.
Thanks.
Todd Smithgall

Bug report: Mail sends messages with empty bodies

Over the last year, I have experienced a particularly irritating bug in Mail.app at least a dozen times. I finally have a good idea as to what causes it.
The problem involves long email messages (often with attachments) that end up being sent with blank bodies (and no attachments). Even the copy in the "Sent" folder ends up blank, and several minutes or hours of work vanishes into thin air, not to be seen ever again.
I finally realized that this bug only occurs when sending mail through our work SMTP server while outside the work firewall, and only as a result of a certain sequence of events. Here is what happens:
When we connect to our work SMTP server from outside the local network and without going through the VPN, the SMTP server requires password authentication. If the current SMTP selection in Mail.app is the one that does not require authentication, the SMTP server rejects the message. At that point, Mail.app opens the email I am trying to send and brings up a modal dialog that says "Cannot send message using the server xxx.xxx -- The server response was: xxx@xxx relaying prohibited. You should authenticate first." The dialog also presents a drop-down list of SMTP server choices. I choose the password-authenticated version of the server and then click on "Use Selected Server" to send the message.
This works almost all the time, but on occasion it ends up sending a blank message! If I have a long email, particularly with attachments such as PDFs that are rendered in the body of the message, it takes a few seconds for the mail message to be rendered underneath the modal dialog box. Since I am used to this STMP rejection behavior, sometimes I am too fast to choose another STMP server from the list and click on "Use Selected Server" before the mail message is rendered on screen! The result, invariably, is a blank email message that gets sent.
I guess what is happening is that when the STMP server rejects the message and hands it back to Mail.app, the message gets copied into a buffer in order to be displayed on screen. Selecting another server and resending it immediately (before the message is copied into the buffer completely) causes the message body to get trashed.
I hope that this description is adequate for Apple QA folks to replicate and isolate the problem (and hopefully fix it). One solution (although not the most elegant one) would be to disable the "Use Selected Server" action until the message is copied into the buffer and rendered on screen.

This could be related to another bug reported here recently:
E-mail looses all images if mail server doesn't accept outgoing email...
You cannot count on Apple looking into this or even noticing it if you report it here, so I suggest you the same I suggested in the other thread, i.e. report it in one of the following places:
http://www.apple.com/macosx/feedback/
http://developer.apple.com/bugreporter/

I accidentally hit the REMOVE FROM LINE button on my Premium Voice Mail. How can I get it back? The only options I found was visual voice mails.

I accidentally hit the REMOVE FROM LINE button on my Premium Voice Mail. How can I get it back? The only options I found was visual voice mails.

TheAshburns,
No worries, we can get you back on the road with the correct voicemail service. Just to be clear, did you want to readd Premium Visual Voicemail? If so, click the link and select question #7 for steps http://www.verizonwireless.com/support/visual-voice-mail-faqs/?lid=sayt&sayt=visual%20voic*
SandyS_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

Found a bug in Mail 4.4

Similar Messages

Maybe you are looking for