Skip to content
Toggle navigation
Toggle navigation
This project
Loading...
Sign in
John McEleney
/
mailutils
Go to a project
Toggle navigation
Toggle navigation pinning
Projects
Groups
Snippets
Help
Project
Activity
Repository
Pipelines
Graphs
Issues
0
Merge Requests
0
Wiki
Network
Create a new issue
Builds
Commits
Issue Boards
Files
Commits
Network
Compare
Branches
Tags
Commit
585132e2
...
585132e2533b7e222b691f057694042955bde883
authored
2002-12-15 21:53:59 +0000
by
Sergey Poznyakoff
Browse Files
Options
Browse Files
Tag
Download
Email Patches
Plain Diff
Spellcheck
1 parent
75e3a3eb
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
16 additions
and
12 deletions
doc/texinfo/libmuauth.texi
doc/texinfo/libsieve.texi
doc/texinfo/libmuauth.texi
View file @
585132e
...
...
@@ -13,7 +13,7 @@ library mechanism.
@menu
*
Data
Types
::
*
Initializing
the
l
u
bmuauth
::
*
Initializing
the
l
i
bmuauth
::
*
Module
Creation
and
Destruction
::
*
Obtaining
Authorization
Information
::
*
Existing
Modules
::
...
...
@@ -57,8 +57,8 @@ For authorization handlers it is @code{const char*} if the handler is called by
@code
{
mu_get_auth_by_uid
()}.
For
authentication
handlers
it
is
always
@code
{
struct
mu_auth_data
*
}
representing
the
user
'
s
data
obtained
by
a
previous
call
to
@code
{
mu_get_auth_by_
@dots
{}}
call
.
representing
the
user
'
s
data
obtained
by
a
previous
call
to
a
@code
{
mu_get_auth_by_
@dots
{}}
function
.
@item
func_data
Any
data
associated
with
this
handler
.
...
...
@@ -114,8 +114,8 @@ struct mu_auth_module @{
@end
example
@end
deftp
@node
Initializing
the
l
u
bmuauth
@section
Initializing
the
l
u
bmuauth
@node
Initializing
the
l
i
bmuauth
@section
Initializing
the
l
i
bmuauth
@deftypefn
void
mu_auth_init
(
void
)
...
...
@@ -289,7 +289,7 @@ main (int argc, char **argv)
@end
group
@end
example
Otherwise
,
if
you
program
will
use
it
'
s
own
modules
,
first
register
Otherwise
,
if
you
r
program
will
use
it
'
s
own
modules
,
first
register
them
with
@code
{
mu_auth_register_module
}
and
then
call
@code
{
mu_auth_init
()},
e
.
g
.
:
...
...
doc/texinfo/libsieve.texi
View file @
585132e
...
...
@@ -115,7 +115,7 @@ typedef struct @{
sieve_data_type
type
;
/* Type of the data */
union
@{
char
*
string
;
/* String value or identifier */
long
number
;
/* Numeric value */
size_t
number
;
/* Numeric value */
list_t
list
;
/* List value */
sieve_runtime_tag_t
*
tag
;
/* Tag value */
void
*
ptr
;
/* Pointer value */
...
...
@@ -308,7 +308,9 @@ associated with @code{data}. See the description of
@deftp
{
Function
Type
}
sieve_tag_checker_t
@example
typedef
int
(
*
sieve_tag_checker_t
)
(
const
char
*
@var
{
name
},
list_t
@var
{
tags
},
list_t
@var
{
args
})
typedef
int
(
*
sieve_tag_checker_t
)
(
const
char
*
@var
{
name
},
list_t
@var
{
tags
},
list_t
@var
{
args
})
@end
example
A
pointer
to
tag
checker
function
.
The
purpose
of
the
function
is
to
...
...
@@ -422,7 +424,7 @@ Returns the mailer.
@deftypefn
{
char
*
}
sieve_get_daemon_email
__P
((
sieve_machine_t
@var
{
mach
})
This
function
returns
the
@dfn
{
daemon
email
}
associated
with
this
instance
of
sieve
machine
.
The
daemon
email
is
an
email
address
used
in
envelope
from
addresses
of
automatic
reply
messages
.
By
default
it
local
envelope
from
addresses
of
automatic
reply
messages
.
By
default
it
s
local
part
is
@samp
{
<
MAILER
-
DAEMON
>
}
and
the
domain
part
is
the
machine
name
.
@end
deftypefn
...
...
@@ -434,7 +436,8 @@ follows:
@example
int
_sieve_default_error_printer
(
void
*
unused
,
const
char
*
fmt
,
va_list
ap
)
_sieve_default_error_printer
(
void
*
unused
,
const
char
*
fmt
,
va_list
ap
)
@{
return
mu_verror
(
fmt
,
ap
)
;
@
}
...
...
@@ -715,7 +718,8 @@ markers are taken verbatim. For example:
@example
text:
**This is an authomatic response from my message filtering program.**
** This is an authomatic response from my message **
** filtering program. **
I can not attend your message right now. However it
will be saved, and I will read it as soon as I am back.
...
...
@@ -860,7 +864,7 @@ The effect of this statement is that the sequence of actions between the
curly braces is executed only if the @code{condition} evaluates to
@code{true}.
The
more elaborate form of this statement allows to execute two
A
more elaborate form of this statement allows to execute two
different sets of actions depending on whether the condition is
true or not:
...
...
Please
register
or
sign in
to post a comment