I have an account with namecheap, let's say domain.com.

I'm trying to set up info@domain.com that forwards to two addresses, say info@earthlink.net and info@yahoo.com, and it doesn't seem to work, or more likely, I don't know how to.

I tried to have one entry and have the forward-to address as "info@yahoo.com, info@earthlink.net" and I get an error.

If I have two entries, I can save ok, but the email only goes to one address, the earthlink one, and not yahoo. I'm guessing it's because earthlink is higher in the sort order.

I emailed namecheap over the weekend but haven't gotten any reply, so I'm wondering if anyone here knows how to do this, or maybe this is not possible (which will be pretty silly, imo). :)

create 2 aliases called info@ and point them to 2 different email addresses.

should work just fine i tried that at enom and works, and i think namecheap uses enom features todo so

Originally posted by Bashar
create 2 aliases called info@ and point them to 2 different email addresses.

should work just fine i tried that at enom and works, and i think namecheap uses enom features todo so

bashar quoted it correctly. They are using enom's e,ail forwarding so what bashar suggested should work nicely

I just tried it again, and it seems to work this time, even though the earthlink one was received almost immediately and the yahoo one the next morning. But yeah, I didn't get the fowrarding error message I got the last time I tried.

Thanks guys! :)

next morning! wow what a delay :D

That delay would almost assuredly be at Yahoo's end of the path.

If the problem is on Yahoo's end, how come if I send an email directly to my Yahoo mail, it's received almost instanteneously?

Good question - but if the forwarding hit one immediately, there's no reason the other wouldn't have gone out at the same time.

Originally posted by cambler
Good question - but if the forwarding hit one immediately, there's no reason the other wouldn't have gone out at the same time.
Oh ... there are A LOT of reasons. E-mail messages very often travel a looong way before getting to their destinations. So ANY one of those nodes could be the suspect.

I was just pointing out that if one went out in a timely manner, it was highly unlikely that eNom's forwarding system was holding on to the other one.

EMail messages very often do NOT travel a long way before getting to their destination. Most often, once it hits the forwarding server, it's a single SMTP connection to the destination cluster. Sure, they might move it to another server, but, again, that was my point. If the forwarding server handed it off to the main Yahoo SMTP server, it's quite possible that Yahoo then sat on it for a while before delivering it.

No way to tell, really, unless he can drag up the headers and we can take a look at the dates and times (and decide that we trust them, of course).

I looked at the headers, and everything is the same until the last end:

Earthlink:
Received: from eforward5.name-services.com ([212.118.243.116])
by robin (EarthLink SMTP Server) with ESMTP id 1bC9QI2Gm3NZFjX0 for <domain@earthlink.net>; Sun, 20 Jun 2004 14:27:36 -0700 (PDT)

Yahoo:
Received: from 212.118.243.116 (EHLO eforward5.name-services.com) (212.118.243.116) by mta148.mail.dcn.yahoo.com with SMTP; Sun, 20 Jun 2004 15:00:34 -0700

As you can see, they're only about 33 minutes apart. But the fact that I received the Yahoo email the next morning confirms that the email sat for a long time at Yahoo before I actually see it in my inbox.

For what it's worth :).

Thanks for all the responses!