Patrick Beart writes: > Folks: > > I'm at my wits end on this: > > My company is using server software that is running Courier v 0.28 as its > MTA. We have a client that prefers to serve their own E-mail, using a > Cobalt Cube appliance in their offices. This Cube is being "fed" by a DSL > connection. We hold the client's DNS and Web site (virtual) account files > on our server. We setup the DNS zone file for this client so that there > are MX records for: > 1) the client's Cube's IP address for "Mail" > 2) our server's "mail" IP address (for mail backup) > 3) our colocation partner's mail backup IP > > ... in that priority order (#1 being highest priority, #2 next, etc.) > > The client has several HTML forms pages on our server, in their virtual > account. The forms pages are set to send the resulting CGI forms data > output to "[EMAIL PROTECTED]". Courier has been bouncing most of the "info" > mail for over 2 months, apparently due to the fact that there is no "info" > mail alias or user on our server for this client account.
Rather than making random guesses, or struggling to describe a complex configuration, it is much easier to simply post the relevant data: the actual DNS records; the contents of Courier's configuration files; a sample non-delivery report, etc... Nobody's going to be able to make heads or tails of this mess based on some vague description, which could be easily misunderstood. -- Sam _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
