On 11/19/2008 5:34 PM, Ben Parker wrote:
> On Wed, 19 Nov 2008 17:04:53 -0500, Ricardo Stella <[log in to unmask]> wrote:
>
>> We standardized all of our addresses to be @domain.org.
>
> For addresses related to humans, this is a good policy, but for mail related to
> LISTSERV it is a bad idea that will cause many ongoing headaches.
> This is only the beginning of your problems:
>
>         Recipient: [SMTP:[log in to unmask]]
>         Reason: Remote SMTP Server Returned: 550 Invalid recipient
>          <[log in to unmask]> (#5.1.1)
>
>> The question is that even if not doable on a global basis
>
> change the value of NODE= in your go.user file and stop/restart LISTSERV.
>

Technically, this is do-able, but it requires changes to both the LISTSERV
service configuration, and the mail server configuration on the MX host(s)
for the rider.edu domain.  The LISTSERV changes are necessary to force
LISTSERV to use the domain name, rather than the server FQDN, as the domain
portion of the sender address on outbound messages.  The mail server changes
are necessary to ensure delivery of inbound messages.

The MX host(s) must be able to verify that a given recipient address in the
rider.edu domain is valid, and identify the internal host to which the message
should be routed for delivery.  Ideally, recipient address verification should
occur during the SMTP session when a message is presented for delivery, so the
server can reject messages for invalid recipient addresses during the SMTP
session, rather than accepting those messages, then generating delivery error
messages to the apparent, but often forged, sender addresses.

There are at least two ways to achieve this goal.  You can maintain alias
files and routing tables on the MX host(s), or you can configure the MX host(s)
to use an LDAP service for recipient address verification and mail routing.
Implementation details are left as an exercise for the reader.

--
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame