Specify another domain for smtp and elmah? - email

I got kinda a weird scenario. I am using google apps for my domain emails so I get chobo2#mydomain.com.
I am using this instead of the my shared hosting provides email server because this gives me alot of flexibility to switch to a new hosting site and not have to transfer all my emails when I switch over. I also like using it over the one my host provides(on average I get emails faster).
Now the only downside to all this is gmail has alot lower email limit(I think like 500 a day). Where as my hosting provider allows something like 1000 an hour.
So I use google apps for my emails that I want to look at and the hosting email servers for automated messages.
What leads me to this problem
<errorMail from="noreply#mydomain.com"
to="myGoogleApssEmail#mydomian.com"
subject="Failed"
async="true"
smtpPort="25"
smtpServer="mail.mydomain.com"
userName="noreply#mydomain.com"
password="password" />
So when an elmah error occurs it should send me an email.This email gets sent through my hosting email servers but it should go to my email address that I have with google(remember they both have the same end domain name - mydomain.com).
I never get the email and I think it is because it probably thinks that they are on the same servers. So instead of sending it to google it probably goes well it must be on the same server as this domain lets try to send it there.
Any ideas on how to fix this? Is it even possible?

It is not possible as MX records are meant to be per domain not per e-mail address.
So if mydomain.com is using Google MX servers all e-mails will be delivered to google in the first place. There you could create forwarding rules to your hosting provider but it does not make sense as it would exceed the limit, too.
What you could do is specifying subdomains - i.e. elmah.mydomain.com plus an MX pointing to your provider.

Related

What happens to Gmail emails after a hosting change?

I am hosting the email for one of my domains at Gmail. I then run an IMAP client on my local computer to read and send email. Totally standard.
I now want to move the hosting for that domain to another email provider, where I will again run an IMAP client to deal with the mail.
Question: What happens to all the messages that are currently on Gmail? I THINK that they will stay in place, and I'll be able to access them via gmail.com and/or a Gmail app. But maybe not? Maybe Gmail will somehow find out about the MX change and decide that it should delete them all, because Reasons. Or it can't find the messages on its own server because the MX has changed, and so won't let me see them. Or something. In any case, losing access to these old messages would be Very Bad.
So, which is it? Will the world behave the way that I'm 99% sure that it will, such that I'll still be able to go to gmail.com and read the old messages after the switch? Or do I need to move the old messages somewhere else before making the hosting switch? Thanks for helping with my paranoia!
Google doesn't care what domain you use to route emails towards your Gmail inbox. If you change your domain to use another email provider, you will still have your existing Gmail inbox, until you shut down your Gmail account. So any existing emails in your Gmail inbox will be left untouched.
The same goes for any other hosting provider.

Sending emails from vendor's multiple domains

We have custom cms that currently sits on a vendor's subdomain, such as cms.vendor.com. It sends email out as coming from user#vendor.com and it seems to be working fine (using Email Queuing + SwiftMailer)
Our vendor asked us to put in the functionality for his users to be able to select from a dropdown, 3-4 other emails address associated with them from other domains he owns. Basically we need to be able to send out emails from our server labeled as being sent from #hisdomains.com, multiple domains.
I am a web programmer and have no clue when it comes to relaying messages. How would I go about being able to send out emails from his other domains? Does he need to setup permissions on his mail servers, or do I need to get into his SMTP servers to send out?
What are some things I should look out for when it comes to SPAM and gmail trusting us?
EDIT:
Not sure if my original question was clear enough. Vendor owns three domains: mysite.com, myothersite.com, mythirdsite.com. He wants a user from our crm to be able to send emails he has on those domains. So my dedicated server will be trying to send an email out as user#mysite.com, user#myothersite.com, and user#mythirdsite.com in the FROM: header.
As long as your server is allowed to send on behalf of a domain your vendor owns, you should not have a problem; just change the From: header to something else when you send out the e-mail.
Stuff like SPF, Sender ID and DKIM have to be properly configured to allow your server to send on behalf of any domain.
See also: http://en.wikipedia.org/wiki/E-mail_authentication
Any domain where the mx record resolves to the same server will work. so user#any.domain will email the same user on the mx contingent server.
To answer your question - just make sure that the mx records in the DNS zone file for each domain name points to the same server as the domain you want to share emails on.
also dependent on server configuration (like shared or whatever) I'm assuming it's dedicated with a simple email server installed. I'm not sure on cPanel/shared servers. but possibly the same.

