Thanks Zenon.  Sound advise to revisit first things first.  Everything
you have described below is logical.  In fact on performing the latter
part of your test, I *do* get an error, and it looks like this:

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 ni-wumpf.com ESMTP
helo localhost
250-ni-wumpf.com Ok.
250-XVERP=Courier
250-XEXDATA
250-XSECURITY=NONE,STARTTLS
250-PIPELINING
250-8BITMIME
250-SIZE
250 DSN
mail From: <ace@localhost>
517 Syntax error.

Hmmm...  What the heck did I do wrong on this?  I know that those darn
"<"'s can get me but...  Any idea of what this means?  Oddly enough, I
have run tests repeatedly prior to this that sent mail from external
accounts to a valid user on the system, and the inbound mail looks good.


-Ace

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:courier-users-
> [EMAIL PROTECTED]] On Behalf Of Zenon Panoussis
> Sent: Friday, October 04, 2002 1:29 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [courier-users] Re: Courier does not deliver mail -
> courieresmtp spins on each outbound message
> 
> 
> David Humphrey wrote:
> 
>  > But I can't figure out what!  What is it about courieresmtp that
needs
>  > to be configured to send mail *out* of the server?!?
> 
> Are you sure it's courier? Take one of the destination addresses from
> the mail in your spool. Do
>     host -t mx domain
> where "domain" is the part after @ in the e-mail address. then try
>     telnet host 25
> where "host" is the reply you got from the previous command. If you
> get an answer, send a mail manually, like this:
>     helo yourownhostname
>     mail From: <youraddress>
>     rcpt To: <destinationaddress>
>     data
> 
>     blah
>     .
>     quit
> 
> Note the sole dot on a line before "quit".
> 
> Then repeat inbound:
>     telnet localhost 25
>     helo localhost
>     mail From: <validuser@localhost>
>     rcpt To: <validuser@localhost>
>     data
> 
>     blah
>     .
>     quit
> 
> If this works, then you should probably go back to fighting with
> the courier configuration. If the first test doesn't work, you have
> a network (configuation) problem. If the second test ends with
> "connection refused", you forgot to flip the last configuration
> directive in esmtpd to YES.
> 
> Forgive me if I suuggest things that you already tried long ago,
> but sometimes the simplest problems are the most difficult to see.
> 
> Z
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> courier-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe:
https://lists.sourceforge.net/lists/listinfo/courier-users



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to