HELO not accepted - Palmtop

This is a discussion on HELO not accepted - Palmtop ; Morning. I use PalmDictate [1]. I want to send a dictation by the internal SMTP client of PalmDictate. The settings for username assword@smtp.server.tld are right. But sending the dictation failes. A message appears: HELO not accepted. What does it mean? ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: HELO not accepted

  1. HELO not accepted

    Morning.

    I use PalmDictate [1]. I want to send a dictation by the internal SMTP
    client of PalmDictate. The settings for
    usernameassword@smtp.server.tld are right. But sending the dictation
    failes. A message appears:

    HELO not accepted.

    What does it mean? What can I do to avoid this misbehaviour?

    TIA and kind regards, Friedrich

    --
    PM to vatolin at mac dot com


  2. Re: HELO not accepted

    On Sat, 20 Jan 2007 09:24:38 -0800, Friedrich Vosberg wrote:

    > Morning.
    >
    > I use PalmDictate [1]. I want to send a dictation by the internal SMTP
    > client of PalmDictate. The settings for usernameassword@smtp.server.tld
    > are right. But sending the dictation failes. A message appears:
    >
    > HELO not accepted.
    >
    > What does it mean? What can I do to avoid this misbehaviour?


    Sounds like the program is only using the simpler(older?) "HELO" command
    when starting the SMTP transaction, instead of the "EHLO" command. The
    EHLO is an Extended "Hello", if I remember right. No clue how to fix the
    trouble tho.

    --
    Doug Herr
    doug*at*wombatz*dot*com


  3. Re: HELO not accepted

    "Friedrich Vosberg" wrote in
    news:1169313878.401660.13070@a75g2000cwd.googlegro ups.com:

    > Morning.
    >
    > I use PalmDictate [1]. I want to send a dictation by the internal SMTP
    > client of PalmDictate. The settings for
    > usernameassword@smtp.server.tld are right. But sending the dictation
    > failes. A message appears:
    >
    > HELO not accepted.
    >
    > What does it mean? What can I do to avoid this misbehaviour?
    >
    > TIA and kind regards, Friedrich
    >
    > --
    > PM to vatolin at mac dot com
    >


    I found an interesting old comment in a web forum for Palm Dictate:
    "The internal smtp function does not have a place to authenticate esmtp,
    which is required apparently for my provider, comcast."
    http://nch.invisionzone.com/index.php?showtopic=1392

    On my pc, I tried

    TELNET MAIL.VATOLIN.DE 25

    and typed

    HELO VATOLIN.DE

    and the server answered properly (EHLO VATOLIN.DE also works).
    If I just type the command HELO, the server says
    501 5.0.0 HELO requires domain address

    My best guess: if PalmDictate is not sending a domain name after HELO,
    it would cause this error. Check your settings again, then try their
    support resources.

    http://www.nch.com.au/palmdictate/index.html

    Here is an explanation of how to test SMTP using TELNET:
    http://exchange.mvps.org/smtp_frames.htm

    For more information about SMTP:
    http://en.wikipedia.org/wiki/Simple_...nsfer_Protocol

  4. Re: HELO not accepted

    Mark Blain schrieb:

    > I found an interesting old comment in a web forum for Palm Dictate:
    > "The internal smtp function does not have a place to authenticate esmtp,
    > which is required apparently for my provider, comcast."
    > http://nch.invisionzone.com/index.php?showtopic=1392


    This I had found too. But the NCH forum seems to be a very lonely
    place. No discussions and no really helpfull hints.

    > On my pc, I tried ...


    Same effects on my Mac.

    > TELNET MAIL.VATOLIN.DE 25
    >
    > and typed
    >
    > HELO VATOLIN.DE
    >
    > and the server answered properly (EHLO VATOLIN.DE also works).
    > If I just type the command HELO, the server says
    > 501 5.0.0 HELO requires domain address
    >
    > My best guess: if PalmDictate is not sending a domain name after HELO,
    > it would cause this error. Check your settings again,...


    It's not possible to modify the HELO command.

    > then try their support resources.


    I did it some days ago. But the support seems to be as quickly as the
    forum is populated. :-(

    Thanks and kind regards, Friedrich


+ Reply to Thread