2 <head><title>xxfi_abort
</title></head>
6 <table border=
"0" cellspacing=
4 cellpadding=
4>
7 <!---------- Synopsis ----------->
8 <tr><th valign=
"top" align=left width=
150>SYNOPSIS
</th><td>
10 #include
<libmilter/mfapi.h
>
11 sfsistat (*xxfi_abort)(
15 Handle the current message's being aborted.
18 <!----------- Description ---------->
19 <tr><th valign=
"top" align=left
>DESCRIPTION
</th><td>
20 <table border=
"1" cellspacing=
1 cellpadding=
4>
21 <tr align=
"left" valign=top
>
22 <th width=
"80">Called When
</th>
23 <td>xxfi_abort may be called at any time during message processing (i.e. between some message-oriented routine and
<a href=
"xxfi_eom.html">xxfi_eom
</a>).
</td>
25 <tr align=
"left" valign=top
>
26 <th>Default Behavior
</th>
27 <td>Do nothing; return SMFIS_CONTINUE.
</td>
31 <!----------- Arguments ---------->
32 <tr><th valign=
"top" align=left
>ARGUMENTS
</th><td>
33 <table border=
"1" cellspacing=
0>
34 <tr bgcolor=
"#dddddd"><th>Argument
</th><th>Description
</th></tr>
35 <tr valign=
"top"><td>ctx
</td>
36 <td>Opaque context structure.
41 <!----------- Notes ---------->
43 <th valign=
"top" align=left
>NOTES
</th>
46 <li>xxfi_abort must reclaim any resources allocated on a per-message
47 basis, and must be tolerant of being called between any two
48 message-oriented callbacks.
50 <li>Calls to xxfi_abort and
<a href=
"xxfi_eom.html">xxfi_eom
</a> are
53 <li>xxfi_abort is not responsible for reclaiming connection-specific
54 data, since
<a href=
"xxfi_close.html">xxfi_close
</a> is always called
55 when a connection is closed.
57 <li>Since the current message is already being aborted, the return
58 value is currently ignored.
60 <li>xxfi_abort is only called if the message is aborted outside the
61 filter's control
<b>and
</b> the filter has not completed its
62 message-oriented processing. For example, if a filter has already
63 returned SMFIS_ACCEPT, SMFIS_REJECT, or SMFIS_DISCARD from a
64 message-oriented routine, xxfi_abort will not be called even if the
65 message is later aborted outside its control.
73 Copyright (c)
2000,
2003 Sendmail, Inc. and its suppliers.
76 By using this file, you agree to the terms and conditions set