Re: |redirect| tag versus |subscriber| fields tag replacement

 
From: "Justin J" <justin@PROTECTED>
Date: October 9th 2009

On Oct 9, 2009, at 3:44 PM, Alex Judd wrote:

I have used the | symbol instead of the [[ or ]] bracket symbol now
so hopefully the mail now makes sense!

Annoying, isn't it? Tags shouldn't really be replaced in discussion
lists, imho It always leads to problems ;)

So that if you have URLs containing information such as the segment
of the database you are emailing, the redirect seems to include the
in the link rather than substituting the values first, then
creating the redirect

I understand exactly what you're saying and I think you're right If
you do write a redirect with a tag, the tag isn't really ever going to
be replaced with the value Here's why:

When you send a message with a redirect, before Dada Mail makes a mass
mailing, it'll scan a message and find all those redirects and save
them in its DB, giving back the shortened redirect URL for Dada Mail
to then replace in the messages

It only does this once, so that it doesn't have to do it for every
message - which literally could be thousands of messages - a pretty
big performance hit!

Since all the redirect URLs are the same for all messages (erm, for
each different redirect link you have), they won't be able to be
dynamic

Now - you've raised a really interesting application for dynamic
redirects - truly I like the idea, and I think there should be
someway to do what you're doing I'll put this in the features request

The clickthrough tracker is one of those things that needs to be
looked at a lot closer in the immediate future I know on this list
we've punting some good ideas that the current clickthrough backend
just can't handle - it's very simple I think a big problem is the way
the clickthrough information is saved - just as a plain text log That
has some serious performance issues

The other big problem is the UI to see this information - it just
doesn't give you enough tools to play with the information Not enough
fancy graphs, and such ;)

  • 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.