Remove the footer in mailchimp - asp.net

I'm sending auto mail for my new subscribers via MailChimp, the mail is sent and every thing is fine but with a footer which gives user option to unsubscribe from the list...anyway I'm trying to disable that footer but all comes in vain, I tried to set the auto footer to false but nothing happens and here is sample of my code
var campaignCreateOpt = new campaignCreateOptions
{
list_id = listID,
subject = Subject,
from_email = from_Email,
from_name = from_Name,
template_id = 0,
auto_footer = false
};

I think you'll have a better chance of your email getting out to most of your list if you allow the unsubscribe.
It's generally not smart to not give people an option to unsubscribe. If they do not see an unsubscribe option, they can mark you as spam. If you get too many "spam" complaints, your email may not reach the inboxes of even the people who would like to stay subscribed.
I doubt mailchimp will allow removal of the unsubscribe.

Reasons:
Mailchimp's Terms of Service does not allow you to send an e-mail
without the unsubscribe link. If you don't provide the unsubscribe
link, they will insert it using the gray footer bar.
Also, if your account is free, and you don't use the REWARDS tag,
they will also insert it through the gray bar.
The third probable reason is that if your code is complicated or
broken, they might see it as an attempt to hide their UNSUBSCRIBE or
REWARDS tag, so they will automatically add the gray bar to your
e-mail.
Hope I helped you.
Source: http://kb.mailchimp.com/article/why-am-i-getting-a-gray-bar-or-a-2nd-footer-that-i-cant-edit

I took the time to invest some further and maybe have to apologize to Mahmoud Ghoz and I will if you can test the following for me.
Probably the following is happening: your not including a *|UNSUB|* tag or you use a free account and not including a *|REWARDS|* tag? If this is the case, the footer will always be added no matter which value you use for the auto_footer property.
So try to include a *|REWARDS|* and *|UNSUB|* tag in your mail and do a recheck. Please let's us know if it works. But like I said earlier you account can be temporary locked if you get to many spam warnings which could be the case if you not supply a unsub link.

I guess this is not allowed for free user to do so

I had a similar problem, it turns out that my issue was a background image (in inline styles) in the footer. MC clearly thought I was trying to hide the unsubscribe link! I have removed and all is now good.

Related

How to incorporate Html in client script code?

I was trying to send email using send button. Inside the save button I have added some code to declare : to, subject and email body. I want to make the email body a bit nice, by adding some html like h1/h5, p. etc
I have tried to added the html tags like h1/h2 etc or p.. but those part also pops up in the email.
"<html><body><h1>Description:</h1></body></html>\n\t\t" + widgets.Objective.value
The reason that is probably happening is because when you are sending the email, you are not doing it correctly. The code you have provided is not really helpful, so I'm only guessing that your logic to send the email on the server side is not the way it should be. Take as a reference the following code snippet:
MailApp.sendEmail({
to: "recipient#example.com",
subject: "Test Email",
htmlBody: "<html><body><h1>Description:</h1></body></html>\n\t\t"
});
Reference: https://developers.google.com/apps-script/reference/mail/mail-app#sendEmail(Object)
P.S. If this answer is not helpful, please considering editing your question and please include your server side code as well since the current way your question is being asked leaves too much questions flying around.

Is it possible to customise the Docusign Iframe and avoid signers to have to enter their information?

Recently I have been looking into some different API for signing documents online, what I am looking for is one that has a customisable Iframe to avoid breaking the already established style of our website.
I would have wanted to know if Docusign proposes this kind of service.
For example, if we would just have the pdf file and a spot to sign, that would be perfect.
I hope I was clear enough with my question, thanks for your possible answers.
EDIT: I would have also liked to know if there is a way for the signer to not have to enter his personal information/sign in. One where that information is entered by us when the procedure is created.
Is it also possible to change the size of the zone where the signer signs, I was some other signing API's proposed it, but haven't seen it on Docusign.
How can I also change the language of the Iframe and disable the automatic mobile version.
Thanks for spending the time reading and helping me with these questions.
You can use an iframe for the signing when you use "embedded signing" in your integration. This is a common scenario and the signer won't have to log-in.
Even when using an email, most people just click on a link and they don't need to log in to DocuSign in order to sign.
The Docusign Iframe isn't 100% customisable, but you can remove some little extra UI with &noDownloadPrint=true&appname=docusignit, or add &disable_cc_for_selfsign=true to remove the "Sign and Return". From the creation of the Docusign EnvelopeAPI, you can't change the language of the Iframe.

