And even when it's possible it's not always desirable. An organization
I'm involved with has many <function>@<organization> email aliases which
forward to the person(s) responsible for those functions. This is
convenient for people who need to communicate with us since they don't
have to hunt for the responsible person(s) and their email address(es),
and is convenient for us since we can easily change the forwarding when
who is responsible for a function changes.
Dave
On Fri, 25 Nov 2022, Philip Paeps via mailop wrote:
> On 2022-11-25 07:28:03 (+0800), Michael Peddemors via mailop wrote:
>> Of course, one thing not mentioned on this thread..
>>
>> Simply stop allowing remote forwarding..
>>
>> Every modern email client can check multiple email accounts.
>> The day when remote forwarding was a necessity has now passed, and now
>> with things like SPF and other email tests, forwarding simply breaks..
>>
>> Stop allowing remote forwarding, and reduce support ;)
>>
>> Not so tongue in cheek.. Local forwarding is one thing, remote
>> forwarding for end users.. not so much.
>>
>> And, you would be surprised how many customer might just prefer using
>> your email services to Gmail's.
>
> This is not always possible.
>
> Wearing my postmas...@freebsd.org hat: we don't want to store users'
> mail. We also don't want to decide for our users who should be storing
> their email. So we give them a choice to forward it to their mailbox
> provider of choice.
>
> I realise we're not a representative use case but I'm sure we're not
> alone.
>
> There are legitimate use cases for remote forwarding.
>
> Philip
>
>
--
Dave Anderson
<d...@daveanderson.com>
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
