Re: [SOLVED]squirrelmail and exim send problem

From: Derrick 'dman' Hudson (dman_at_dman13.dyndns.org)
Date: 10/10/03

  • Next message: csj: "Re: To be safe don't use shift key..." 
    Date: Fri, 10 Oct 2003 12:15:18 -0400
To: debian-user@lists.debian.org

    On Fri, Oct 10, 2003 at 02:58:56AM +0200, benedict.verheyen@pandora.be wrote:
    | > On Fri, Oct 10, 2003 at 09:35:47AM +1300, Edward Murrell wrote:
    | >> On Fri, 2003-10-10 at 02:02, Benedict Verheyen wrote:
    | >> > When i try the smtp method i get this as error message:
    | >> >
    | >> > 2003-10-09 14:27:33 rejected EHLO from arthur.camelot [192.168.0.1]:
    | >> > syntactically invalid argument(s): <domainname>.ddts.net:<apacheport>
    | >>
    | >> That should be HELO, not EHLO. Either someone/thing has modified the php
    | >> code that sends that, or the version you got is just plain corrupt.
    | >
    | > Uh ... EHLO is the Extended HELLO command in SMTP. See RFC 2821.
    |
    | Thanks Derrick, Edward and Colin for responding.

    You're welcome.

    | I looked it up and it is indeed a bug in squirrelmail (1.4.0)
    | currently available in testing. (#200108)
    | It should be fixed in version 1.4.2-1
    | I says how to solve the problem: some code needed to be commented.

    This provides a good example of one advantage of interpreted languages
    over compiled languages. This code change can be made without the
    need for recompilation or installing a new pacakge :-).

    | As to the EHLO, i changed that also in the source code to HELO.

    I wouldn't do that. ESMTP (Extended SMTP) provides a number of
    advantages over SMTP. If you follow Colin's suggestion of reading RFC
    2821 then you'll see that EHLO replaces HELO for an ESMTP connection.
    Only antiquated (and broken, eg Cisco PIX's "smtp fixup") mail servers
    will not understand EHLO. (not that using plain SMTP is /wrong/, just
    sub-optimal)

    | I can now send email via webmail too.

    Good.

    | Next, i'll be looking into ssl to get a secure connection.

    What you need here depends on what you are trying to secure. If exim
    and squirrelmail are on the same machine then you don't really need
    SSL between them. If you do want SSL between squirrelmail and exim
    then you will definitely need to use ESMTP instead of SMTP (ESMTP
    allows for STARTTLS but SMTP doesn't). If you want the connection
    between your browser and squirrelmail to be secured then you need to
    work on apache's configuration to use HTTPS in place of HTTP.

    -D 

    -- 
\begin{humor}
Disclaimer:
If I receive a message from you, you are agreeing that:
   1. I am by definition, "the intended recipient"
   2. All information in the email is mine to do with as I see fit and make
        such financial profit, political mileage, or good joke as it lends
        itself to. In particular, I may quote it on USENET or the WWW.
   3. I may take the contents as representing the views of your company.
   4. This overrides any disclaimer or statement of confidentiality that may
        be included on your message
\end{humor}
 
http://dman13.dyndns.org/~dman/



    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: csj: "Re: To be safe don't use shift key..."

    Relevant Pages
    Loading