Link to home
Start Free TrialLog in
Avatar of gregholl
greghollFlag for Ecuador

asked on

Using group mail software in windows for email marketing - IP problems

THE SET UP

Rather than using services such as constant contact, we have set up our own mail marketing solution. I have a static IP address and I also have this white listed with service called return Path ( also known at sender score certified )

THE PROBLEM

This has been working for us very nicely, With 95% email deliverability (sending 75,000 to 100,000 emails per month). These are sent on port 25 with a computer software called "group mail" by infacta. It works very nicely, and I am not looking for suggestions on changing my current set up.

We recently changed infrastructure and I am needing little bit of assistance. In our last Mailout of 70,000 marketing emails the return path service didn't register one single email as having been sent. (They use the IP address, that is our static IP, to monitor this).

Also, the various feedback loops (FBL) that we are subscribe to such as with Hotmail and Yahoo did not register any complaints from any users, which is also odd.

When I do a "what is my IP?" query on Google, they give the following response:
Your public IP address is 186.101.132.98

This is indeed my static IP.

I think that the problem is that: my PC which is sending the emails is behind a router (namely, Apple Time machine). Does that change the IP address which the various services are seeing as having sent the emails?

QUESTION:

Would my computer is being behind router make it have a different IP address for the purposes of the various services seeing who is sending the emails? If so, is my solution simply to directly connect the computer to the modem and not use the router when I am doing the mail out? I think that would work, however I wanted to get professional opinion before attempting another Mailout.

That me know your opinions.

Thank you so much for your help!

Greg
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

We recently changed infrastructure and I am needing little bit of assistance. In our last Mailout of 70,000 marketing emails the return path service didn't register one single email as having been sent. (They use the IP address, that is our static IP, to monitor this).

What did you change? Normally one white-lists specific ip addresses to send mail to prevent being an open relay. These are normally held in your spf records
http://en.wikipedia.org/wiki/Sender_Policy_Framework#FAIL_and_forwarding
Avatar of gregholl

ASKER

I am using a Windows computer at home using software called groupmail.

I used to use a computer hosted on a VPN.
That will do it.. most isp's block smtp ports to prevent the user from becoming a spambot. try using telnet to your mail provider and see if you can get through.
I have a business service with my ISP. I am not being blocked. Yesterday I sent 60,000 emails. There is no problem here.
Please re-read my original question. It has nothing to do with the email "getting through" or not. They are "Going through". BUT. It is not "registering" with the correct IP address. Pardon me if I don't know the tech terms. I hope you understand what I mean.
if you look through the header is it showing YOUR Internet IP Address?

What do you mean registering with the correct IP address, please elaborate.

is the "return path service" configured to use the business IP address or YOUR WAN ip address?
I'll check the email header. good idea. I'll check and get back to you

 Return Path is configured to use the business IP address.

Maybe the WAN IP address is showing. that's probably the correct term.  If so, how do I correct this?
You can't (at least under the EE TOS) you need to configure the 'Return Path' software to use your WAN address
1: I don't understand "EE TOS"
2: It worked perfectly fine with my Virtual Private server. What would be the difference have the windows desktop computer at my house or on a remote location?
spoofing an IP address which is done by many spammers is something you'd have to research yourself as it is not allowed by Experts-Exchange Terms of Service.

When you vpn'd into a corporate network the mail was sent via their internet and not by yours
I'm not being understood

I'm not spoofing anything.

I'm not spamming. We send legitimate opt-in marketing. I we not be a certified sender on Return Path if I were.

before I had a DIFFERENT static IP, that of the VPS.

this worked fine for me.

One step at a time:

BEFORE

1. I logged in to VPS.
2. VPS had a dedicated static IP.
3. this IP was registered as my IP with Return Path
4. rDNS entry all set up to point back to my website
5. FBLs set up with that IP to the major email services like Yahoo, Hotmail.
6. I send 60,000 to 100,000 emails. They all go through fine.
7. I get reports back from Return Path with regards to how many emails are being sent via my static IP, and how many complaints are being reported by yahoo, hotmail, etc.
8. Via the FBLs, Hotmail and others also email me directly whenever a subscriber complains (i.e. hits "this is spam") so that I can remove the person from the mailing list.

1. I logged in to VPS.
2. VPS had a dedicated static IP.
3. this IP was registered as my IP with Return Path
4. rDNS entry all set up to point back to my website
5. FBLs set up with that IP to the major email services like Yahoo, Hotmail.
6. I send 60,000 to 100,000 emails. They all go through fine.
7. I get reports back from Return Path with regards to how many emails are being sent via my static IP, and how many complaints are being reported by yahoo, hotmail, etc.
8. Via the FBLs, Hotmail and others also email me directly whenever a subscriber complains (i.e. hits "this is spam") so that I can remove the person from the mailing list.

AFTER:

Now I've cancelled the VPS service, and bought a PC to dedicate to this work

1. ISP is granting access to port for sending emails.
2. I have a dedicated static IP.
3. this IP was now registered as my new IP with Return Path
4. rDNS entry all set up to point back to my website with my NEW IP
5. FBLs set up with the NEW IP to the major email services like Yahoo, Hotmail.
6. I send 60,000 to 100,000 emails. They all go through fine.
7. I get reports back from Return Path with regards to how many emails are being sent via my static IP. THE REPORTS SHOW ZERO EMAILS BEING SENT.
8. I get no reports back from the FBLs.

Does all that make sense? The problem is in the second scenario, numbers 7 and 8
I didn't say that you were a spammer.  You did NOT say that you changed everything to point to your new ip address.

You originally stated:
Return Path is configured to use the business IP address.
Maybe the WAN IP address is showing. that's probably the correct term.  If so, how do I correct this?


To show the email originating from your business IP address would require spoofing

You NOW say that return path is configured to use your WAN address.. Which is correct?

send an email to yourself and check its headers and verify that the information matches what you have configured elsewhere.
DNS takes time to propagate (24-48 hours depending upon your TTL)
Sorry I thought WAN had something to do with the local network in my home.  I see know that the "WAN" refers to the VPS?

Anyway, indeed. I erred if that is the case.

I will do some testing later and let you know. thanks
And also , we need to sort out the confusion about "business IP address"

My business is IN MY HOME. The Internet Service IN MY HOME is the "business IP address".

It is  static IP address
ASKER CERTIFIED SOLUTION
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thanks. travelling at the moment. I'll be home tomorrow evening. and I will try the suggestions
Thanks. it turns out There was a problem. The ISP had changed hardware for me, but they neglected to update something. Therefore, it turns out that all this time I have been sending out emails with 186.xxx.xxx.98 instead of 186.xxx.xxx.117.

All fixed now