Google spam rules

 
From: "H.E. Weenink | Aristo Advies & Internet" <h.e.weenink@PROTECTED>
In-Reply-To: Re: New Feature Ideas for the Future: Private Mailing Lists
Date: December 10th 2013
Untitled Document

Hello list/Justin

 

I have problems for mails coming on spamlist (specally gmail.com mailaddresses).
Now I see these are Google rules:

 

·              A prominent link in the body of an email leading users to a page confirming his or her unsubscription (no input from the user, other than confirmation, should be required).

·              By replying to your email with an unsubscribe request.

·              Provide a 'List-Unsubscribe' header which points to an email address or a URL where the user can unsubscribe easily from future mailings.

·              All bulk messages you send must be formatted according to RFC 2822 SMTP standards and, if using HTML, w3.org standards.

·              Messages should indicate that they are bulk mail, using the 'Precedence: bulk' header field.

·              Attempts to hide the true sender of the message or the true landing page for any web links in the message may result in non-delivery.

·              The subject of each message should be relevant to the body's content and not be misleading.

 

I wonder if the unscubscribe link in dadamail is formatted correctly (I use the default option, so people go to unsubscribepage and input mailaddress + submit)

Seems that emailaddress should always be added automaticly, or people should just have the email-reply thing (we had that before, but is not working in latest versions).


Please advice on how to get this fixed (or is it allreday OK in default version? )

 

 

 

Vriendelijke groet, Eef

 

H.E Weenink MBA

Aristo Advies & Internet B.V.

0(031)-545-431634

0(031)-630065069

Van: Mary Ann Kelley [mailto:maryann@PROTECTED]
Verzonden: vrijdag 18 oktober 2013 0:16
Aan: Dada Mail Developers
Onderwerp: [dadadev] Re: New Feature Ideas for the Future: Private Mailing Lists

 

But, I am curious.  You have the DaDa mail .htaccess files protecting wordpress pages as well?  So someone goes to a page in wordpress, they are prompted for the DaDa password, and then allowed to view it? If that is the case, you may have already worked out a viable skeleton for a wordpress plugin.

 

No, because that is where the second install comes in. Wordpress seriously hates it when you mess with the permalink structure, and I couldn't find a way to protect an actual WP page with the Dada plugin. It just throws a 404 error. The only way I could get around it (at my skill level and budget - which was zero - under the time constraints I had, anyway) was to use 2 installs. I put the first install in the site root. The second install is in a subdirectory of the main site. The subdirectory is the one that is protected by the .htpassword file created by Dada, which is running on the same domain. 

 

To load the second install without it looking like a separate site, I customized a template for the first install with an iframe that feeds the home page of the second install into the main content area (but uses the sidebars and header of the first install so that the menus and widgets appear the same in the protected area). I assigned that template to a page in the main install. When someone clicks over to that page, the page loads up to the iframe content, where the Dada login pops up. If they don't login, they are redirected to a page that tells them how to register for a profile or recover their password. If they do login, the home page of the second install loads in the iframe. 

 

Like I said - it's not very elegant but it works. I would love to find a way to do it with just one install, but it's beyond my skill level.

Warm regards,

Mary Ann

 



Post: mailto:dadadev@PROTECTED

Unsubscribe »

rss/atom
‹ App Developments
Index
Re: Google spam rules ›
  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)

  • Start a new thread, email: dadadev@dadamailproject.com

This is the developer discussion mailing list for Dada Mail.

If you are just looking for support Dada Mail, consult the message boards at:

https://forum.dadamailproject.com

Documentation for Dada Mail:

https://dadamailproject.com/d

Specifically, see the Error FAQ:

https://dadamailproject.com/d/FAQ-errors.pod.html

To post to this list, send a message to:

mailto:dadadev@dadamailproject.com

All subscribers of this list may post to the list itself.

Topics that are welcome:

  • Constructive critiques on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

Dada Mail is on Github:

https://github.com/justingit/dada-mail/

If you would like to fork, branch, send over PRs, open up issues, etc.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.