1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
|
%global _empty_manifest_terminate_build 0
Name: python-django-postman
Version: 4.3.1
Release: 1
Summary: User-to-User messaging system for Django, with gateway to AnonymousUser, moderation and thread management, user & exchange filters, inbox/sent/archives/trash folders, support for apps: auto-complete, notification, mailer.
License: BSD
URL: https://bitbucket.org/psam/django-postman
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/df/23/ee33c1a1d5c96ab487e790be665ed926e6e25bf910049661eedbdd584641/django-postman-4.3.1.tar.gz
BuildArch: noarch
%description
This is an application for `Django <https://www.djangoproject.com>`_-powered websites.
A list of available translations is maintained in the `Wiki <https://bitbucket.org/psam/django-postman/wiki/>`_.
Your contribution to the translations is welcomed `here <https://www.transifex.com/psam/django-postman/>`_.
Basically, the purpose is to allow authenticated users of a site to exchange private **messages**
within the site. In this documentation, the word *user* is to be understood as an instance of a User,
in the django.contrib.auth context.
So it is mainly for a User-to-User exchange.
But it may be beneficial for a subscriber to receive inquiries from any visitor, ie even if non authenticated.
For instance, a subscriber as a service provider wants an ask-me-details form on a presentation page
to facilitate possible business contacts.
In this case, the visitor is presented a compose message form with an additional field to give
an email address for the reply. The email is obfuscated to the recipient.
What is a message ? Roughly a piece of text, about a subject, sent by a sender to a recipient.
Each user has access to a collection of messages, stored in folders:
* **Inbox** for incoming messages
* **Sent** for sent messages
* **Archives** for archived messages
* **Trash** for messages marked as deleted
In folders, messages can be presented in two modes:
* by **conversation**, for a compact view: the original message and its replies are grouped in a set
to constitute one sole entry.
The lastest message (based on the time) is the representative of the set.
* by **message**, for an expanded view: each message is considered by itself.
Here is a summary of features:
* A non-User (email is undisclosed) can write to a User and get a reply
(can be disabled by configuration)
* Exchanges can be moderated (with auto-accept and auto-reject plug-ins)
* Optional recipient filter plug-ins
* Optional exchange filtering plug-ins (blacklists)
* Multi-recipient writing is possible (can be disabled by configuration)
with min/max constraints
* Messages are managed by conversations
* Messages in folders are sortable by sender|recipient|subject|date
* 'Archives' folder in addition to classic Inbox, Sent and Trash folders
* A Quick-Reply form to only ask for a response text
* A cleanup management command to clear the old deleted messages
It has support for optional additional applications:
* Autocomplete recipient field (default is 'django-ajax-selects'),
with multiple recipient management
* New message notification (default is `pinax-notifications`_)
* Asynchronous mailer (default is `django-mailer`_)
%package -n python3-django-postman
Summary: User-to-User messaging system for Django, with gateway to AnonymousUser, moderation and thread management, user & exchange filters, inbox/sent/archives/trash folders, support for apps: auto-complete, notification, mailer.
Provides: python-django-postman
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-django-postman
This is an application for `Django <https://www.djangoproject.com>`_-powered websites.
A list of available translations is maintained in the `Wiki <https://bitbucket.org/psam/django-postman/wiki/>`_.
Your contribution to the translations is welcomed `here <https://www.transifex.com/psam/django-postman/>`_.
Basically, the purpose is to allow authenticated users of a site to exchange private **messages**
within the site. In this documentation, the word *user* is to be understood as an instance of a User,
in the django.contrib.auth context.
So it is mainly for a User-to-User exchange.
But it may be beneficial for a subscriber to receive inquiries from any visitor, ie even if non authenticated.
For instance, a subscriber as a service provider wants an ask-me-details form on a presentation page
to facilitate possible business contacts.
In this case, the visitor is presented a compose message form with an additional field to give
an email address for the reply. The email is obfuscated to the recipient.
What is a message ? Roughly a piece of text, about a subject, sent by a sender to a recipient.
Each user has access to a collection of messages, stored in folders:
* **Inbox** for incoming messages
* **Sent** for sent messages
* **Archives** for archived messages
* **Trash** for messages marked as deleted
In folders, messages can be presented in two modes:
* by **conversation**, for a compact view: the original message and its replies are grouped in a set
to constitute one sole entry.
The lastest message (based on the time) is the representative of the set.
* by **message**, for an expanded view: each message is considered by itself.
Here is a summary of features:
* A non-User (email is undisclosed) can write to a User and get a reply
(can be disabled by configuration)
* Exchanges can be moderated (with auto-accept and auto-reject plug-ins)
* Optional recipient filter plug-ins
* Optional exchange filtering plug-ins (blacklists)
* Multi-recipient writing is possible (can be disabled by configuration)
with min/max constraints
* Messages are managed by conversations
* Messages in folders are sortable by sender|recipient|subject|date
* 'Archives' folder in addition to classic Inbox, Sent and Trash folders
* A Quick-Reply form to only ask for a response text
* A cleanup management command to clear the old deleted messages
It has support for optional additional applications:
* Autocomplete recipient field (default is 'django-ajax-selects'),
with multiple recipient management
* New message notification (default is `pinax-notifications`_)
* Asynchronous mailer (default is `django-mailer`_)
%package help
Summary: Development documents and examples for django-postman
Provides: python3-django-postman-doc
%description help
This is an application for `Django <https://www.djangoproject.com>`_-powered websites.
A list of available translations is maintained in the `Wiki <https://bitbucket.org/psam/django-postman/wiki/>`_.
Your contribution to the translations is welcomed `here <https://www.transifex.com/psam/django-postman/>`_.
Basically, the purpose is to allow authenticated users of a site to exchange private **messages**
within the site. In this documentation, the word *user* is to be understood as an instance of a User,
in the django.contrib.auth context.
So it is mainly for a User-to-User exchange.
But it may be beneficial for a subscriber to receive inquiries from any visitor, ie even if non authenticated.
For instance, a subscriber as a service provider wants an ask-me-details form on a presentation page
to facilitate possible business contacts.
In this case, the visitor is presented a compose message form with an additional field to give
an email address for the reply. The email is obfuscated to the recipient.
What is a message ? Roughly a piece of text, about a subject, sent by a sender to a recipient.
Each user has access to a collection of messages, stored in folders:
* **Inbox** for incoming messages
* **Sent** for sent messages
* **Archives** for archived messages
* **Trash** for messages marked as deleted
In folders, messages can be presented in two modes:
* by **conversation**, for a compact view: the original message and its replies are grouped in a set
to constitute one sole entry.
The lastest message (based on the time) is the representative of the set.
* by **message**, for an expanded view: each message is considered by itself.
Here is a summary of features:
* A non-User (email is undisclosed) can write to a User and get a reply
(can be disabled by configuration)
* Exchanges can be moderated (with auto-accept and auto-reject plug-ins)
* Optional recipient filter plug-ins
* Optional exchange filtering plug-ins (blacklists)
* Multi-recipient writing is possible (can be disabled by configuration)
with min/max constraints
* Messages are managed by conversations
* Messages in folders are sortable by sender|recipient|subject|date
* 'Archives' folder in addition to classic Inbox, Sent and Trash folders
* A Quick-Reply form to only ask for a response text
* A cleanup management command to clear the old deleted messages
It has support for optional additional applications:
* Autocomplete recipient field (default is 'django-ajax-selects'),
with multiple recipient management
* New message notification (default is `pinax-notifications`_)
* Asynchronous mailer (default is `django-mailer`_)
%prep
%autosetup -n django-postman-4.3.1
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-django-postman -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 4.3.1-1
- Package Spec generated
|
