For logo:
There is an email var for that:
{{skin url="images/logo_email.gif" _area='frontend'}}
To make it your own, upload and replace logo_email.gif
For email variables:
Some of these exist by default:
General Store Email address:
{{config path="trans_email/ident_general/email"}}
Store Name:
{{config path="general/store_information/name"}}
Store Code is trickier. This is not exposed in the config to my knowledge for use by the email templates. I suggest using a custom template file, and refer this way:
{{block type="core/template" template="custom/storecode.phtml"}}
storecode.phtml:
<?php
echo Mage::app()->getStore()->getCode();
Alternatively, and maybe less-desirable, are Custom Variables.
Custom Variables
System > Custom Variable > Add New Variable
To Implement a custom variable into a Transactional Email, do the
following: In the Admin Panel, select System > Transactional Emails
Click the row of predefined template to edit or click [Add New
Template] button to create a new one. Create a new transactional email
first if needed. In the Template Content field, select a location for
your custom variable. Click [ Insert Variable ] and select the Custom
Variable you would like to insert.
Source: http://www.magentocommerce.com/knowledge-base/entry/creating-custom-variables
Take a look at Magento Newsletter form not working
Try
{{block type="newsletter/subscribe" template="newsletter/subscribe.phtml"}}
The form need to be posted to newsletter/subscriber/new
which is define in
Mage_Newsletter_Block_Subscribe
/**
* Retrieve form action url and set "secure" param to avoid confirm
* message when we submit form from secure page to unsecure
*
* @return string
*/
public function getFormActionUrl()
{
return $this->getUrl('newsletter/subscriber/new', array('_secure' => true));
}
Best Answer
The controller that process newsletter subscription is
and the condition that arises this message seems like this
As you can see this code checks whether the customer assigned with given email address matches with email address of logged in customer. If those customer ids do not match, then it will raise this error.
So my assumption is email address that you provided through newsletter and current logged in email address is different. That is why it raises this error.
If the error is not because of this, then you need to dig more from this file.