Can't Send Email

  • Thread starter Thread starter JP
  • Start date Start date
J

JP

I can receive email, but can't send using Windows Mail in Vista.

I get the following after a test message:

"The message could not be sent. The authentication setting might not be
correct for your outgoing e-mail [SMTP] server. For help solving this
problem, go to Help, search for "Troubleshoot Windows Mail", and read the
"I'm having problems sending e-mail" section. If you need help determining
the proper server settings, please contact your e-mail service provider.

The rejected e-mail address was '(e-mail address removed)'. Subject 'Test',
Account: 'incoming.delhitel.net', Server: 'outgoing.delhitel.net', Protocol:
SMTP, Server Response: '550 5.7.1 <[email protected]>... Relaying denied',
Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79"

Any suggestions?

JP
 
Hi,

Seems to me a mail server configuration problem. Add the host you are
sending from to the list of host the mail-server will relay for. (normally a
good mail server wouldn't relay message at all).

Regards, Ron AF Greve

http://informationsuperhighway.eu
 
JP said:
I can receive email, but can't send using Windows Mail in Vista.

I get the following after a test message:

"The message could not be sent. The authentication setting might not be
correct for your outgoing e-mail [SMTP] server. For help solving this
problem, go to Help, search for "Troubleshoot Windows Mail", and read the
"I'm having problems sending e-mail" section. If you need help determining
the proper server settings, please contact your e-mail service provider.

The rejected e-mail address was '(e-mail address removed)'. Subject 'Test',
Account: 'incoming.delhitel.net', Server: 'outgoing.delhitel.net', Protocol:
SMTP, Server Response: '550 5.7.1 <[email protected]>... Relaying denied',
Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79"

Any suggestions?

JP
Click to expand...

You need to authenticate to the server (i.e., provide the login
credentials to it rather than try to reuse those that were given for the
prior POP session). Go into your e-mail client and configure the e-mail
account defined therein to authenticate to the SMTP (outbound) mail
host.
 
I can receive email, but can't send using Windows Mail in Vista.

I get the following after a test message:

"The message could not be sent. The authentication setting might not be
correct for your outgoing e-mail [SMTP] server. For help solving this
problem, go to Help, search for "Troubleshoot Windows Mail", and read the
"I'm having problems sending e-mail" section. If you need help determining
the proper server settings, please contact your e-mail service provider.

The rejected e-mail address was '(e-mail address removed)'. Subject 'Test',
Account: 'incoming.delhitel.net', Server: 'outgoing.delhitel.net', Protocol:
SMTP, Server Response: '550 5.7.1 <[email protected]>... Relaying denied',
Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79"

Any suggestions?
Click to expand...
Yes. Your server settings for Gmail are wrong. It needs to be set to
use port 465 and have SSL enabled.
 
Conor said:
I can receive email, but can't send using Windows Mail in Vista.

I get the following after a test message:

"The message could not be sent. The authentication setting might not be
correct for your outgoing e-mail [SMTP] server. For help solving this
problem, go to Help, search for "Troubleshoot Windows Mail", and read the
"I'm having problems sending e-mail" section. If you need help determining
the proper server settings, please contact your e-mail service provider.

The rejected e-mail address was '(e-mail address removed)'. Subject 'Test',
Account: 'incoming.delhitel.net', Server: 'outgoing.delhitel.net', Protocol:
SMTP, Server Response: '550 5.7.1 <[email protected]>... Relaying denied',
Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79"

Any suggestions?
Click to expand...
Yes. Your server settings for Gmail are wrong. It needs to be set to
use port 465 and have SSL enabled.
Click to expand...

The OP isn't using Gmail to send his outbound e-mails (in this case).
You can specify whatever you want in the From header since that is added
by your e-mail client. It doesn't have to be an e-mail address at
whomever you are using for an SMTP mail host. The OP wants recipients
to send e-mails to him using his Gmail service, but he wants to send his
e-mails using delhitel.net.

I've used Gmail for awhile so I don't remember if Gmail spammifies all
outbound e-mails sent using a freebie Gmail account. That is, some free
e-mail providers attach a tagline onto all e-mails sent out using their
free service. They add their spam to your e-mails that your recipients
get afflicted having to see. I remember Yahoo Mail used to add a spam
tagline to e-mails sent out using their webmail interface for free
accounts. Awhile back, I used YahooPOPs to retrieve my e-mails from my
free Yahoo Mail account. I could have also used YahooPOPs to send my
e-mails out through the Yahoo Mail account except they added their
tagline. This makes e-mails look spammy and non-professional. So I
used my own ISP's SMTP mail host to send my outbound e-mails but the
E-mail Name field (which becomes the From header in the e-mail) had my
Yahoo Mail address. So I received from a free Yahoo Mail account but I
sent using my ISP's SMTP mail host instead of Yahoo's webmail service.
Recipients would still send to my Yahoo Mail account because that's
where I told them was my account.
 
Mike said:
The OP is attempting to use the delhitel servers to send an email to a
gmail *recipient* (not a bogus From - MAIL FROM). You are correct that he
isn't trying to use the gmail servers and Conor is mistaken in thinking he
is.
Click to expand...

Oops, got misled by Conor saying the OP was using Gmail. You're right.
 
Mike said:
Also; if you use gmail's smtp server and attempt to put/use a bogus From,
then gmail replaces that From with the address of the gmail account which
is being used to access the gmail smtp.
Click to expand...

Corporations do this in Exchange, too. Too bad that isn't standard
practice.
 
Back
Top