skip to the main content area of this page
EMM Help: Configuration

Configuration

The majority of the configuration of this application is already accomplished by your initial configuration of ASPDNSF. If you have properly configured ASPDNSF's Email settings, then EMM should work for you right out of the box.

Configuration Options (appconfig)

  • LiveServer - The domain name that your registration key will check against to validate license and enable all of the features of EMM to become active.
  • MailMe_FromName - The default "From Name" when creating a new campaign.
  • MailMe_FromAddress - The default "From Address" when creating a new campaign.
  • MailMe_Server - The mail server used by EMM and ASPDNSF to send emails.
  • MailMe_Port - The mail server port used by EMM and ASPDNSF (not implemented yet) to send emails.
  • MailMe_User - The mail server username used by EMM and ASPDNSF (not implemented yet) to send emails if authentication is required by your SMTP server.
  • MailMe_Pwd - The mail server password used by EMM and ASPDNSF (not implemented yet) to send emails if authentication is required by your SMTP server.
  • MailMe_UseSSL - The mail server SSL flag used by EMM and ASPDNSF (not implemented yet) to send emails if SSL is required by your SMTP server.
  • xaEmm.DailySendLimit - This value is for future use.
  • xaEmm.DoubleOptIn - This value determines whether system will require double opt-in or single opt-in for subscriptions. Default is Double Opt-In. A false value is the same as setting Single Opt-In for subscription permissions.
  • xaEmm.InstalledVersion - DO NOT MODIFY THIS VALUE. This value should only be changed by the Install/Update routines for EMM.
  • xaEmm.PageSendLimit - This is the maximum number of messages that will be sent in each batch of outbound emails. The number is initially set to 100 but can be set to any value that you and your mail server will be happy with.
  • xaEmm.PageSendWaitTime - This value determines the amount of time (in seconds) before refreshing page and sending another batch of emails. Default is 15 seconds.
  • xaEmm.RegistrationKey - This is the registration key, as provided by Exhibit A Communications (http://www.exhibita.com/emm/) that will enable all the features of this program.
  • xaEmm.SubscribeEmailOnly - This value determines if an email address ONLY is acceptable for subcribing to newsletters/mailings. A false value will force user to enter a first and last name in addtion to a valid email address. Defaults to true.

Template Files

  • xaEmm-Template.htm - If this file is found in the /admin directory, it will be used as the default content for the HTML version of outbound messages in a given campaign. Once a new campaign is created, you can modify this to your heart's content but this makes it easier for you to maintain a sense of consistency across your campaigns.
  • xaEmm-Template.txt - If this file is found in the /admin directory, it will be used as the default content for the TEXT version of outbound messages in a given campaign. Once a new campaign is created, you can modify this to your heart's content but this makes it easier for you to maintain a sense of consistency across your campaigns.

Topics

  • xaEmmAlreadySubscribed - This is the content that will show at the top of the Subscription pages (that accept input from signup forms) if the user's email address is already found in the appropriate database.
  • xaEmmDoubleOptIn - This is the content that will show at the top of the Subscription pages (that accept input from signup forms) when you have xaEmm.DoubleOptIn AppConfig value (discussed above) set to true. This should explain to that to complete their signup, they will need to look for the email that is sent (as defined in the following topic)
  • xaEmmOptInEmail-HTML - This is the template for the email sent to those who sign up for your newsletters if you have the xaEmm.DoubleOptIn AppConfig value (discussed above) set to true.
  • xaEmmThanksForSubscribing - This is the content that will show at the top of the Subscription or Opt-In Confirmation pages when a new user succeeds in signing up for your newsletter or offers. If Double Opt-In Appconfig value is set to true, then this only shows after they have confirmed their subscription. If Double Opt-In is set to false, this content is shown as soon as they have submitted the required amount of valid information to sign up (as defined by xaEmm.SubscribeEmailOnly AppConfig variable (discussed above).

Newsletter Signups

V1.01.0 has added in new functionality that includes the ability to accept either email addresses only or first and last names and email address to set up a subscriber as either a customer or an external customer. The default installation sets these up as Email Address only subscriptions with a Double Opt-In. This means that a user will only need to provide a valid email address to be added as either a customer or an external customer (per the site administrator's choice) and that their subscription will not be set for OkToEmail until they have confirmed their subscription.

Site administrators can determine at the form where new subscribers will be added by modifying the form ACTION so it points to either xaEMMSubscribeCustomer.aspx or xaEMMSubscribeXCustomer.aspx. The former will add the new subscriber to the store's customer database while the latter will add them to EMM's external customer database.

Sample Code:
Subscribe to our newsletter!
<form action=/xaEmmSubscribeXCustomer.aspx>
Email Address: <input name=txtEmail>
<input type=submit value=Subscribe name=Submit>
</form>
Which would look like:


Manual File Modification (optional)

  • /admin/skins/skin_1/menuData.xml - If you want to make it easier to access EMM from within the administrative interface, you'll need to modify this file to get a link to EMM to show up. We strongly recommend adding this to the top level of the menu, to the right of the User's link. This should serve as a constant reminder of the value of regularly sending email campaigns to your customers. The best way to do this is on the 3rd to last line of this file, insert the following code:
         <item Text="(!xaEmm.admin.menu!)" NavigateUrl="xaEmm.aspx" LookId="TopItemLook">
           <item Text="(!xaEmm.menu.0!)" NavigateUrl="xaEmm.aspx" />
           <item Text="(!xaEmm.Campaigns.10!)" NavigateUrl="xaEmm.aspx?Action=ShowCompleted" />
           <item Text="(!xaEmm.menu.2!)" NavigateUrl="xaEmmUnsubscribes.aspx" />
           <item Text="(!xaEmm.menu.5!)" NavigateUrl="xaEmmAddExternalUsers.aspx" />
         </item>
    This puts it behind the item that links to customers.aspx (and all it's child elements) and before the final element that is empty save for a width and a LookID.