1. In your authorized senders list, you can now enter Basecamp authorization tokens on an address-by-address basis:
   
2. Or you can update your current addresses to use different Basecamp tokens (it will default to using the Basecamp token from your Mailmanagr account, so you don’t HAVE TO do this if you want Mailmanagr to just keep working as it always has).
   

Sending a message to “test@mailmanagr.com” from “info@industryinteractive.net” will post the message to Basecamp as my “Mailmanagr” account.  Sending a message to “test@mailmanagr.com” from “jonathan@industryinteractive.net” will post the message as my own personal account in Basecamp.

The best setup would be to hook Mailmanagr up using one of your administrator accounts in Basecamp (that way, Mailmanagr will have access to post to all projects).  Then, get your team mates to e-mail you their Basecamp tokens as well as any addresses they’d like added to the authorized senders list.

If you are experiencing trouble (messages not getting posted) after setting up your 37signals ID, please log in to the web interface for Mailmanagr and update your Basecamp account settings.  You should only need to do this if your username and/or password has changed with the transition to 37signals ID accounts.

If you’ve tried that, and are still having trouble, please get in touch.  We’re here to help!

Luckily, the removal process is very straightforward.  We’ve submitted our removal request, and everything should be updated in a half hour or so.

This list would have only affected outgoing mail (bounce messages, account sign-up messages, lost password messages), not incoming messages.  So if you’ve tried to sign up for Mailmanagr, or requested a password reminder in the last few days and haven’t received a message, try again tonight.

You can now force  the plain text version of a message, on an address by address basis.  We built in a tweak a while ago allowing you to use “Ptext:” in the subject line of a message to force Mailmanagr to ignore any HTML formatting.  That’s great for single messages here and there, but if you’re having problems getting your mail client to play nice with Mailmanagr, you might need to force the issue.

This feature is free for everyone, so enjoy.

Why on earth would you want to do that?

Some folks have asked for the ability so that they can use Basecamp to handle requests from their customers and web sites.  There are cases where it’s impossible to know where all of your mail is going to come from, or the potential authorized senders list is just too big, this new feature will let you work around that.

Just bear in mind that you might receive proposals from Nigerian political officials in your Basecamp projects.  You’ve been warned.

So, with this announcement comes a couple of notes:

1. We don’t filter spam.  If you create an open address in Mailmanagr, and post it on a public web site, expect to get junk mail.  If you’re concerned about who can add content to your Basecamp projects, this feature probably isn’t for you.
2. This is a paid-account-only feature.  Sorry.  We try to look at features in terms of the resources needed to support them.  This could generate significantly more traffic to our mail servers.
3. If things go absolutely insane, and the mail volume spikes to a crazy level, we might have to rein things in on an account-by-account basis.  We’re not going to be prudish about it, but please think twice before doing something that is going to result in thousands of messages per minute.

So here’s a few tips, if you’re considering using this new feature, but you aren’t sure about how to keep things somewhat secure.  They aren’t requirements, but they are ideas you might want to consider:

1. If you’re going to post one of these addresses for customers to use, do it on a client portal; somewhere that is password-protected.
2. Build a contact form for your web site, and have that send the message through Mailmanagr, instead of posting the address out in the open.
3. Make the addresses hard to guess.
4. Feel free to change your addresses up on occasion if you do start receiving spam.

With that, enjoy!  As always, we’d love to hear from you about any ideas, problems or concerns you might have.

You might notice that Milestones with comments can now be created.

There’s a slew of other enhancements coming in the next while now that things have been cleaned up.  We’ve had requests for multiple auto-notifies, private addresses (everything sent through them will be marked private), and cleaning up the “syntax” of things.  We’re going to move a lot of the “commands” out of the body of the message and into the subject line for more consistent processing.

(Guess we’ll need to update the intro video on the home page now.  If you’re new here, things look a little different, but the idea is still the same.)

What we’re announcing today, though, is if you attach a .zip file, but you would actually prefer to upload the individual component files to Basecamp, Mailmanagr can take care of that for you.  Just attach your .zip file to your message, and put “unzip:” in your subject line.  Mailmanagr will then process your message/todo/(just testing milestones now) and attach each file contained within the .zip archive you’ve uploaded.

If you’re having trouble with a particular message, and the formatting is getting all messed up, just put “Ptext:” in the subject line of your message.  Mailmanagr will then force itself to only deal with the plain text part of your message, and will ignore all of the HTML gobbledygook.

If you’d like to post a new message through Mailmanagr and have it marked private, just put ppp before your subject line.

1. After waiting entirely too long for one company to get their act together on payment processing, we just decided to ditch them and go elsewhere. Within 24 hours, the paid plan was live. All current subscribers received an e-mail outlining the differences between paid and free, and we’re extending a 30 day window to folks before all of the free restrictions kick in.
2. We put out an update tonight for our OpenID authentication. We were using some old code that didn’t fully support OpenID 2.0, so Yahoo users (among others) were being left out. That’s been fixed now, and a wider range of OpenID providers is now supported. If you run into any trouble, please let us know ASAP.

The future of Mailmanagr is looking pretty good. We’ve had a fairly positive response to our paid plans, and we’re nearing the break-even point on things. Regardless, now that we’re done treading water with payment processors, it’s full speed ahead on those new features we’ve been talking about.