Mail App For Mac That Filter Utf Encoding Subject Rating: 4,7/5 2455 reviews

Utf 8 charset doesn't work with javax mail. Ask Question. SetText(message, 'UTF'), so both for subject and content the encoding must be set. – Joop Eggen Feb 23 '13 at 18:36. This filter sets the encoding to be UTF-8 and force the encoding to all requests comming at the url ' /. '. Download ZIP. Python script to export Apples Mail.app rules into gmail filters. Load in apple mail rules file. Rulesfile = '/Library/Mail/V2/MailData/SyncedRules.plist'. Newcriteria = newcriteria + negation + 'subject:' + exp.


Force Mail.app to always send UTF-8 messages 20 comments Create New Account
Click here to return to the 'Force Mail.app to always send UTF-8 messages' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
This does work, it's just not obvious, as the change affects what 'Automatic' is defined to be. After running the defaults command, I see Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed in the message headers, whereas before I had Content-Type: text/plain; charset=ISO-8859-1; format=flowed.

I should also mention that I didn't do this as root, just as my regular user. I don't see why you would need to do it as root unless perhaps you wanted to make the change for all users on your system.

Why should one have to log in as root? I think, that defaults works on the current logged in user, so when you switch to root in the Terminal, you set the behavior for you root user, which you hopefully not use as your daily user ;) /SebastianMail app for mac that filter utf encoding subject 2

---
/Sebastian

I tried it too, not as root, but as my normal user, and it did not work, not even after quitting Mail before making the change.

Can you send yourself an email and then check the message header to see what encoding is set? As I said in my comment above, I have had success with this, but it only is clear that you were successful if you look at the message headers, not what the encoding submenu shows.

Yes, I sent myself an email to check the message encoding, and it did not work. Also, since I normally have mail default to RTF format, I switched the format to plain text and sent another test email. It still did not work. I have not tried changing the setting as root, but I don't see why that would affect the settings in a single user's account above and beyond changing the setting within the account itself.

I just did it as myself, and it did work on both my MacBook Pro and my old G5 tower.
Is everyone on 10.4.10?

I have several encoding problems with Mail.app.
For Brazil, the best option is ISO 8859-1 as UTF-8 is not properly understood by yahoo webmail.
Here is how it works, if you use the 'defaults write' hack you will send in your chosen format despite the fact that 'automatic' is still selected ( you can check you mail headers as noted before). However, if you send your message in rich text format, Mail will encode the plain text part in your chosen format and the html part in ISO 8859-1, which will choke outlook.
I had a tread open discussing about this very issue, but that didn't seem to grab much attention
http://forums.macosxhints.com/showthread.php?t=76364

So let me see if I'm correct in my understanding of this so far..
If I have Mail.app set to send in Plain Text, but run the defaults write command above, the messages will be sent encoded as UTF-8. But, as soon as I switch to Rich Text, it will send a two-part message, with each part encoded differently??? That seems just plain weird! Can anyone confirm that? What would the possible point of that be??
I send 99% of my messages as Plain Text, so am I right that it would make sense for me to run the command above anyway, just to be sure my messages appear 'clean' for most Windows users?
This is one of those 'hints' that almost needs its own background article to be understandable by all types of users..

I was kind of simplistic in my post. If you set UTF-8 default, it will always send in UTF-8, but that doesn't work for me because of yahoo webmail.
So if you set it to ISO 8859-1 it will work for both plain and html only if you don't add an attachment. If you do, you'll get plain text in UTF-8 and HTML in ISO 8859-1. This is a bug in my opinion, cause it doesn't make any sense. But it is, however, triggered by a non GUI option (meaning a hack, a hack suggested by Apple itself, but hack nevertheless).
http://docs.info.apple.com/article.html?artnum=301986

Actually, you're quite wrong about it being a 'hack.' First, it is a developer-provided option, so its not a hack. Second, it is a developer-supported option, as you yourself showed by linking to the kbase article.
Its just a way of changing what 'automatic' means.
JP
---
Pell

Off topic but can't resist: as Outlook is the biggest bug farm in the history of the universe I somehow think your choking it is not such a bad thing? Seriously: I don't get why M$ are still peddling that thing, why people are still using it, and why we should have to adjust to them and not to us. Sorry but it does irk me and others. UTF-8 (and not UTF-16) is a good general idea for mail but we'd all have to use it. But I think that will become a standard. Yes Yahoo mail is really bad at that but they're bad at a lot of things. Give them another ten years and they'll catch up. No place for a rant but if you ever have a bad day computing then count your blessings for Apple Mail and mail standards are a giant leap ahead of what everyone else suffers through every day.