How can I test an email-sending script that will send out to over 1,000 users?

I have a PHP web app that is going to send out about 1,000 emails. I would love to test the performance beforehand. Is there any kind of service that provides dummy email addresses to send to, for this kind of testing? I can't find anything that's not just a general bulk-email service. The key here is I just want dummy addresses to send to.
If you have the ability to just purchase a domain name from a hosting service, I know at least 1&1 gives you like 2500 email addresses per domain so you could literally spam yourself to death and not worry about any other 3rd party. You can pick up a domain name for like
When you say "test the performance", do you mean you want to know about your deliverability rates, or how your emails look?
Deliverability Rates
This is entirely dependent on your SMTP server and the reputation of the IP that it will be sending from along with your domain's SPF records and the content of your email. To maximize this, I would recommend using a marketing email service such as MailChimp or MadMimi.
Appearance of Emails
You could always just send yourself a test email to see how it looks. An alternative is to use a service like PostageApp that has a built in template designer that has both an easy email preview function and a test send email function.
(Full Disclosure: I am the Product Manager of PostageApp.)
If you use "Post Hoc" you can send email to an unlimited number of email addresses. Post Hoc acts like an SMTP server, and receives the email messages that you are sending, but it does not forward them on anywhere. You do not need to set up any email inboxes ahead of time, so there is no problem if you have 1000 different unique email addresses. They do not need to be from a single domain -- you can use any email address you want. It stores the email messages received so that you can inspect them if necessary. You would run it locally so that there is no concern about network problems, and it is very low overhead since it does almost no processing of the email. This way, the performance measure will be mostly the sending side processing. Best of all, it is open source and freely available:
Find it on GitHub: GitHub for Post Hoc
Also see the blog post: PostHoc: Testing Apps that Send Email

Sending an email from one server to another using same domain name

Just rebuilt a companies website, updated their A records to point to it's new server location but kept their email function as was.
Sending from the server works fine, and they receive mail from elsewhere fine but now when trying to send forms as emails to their existing addresses they never arrive.
For example trying to send an email (more specifically a Drupal Webform) from domain.com from Server 1 to email#domain.com on Server 2.
I've tried adjusting the send address from Server 1 which doesn't change anything. I think their IT person said something about receiving email at an exchange (Microsoft?) but I'm not savy this area at all.
Any ideas about this? I guess something is stopping it before it gets delivered (no spam) and the domains are conflicting, had a Google about but it's one of those where I'm not quite sure how to phrase the question. Thanks
SOLVED! In my CPanel I just needed to change my MX Entry to Remote Mail
Server Exchanger

Can I have two mail server for different emails

I have a registered domain name where the emails are handled by windows live admin center having a single mx record for my domain. I also have access to modify the dns records any time.
We have around 20 email registered in windows live for my domain. for e.g. user1#example.com, user2#example.com etc.
Some users want to go in for google app accounts as they say there are lots of features in it, and therefore I think I need more than one mail server in my organization.
Is it possible that i can have some emails redirected to windows live and some to google apps, provided that I have access to change the dns and mx records?
So you want different users for the same domain to go to different mail servers?
You can't do this by manipulating the DNS records - the mail will be delivered to the server(s) defined by your MX record for the domain without any reference to the user name.
However, there's nothing stopping that mail server being an application that forwards mail onto several other servers based on the user name of the recipient...
This can't be done within the DNS - mail routing is done on the domain part only.
You'll need to arrange for all of the mail to arrive at one central place, and for it to be then forwarded-on depending on who it's for.
Do note that that isn't completely trivial, although any decent mail server should be able to do it. This is because in some cases (cc:, etc) that forwarding will need to result in two copies being forwarded, i.e. if there are multiple recipients and they're not all on the same service.