Re: Change Reply-To email address

 
From: "Justin J" <justin@PROTECTED>
Date: September 1st 2010

On Aug 31, 2010, at 4:18 PM, Martyn Davison wrote:

In line 4049 (approx?) the entry "add_reply_to => 1," appears - I am presuming that the digit 1 indicates that the field is to be included in the email header

No Here's the line you're looking for, with a few lines around it:

Dada Bridge Plugin:

group_list                   => 0, 

open_discussion_list         => 0, 


discussion_template_defang   => 1,
only_allow_group_plain_text  => 0,
add_reply_to                 => 1,  # here's your line
mail_group_message_to_poster => 1,
append_list_name_to_subject  => 1,

You're looking inside the %LIST_SETUP_DEFAULTS hash, in the group of key/value pairs that deal with Dada Bridge That key/value maps to the Dad Mail-specific setting in Dada Bridge:

[ ] Automatically have replies to messages directed to the group A 'Reply-To' header will be added to group list mailings that will direct replies to list messages back to the list address (some email@example com)

Failing that, where abouts in the scripts can I hard code the address so that the required address gets included rather than the default one?

Try this - I haven't tested it In DADA/App/MassSend pm find this line:

        $message_id = $mh->mass_send(
            {
                -msg              => {%mailing},
                -partial_sending  => $partial_sending, 
                -multi_list_send  => {
                                        -lists    => [@alternative_list], 
                                        -no_dupes => $multi_list_send_no_dupes, 
                                     },
                -also_send_to     => [@alternative_list],
            ($process =~ m/test/i) ? (-mass_test => 1, -test_recipient => $og_test_recipient,) : (-mass_test => 0,)

            }
        ); 

And just append that %mailing hash, like this:

        $message_id = $mh->mass_send(
            {
                -msg              => {
                    %mailing,
                    'Reply-To' => 'somewhere
else@example
com',

                },
                -partial_sending  => $partial_sending, 
                -multi_list_send  => {
                                        -lists    => [@alternative_list], 
                                        -no_dupes => $multi_list_send_no_dupes, 
                                     },
                -also_send_to     => [@alternative_list],
            ($process =~ m/test/i) ? (-mass_test => 1, -test_recipient => $og_test_recipient,) : (-mass_test => 0,)

            }
        ); 

That'll change things for your Mass Mailing -> Send a Message screen

As an aside, adjacent to the Reply-To information in the config pm file ther is unsubscription the return path field Placing a value in here in place of the undef value results in the specified email address getting included

Yeah, don't do that Return-Paths usually shouldn't be set directly, but rather by the MTA itself

This problem is becoming quite an issue because, even though a line is included in the mailings which says "don't click on the reply to button on the email programme", a not insignificant number of people are ignoring this

That's the thing - why would you want to send a message out to a bunch of people, but not want them to communicate back? To me, that's almost akin to breaking the stuff in Dada Mail, since you think you'd do a better job with an outside system of your own Doing so adds a whole new set of problems, ones that the program is then blamed for

If there is an issue, that setting a default Reply-To header doesn't work, could you please add it to the issue tracker?

http://github
com/justingit/dada-mail/issues

I'll then look at it I never look at problems, unless they're in there I need some help, because I can't do everything here myself Please help Everyone: if there's problems: add them to the issues tracker

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