April 28, 2020 11:02 AM, "Joerg Jung" mailto:m...@umaxx.net?to=%22Joerg%20Jung%22%20)> wrote:
On 28. Apr 2020, at 10:10, gil...@poolp.org (mailto:gil...@poolp.org) wrote:
April 28, 2020 8:55 AM, "Joerg Jung" mailto:m...@umaxx.net)>
wrote:
Also this change might break existing valid setups
On Sun, 26 Apr 2020 18:30:25 +0200, Eric Faurot wrote:
> When a catch-all entry (@) is used in a virtual alias table, it
> eventually (and mistakenly) catches everything that expands to a
> username. For example, with:
>
> f...@example.com user
> @catchall
>
>
> On 28. Apr 2020, at 10:10, gil...@poolp.org wrote:
> April 28, 2020 8:55 AM, "Joerg Jung" mailto:m...@umaxx.net>>
> wrote:
>
>> Also this change might break existing valid setups (e.g. with mailing list
>> servers), but people will likely know how to cope with it.
>
> Do you have an example
April 28, 2020 8:55 AM, "Joerg Jung" wrote:
>> On 26. Apr 2020, at 18:30, Eric Faurot wrote:
>>
>> When a catch-all entry (@) is used in a virtual alias table, it
>> eventually (and mistakenly) catches everything that expands to a
>> username. For example, with:
>>
>> f...@example.com user
>>
> On 26. Apr 2020, at 18:30, Eric Faurot wrote:
>
> When a catch-all entry (@) is used in a virtual alias table, it
> eventually (and mistakenly) catches everything that expands to a
> username. For example, with:
>
>f...@example.com user
>@catchall
>
>
