March 26th 2013 UTC
> You'd first want to fork the repo, > > https://help.github.com/articles/fork-a-repo > > And then merging the email tracking stuff is as easy as, > > git merge features-email_tracking > > Just remember that nothing except master is stable, so there's most likely > issues that need to be dealt with, before it gets released. > -- [[ AJ ]] Well that’s easy enough. Thanks for such a quick response! A.J. > On Mar 25, 2013, at 9:49 AM, AJ wrote: > > > > >> Dun ...Continue Reading
March 26th 2013 UTC
I am testing out the new Pipe to Program feature. I love the idea, but on my test list not all of the addresses on the list are getting the emails. I'm checking it on another small list as well to be sure it isn't just a problem with one of my test email addresses. They are being sent out instantaneously, which is great since the shared server has a limit of cron jobs of running every 15 minutes. I have to be sure it's going to send all of the emails out before I can use it. The logs say they are going out, but I' ...Continue Reading
March 26th 2013 UTC
I just checked the settings on one of the installs that you did and realized that. I didn't realize it had changed. Thanks. Warm regards,Mary Ann On Mar 26, 2013, at 12:20 PM, Justin J wrote:On Mar 26, 2013, at 10:06 AM, Mary Ann Kelley <maryann@PROTECTED> wrote:Should there be an autopickup.pl file in the extensions directory? No. The extension has been superseded by the Mailing Monitor plugin (and has for, for a while) - your cronjob would want to look more like this: /usr/bin/curl -s --get --data r ...Continue Reading
March 26th 2013 UTC
On Mar 26, 2013, at 10:06 AM, Mary Ann Kelley wrote: > Should there be an autopickup.pl file in the extensions directory? No. The extension has been superseded by the Mailing Monitor plugin (and has for, for a while) - your cronjob would want to look more like this: /usr/bin/curl -s --get --data run=1\;passcode=\;verbose=0 --url http://www.domainname.com/cgi-bin/dada/plugins/mailing_monitor.cgi ...Continue Reading
March 26th 2013 UTC
Should there be an autopickup.pl file in the extensions directory? Because there isn't. And I just upgraded to the latest stable version and it didn't put one there either. What is the cron job supposed to be triggering if there is no file there? Warm regards,Mary Ann On Mar 26, 2013, at 11:26 AM, Mary Ann Kelley wrote:This install lives on a domain where WordPress is installed on the main directory. When the cron job calls auto_pickup.pl, WordPress is throwing a Not Found error. We dealt with this problem with t ...Continue Reading
March 26th 2013 UTC
Okay, that error was because I forgot to take the > out at the end of the line. I figured out what is happening but I have no idea how to fix it. When I took the > out, the cron is sending me the HTML from the WordPress 404 page. This install lives on a domain where WordPress is installed on the main directory. When the cron job calls auto_pickup.pl, WordPress is throwing a Not Found error. We dealt with this problem with the password protect directories plugin (Dada was overwriting the change ...Continue Reading
March 26th 2013 UTC
Following up - this is the error I'm getting from the cron job:/bin/sh: -c: line 0: syntax error near unexpected token `newline'/bin/sh: -c: line 0: `/usr/bin/curl -s --get --data run=1\;passcode=\;verbose=0 --url http://www.domainname.com/cgi-bin/dada/extensions/auto_pickup.pl > 'In addition to that, bridge is sending duplicates of many mailings. Ideas? Warm regards,Mary Ann Post: mailto:dadadev@PROTECTED Unsubscribe » ...Continue Reading
March 26th 2013 UTC
I am running Dada bridge and continue to have a problem with mailings getting stuck (and sometimes going stale). The cron job is running but once a mailing gets stuck in the mailer, it won't check messages because there are already the max amount of mailings going out. Shouldn't the autopickup cron command be taking care of preventing mailings from getting stuck? Because it doesn't seem to be doing anything. Here is what I have for the command:/usr/bin/curl -s --get --data run=1\;passcode=\;verbose=0 --url http://www.d ...Continue Reading
March 25th 2013 UTC
On Mar 25, 2013, at 9:49 AM, AJ wrote: > [[ AJ ]] I really need to start spending more time with Git. Unfortunately, I am still mainly stuck in the subversion world with a little Bazaar thrown in. Do you have any basic procedures for merging in the email tracking? I have quite a bit of experiencing coding in perl so you should not have to 'dumb it down'. Just, as I said, not a Git developer yet. You'd first want to fork the repo, https://help.github.com/articles/fork-a-repo And then merging the email tracking ...Continue Reading
March 25th 2013 UTC
> Dunno! That's sort of just what I picked. I doubt it would hurt things, if you > changed for your install (barring any charset conversion problems). I can't say > I know the difference between the two on the top of my head. Since Dada > Mail supports 3 different (SQL) backends, and all the backends are a little > different, their schemas are also a little different. So, for example, the > PostgreSQL doesn't set a charset for any of the tables, 'cause (I think) ya > don't, in PostgreSQL - rather y ...Continue Reading
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:
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:
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.
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.