Mail account claims to have more storage space used than actually used
 

Here, take a look:

http://xs202.xs.to/xs202/06261/fastmail.jpg


Note that I'm apparently using 9.8mb. There is one message in the inbox, two in the trash - none are more than 5KB.

What's going on?


EDIT:

Additionally, here's the quota screen - a barrel of hypocrisy (I removed the things from the trash by the way):

http://xs202.xs.to/xs202/06261/fmquota.JPG

Re: Mail account claims to have more storage space used than actually used
 

That's a very harsh thing to say, how do you know it's not caching issue?

Or that Fastmails MB display doesnt take a while to update?

Or that it's a genuine error on Fastmails part?

Or that your not in some way mistaken?

I'm also made suspicious of your comments based on the fact your a representative of "BeanRack.com" although right now your service seems down altogether.

Jason

Re: Re: Mail account claims to have more storage space used than actually used
 

This has been going on for weeks, but since I've decided to actually start using my fastmail account, this is a fantastic time to fix it.

1. I've never had 9.7/9.8Ms of email
2. That's what I'm trying to figure out
3. ^

Beanrack.com has been down for a while - I just noticed it's still on there. I'll ask Edwin to have it changed.


Now that we're done with the, er, mudslinging, can we get to finding out what the problem is caused by? Or that perhaps someone else may be experiencing it?

It's not something I've seen reported before, I'm not sure that anyone here can help you.

I know that Fastmail dont offer email support to Members, but as it seems to be a "fault" in their system and not a mistake you've made I'm not sure what else you could do.

Jason

I seem to recall someone posting with the same or similar problem awhile back, and the solution was to click some link to cause the system to recalculate the amount of storage used. I don't remember if it was a problem with storage used by mail or by file storage, however.

Thanks to a bug report to Fastmail (in which they responded with the below), my problem is fixed!


Thanks to Fastmail's quick response, and hopefully the above email helped more than just my sorry ol' self.