html

type AllData struct {
	Lists           []ulist.ListInfo
	StorageFolderer interface{ StorageFolder(ulist.ListInfo) string }
}

type CreateData struct {
	Address   string
	Name      string
	AdminMods string
}

type JoinAskData struct {
	Email       string
	ListAddress string
}

type JoinConfirmData struct {
	ListAddress   string
	MemberAddress string
}

type KnownsData struct {
	Auth   ulist.Membership
	Knowns []string
}

type LeaveAskData struct {
	Email string
	// use user input only, don't reveal whether the list exists
	ListAddress string
}

type LeaveConfirmData struct {
	ListAddress   string
	MemberAddress string
}

type LeaveData struct {
	Auth        ulist.Membership
	Email       string
	ListAddress string
}

type LoginData struct {
	CanLogin bool
	Mail     string
}

type MemberData struct {
	List   *ulist.List
	Member ulist.Membership
}

type MembersAddRemoveData struct {
	Auth  ulist.Membership
	List  *ulist.List
	Addrs string
}

type MembersAddRemoveStagingData struct {
	Auth  ulist.Membership
	List  *ulist.List
	Addrs []string // just addr-spec because this it what is stored in the database, and because will be parsed again
}

type MembersData struct {
	Auth    ulist.Membership
	List    *ulist.List
	Members []ulist.Membership
}

type ModData struct {
	Auth      ulist.Membership
	List      *ulist.List
	Page      int
	PageLinks []PageLink
	Messages  []StoredMessage
}

type MyData struct {
	Lists           []ulist.Membership
	StorageFolderer interface{ StorageFolder(ulist.ListInfo) string }
}

type PageLink struct {
	Page int
	Url  string
}

type PublicData struct {
	PublicLists []ulist.ListInfo
	MyLists     map[string]interface{}
}

type SettingsData struct {
	Auth ulist.Membership
	List *ulist.List
}

type StoredMessage struct {
	mail.Header
	Err      error // User must see emails with unparseable header as well. Many of them are sorted out during the LMTP Data command, but we're robust here.
	Filename string
}