Re: Return path rewritten

> > No.  On your PMDF host, such an error would not have been generated
> > at all -- it would instead have been silently ignored (other than being
> > reported by pmdf test -rewrite -check_expansions, if you tried that).
> > Some _different_ sorts of errors (such as delivery problems to group
> > members _after successful group expansion_) would have been reported (only)
> > to the original sender -- and that behavior is still the same in the JES
> > MS MTA.

> I can assure you that the same alias file produced
> a different behaviour.

That's becauze you're comparing two very different setups.

> On the pmdf host, when the email is sent to this list
> an error message is sent to the original sender only.
> But on JES the error is sent to all emails in the group.

I have already explained the logic behind this.

> With pmdf, the email is passed to the directory channel.
> Then the email is sent to a jes store that bounce back
> to the original recipient.

Which in turn means that the error could not be detected during
expansion of the autoforwarder. Had the error been detected at
expansion time PMDF would have silently ignored it.

> With jes, the mta sees that there are emails invalid
> (inetUserStatus: deleted) and bounces back
> (without sending to the jes store) to the whole list.

Exactly. THis check occurs at the time the list expanded. Had the error
been detected later you would have found the behavior to be the same as
PMDF.

> What I am plannig to do is to add
> a chosen error-return-address to all my 400 groups
> in my pmdf alias file.

A very good idea IMO.

> When this works, I would migrate again this alias file on my jes host.
> Is there an easier solution?

No.

> Are there other things that I should care off when
> migrating aliases file from pmdf to jes?

If I were you I'd give serious thought to migrating your lists to LDAP.

                                Ned