Can I prevent spam bots from submitting a form if its hidden?

If I display:none over a form wrapper on my website contact page will a spam bot still be able to submit it?
If no, then would a possible solution be to just place a link saying - send us an email - and when clicked it display:show the wrapper with the form thus this preventing spam?
Thanks,
-O
A spam bot is usually a script that is executed and run automatically. It's not an actual human being so the bot would not care if it is actually hidden by the style or not. You could add it to the DOM in the moment the user clicks a button if you wanted to prevent a "spam bot" to abuse it.
There are many different types of spam bot out there, and many different approaches used in filling in your form (and thus: sending you spam).
For the most part these are automated scripts which don't actually 'see' the page at all but simply use the markup it finds on-page. To that end, using CSS to hide a form won't stop them at all.
On the same vein: you'll find that there are a lot of bots out there which will scrape your email address and send you spam directly if you leave a mailto: link on your site.
There's no sure-fire way of stopping spambots I"m afraid. There are a lot of techniques that you could employ to reduce it though.
The most common is to use a captcha service like recaptcha although even this isn't a concrete guarantee that some spam still won't filter through.
The other trick I tend to employ is a Honey Pot input which is relatively easy to employ and seems to do a fairly good trick of keeping the spammers out.
Spambots are meant to be fast, and they don't parse CSS or JavaScript. If you want to protect against them you can include a CAPTCHA, even a simple one, like asking the user to write the sum or product of small numbers (obviously write the request in a sentence, using letters and not numbers). A cheap solution like this should prevent most spam, but it's easily attackable, if someone wants to target you.
I wouldn't suggest to create dynamically the form, since users that aren't capable to execute JavaScript wouldn't be able to see it.
If using a honey pot, which is the most user friendly, simple and extremely effective, try not to hide your input field with the css hidden command. Bots can see this if they are complex..
Position the field absolutely at the top of the form, to the left or right, have it with no border, and the background and text colour the same as the element the form is within.

Screen reader and error messages

In general, how do you display client-side validation messages on a web page to make it easy to read out? Alerts are read out nice but are forbidden in the current design.
I'd suggest using a paragraph or similar (optionally invisible) with a role of alert.
<p id="error-msg" role="alert"></p>
When something goes wrong, put the text in the error-msg element, with Javascript of some description.
document.getElementById("error-msg").innerHTML="What are you doing you fool!";
Or something to that effect.
I believe this is what YouTube uses to let a user know when a new video in a playlist is loading.
Hope this helps.

SEO for CSS and JS hide/show

We're building a site for an academic institution. This institution offers many subjects, and we don't want to show all of them at once on the homepage. So we designed a homepage that shows the 2 main categories of studies, and clicking on a category will show a div with the list of subjects in that category.
Our client is worried SEO-wise about those div's being hidden on page-load. Is he correct in his concern?
It depends on how you hide them if you use a z-order or a far left off screen position they will still be read by the Google bot. if you use display none or hidden then it may have an effect on your SEO.
You're right to have concern. Google will count some of or significantly reduce content that isn't displayed on page load. I would recommend letting the text display at load, then setting it to display none via JavaScript. This way the search engine picks it up.
You can do so with a simple jQuery hide snippet like this:
<p class="remove">Text displayed on load.</p>
$j(document).ready(function(){
$('.remove').hide();
});
I read an article by Roger Johansson on this subject, and it seems that the conclusion is that as long as the intent isn't to show that content only to search engines, hiding is fine. I don't see any mention of preferring one method of hiding over the other.
In addition, in that post's comments there was a link to an answer by a Google worker that said:
Merely using display:none will not automatically trigger a penalty. The key is whether or not there is a mechanism - either automatic or one that is invoked by the user - to make the content visible
In my case of course there will be such a mechanism, because we want our users to see that content, just not at page-load...

Resources