bounce.cgi and signup-list1.cgi signup-list2.cgi etc clarity

[davemarcotte]

Hi Dean,
Brand spankin new user here. I'm liking the simplicity of the interface and ease of use very much so far. So I hope you'll forgive the many questions that follow.

But I do want to get your input on two aspects of your documentation that are leaving be a bit in the dark still:

1. In the help file I read about the 4 steps required to setup the bounce.cgi and additional list files. (I believe I need to manually create an additional signup-listX.cgi file every time I create a new list? (if using bounce.cgi) Is this correct? Also, what's the benefit of these individual signup.cgi files? Do they somehow redirect the bounces back to specific lists or something? Some more clarity in the docs would be wonderful.

Anyway, so I basically understand that I've got to do the following:
Quote from Helpfile:
1. Modify each script to contain your ListMail URL. In the case of signup scripts, set the $list variable to the list you want to subscribe to.
2. Upload your scripts to your, usually pre-created, cgi-bin folder on your host.
3. Determine your server's method and set up "email aliases" for each of your desired address to script redirections.
4. Test if it worked.
END Quote

Okay, so the first sentence of #1 is clear and easy. But the second sentence is not so clear. So this means that I name each consecutive signup-listX.cgi both internally (edit script) and externally (filename) with a consecutive number for however many lists I've got? If correct, that's not too hard. (But I still am not sure what benefit I get for all this tweaking to each file.)

#2 is easy and done.

#3 Not very clear what I need to do from the sentence, but after reading around the forum a bit it seems you just want me to create a redirect from within cpanel for my bounce@domainname.com address back to the URL location of the bounce.cgi location, correct? Easy enough. But I'm confused on why you're mentioning this in the plural? Don't I need just a single "bounce@mysite.com" address for all bounces? Or are you meaning that I can use ListMail Pro for unlimited domains and therefore I have to set up a bounce@xxxxx.com for each domain? If so, THAT'S COOL! I was hoping for unlimited domain use from a single installation. (Which is one of the main reasons I bought it.)  

And then #4 Test if it worked. ... What am I looking for to validate both pass and fail conditions? Is there a specific return syntax/wording I'll get back in a returned email? And the TESTBOUNCE seems to force a bounce, correct? So it'll bounce from an address that would normally not bounce, correct?

Okay, I believe I have it all straight. I thought I'd type this up in case anyone else was needing their bearings set straight like me on these fine details.

And the last thing. In the (Article A) portion of script below, I have a few more quesitons.

If I am creating a separate signup-listX.cgi for each list, shouldn't I just leave each of these instances set to "single list"? I assume the multiple list option is if I wanted to have multiple lists bounce to a single bounce address, and matching signup-listX.cgi file? Why would I ever want something like that? For list segmentation, but a matching bounce address? Not sure I understand this part or the benefit(s).

And why are they listed non sequentially? 1,3,2? What's going on here that would be of benefit?

And I have no clue how I'd use or why I'd benefit from the custom fields, and parsing the subject line into a custom field options.... Could you give me some examples of why this would ever be necessary?

I also read that the signup-listX.cgi files are optional? Only the bounce.cgi is mandatory? Why is this and what might I be losing by simplifying this way.

Okay, I've bet you're overwhelmed with too many questions, so I'd better sign off and promise you that I got all my first day installation questions out of the way all at once.

Anyway, I hope this helps others with the same questions. And if you respond to all of this in detail I'll be shocked and impressed!

Take care,
Dave

PS, can't the signup-listx.cgi file configurations be configured from a form, or auto configured instead?

Thanks again.


Article A:

# SET the variable $list to one of the following:

# single list
$list = '1';

# multiple lists
# $list = '1,3,2';

# parse subject into a custom field? (uncomment to enable)
# $parse_subj = 1;

# custom field for subject line data, 'user1' thru 'user10'
$parse_subj_field = 'user1';

# For multiple lists, use commas.  Each list's welcome / confirmation
# setting and email will be taken into account.

[DW]

Hi Dave,

Thanks for your kind comments.

1. In the help file I read about the 4 steps required to setup the bounce.cgi and additional list files. (I believe I need to manually create an additional signup-listX.cgi file every time I create a new list? (if using bounce.cgi) Is this correct? Also, what's the benefit of these individual signup.cgi files? Do they somehow redirect the bounces back to specific lists or something? Some more clarity in the docs would be wonderful.

The signup-listX.cgi scripts are completely optional whether you use bounce.cgi or not.  Most users do not use signup-by-email, but rather use the "List Settings" -> "Signup Code" page to generate a simple signup form to accept subscribers via their web site.

A new signup-listX.cgi file is needed for each list, or set of lists, you want the user subscribed to.  Specifying the list in each script allows us to provide subscription by having the user simply send a blank email to a configured address.  More than one address can point to one script, but one script cannot point to more than one list or set of lists. (If that makes sense!)

I'm confused on why you're mentioning this in the plural? Don't I need just a single "bounce@mysite.com" address for all bounces? Or are you meaning that I can use ListMail Pro for unlimited domains and therefore I have to set up a bounce@xxxxx.com for each domain? If so, THAT'S COOL!

You only need one bounce script configured per installation. While you can set the list "Send From Email" to anything you want you cannot have more than one bounce address on a single installation.  Therefore if you will be sending "From" multiple domains I recommend setting up ListMail on a more 'generic' domain name that can be used with all of your businesses.  This is because links in your messages and display in the "Address bar" of the browser when displaying Custom HTML will display the ListMail installation domain.  I do currently allow you to install ListMail on more than one of your own web sites if you prefer that method.

And then #4 Test if it worked. ... What am I looking for to validate both pass and fail conditions? Is there a specific return syntax/wording I'll get back in a returned email? And the TESTBOUNCE seems to force a bounce, correct? So it'll bounce from an address that would normally not bounce, correct?

Cilcking "Test Mail Settings" is the same as sending a manual email to your "Bounce to address" with "TESTBOUNCE" in the subject.  The latter has the advantage of returning the bounce from the server in case of a delivery problem, which can help with troubleshooting.  cPanel usually works as described in the help pages here.  The most common problem is needing to use an alternative to wget.

If I am creating a separate signup-listX.cgi for each list, shouldn't I just leave each of these instances set to "single list"? I assume the multiple list option is if I wanted to have multiple lists bounce to a single bounce address, and matching signup-listX.cgi file? Why would I ever want something like that? For list segmentation, but a matching bounce address? Not sure I understand this part or the benefit(s).

I'm not sure if I've made this clear but the bounce.cgi script is completely independent of the signup scripts, should you choose to use them.  The bounce process simply works based on email address across all lists.  Each list does not have a separate bounce process.

And why are they listed non sequentially? 1,3,2? What's going on here that would be of benefit?

The sequence is not important.  This is just an example of signup-by-email to multiple lists.

And I have no clue how I'd use or why I'd benefit from the custom fields, and parsing the subject line into a custom field options.... Could you give me some examples of why this would ever be necessary?

The "User Selection" feature can send to parts of your list based on searching user data fields, such as custom fields.  You could have users from, say, the UK enter "signup-UK" in the subject line, and users from the US enter "signup-US" in the subject line and have that recorded in ListMail, both on the same list.  Later on you can then use the "User Selection" feature to send to users in the UK and US separately.

If any of this is still unclear please let me know and I will attempt to clarify further!

Regards