HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   HOWTO-Related Questions (http://www.howtoforge.com/forums/forumdisplay.php?f=2)
-   -   not able to send and recieve emails (http://www.howtoforge.com/forums/showthread.php?t=37950)

ayad 4th August 2009 10:42

not able to send and recieve emails
 
hi

I have started to work in an email marketing company and i am facing with an issue.
One of our clients is not able to send and receive emails. Actually we are hosting the clients sub domain and he is not able to send and receive emails from the domain that is hosting it. Rest apart the client is able to send and receive emails normally accept to the mail hosting mail server.
I have listed the error :

This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: abc@xyz.co.nz No Such User Here ------ This is a copy of the message, including all the headers. ------ ------ The body of the message is 384958 characters long; only the first ------ 106496 or so are included here. Return-path: Received: from pmlive by host2.example.co.nz with local (Exim 4.69) (envelope-from ) id


I have not provided the actually web adress.
host2.example.co.nz is the server that is hosting the subdomain xyz.co.nz.
plz help



regards
Ayad

falko 5th August 2009 13:06

Did you create an email account for abc@xyz.co.nz on the server?
Does the MX record for xyz.co.nz point to the correct server?

ayad 5th August 2009 19:47

thanks falko

ya the account has already been created, we have also confirmed from the ISP that the newsletter is
reaching to them (the ISP created a test account and we send a test newsletter n they verified that
they have recieved it).Apart from MX record can there be any other reason.

falko 6th August 2009 15:47

If the MX record is correct, then there must be something wrong with the way you set up the mail account because it says "abc@xyz.co.nz No Such User Here"...

ayad 14th August 2009 00:50

we have found that there is some problem with the MX records.
Thnks for help and suggestion

ayad 14th August 2009 01:28

Hi there

Does any one have an idea how SPF (sender policy framework) works,
do we only need to authenticate the IP address from which we are sending emails or there is any thing else involved.
In our company we send emails from on behalf of our clients to their respective clients, the email address is used of the client itself and not of our company.
To implement the SPF do we need to authenticate only the IP address from which we are sending the emails or their is something else involved.

thanks

falko 14th August 2009 12:59

The SPF record should involve all servers that send email for that domain. You can use this SPF wizard: http://old.openspf.org/wizard.html?mydomain=&x=10&y=8

ayad 14th August 2009 13:04

thanx falko

does SPF authentication depend upon the IP adress

falko 15th August 2009 13:57

You can include your server's IP in the SPF record, but it's not necessary if it's already covered by the A or MX record.

ayad 24th August 2009 04:52

thanks for the reply,

Does that mean i have to specify my domain and subdomain adress only.
Also as informed earlier our company is in email marketing business, when we send the email from our server (example.com), in the from option we specify the name of our clients domain rather than ours.
In the sence that although we sent the email from our end, the receiving person sees the clients name in the "from option" not our domain name (example.com).

In this case do we need to define the SPF for each of our clients or just for the domain from which we are sending because in one of the SPF forums i read that SPF also performs the 1st authentiction using "from name".

Plz let me know


All times are GMT +2. The time now is 11:31.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.