I know I am not supposed to ask use-case questions here as described here, but I am having no success elsewhere, plus if there is no answer to my question, this could become a feature request.

Currently, in mailmason a template with no Layout set, fills both HTML and Text versions of the email template in postmarkapp.

How do I create a template in mailmason so the HTML field in postmark will be empty, and Text set?

That is important for creating small size ticket emails without bloating customer service management service.

The grunt config has livereload set to True, but when I open previews.html and make a change this does not reload the templates.

is there extra configuration needed?

Do you plan to ease the process of translating email templates?
I understand that postmark is for English-speaking developers, but do you have any feedback on maintaining templates in multiple languages with mailmason?

• Outlook 2007
• Outlook 2010
• Outlook 2013
• Yahoo! Mail - All browsers

Should be able to fix this in the template cleanup/testing phase.

Some mobile clients require style block type attribute to be set to "text/css" in order to render responsive layout.

See if assemble or premailer is stripping out the VML button tags.

An additional unneeded style tag is being inserted into the body tag. It only contains a duplicate body selector.

Hello,

all the links to the examples on this page are broken, I get an S3 error:

<Error>
  <Code>AccessDenied</Code>
  <Message>Access Denied</Message>
  <RequestId>A116E771F9CE9625</RequestId>
  <HostId>TXWC1WrmFqhcwBAM87qR4zm50lQj1tJsoPMtK4Asg2Rt4+yITaBMhQgzbHUwcOKfXAVV4+YwAr0=</HostId>
</Error>

We should replace premailer with something that's fully compatible through node. Requiring gems to be installed is kind of a mess.

Right now, they're red, green, blue. Those are a little less than semantic.

Not exactly sure who or where to reach out, but is this library still actively maintained? I know postmark still has a link to this repo but my biggest concern with using this library are the outdated dependencies. A lot of them haven't been updated in years.

Related, are there plans to using something a little more modern like webpack instead of grunt? I'm looking into expanding some of the functionality and would prefer to use es modules instead of the old commonJS way of doing things.

Thanks

This would support users using Google Cloud Storage as their CDN, as well as users using Firebase which uses Google Cloud Storage.

It should be left aligned.

We need to modify the build process for templates that are stored in PM. Since it's so specific to PM it shouldn't necessarily be reflected in MailMason, so we need to figure out how to keep this part of the build process separate and out of master.

Here's what needs to change:

• Prevent premailer task from running – We're already using mustachio to inline CSS on PM.
• Remove premailer properties from inline CSS – Should be fairly easy with the replace task.
• Add an HTML comment above the style block – "Style block is collapsed blah blah blah..." The idea you mentioned where we call it out if people can't find the collapsed style block.

One idea is to create a separate Postmark branch that gets used for this only. It would still be public but since it's not in master I don't think it's a huge deal. @garrettdimon thoughts?

I'd like to tag a release, push my templates into Postmark, and then run a local hook to update my configuration database with the template IDs. I'm working on a first pass but wanted to open discussion on requirements if anyone has thoughts.

Hi, I have just initiated the development of a project using mailmason. It looks very promising :)

When following your guide, it is stated that secrets.json is not required. However, I was met with the following error when using 'npm start':
..ERROR
>> Unable to process task.
Warning: Required config property "watch" missing.

When secrets.json was created everything works, so I expect there is some kind of ignore-function that is not activated?

Button color modifiers should affect VML versions as well.

Right now the whole content of the CSS file is being loaded into the inline style blocks. We need a smarter way of doing this so that it's only loading classes that are actively being used in the template.

In Postmark you can view and edit the template and edit test variables to see how the template works with actual data however, it does not work locally. I even tried (just out of curiosity) to edit preview.html and add some variables as in the code below

<script>
    var templates = {
      "test_mail_template": {
         // name, description, and guide keys
         // and then template variables
        "template_entity_1": { "template_variable_1": "some custom value 1" },
        "template_entity_2": { "template_variable_2": "some custom value 2", "template_variable_2": "some custom value 3" }
      }
</script>

I think this is very useful not to push some unfinished templates to postmark and have the ability to test templates with actual content on your local machine

Consider this as a feature request, thank you

• Image optimization
• Upload images to CDN
• MD5 hash on assets

Sadly the wiki is write-only so I can't create a PR for it.

On this page:
https://github.com/wildbit/mailmason/wiki/Getting-Started#configuration

preview.html => previews.html

I'm wondering if this is intentional, or if there's an error on my end somewhere. Using the default example_config.json, and default templates, compiled using npm run build, I'm seeing the following differences between Firefox (left) and Outlook 2016 (right):

Obviously, I'd like the Outlook version to look identical to the browser. Is this possible?

Add MD5 hash on assets for explicit asset expiration when they change so we can aggressively cache assets.

Right now, you have to manually run any images through an optimizer. It would be nice if this was automated with the upload process or as its own standalone task. (Or both.)

A few months ago I upgraded mailmason to take advantage of the built in deployment to postmark as well as the first class support for postmark Layouts. I think I broke preheaders when I made that change.

As far as I can tell Layouts only support the {{{ @content }}} placeholder and has no other mechanism for a template to inform the layout - for example by providing a preheader that should sit above all the other content in the Layout.

Is there a work around to get preheaders working? Thanks!

Running "watch" task
Waiting...
Verifying property watch exists in config...ERROR

Unable to process task.
Warning: Required config property "watch" missing.

Running "watch" task
Waiting...
Verifying property watch exists in config...ERROR

Unable to process task.
Warning: Required config property "watch" missing.

Hi there,

One issue which isn't really documented and there is currently only one workaround for is that it is not possible to have a layout use different values depending on the template.

For example, the preheader cannot be set from the template even though it appears that way from the source code. The reason for this is that the template and layout are uploaded separately and any variables that the layouts use that are set by the template are stripped away.

The workaround is to add the information as a Template Model field when sending the email (which is far from ideal).
This makes it difficult to do things like customize the footer depending on the template.

The documentation should be updated and the preheaders in the template code should be removed to make this clearer.

Cheers,
Stefan

Hey,

The dark mode templates in Outlook render with a strange background:

Thanks!