I hate Outlook with all my strengths, but Mail.app is one buggy awkward beast.
Just have a quick search for Mail.app in this site and you'll see.
It is amazing how such an old simple thing, such as sending an email, can still be a problem in 2007.
I share your feelings about UTF-8. Why can't we all use it for everything that involves text and be through with it. Standards have a reason to be.
Email needs a reformulation. Let's decide about plain vs html vs text/enriched, and what char encoding to use. And while we are at it, we could have a look at this tiny thing called spam. Web 2.0 .. Email 2.0.

This was all worked out long ago when Tiger was first released. Here is the reference note used extensively in the Apple forums since then:
http://homepage.mac.com/thgewecke/woutlook.html

No it was not. See my post above

Pedro -- Sorry, I don't understand what you mean. What exactly in the woutlook.html note do you not find correct? I of course want to make it as correct as possible regarding the Outlook issue. Send me email if you like (tom at bluesky dot org).

Well, it works for me only if I include foreign characters in my email (like ישח). Then mail uses UTF-8. Otherwise it uses USASCII. Krs khs software for mac.

Yes, in certain circumstances, like when your text only has ascii in it, you need to use Fix C in the note http://homepage.mac.com/thgewecke/woutlook.html, namely put a dingbat or some other character in your text which will force UTF-8.

Well, of course if it's ASCII only there's no point in forcing UTF-8, as ASCII and UTF-8 are identical (where they overlap). That was one of the rationales behind the design of UTF-8. UTF-8's first 128 characters have the same binary as ASCII and so even if your computer doesn't understand UTF-8 it'll still understand the most common letters (in English at least).

I think that a text which the composer considers to be ascii (e.g. no accented chars or smart punctuation) may contain non-ascii nbsp's if in Rich Text (=html) in Mail, and these can get misread by Outlook as non-characters, displaying as question marks. In this situation it is desirable to force the message into uniform UTF-8 so as to get the nbsp's read as spaces. I don't think the terminal command will do this, but adding a Unicode dingbat will.

This page contain various suggestions to help you make the most of Apple Mail, the default email program on Macintosh computers.

  • 1Receiving messages
  • 2Sending messages
    • 2.5Sending HTML emails

Using folders

By default, messages arrive in your Inbox. Keeping them there leaves them somewhat vulnerable, because if you were to delete an account in Apple Mail, or even change certain settings such as the server name, you'd lose all the messages for that account that were still in the Inbox. It is therefore highly recommended to create folders in the section of mail called ON MY MAC, and move messages there. Especially, move messages from your inbox into such folders before changing/deleting account settings.

Filtering your emails

It is useful to set up filters for incoming emails from busy mailing lists such as Mac-Min so that they will automatically go into their own separate folders. This means that your inbox will only contain personal and sundry messages, and that you can catch up on your mailing lists when you have time.

To set up a rule, choose the menu command Mail > Preferences, then click on the Rules icon.

A simple rule for subject lines containing [Mac-Min] works for this list. However, this would mix off-list replies sent to you into the list traffic.

A more specific way to filter Mac-Min messages is to filter by Mailman's list-id header. All messages sent through Mac-Min will have a list-id header that containsmac-min_catug.org.catug.org

In Apple Mail, if List-id is not in the list of fields that you can use in Rules, then select Edit Header List.


This brings up the Message Headers window; click on the + tool at the lower left, and add List-id.


After this, you will be able to use List-id in the same way that you could already filter on From, To, Subject etc.

Junk mail filter

Mail has a pretty good junk filter. You can train it to be even better by using the 'Junk' button on the toolbar to toggle the junk flag on individual messages.

If you make a mistake using this, e.g. you label a good message as junk or switch off the junk setting on a bad message, this confuses Mail's rules. It doesn't seem to ignore the mistake even if you correct yourself straight away. The only way out of this is to press the reset button in Mail's Preferences: Junk tab. After this you will have to start again with training Mail's junk filter.

Viewing messages in threads

If you subscribe to Mac-Min as individual messages rather than the Digest, you can view messages by thread. This groups messages together by conversation/subject. The menu command is View > Organize by Thread.

Sometimes different subjects appear as one thread; this is not a bug but is caused by the senders, as explained at Posting guidelines#Subject lines.

Password refused

Mail app for mac that filter utf encoding subject list

If you get 'password refused' when Mail connects, this is probably a fault with the ISP's mail server. This also happens when you change your connection e.g. from ethernet to wifi. If you enter the password manually, you may have to do it a few times. The annoying thing is that Mail seems to assume that if the password has been rejected once, it must be invalid, so it knocks out the password and you may have to re-enter it in the Accounts section of Preferences.

