Forum Moderators: open
The client that I have a problem with is name@cox.com (I have a few customers that use cox.com) the invoices are emailed to them but they are not getting them. I get no error message on my end. No error in any log file. I don’t know where the problem is…
string body = "<HTML><BODY>";
body += db.UShowLogox(type);
body += db.UInvoiceSummary(cust_ref, inv_str);
body += "</HTML></BODY>";
MailMessage msg = new MailMessage();
msg.BodyFormat = MailFormat.Html;
msg.From = "customerservice@#*$!#*$!x.com";
//msg.To = "faxadmin@xxxxxxx.com";
msg.To = email_name;
//msg.Bcc = "info@yyyy.net";
msg.Subject = "Your invoice is ready";
msg.Body = body;
//SmtpMail.SmtpServer = "mail.yyyy.net"; // DNS server
//SmtpMail.SmtpServer = "mmm.mmm.mmm.mmm"; // DNS server
SmtpMail.Send(msg);
I tried it with assigning SmtpServer and without but still it doesn’t work. Mind you that since I upgraded from 2000 server to 2003 server this future doesn’t work for this customer.
Maybe I am lacking a piece of code or I have to setup something on my 2003 server or
Maybe I need a software component to do this. Can you experts find out please?
You say it worked on Server 2000, but not on 2003. Is the new server on the same ip? If you're on a different ip, it might be blacklisted or filtered by cox. I'd try assigning a different smtp server on a different ip to see what happens.
One reason may be a reverse lookup. ISPs are checking for validity of
the emails by doing a reverse lookup. Maybe that's where it fails. Since
I am using internal IP addresses (192.168.1.10)
Other reason maybe the SMTP server. Since local SMTP server is (zdsrv2
-- name of my DNS server) and the IP address is internal (192.168.1.10),
then it can't resolve the name or/and the IP address.
On windows 2000 server I didn't have this problem (so that's what they
tell me anyway) I am not sure if this is a coincidence or windows 2003
server is diff than windows 2000 server or the ISPs just changed this.
Or maybe since I was using public IP addresses before I wasn't running
into this problem.
The solution may be an asp.net SMTP component (but I am not sure if this
will solve the problem either)
Isn't it something like pop.east.cox.com for POP3, and smtp.east.cox.com?
(Server names are for east coast locations. It will vary depending on your location)
Sorry, but you've got me stumped.
Here us just side note. I've had some trouble with CDO in jsp before. Had a site that wouldn't send mail anywhere. I just built one file in VBScript to send the mail with CDO, and called it from jsp pages. Everything then worked fine.
we should fix the problem with the SMTP server...we should be able to easily add these names (cox.com, ...) to our SMTP server which is our
DNS server as well.
I feel like either I am not adding the right name or adding it in the wrong place. That's why I think that
we need the component to send emails through.
So you are saying that I should add the domain name (cox.com or does it have to be something else like mail.cox.com?) in the remote domain name and then use the same name in my asp code?
By the way I have already done this:(
also, you need to check your remote server properties
[microsoft.com...]
1 - Reverse lookup
2 - Trace the mail to its root to check if it is not a spam
I think the problem is that I am using internal IP addresses. Now, what I want you to do is:
1 - How to setup the DNS or IIS to pass reverse lookups
2 - Check Cox.com or any documentation available to us regarding Cox.comto fulfill their requirements.
3 - Check if Internal IP addresses are the problem when they do a reverse lookup.
Thank you
