I understood it, thanks for explaining
>It is not *required* to create a "User" object associated with a Django user
>until that user actually subscribes to a list.
For my current aim of processing bounces, I think my target people are only
those who are subscribed to some list right?
Because
I actually am trying to understand the model architecture as a whole, I admit
the pace is slow due to my machine had hardware problems recently ( I notified
this as soon as possible to Abhilash and it is fixed now ),
As mentioned in my proposal [1] I actually need an entity ( any model, class
On Wed, Jun 12, 2019, at 11:18 AM, Aaryan Bhagat wrote:
> >This used to be the case before Django-Mailman3 exited. With move to
> >django-allauth, we now sync _most_ of the changes in Postorius down
> >to Core.
>
> So you are implying if we create an account using Postorious, a
> User/Address
>This used to be the case before Django-Mailman3 exited. With move to
>django-allauth, we now sync _most_ of the changes in Postorius down
>to Core.
So you are implying if we create an account using Postorious, a User/Address
object is created automatically in the Core but this is not important,
Xiaoxing Ye wrote:
> Hi Ariessa,
>
> May I know what do you mean by a documentation guideline? And what part of
> the doc is informal?
Perhaps a page that explains how the documentation for Mailman should be
written. For example, every documentation page must have an introduction
section or
