Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Synchronet
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Main
Synchronet
Commits
f65323a6
Commit
f65323a6
authored
16 years ago
by
rswindell
Browse files
Options
Downloads
Patches
Plain Diff
Many updates covering the recent improvements to the mailproc support.
parent
8d495ba0
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ctrl/mailproc.ini
+48
-26
48 additions, 26 deletions
ctrl/mailproc.ini
with
48 additions
and
26 deletions
ctrl/mailproc.ini
+
48
−
26
View file @
f65323a6
...
...
@@ -8,34 +8,47 @@
; slightly different (and less flexible) format.
; Each mail processor is specified in a separate "section", comprised of the
; mail processor command-line enclosed in square brackets ("[]"), followed by
; a list of optional "key = value" pairs.
; mail processor name (or command-line) enclosed in square brackets ("[]"),
; followed by a list of optional "key = value" pairs.
; If no "Eval" or "Command" key value is specified, the mail processor name
; will be used as teh command-line to execute.
; Non-JavaScript mail processors (i.e. native executables), must have the
; "native" key set to "true" (e.g. "native = true").
; For a mail processor to only process mail received for a specific name,
; it must have a "
t
o" key with a comma-separated list of destination names.
; Example: "
t
o = listserver, listserv" would cause a mail processor to only
; it must have a "
T
o" key with a comma-separated list of destination names.
; Example: "
T
o = listserver, listserv" would cause a mail processor to only
; process mail received for either "listserver" or "listserv".
; If no "
t
o" value is specified, then the mail processor will process *all*
; If no "
T
o" value is specified, then the mail processor will process *all*
; incoming (SMTP) e-mail messages.
; If a "
t
o" value is specified, but is not a valid user, then the
"passthru"
; key must be set to "true" or the mail may be rejected or
forwarded
; (depending on the system configuration).
; If a "
T
o" value is specified, but is not a valid user
name
, then the
;
"PassThru"
key must be set to "true" or the mail may be rejected or
;
forwarded
(depending on the system configuration).
; Additional variables available to JavaScript mail processors:
;
; message_text_filename
; recipient_list_filename
; processing_error_filename
; sender_name
; sender_address
; reverse_path
; Additional (read-only) variables available to JavaScript mail processors:
;
; See exec/mailproc_util.js and exec/listserver.js for example use.
; message_text_filename // filename contains complete message header and body
; recipient_list_filename // list of all SMTP recipients for this message (.ini format)
; processing_error_filename // a filename that if created will reject this message with an SMTP error
; hello_name // the "HELO" name specified by the sender during the SMTP session
; sender_name // the name of the sender, possibly the same as the sender_address
; sender_address // sender's email address (e.g. "user@domain.com")
; reverse_path // sender's SMTP reverse-path from SMTP envelope (e.g. "<user@domain.com>")
; recipient_address // last specified recipient in SMTP session (e.g. "you@your.host.com")
;
; Command-line specifiers (variables) available for use in command-lines:
; See exec/mailproc_util.js and exec/listserver.js for example uses.
; JavaScript mail processors may be implemented as either a single "Eval"
; string or an external JavaScript file (e.g. *.js).
; External JavaScript mail processors (.js files) are loaded from the "mods"
; or "exec" directory if no path is specified on the command-line.
; If no file extension is specified on the command-line, ".js" is assumed.
; Command-line specifiers (variables) available for use in command-lines
; (native or JavaScript mail processor):
;
; %m mail message (header and body text) path/filename
; %l recipient list path/filename
...
...
@@ -43,10 +56,11 @@
;
; %h sender's host name
; %i sender's IP address
; %s sender's name
(portion of e-mail address)
; %a sender's address
(portion of e-mail address)
; %s sender's name
; %a sender's address
; %u sender's user number (0 if unauthenticated)
; %r reverse path (of SMTP "envelope")
; %t recipient's address (from SMTP "envelope")
;
; %! exec dir
; %g temp dir
...
...
@@ -65,10 +79,18 @@
; PassThru = true
; Native = false
; IgnoreOnError = false
; To =
; AccessRequirements =
; To = <none>
; AccessRequirements = <none>
; Command = [section_name]
; Eval = <none>
[MailAuth]
Command
=
mailauth.js
AccessRequirements
=
user equal 0 or guest
Disabled
=
false
[listserver.js]
To
=
listserver, listserv
Passthru
=
false
Disabled
=
false
\ No newline at end of file
[ListServer]
Command
=
listserver.js
To
=
listserver, listserv
PassThru
=
false
Disabled
=
false
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment