[courier-users] Re: troubleshooting virtual domains and courier in general

[Sam Varshavchik]

David Jones writes:

On September 29, 2003 10:50 pm, Sam Varshavchik wrote:

David Jones writes:
> I am running various tests on my new Courier installation before putting
> it
>
> into service.  I cannot get virtual domains to work:
>> telnet 172.16.2.206 25
>
> Trying 172.16.2.206...
> Connected to slam.inode.org.
> Escape character is '^]'.
> 220 mail.inode.org ESMTP
> HELO mail.inode.org
> 250-mail.inode.org Ok.
> 250-XVERP=Courier
> 250-XEXDATA
> 250-XSECURITY=NONE,STARTTLS
> 250-PIPELINING
> 250-8BITMIME
> 250-SIZE
> 250 DSN
> MAIL From:<[EMAIL PROTECTED]>
> 250 Ok.
> RCPT To:<[EMAIL PROTECTED]>
> 550 User unknown.
>
> /usr/local/etc/courier/aliases/system contains:
>
> @thebridgeconnection.ca: bridgeian

And your 'me' file contains?

And your 'locals' file contains?

And your 'hosteddomains' file contains?

And did you run makealiases?

cd /usr/local/etc/courier
cat me

mail.inode.org

cat locals

inode.org
slam.inode.org
coup.inode.org
thebridgeconnection.ca

There's your problem: schizophrenia. The same domain cannot be defined both as a local domain, and as a virtual domain alias. Remove it from locals, and rerun makealiases.

ESMTP EXPN and VRFY will work.

Not really. They show you the end result, but not how it got there. If the end result is not what you expected, then is there a way to determine what intermediate operations happened? If there are five configuration options/
files/DNS entries that must be "just so" in order for something to work then it would be nice to determine that the first two checks were OK, and the third buggered, and Courier didn't get around to using the fourth and the fifth.

You need the debug option for sendmail because of it's Turing-complete meta-language. Courier's rewriting rules are straightforward. You just need to know a few simple rules.

pgp00000.pgp

Description: PGP signature