Instead of typing the password even once, close the app (Mail), wait a second or two and open Mail again. It usually works then without asking for the password this time around.

For repeated requests to enter the password, see this OSXDaily article.

Storing attachments

This MacWorld article explains where attachments are stored, and how to find them again if you have made changes to them.

Attachments are also still in the emails themselves (making some emails huge, of course). Here is a simple way to remove attachments and get them all where you can find them. First, create a smart mailbox that shows all emails with attachments. Next, select them all, and in the File menu, choose 'Save Attachments..' and save them in a nice, new folder. Then, go to the Message menu, and at the bottom, choose 'Remove Attachments', and they'll all be gone. Repeat this as often as necessary to keep your mail folder down to a reasonable size.

Sending to a group

Make groups of contacts in Contacts (this app is called Address Book in OS X versions older than 10.9 Mavericks). Mail can then use these groups.

Previous recipients

Mail helpfully builds an archive of previous recipients. However, this sometimes needs weeding. If you start typing a name or email address in the To: field, and Mail prompts you with some that are obsolete or were wrong to begin with, you can remove these quite easily.

In Mail, choose the menu command Window > Previous Recipients. From this window, you will be able to remove those with whom you no longer correspond.

Removing quoting

When forwarding an email, Mail makes it easy to remove quoting on text that that is indented several times.

If the message is in Plain Text format, select the quoted paragraphs (or Edit > Select All), then Format > Quote level > Decrease. There are keyboard shortcuts for this: Command Quote ( ⌘ ' ) adds a quoting level, and Command Option Quote ( ⌘ ⌥ ' ) removes a quoting level.

HTML mail can be more tricky; the above usually only removes one level. Select the quoted paragraphs (Mail helps by showing black boxes around blocks that you can select) and try Format > Quote level > Decrease. The keyboard equivalent is ⌘ [ . Alternatively, if you don't mind losing the font formatting, change the message to Plain Text, using the menu command Format > Make Plain Text; the keyboard equivalent is Shift Command T ( ⇧ ⌘ T ).

Default text encoding

Mail automatically handles text encoding for scripts which have special characters not found in English. However, people who regularly exchange messages in such languages, or including other special characters, it may be helpful to change the default text encoding to Unicode (UTF-8).

On the command line in Terminal, type:

This works fine in Tiger and Snow Leopard, but in Leopard (OS X 10.5), the Mail app omitted this capability. To get it back, apply a download from here.

It seems that Mail will always default to the simplest encoding it can, so when you're setting the 'default' encoding, all you're overriding is what choice it makes when it has to deviate from its preferred encoding. For a message in plain English, Mail will use US-ASCII which is a simple encoding; but if special characters are present, Mail will use UTF-8 if the above preference has been set.

To check the encoding of a message, use the menu command View > Message > Raw Source, then find the key word 'charset'.

Sending HTML emails

The easy part

Assuming that you already know the difficult bit i.e. how to create an HTML file, and just want to send it as an HTML-formatted email rather than an attachment, this is easy on a Mac. Open the html document in Safari, then use the menu command File > Mail Contents of This Page, and Mail will create an html formatted email.

If you need to send it with an email program other than Mail for some reason, just use Mail to email it to yourself and pick it up with the other email application, then re-send it using that app.

The hard part

Doing HTML emails isn't an easy thing to do. If this is for a non-profit 501(c)3 organization in the US, Christi recommends a free account with Vertical Response. It takes the headache out of HTML emails, and keeps track of your newsletter email list.

If you still want to forge forward in designing HTML emails yourself, this tutorial article might help, but it isn't for the faint in heart.

An alternative

These days, most people's computers have software for reading PDF files, and Macs can print to PDF. Consider whether sending your message as a PDF file would be adequate for your needs.

Just adding links

It is easy to simply add links into an email. If the links you want to send are already on a website, just start a new email, then select the text including links on the web page, and drag it into the new email message window. (This always works with simple web pages e.g. on a wiki, but others might be protected from copying like this.)

Alternatively, to manually add a link to some text in your message, first select the text, then right-click and choose Link > Add Link… from the popup menu, and paste (or type) the link. Mail will fill in http:// at the beginning if your link does not start with this or another specific protocol.

  • Opening Windows files – how to get into those pesky attachments!

Contributed by various members of CATUG, up to July 2015. Thanks to Jon Glass for advice on filing attachments; David Burke, Eric and Marvin for investigating text encodings; and Christi for her advice on learning HTML.

Retrieved from 'http://wiki.catug.org/index.php?title=Making_the_most_of_Apple_Mail&oldid=1475'