Mike, DW,
Thanks for the great tips..
The URL of your LMP is subject to the same standards as any other URL... therefore it could be causing problems. You should check your IP and URL for black listings.
Good point, I'll do that after I move it all over to the new Dedicated server, as soon as I have the new DNS up running properly, actually this isn't too bad, I'm almost there already, and hope to be done before the days over.
On another note... the sawmill might help show initial delivery, but even that in NO WAY guarantees the person actually saw the email or actually even got it. Many mail systems will accept the mail, which to your system seems like it was delivered. But then they process it and run it through checks, blacklists, etc and if it fails just discard it...
Ok, got it, on this - I know I've blasted anyone wanting to check 'delivery rates' using image files in the email, but I wonder if it might be worth it at this point, as it seems sawmill will only show that the email was accepted, and I still won't know if it ever got to anyone.
If not, why do you need to use procmailrc?) If you use signup-by-email I still recommend contacting your host about the possibility of them manually setting up email forwarding to CGI.
Yes, I use signup scripts from the forwarded emails, this works great for me. Regarding setting up the manual forwarding to CGI - I'll consider it, but now that I'm on dedicated they've already told me I can use "Courier Dot Mail" for email forwarding to scripts - supposedly I may even be able to drop my .procmailrc file into it, but I haven't tested that yet and don't know where to find it, I'll be contacting their tech people heavily the rest of the day until I'm all setup
.
Quote:
I want to remove the 'throttling' code if I can and see if I get more clicks.
I think throttling can only help delivery, so if all the messages are getting to the server it should only be a few days until the majority of clicks come in. Removing throttling IMHO should not improve things.
No, I've shown previously that throttling even helps get more clicks, because when you're not throttling the system is so busy handling the bounced mail and sending that the clicks increased - this was on shared server, but if you feel it won't do a thing on dedicated, I'll just try to adjust the throttling to get closer to 150K/day which should be no problem, actually I'm getting that on shared server right now, the last broadcast email I sent was running at 2.2/second or about 8,000/hour which is roughly 160,000/day, but I don't think it could handle it continuous because at several points it would just pause for several minutes or more, either that or I hit a limit (on the shared server).
I'll leave the throttling in - but I thought one of the points of running on dedicated is that I could remove the throttling and then get 20,000-30,000/hour out of LMP?
Regarding DNSreport.com that looks amazing, especially this:
This site will provide you with a DNS report for your domain (56 tests are run per DNSreport). A very large percentage of domains have DNS problems; this site will help you find those problems and fix them. Also, the “Mail Test” tool will help find mail delivery problems for your domain.
I had no idea anything was available like that, so I'll put that in place too, but first have to get DNS setup, running properly on the dedicated server... and thanks for the instructions on the Reverse IP, I know that's a problem from previous AOL whitelisting attempts, they wouldn't whitelist me previously because the setup on the shared mail server was not correct.
In my experience AOL will not whitelist you unless you are the sole-sender from your server.
They told me I was whitelisted - using the shared server at my host, that was back in November, 2005, here's the reply email I got from AOL:
Your Whitelist request, with the
confirmation code xxxxxxxxxxx-425774, has been approved.
Anyway, I'm hoping (praying) that this move and dedicated IP/server are going to solve some of the mail delivery and acceptance problems I've had, especially in the last 6-8 months, but even then, the shared server worked fine, so I'm not positive this is going to affect things, I'm a little worried that my list might just be totally unresponsive at this point...
If you think of anything else let me know - but I'm sure I'll be back posting what I have found, in the next few days...