🚀 go-pugleaf

In article 
<dck-0E31D0.06063914072004@nntp.bloor.is.net.cable.rogers.com>,
 David C King <dck@myprivacy.ca> wrote:

>The error I'm getting reads:
>
> Can't send to "<name@domain.com>"; SMTP server says "550 5.1.2 
> <name@domain.com> ... Unsupported mail destination".
> [...]
> is the above error msg coming from the rogers.com SMTP server or is it 
> coming from Eudora

You've already answered both your questions:

- the whole error message you quoted is obviously coming from Eudora, 
since that's what presented it on your screen for the pleasure of your 
reading.

- the actual transaction error that Eudora is telling you about -- "550 
5.1.2 <name@domain.com> ... Unsupported mail destination" -- is coming 
from the Rogers SMTP server you're trying to send through (note the 
"SMTP server says").

Based on a googling for "5.1.2 unsupported mail destination" and the 
subject of the first result, my guess is that Rogers is running postfix 
and will not allow relaying unless you are using authenticated SMTP.

I'm not familiar with Rogers policies these days, but a couple of things 
to check:  are you sending the mail via your Rogers connection (vs. at a 
friend's or someplace else)?  are you using plain SMTP or authenticated?  
are you able to send to another @rogers.com address (i.e. is it only 
non-rogers.com addresses which fail)?

-ben

David C King <dck@myprivacy.ca> muttered darkly in news:dck-
0E31D0.06063914072004@nntp.bloor.is.net.cable.rogers.com:


> is the above error msg coming from the rogers.com SMTP server or is it 
> coming from Eudora (I set up an account using Outlook Express 5.0.2 for 
> the Mac and I was able to send outgoing messages)
> 
> I'm using OS9.1 and Eudora 6.
> 



http://www.eudora.com/techsupport/kb/1592hq.html



-- 
TeGGeR�

How to find anything on the Internet:
www.google.com

or in Usenet Groups:
www.groups.google.com

Google is your friend. Learn how to use it.

David C King <dck@myprivacy.ca> wrote in news:dck-0E31D0.06063914072004
@nntp.bloor.is.net.cable.rogers.com:

> Can't send to "<name@domain.com>"; SMTP server says "550 5.1.2 
> <name@domain.com> ... Unsupported mail destination".

Seems like Eudora's SMTP Auth is broken... because I have a similar problem 
with my hosting company as well (alterhosting).

-- 
Lucas Tam (REMOVEnntp@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

In article <ben-A1552D.11294814072004@ip198.istop.com>,
 Ben Kennedy <ben@zygoat.caSPAMLESS> wrote:

> In article 
> <dck-0E31D0.06063914072004@nntp.bloor.is.net.cable.rogers.com>,
>  David C King <dck@myprivacy.ca> wrote:
> 
> >The error I'm getting reads:
> >
> > Can't send to "<name@domain.com>"; SMTP server says "550 5.1.2 
> > <name@domain.com> ... Unsupported mail destination".
> > [...]
> > is the above error msg coming from the rogers.com SMTP server or is it 
> > coming from Eudora
> 
> You've already answered both your questions:
> 
> - the whole error message you quoted is obviously coming from Eudora, 
> since that's what presented it on your screen for the pleasure of your 
> reading.
> 
> - the actual transaction error that Eudora is telling you about -- "550 
> 5.1.2 <name@domain.com> ... Unsupported mail destination" -- is coming 
> from the Rogers SMTP server you're trying to send through (note the 
> "SMTP server says").
> 
> Based on a googling for "5.1.2 unsupported mail destination" and the 
> subject of the first result, my guess is that Rogers is running postfix 
> and will not allow relaying unless you are using authenticated SMTP.
> 
> I'm not familiar with Rogers policies these days, but a couple of things 
> to check:  are you sending the mail via your Rogers connection (vs. at a 
> friend's or someplace else)?  are you using plain SMTP or authenticated?  
> are you able to send to another @rogers.com address (i.e. is it only 
> non-rogers.com addresses which fail)?
> 
> -ben

Ben

I'm sending email from my home computer using Authenticated SMTP. I made 
no changes to Eudora and it all worked fine for many years.

This problem has occurred as soon as Rogers has migrated to their new 
Yahoo system.

I am unable to send an email to myself at rogers.com or to any other 
address.

The purpose of my request was to find out whether it was a Eudora 
problem or a Rogers problem. Inevitably, the Rogers support people will 
say (1) Eudora is the problem and (2) we don't support Eudora. 

None of which, as you can imagine, is very helpful!

If the problem lies with Eudora, then I need to look for a solution. If 
the problem lies with Rogers, then nothing that I do at my end will 
achieve any results - it's something that they have to fix. Not that 
they will ... something similar happened when they cutover from 
@home.com and the fix was finally a plugin provided by the good folks at 
Qualcomm!

DCK

-- 
Check out http://www.pcweenies.com - Krishna Sadasivam's great 'toons

David C King <dck@myprivacy.ca> wrote:

> Rogers.com has made some changes (co-branded with Yahoo) in their system
> and now Eudora is not letting me send out messages.
> 
> The error I'm getting reads:
> 
> Can't send to "<name@domain.com>"; SMTP server says "550 5.1.2 
> <name@domain.com> ... Unsupported mail destination".
> 
> Rogers tech support says that this is a Eudora problem, not a rogers 
> SMTP problem.
> 
> All my settings are correct (username is <name@rogers.com>, 
> pop.broadband.rogers.com, smtp.broadband.rogers.com, Use Authentication
> is checked on) per Rogers setup instructions.

If Tegger�'s suggestion didn't work, it may be that you need to check
the block for using the percent hack.  (I think you'll have to install
the Esoteric Settings plugin to access it, if you haven't already.)

-- 
Kathy - read reviews of other newsgroups in news:news.groups.reviews
help for new users at <http://www.aptalaska.net/~kmorgan/>
Good Net Keeping Seal of Approval at <http://www.gnksa.org/>

In article <1ggxhnx.143vc7bk0oc4uN%kmorgan@spamcop.net>,
 kmorgan@spamcop.net (Kathy Morgan) wrote:


> 
> If Tegger�'s suggestion didn't work, it may be that you need to check
> the block for using the percent hack.  (I think you'll have to install
> the Esoteric Settings plugin to access it, if you haven't already.)

Thanks, Kathy

I have Esoteric Settings 6.0 sitting in my Extra Plugins folder within 
the Eudora Application folder. Is that the correct folder for the plugin?

I'm afraid I don't know what the 'percent hack' is ... how do I set that 
up?

Cheers

DCK

-- 
Check out http://www.pcweenies.com - Krishna Sadasivam's great 'toons

David C King <dck@myprivacy.ca> wrote:

> In article <1ggxhnx.143vc7bk0oc4uN%kmorgan@spamcop.net>,
>  kmorgan@spamcop.net (Kathy Morgan) wrote:
> 
> > If Tegger�'s suggestion didn't work, it may be that you need to check
> > the block for using the percent hack.  (I think you'll have to install
> > the Esoteric Settings plugin to access it, if you haven't already.)
> 
> I have Esoteric Settings 6.0 sitting in my Extra Plugins folder within
> the Eudora Application folder. Is that the correct folder for the plugin?

No, you need to move it to the Eudora Stuff folder and restart Eudora to
make it active.

> I'm afraid I don't know what the 'percent hack' is ... how do I set that
> up?

It's used for some SMTP servers if your user name contains an "@".  You
indicated that your user name is name@rogers.com, so the % hack may be
helpful.  (If name@rogers.com is actually your email address and your
username is just "name," then the hack probably won't help.)  Once you
have the Esoteric Settings available, you'll have a lot of new panes in
the Settings panel.  Look for "Ports & Protocols" and click on the box
for "Use % Hack."

-- 
Kathy - read reviews of other newsgroups in news:news.groups.reviews
help for new users at <http://www.aptalaska.net/~kmorgan/>
Good Net Keeping Seal of Approval at <http://www.gnksa.org/>

David C King wrote:
> The purpose of my request was to find out whether it was a Eudora
> problem or a Rogers problem. Inevitably, the Rogers support people will
> say (1) Eudora is the problem and (2) we don't support Eudora.

If you have the tools, trace the TCPIP connection between you and the Rogers
SMTP server, log it to a file, and use that to argue your case with Rogers. 

They may not be supporting "Eudora", but they should support standards such as
SMTP and if you can show that you are in fact sending your authentication
properly and that it is their server which fails, then you can safely throw
the ball in their court.  Don't forget to point the Rogers drones to the URL
containing the SMTP RFC that deals with authentication.

In article <40F6AA44.A295B62@teksavvy.com>,
 JF Mezei <jfmezei.spamnot@teksavvy.com> wrote:

> David C King wrote:
> > The purpose of my request was to find out whether it was a Eudora
> > problem or a Rogers problem. Inevitably, the Rogers support people will
> > say (1) Eudora is the problem and (2) we don't support Eudora.
> 
> If you have the tools, trace the TCPIP connection between you and the Rogers
> SMTP server, log it to a file, and use that to argue your case with Rogers. 
> 
> They may not be supporting "Eudora", but they should support standards such as
> SMTP and if you can show that you are in fact sending your authentication
> properly and that it is their server which fails, then you can safely throw
> the ball in their court.  Don't forget to point the Rogers drones to the URL
> containing the SMTP RFC that deals with authentication.

Thank yoy all for helping out.

Here's how I solved the problem: 
Under the Settings, Hosts section there is a box for Sending Mail. 
Within that box is a check-box for "Use mail-exchange records". That was 
checked. I unchecked it and 'voila', it all works.

Prior to doing that, I googled the error msg that I was receiving. After 
digging through a LOT of pages, I found several references to Yahoo's MX 
records that generated an identical error message.

I then ran a DNS check on the SMTP server that Rogers has given us to 
use. Got an IP number. Checked that when messages were going out, they 
were going to a different IP number.

Ergo - Rogers mail must be going out via Yahoo servers - which have a 
different IP number than Rogers. That's how I realised that the problem 
was with the MX record that Eudora was looking for.

I then dug through every pane in the Settings of Eudora and found the 
Hosts had a setting for MX which I unchecked ... and it worked!!

Thank you all for helping out. 

Clearly a Rogers problem, but I would have bet a million dollars that 
they would NEVER have figured it out!

Cheers

DCK

-- 
Check out http://www.pcweenies.com - Krishna Sadasivam's great 'toons

In article 
<dck-72EE63.18354815072004@nntp.bloor.is.net.cable.rogers.com>,
 David C King <dck@myprivacy.ca> wrote:

> Under the Settings, Hosts section there is a box for Sending Mail. 
> Within that box is a check-box for "Use mail-exchange records". That was 
> checked. I unchecked it and 'voila', it all works.

So what's the deal, your mail client was trying to talk directly with 
the destination MX instead of relaying through Rogers SMTP?  (e.g. if 
you were sending me mail, your client would have tried connecting to 
reverb. or basil.zygoat.ca directly?)

> I then ran a DNS check on the SMTP server that Rogers has given us to 
> use. Got an IP number. Checked that when messages were going out, they 
> were going to a different IP number.

How did you check the latter?

> Ergo - Rogers mail must be going out via Yahoo servers - which have a 
> different IP number than Rogers. That's how I realised that the problem 
> was with the MX record that Eudora was looking for.

Really, an MUA (mail user agent) shouldn't be looking up MX records ever 
(that's the job of the MTA -- mail transfer agent, on the SMTP server).  
Eh?

> I then dug through every pane in the Settings of Eudora and found the 
> Hosts had a setting for MX which I unchecked ... and it worked!!

Well, glad you've got it working again.

-ben

In article 
<dck-0E31D0.06063914072004@nntp.bloor.is.net.cable.rogers.com>,
 David C King <dck@myprivacy.ca> wrote:

> Need some urgent help please.
> 
> Rogers.com has made some changes (co-branded with Yahoo) in their system 
> and now Eudora is not letting me send out messages.
> 
> The error I'm getting reads:
> 
> Can't send to "<name@domain.com>"; SMTP server says "550 5.1.2 
> <name@domain.com> ... Unsupported mail destination".
> 
> Rogers tech support says that this is a Eudora problem, not a rogers 
> SMTP problem.
> 
> All my settings are correct (username is <name@rogers.com>, 
> pop.broadband.rogers.com, smtp.broadband.rogers.com, Use Authentication 
> is checked on) per Rogers setup instructions.
> 
> My question is:
> 
> is the above error msg coming from the rogers.com SMTP server or is it 
> coming from Eudora (I set up an account using Outlook Express 5.0.2 for 
> the Mac and I was able to send outgoing messages)
> 
> I'm using OS9.1 and Eudora 6.
> 
> Thanks for any guidance that you can provide.
> 
> DCK

I found the problem ... under Settings, Hosts, Sending Mail, 'Use mail 
exchange records' was checked on. Once I unchecked that box, I was able 
to send out mail.

I zeroed in on this after googling the error msg that I received (see 
above) and found that there was a problem with Yahoo mail-exchange (I 
don't know the technical stuff).

I then checked the IP number of the SMTP server setting that Rogers has 
given us ... against the IP number that Eudora is trying to connect with 
when sending mail. They were different!!

Unchecking the setting for 'use mail-exchange records' solved that 
problem. Rogers would NEVER have been able to tell me that!!

Thanks again for everyone's help.

DCK

-- 
Check out http://www.pcweenies.com - Krishna Sadasivam's great 'toons

On Wed, 14 Jul 2004 10:06:16 GMT, David C King <dck@myprivacy.ca>
wrote:
>
>All my settings are correct (username is <name@rogers.com>, 
>pop.broadband.rogers.com, smtp.broadband.rogers.com, Use Authentication 
>is checked on) per Rogers setup instructions.

I have same setting on Eudora, except that username is just "name" and
doesn't have the @rogers.com on it.  Works fine since I changed the
settings on Wednesday when Rogers changed the settings and didn't
provide notice.

NjS.