Justin J <email@example.com>
Subject: Re: Amazon SES additional Perl library configuration
In-Reply-To: Amazon SES additional Perl library configuration
Date: March 8th 2012
On Mar 8, 2012, at 5:04 PM, Alexander Judd wrote:
> As far as I can tell the Amazon SES integration in Dada 5 needs Perl modules Digest::SHA and LWP::Protocol which for our testing server I have to install locally, rather than to the root libraries.
LWP version 6'
> Can we append to the library include path using the local dada configuration file,
I don't think that'll work - but have you tried?
> or is the only option with this to add them to the
> use lib qw()
> array in mail.cgi (which means they get overwritten when I upgrade RC3 to RCFinal)?
Can you add the path to your PERL5LIB environmental variable?
<< Previous: Re: Discussion List settings
| Archive Index |
Next: Re: Discussion List settings >>
This mailing list is to discuss the nerdy programming development of Dada Mail -
If you are just looking for support Dada Mail, consult the message boards at:
To post to this list, send a message to:
All subscribers of this list may post to the list itself.
Some on topic... topics include:
At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.
Please, please please familiarize yourself with the documentation at:
Since no one wants to answer the same question twice.
Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.
NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.