Getting [Unassigned newsletter] before subject in e-mail subject line

Same issue here using dev. version. I have Mimemail 6 dev module installed, and happens with both HTML and plain text mails.
My setup don't use i18n module, but use Content translation 6.14, Locale 6.14, Localization client 6.x-1.7 and I have one non English language added that is the default one.

subcribing

This error may be related to your taxonomy translation set-up. Please read the README.txt, follow instructions and describe the setup if persistent. With the details give here it is impossible to reproduce.

I found this issue only occurred when trying to send a node as a newsletter which was created before the simplenews module was enabled. These older nodes don't get an entry in the 'simplenews_newsletters' table when editing and updating them.

Any new nodes are fine.

Same for me, tried with new content and it's all OK. The issue only happen with content created before the simplenews module was installed.

EDIT: Also the issue I had at #530232: "Unsubscribe" link returns "page not found" with the unsubscribe link at newsletter, doesn't appear trying with new content.

This is very easy to reproduce. Here is how I ended up with this problem:

1. I had a clean installation of Drupal for a new website I was working on.

2. I created a few "Story" nodes for the news section of our website. (which will also be the source of our newsletters)

3. Downloaded Simple News and turned it on and configured the newletter.

At this point if I send the previously created news items then I get [Unassigned newsletter] in the subject line.

4. If I then create a new "Story" and send it then I was getting the correct [Company Newsletter] header.

As a work around, what newsletter table records would I need to change to get the old Story items to have the correct token on the subject line?

Also, can I make an additional feature request here: How do we turn off the "[ ]" token on the subject line?

At pt. 3 did you select a newsletter taxonomy term on the existing stories and save them?

Remove the square brackets with a theme override function.

Yup, I did that. The newsletter Taxonomy term is applied to Story but still, no change in the subject token.

I don't know if this provides another hint but it appears I ran into a "bug" (but in this case I prefer the behavior) when I ran through the sequence above: http://drupal.org/node/713874

Can you give me a little more detail on the "theme override function"?

OK. Found the issue, with stories created before the simple news module is installed, even if you set the newletter vocabulary, it doesn't show up in the "simplenews_newsletter" table. When I manually add the Node ID to this table and then send the newsletter, the subject token correctly shows up as the token I want.

Thanks for reporting your solution. An other way to get the 'old' newsletters listed is to edit and save them. The behaviour is by design and similar to many other drupal modules.