OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Alastair Sherringham (alastaircalliope.demon.co.uk)
Date: Mon Mar 18 2002 - 16:03:01 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Mon, Mar 18, 2002 at 10:13:02AM -0500, HOLLOW, CHRISTOPHER wrote:
    > Alastair...
    >
    > Thx for the response. I did notice that the mailserver address that
    > my ISP provided me resolved to a different name. For this reason I
    > actually have 2 entries in my password file:
    >
    >
    > smtp.yec.phub.net.cable.rogers.com chris.hollowrogers.com:password
    > smtp.bloor.is.net.cable.rogers.com chris.hollowrogers.com:password
    >
    > I think it only needs the first one but I figured that it couldn't hurt
    > having both. I also modified the file as per a recommendation (thx
    > Prick) to reflect what the Rogers Help page asked for as far as
    > username. Still no dice. Postfix is trying to send every 10 minutes or
    > so and still receiving the same message...

    As Patrick tried, it might be worth trying a manual session to the SMTP
    server. I don't think it should be a TLS issue however because, having
    just looked at the rogers.com link, some mail clients are supposed to be
    configured as "Use secure connection (SSL): is set to Never".

    telnet smtp.yec.phub.net.cable.rogers.com 25

    and give a ;

    EHLO rogers.com

    This gives, for me ;

    250-fep02-mail.bloor.is.net.cable.rogers.com
    250-HELP
    250-AUTH=LOGIN PLAIN
    250-AUTH LOGIN PLAIN
    250-PIPELINING
    250-DSN
    250-8BITMIME
    250 SIZE 7168000

    So ...

    Using the SASL_README, can you try some combinations of your username &
    password i.e. SASL_README uses an example ;

    AUTH PLAIN dGVzdAB0ZXN0AHRlc3RwYXNz

    "Instead of dGVzdAB0ZXN0AHRlc3RwYXNz, specify the base64 encoded
    form of username\0username\0password (the \0 is a null byte). The
    example above is for a user named `test' with password `testpass'."

    Produced via a Perl command line of ;

    perl -MMIME::Base64 -e 'print encode_base64("test\0test\0testpass");'

    What about trying typing ;

    AUTH PLAIN <N>

    and use whatever <N> is produced from the above Perl command line - for
    2 formats ;

    user = 'userrogers.com' + normal password
    user = 'user' + normal password

    (there seem to be 2 username formats for different clients)

    For PLAIN or LOGIN, the readme says that you need ;

    smtp_sasl_security_options =

    in the /etc/main.cf file. Check via ;

    postconf smtp_sasl_security_options

    There has to be some way of getting this manual method working surely?
    If not, I'd hope the ISP would be able to diagnose.

    Cheers,

    --
    AS |
    alastaircalliope.demon.co.uk |
    http://www.calliope.demon.co.uk | PGP Key : A9DE69F8
    -------------------------------------------------------------------
    -
    To unsubscribe, send mail to majordomopostfix.org with content
    (not subject): unsubscribe postfix-users