This special address only appears in the headers of the message and is not normally seen by the subscriber. By default, it will be bounce@yourdomain.com. This address can be set up either as a mailbox, for use with the mailbox method of bounce processing, or as a forwarder to bounce.cgi for on-the-fly processing.
Dean
Thanks for the prompt reply and kind feedback. Flattery will get you everywhere :-)
I had been looking at the Return Path aka envelope sender on the confirmation message and welcome message, and they do not have the bounce address. I notice later on that you handle those differently than sending out a scheduled follow up.
I've gone ahead and completed the setup of bounce handling via cgi, and I will test it later on today.
2) I'm also having trouble wrapping my head around custom
user fields. I want to ask them what their biggest problem
is. So I can get that in the signup form ok. Now where
does it go when they type an answer in.
I'm guessing it does not go into the user database, and the
only way I can see it is by having an email forwarded to me
?
To "enable" a custom field, give it a short description in List Settings -> Custom Fields. Once enabled, you can view the user's data on the "Edit" page for your users on that list.
On your form, the variable user1 corresponds to Custom Field #1 for your list.
Ok, I've got it now. I'm glad to see that custom field data being stored in your database.
I do see that the email address is required and handled by
LM. Do I have access to the error message so I can
customize it ?
Yes. You can customize the error messages under
List Settings ->
Errors.
Thank you.
I set up a New Errors array, and tweaked a couple of them. That works.
However the error page still says
There were errors with your for your copy of the Special Report.
The error messages are as follows:
You didn't enter your first name. Please go back and try again.
Please press the back button on your browser and re-enter your information.
I'm not sure if I edited the first and last lines someplace else, or if that is boilerplate.
For example, the phrase with your in the first line looks like it's trying to drop in a variable, but not succeeding.
So if I can edit that thru your interface, please clarify. Otherwise, it's good enough for my purposes.
I had this working via password authentication on the
testing the other day, but when I look at my list
confirmations and followups, the emails are going thru their
server.
Are they intercepting my Port 25 calls, or do I need to set
up something else in the configuration ?
Welcome, confirmation, and notifications all use internal PHP mail() for sending. This prevents too many connections to SMTP in the event of a ton of signups at once. Followups should be sent with SMTP, if enabled. It is highly recommended that, unless ListMail is actually installed on your home computer (not easy and probably against your ISP's policies), you use your commercial web host for sending your email.
Ok, I understand now. I'm in the unique position of having some mail servers that are not on any RBL's, and I'm my own ISP, and I was wanting to send all email thru my servers. I'm sure the hosting companies do the best job they can, but when you have lots of people sharing the same IP address, it's going to be blacklisted some of the time.
So if you are collecting distant future wishes, I'd like to see the SMTP server option be applied to all emails.
6) Can I get Apache ENV variables like
"REMOTE_HOST,HTTP_USER_AGENT" into the signup email or some
place that I could reference it if a problem arose and
somebody was spoofing an email address ?
The REMOTE_HOST value is stored as the user's IP address in ListMail. The user agent is not currently tracked, but could be, possibly by utilizing ListMail's included signup-xtra.php (see Customizations forum)
Yes, I see that now in the headers of your email, and also the User Details, which I had not paid much attention to.
>I am pleased to answer your questions! Please let me know if I can be >of further assistance.
Thanks again, ane more questions will be on the way :-)
mark