catch-all vs catch-leftovers about forwardemail.net

[Slugger]

Are you sure this is how it's working for you? I'm a Gsuite Legacy convert and things are working for me how you want them to work. That is, I (userC) am the catch all address for the domain and I'm definitely not ever receiving emails to userA, userB, etc. family members. Those messages are going direct to their private gmail boxes. I do receive the aliases (and the made up addresses by spammers) delivered to me, but I never receive emails addressed userA, userB, etc. Incoming mail looks for a matching alias first then if nothing matches, is delivered to the catchall, if defined.

[mlsad3]

A workaround I think could work is to register two domains (custom2.com and custom.com).

custom.com Rules:

forward-email=userA:[email protected]
forward-email=userB:[email protected]
forward-email=userC:[email protected]
forward-email=custom2.com  # Just forward emails to new domain

custom2.com Rules:

forward-email=!userA   # Block userA emails
forward-email=!userB   # Block userB emails
[email protected]  # Hopefully catch-all does not catch userA/userB

But this doesn't seem as elegant as having "catch-leftovers" natively supported (not sure how many people would want to register a second domain to just do this)

AND the catch-all might still forward userA and userB's emails even in this scenario.

[mlsad3]

Okay thanks @Slugger for the confirmation. I never signed up for forwardemail, since when I asked customer support regarding this, they said otherwise. But if it works for you, then I'm sure it will work for me. Thanks!

[titanism]

Sorry for the confusion in the past!

To clarify, global forwarding catch-alls are only used if there are NO other matches found.

[titanism]

We deleted the previous comment - the paid plans do in fact match free plans currently in this concept as mentioned in the comment above today.

[schultzter]

This is a great explanation, it should be added to the FAQ