Re: sender rewrining advice

mailertable, only a few entries in LDAP routing

 Please elaborate on which you're using when and why.
 

both on MX. LDAP routing when an email destined for host B, should temporary go to host A.

I think it would be nicer if I could skip processing on LOCAL.

 You should be able to forward directly on MX without needing to loop through LOCAL.
 

There will be email addresses on this @me.com that are just delivered to regular mailboxes on LOCAL.

 It looks like you are using @me.com as a reference to your own domain, not Apple's iCloud me.com.
 

correct

Which system thinks that it is responsible for -- I'm going to say -- @example.com?  MX or LOCAL?

LOCAL

If you are using LDAP routing, you can have MX think that @example.com is local to it.  --  I think, based on my understanding.

Ok so for this setup I should create Ldap routing entries like this.
mailLocalAddress: test@me.com / test@example.com
mailHost: (OUTGOING server)
mailRoutingAddress: test@guerrillamail.com
but I have to allow relaying on OUTGOING with something like this in the access map
Connect:(MX server) RELAY
Is it wise to maybe reduce this to only the me.com/example.com or is there something different.
Would this be possible/better
FEATURE(`blacklist_recipients')
@me.com RELAY
@example.com RELAY
Is this what you had in mind?

 I'm not using a milter to do SRS.  I've got SRS hooked into Sendmail as part of one of it's rule sets.

Can you specify ip ranges there or host domains, so you do not do envelope rewriting when it is not necessary?
Do these sendmail rules get MX hosts for test@guerrillamail.com compare them with some configured/identified local network and everything not in the local network is rewritten?

  - MX is a function, not a host name
  - LOCAL is a definition for addresses, much like loopback / 127.0.0.1 in IPv4

I know, I thought referring to their function would be more clear.

  - @me.com is an often used domain name that is registered to Apple for their iCloud.

Yes indeed not nice, I have asked them to change it to ime.com. That fits better with the rest of their stuff.

I think that clearer names / identifiers would help this discussion.
 Also, please provide the name(s) that Sendmail things are local to each system.  Feel free to redact part of them if you want to, but something like a.example is on ${HOST_PREVIOUSLY_CALLED_MX}, b.example is local to ${HOST_PREVIOUSLY_CALLED_LOCAL}, and c.example is local to ${HOST_PREVIOUSLY_CALLED_OUTGOING}.  I think these (place holder) names are going to quickly become extremely important.
 

ok