blob: a8d513b71d69b248271a905e7961b30f1840b510 (
plain)
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
|
=encoding utf-8
=head1 NAME
ngx_mail_pop3_module - Module ngx_mail_pop3_module
=head1 Directives
=head2 pop3_auth
B<syntax:> pop3_auth I<I<C<method>> ...>
B<default:> I<plain>
B<context:> I<mail>
B<context:> I<server>
Sets permitted methods of authentication for POP3 clients.
Supported methods are:
=over
=item C<plain>
L<USERE<sol>PASS|https://datatracker.ietf.org/doc/html/rfc1939>,
L<AUTH PLAIN|https://datatracker.ietf.org/doc/html/rfc4616>,
L<AUTH LOGIN|https://datatracker.ietf.org/doc/html/draft-murchison-sasl-login-00>
=item C<apop>
L<APOP|https://datatracker.ietf.org/doc/html/rfc1939>.
In order for this method to work, the password must be stored unencrypted.
=item C<cram-md5>
L<AUTH CRAM-MD5|https://datatracker.ietf.org/doc/html/rfc2195>.
In order for this method to work, the password must be stored unencrypted.
=item C<external>
L<AUTH EXTERNAL|https://datatracker.ietf.org/doc/html/rfc4422> (1.11.6).
=back
Plain text authentication methods
(C<USERE<sol>PASS>, C<AUTH PLAIN>,
and C<AUTH LOGIN>) are always enabled,
though if the C<plain> method is not specified,
C<AUTH PLAIN> and C<AUTH LOGIN>
will not be automatically included in L</pop3_capabilities>.
=head2 pop3_capabilities
B<syntax:> pop3_capabilities I<I<C<extension>> ...>
B<default:> I<TOP USER UIDL>
B<context:> I<mail>
B<context:> I<server>
Sets the
L<POP3 protocol|https://datatracker.ietf.org/doc/html/rfc2449>
extensions list that is passed to the client in response to
the C<CAPA> command.
The authentication methods specified in the L</pop3_auth> directive
(L<SASL|https://datatracker.ietf.org/doc/html/rfc2449> extension) and
L<STLS|https://datatracker.ietf.org/doc/html/rfc2595>
are automatically added to this list depending on the
L<ngx_mail_ssl_module> directive value.
It makes sense to specify the extensions
supported by the POP3 backends
to which the clients are proxied (if these extensions are related to commands
used after the authentication, when nginx transparently proxies the client
connection to the backend).
The current list of standardized extensions is published at
L<www.iana.org|http://www.iana.org/assignments/pop3-extension-mechanism>.
|
