I think this is related to the DMARC mitigation measures in the list config. It could be fixed by returning the list to its original configuration, but then any receiving domains that enforce DMARC checking might throw the message away. On 06/04/2017 08:58 PM, Jeremy Davis via TriLUG wrote: > Does anyone recall why this happens and how to fix it?