Robio's dashboard

Haven't had a winmail.dat problem in a while, but it cropped up again yesterday. Gotta get this one fixed.

Seth,

I didn't mean "Local Folders," I'm afraid. I don't use "Local Folders." But it seems your solution may work for me anyway.

What I'm looking for in that part of my question is for Postbox to index ONLY the local copy of each email, and NOT index the copy still on Gmail.

The problem I'm having is that whenever I do a search, I find two copies of every email in the search results. One is in Folder > Subfolder on my own machine. The other one is in Gmail > All Mail.

I want Postbox to STOP indexing Gmail > All Mail, and ONLY give me search results from the local folders.

Is the only way to do that by Advanced Search? – Robio, on November 23, 2009 14:07

Sherman,

If Postbox is running, but not in the foreground (i.e. I'm in another app), my CPU is always pinned no matter how long the screensaver is on. But the computer is also set to sleep after 10m of no activity, so beyond 10m, I cannot say. – Robio, on November 23, 2009 14:02

Been running 1.1b1 about an hour now, and I LOVE the speed improvements!

Semi-off-topic: Is Postbox migrating its support to postbox.tenderapp.com? Or are you just taking it for a test-drive?

I think that will be OK. As long as people can converse in French and Spanish without there being any bugaboos, which I imagine won't be a problem since the fields in which one types are basically <textarea />

Will try that as a test ASAP.

This had been fixed in a previous build, but now in 1.0.2 (and perhaps earlier) it's back again.

This is a MUST FIX.

This had been fixed in a previous build, but now in 1.0.2 (and perhaps earlier) it's back again.

This is a MUST FIX.

Hi Scott,

This problem, which had gone away at some point (either 1.0 or 1.0.1) is definitely back in 1.0.2. Even senders who had been OK'd before and were no longer a problem, I now have to click "allow remote images from..."

The problem is exactly as described in my original post.

Serous BUMP! This is happening daily now.

Events I created, then got this bug, did turn up later. But events I tried to accept from an incoming email have not.

Plus, when I tried to create an event from scratch just now, it did not appear. I imagine it will turn up in a few hours.

Is Provider perhaps a better alternative to Lightning?

HTML. I can send you an email, Scott, if you want to see it happen.

@:)R

Bump!

Problem still happens in 1.0.2. – Robio, on October 29, 2009 11:20

Scott,

Several things here:

-------------------------
1) I've experienced Manfred's problem with forwards as well — and only in the last few weeks. The problem did NOT start with the release of 1.0.1, but began a week or two AFTER that release.

I've had 3 forwards that appeared to be blank. But I discovered they DID have content when I went to View > Message Body As > Plain Text.

I no longer have these emails, but I'll save the next one for you. Note: I DID check the HTML of these messages, and the coding appears to be fine. No coding errors I could see that would prevent the text from appearing.

-------------------------
2) I was able to reproduce the Resend Bug with a couple emails I'd originally sent to YOU, so I'm using resend on those same messages. You should have the resends in your (and/or the support@) In Box now, so if you can go back and find the originals (assuming you still have them) you can compare them.

Attachments do seem to be a factor (I can't recreate the problem with any message that didn't originally have an attachment). Another apparent factor: If the message you're resending was one you originated from scratch (the bug does occur) or if the message you're resending is a reply to someone else's email (the bug does not occur). In both these cases, the message being resent DID have an attachment.

Please note that the way *I'm* using resend, it's not on incoming messages, but to SEND AGAIN something I originally sent. For example, I send the same message to two people separately, using Resend to create the second.

Here's what you're getting from me, so you can make sense of them (note the subject lines are the same as the originals, save the capitalized intro):

RESEND SAMPLE 1: 1.0.1 Still stuck when Quitting — sample attached
This is a resend of my ORIGINAL email from 10/03 in which I sent you a process sample. It was sent both to your direct email addy and to support@. The original email had a greeting, three paragraphs separated by breaks, and my standard signature of @:)R. (I tell you this so you don't mistake the signature in the resend for wildcard characters.) As you'll see, the resend has lost all the paragraph breaks that were in the original.

RESEND SAMPLE 2: 1.0.1 Still stuck when Quitting — sample attached
This is a resend of a LATER email in the same conversation from 10/12. This one also had an attachment of a process sample, but this one was a REPLY to an email you'd sent me. In this case, the formatting of the resend is FINE.

RESEND SAMPLE 3: Never-ending progress bar & wheel + 35% CPU
This is another resend of another email I originated on 10/13, which was sent only to the support@ address, and not to your personal address. The original composition had a greeting, and several paragraphs that included single "returns" followed by links to other GetSatisfaction threads. With all that variety, the Resend being stripped of its formatting makes for quite a mess. This email also included a process sample as an attachment.

-------------------------------------
3) And just to help keep things clear, a few FYIs:

FYI #1: I think this problem may be related to another issue I previously reported regarding attachments being turned into inline text despite being dragged specifically to the ATTACHMENTS box in the header. As such, this may all be moot because of the attachment updates in 1.0.2. (But I haven't tried 1.0.2 yet because I'm still running the special 1.0.1 build you had me try looking for specific bugs.)

FYI #2: The three resends described above are being sent from that special build of 1.0.1.

FYI #3: To further complicate matters, I also happen to be sending you NEW process samples from that special build, and relating to the problems for which you'd send me that build. I'll distinguish those emails with a subject of "NEW PROCESS SAMPLES FROM SPECIAL 1.0.1 BUILD."

*WHEW!* I seriously hope you could follow all that. I tried to make it as clear as possible. You know how to find me if you need more/better info because I made you go cross-eyed and jelly-brained reading all this.