PMDF System Manager's Guide


Previous Contents Index

Table 2-5 below lists channel keywords alphabetically; Table 2-6 further below lists channel keywords by functional group. Keywords shown in bold face type are defaults; keywords marked with + are only supported under OpenVMS; keywords marked with § are only supported for PMDF-TLS sites.

Table 2-5 Channel Block Keywords Listed Alphabetically
  Keyword Section Usage
  733 2.3.4.1 Use % routing in the envelope; synonymous with percents
  822 2.3.4.1 Use source routes in the envelope; synonymous with sourceroute
  acceptalladdresses 2.3.4.92 Accept all recipient addresses during SMTP dialogue.
  acceptvalidaddresses 2.3.4.92 Accept only valid recipient addresses during SMTP dialogue.
+ addlineaddrs 2.3.4.94 Add all addresses from VMS MAIL TO and CC lines to PMDF headers. (Usage discouraged; use with caution.)
  addrsperfile 2.3.4.15 Number of addresses per message file
  addrsperjob 2.3.4.14 Number of addresses to be processed by a single job
  after 2.3.4.18 Specify time delay before master channel programs run
  aliaslocal 2.3.4.69 Query alias file and alias database
  aliaspostmaster 2.3.4.63 Redirect postmaster messages to the local channel postmaster
  allowetrn 2.3.4.34 Honor SMTP client ETRN commands
  allowswitchchannel 2.3.4.42 Allow switching to this channel from a switchchannel channel
  authrewrite 2.3.4.44 Use SMTP AUTH information in header
  bangoverpercent 2.3.4.2 Group A!B%C as A!(B%C)
  bangstyle 2.3.4.1 Use UUCP ! routing in the envelope; synonymous with uucp
  bidirectional 2.3.4.7 Channel is served by both a master and slave program
  blocketrn 2.3.4.34 Do not honor SMTP client ETRN commands
  blocklimit 2.3.4.78 Maximum number of PMDF blocks allowed per message
  cacheeverything 2.3.4.13 Cache all connection information
  cachefailures 2.3.4.13 Cache only connection failure information
  cachesuccesses 2.3.4.13 Cache only connection success information
  channelfilter 2.3.4.86 Specify the location of channel filter file; synonym for destinationfilter
  charset7 2.3.4.51 Default character set to associate with 7-bit text messages
  charset8 2.3.4.51 Default character set to associate with 8-bit text messages
  charsetesc 2.3.4.51 Default character set to associate with text containing the escape character
  checkehlo 2.3.4.32 Check the SMTP response banner for whether to use EHLO
  client_auth 2.3.4.43 Specify which CLIENT_AUTH section to use for client SASL
  commentinc 2.3.4.67 Leave comments in message header lines intact
  commentomit 2.3.4.67 Remove comments from message header lines
  commentstrip 2.3.4.67 Remove problematic characters from comment field in message header lines
  commenttotal 2.3.4.67 Strip comments (material in parentheses) everywhere
  connectalias 2.3.4.5 Do not rewrite addresses upon message dequeue
  connectcanonical 2.3.4.5 Rewrite addresses upon message dequeue
  convert_octet_stream 2.3.4.54 Convert application/octet-stream material as appropriate
  copysendpost 2.3.4.21 Send copies of failures to the postmaster unless the originator address is blank
  copywarnpost 2.3.4.22 Send copies of warnings to the postmaster unless the originator address is blank
  daemon 2.3.4.81 Specify name of a gateway daemon (host) to route to
  datefour 2.3.4.72 Convert date/time specifications to four digit years
  datetwo 2.3.4.72 Convert date/time specifications to two digit years
  dayofweek 2.3.4.73 Include day of week in date/time specifications
  defaulthost 2.3.4.47 Specify a domain name to use to complete addresses
  defaultmx 2.3.4.38 Channel determines whether or not to do MX lookups from network
  defaultnameservers 2.3.4.38 Consult TCP/IP stack's choice of nameservers
  deferred 2.3.4.19 Honor deferred delivery dates
  defragment 2.3.4.76 Reassemble any MIME-compliant message/partial parts queued to this channel
  description 2.3.4.87 Channel description
  destinationfilter 2.3.4.86 Specify the location of channel filter file to apply to outgoing messages
  disableetrn 2.3.4.34 Disable support for the ETRN SMTP command
  domainetrn 2.3.4.34 Honor only those SMTP client ETRN commands that specify a domain
  domainvrfy 2.3.4.35 Issue SMTP VRFY commands using full address
  dropblank 2.3.4.49 Strip blank To:, Resent-To:, Cc:, or Resent-Cc: headers
  ehlo 2.3.4.32 Use EHLO on all initial SMTP connections
  eightbit 2.3.4.50 Channel supports eight bit characters
  eightnegotiate 2.3.4.50 Channel should negotiate use of eight bit transmission if possible
  eightstrict 2.3.4.50 Channel should reject messages that contain unnegotiated eight bit data
  errsendpost 2.3.4.21 Send copies of failures to the postmaster if the originator address is illegal
  errwarnpost 2.3.4.22 Send copies of warnings to the postmaster if the originator address is illegal
  expandchannel 2.3.4.16 Channel in which to perform deferred expansion due to application of expandlimit
  expandlimit 2.3.4.16 Process an incoming message "off-line" when the number of addressees exceeds this limit
  exproute 2.3.4.3 Explicit routing for this channel's addresses
  exquota 2.3.4.80 On OpenVMS, use EXQUOTA privileges if necessary to deliver VMS MAIL messages; on UNIX treat as holdexquota for Berkeley mailboxes; on all platforms deliver to overquota PMDF MessageStore or PMDF popstore accounts
  fileinto 2.3.4.86 Specify effect on address when a mailbox filter fileinto operation is applied
  filesperjob 2.3.4.14 Number of queue entries to be processed by a single job
  filter 2.3.4.86 Specify the location of user filter files
+ foreign 2.3.4.53 Use VMS MAIL's foreign message format as needed with VMS MAIL
  forwardcheckdelete 2.3.4.40 If a reverse DNS lookup has been performed, next perform a forward lookup on the returned name to check that the returned IP number matches the original; if not, delete the name and use the IP address
  forwardchecknone 2.3.4.40 Do not perform a forward lookup after a DNS reverse lookup
  forwardchecktag 2.3.4.40 If a reverse DNS lookup has been performed, next perform a forward lookup on the returned name to check that the returned IP number matches the original; if not, tag the name with *
+ goldmail 2.3.4.26 Generate Gold-Mail compatible read receipts
  grey 2.3.4.83 Use Grey Book address formats (inverted order domains)
  header_733 2.3.4.1 Use % routing in the message header
  header_822 2.3.4.1 Use source routes in the message header
  header_uucp 2.3.4.1 Use ! routing in the header
+ headerbottom 2.3.4.58 Place the message header at the bottom of the message (usage discouraged; use with caution; see 2.3.4.58)
  headerinc 2.3.4.58 Place the message header at the top of the message
  headerlabelalign 2.3.4.75 Align headers
  headerlinelength 2.3.4.75 Fold long headers
+ headeromit 2.3.4.58 Omit the message header from the message (usage discouraged; use with caution; see 2.3.4.58)
  headerread 2.3.4.59 Apply source channel header trimming rules from an options file to the message headers before headers are processed (use with caution)
  headertrim 2.3.4.59 Apply destination channel header trimming rules from an options file to the message headers after headers are processed (use with caution)
  holdexquota 2.3.4.80 Hold messages for users that are over quota
  holdlimit 2.3.4.16 .HELD an incoming message when the number of addressees exceeds this limit
  identnone 2.3.4.40 Perform IP to hostname translation; include both hostname and IP address in Received: header
  identnonelimited 2.3.4.40 Perform IP to hostname translation, but do not use the hostname during channel switching; include both hostname and IP address in Received: header
  identnonenumeric 2.3.4.40 Do not perform IP to hostname translation
  identnonesymbolic 2.3.4.40 Perform IP to hostname translation; include only the hostname in Received: header
  ignoreencoding 2.3.4.60 Ignore Encoding: header on incoming messages
  ignoremessageencoding 2.3.4.60 Ignore Encoding: header in embedded messages
  ignoremultipartencoding 2.3.4.60 Ignore Encoding: header in multipart messages
  immediate 2.3.4.9 Delivery started immediately after submission for messages of second-class or higher priority
  immnonurgent 2.3.4.9 Delivery started immediately after submission even for messages with lower than normal priority
  immnormal 2.3.4.9 Delivery started immediately after submission for messages of normal or higher priority
  immurgent 2.3.4.9 Delivery started immediately after submission for urgent messages only
  improute 2.3.4.3 Implicit routing for this channel's addresses
  includefinal 2.3.4.27 Include final form of address in delivery notifications
  inline 2.3.4.90 Perform directory lookups immediately
  inner 2.3.4.56 Rewrite inner message headers
  innertrim 2.3.4.59 Apply header trimming rules from an options file to inner message headers (use with caution)
  interfaceaddress 2.3.4.37 Bind to the specified TCP/IP interface address
  interpretencoding 2.3.4.60 Interpret Encoding: header on incoming messages
  interpretmessageencoding 2.3.4.60 Interpret Encoding: header in embedded messages
  interpretmultipartencoding 2.3.4.60 Interpret Encoding: header in multipart messages
  lastresort 2.3.4.39 Specify a last resort host
  linelength 2.3.4.52 Message lines exceeding this length limit will be wrapped
  linelimit 2.3.4.78 Maximum number of lines allowed per message
  localvrfy 2.3.4.35 Issue SMTP VRFY command using local address
  logging 2.3.4.84 Log message enqueues and dequeues into the log file
+ logicaldisk 2.3.4.30 Spread PMDF channel queues across multiple disks
  loopcheck 2.3.4.91 Automatically detect mail loops when sending.
  mailfromdnsverify 2.3.4.41 Verify that the domain specified on MAIL FROM: line is in the DNS
  master 2.3.4.7 Channel is served only by a master program
  master_debug 2.3.4.85 Generate debugging output in the channel's master program output
  maxblocks 2.3.4.77 Maximum number of PMDF blocks per message; longer messages are broken into multiple messages
  maxheaderaddrs 2.3.4.74 Maximum number of addresses per message header line; longer header lines are broken into multiple header lines
  maxheaderchars 2.3.4.74 Maximum number of characters per message header line; longer header lines are broken into multiple header lines
  maxjobs 2.3.4.14 Maximum number of jobs which can be created at once
  maxlines 2.3.4.77 Maximum number of message lines per message; longer messages are broken into multiple messages
  maxperiodicnonurgent 2.3.4.11 Specify that periodic jobs should only process messages of nonurgent or lower priority
  maxperiodicnormal 2.3.4.11 Specify that periodic jobs should only process messages of normal or lower priority
  maxperiodicurgent 2.3.4.11 Specify that periodic jobs should process messages of urgent or lower priority
  maxprocchars 2.3.4.79 Specify maximum length of headers to process
  maysasl 2.3.4.43 Allow SMTP server and client SASL authentication
  maysaslclient 2.3.4.43 SMTP client attempts to use SASL authentication
  maysaslserver 2.3.4.43 SMTP server offers SASL authentication
§ maytls 2.3.4.45 SMTP client and server allow TLS use
§ maytlsclient 2.3.4.45 SMTP client will attempt TLS use
§ maytlsserver 2.3.4.45 SMTP server allows TLS use
  minperiodicnonurgent 2.3.4.11 Specify that periodic jobs should only process messages of nonurgent or higher priority
  minperiodicnormal 2.3.4.11 Specify that periodic jobs should only process messages of normal or higher priority
  minperiodicurgent 2.3.4.11 Specify that periodic jobs should only process messages of urgent priority
  missingrecipientpolicy 2.3.4.48 Set policy for how to legalize (which header to add) messages that are lacking any recipient headers
  msexchange 2.3.4.46 Channel serves MS Exchange gateways
  multigate 2.3.4.82 Channel serves multiple BITNET gateways
  multiple 2.3.4.15 Accepts multiple destination hosts in a single message copy
  mustsasl 2.3.4.43 Must use SASL authentication
  mustsaslclient 2.3.4.43 SMTP client insists upon SASL authentication
  mustsaslserver 2.3.4.43 SMTP server insists upon SASL authentication
§ musttls 2.3.4.45 SMTP client and server insist upon TLS use and will not transfer messages with remote sides that do not support TLS
§ musttlsclient 2.3.4.45 SMTP client insists upon TLS use and will not send messages to any remote SMTP server that does not support TLS use
§ musttlsserver 2.3.4.45 SMTP server insists upon TLS use and will not accept messages from any remote SMTP client that does not support TLS use
  mx 2.3.4.38 TCP/IP network and software supports MX record lookups
  nameservers 2.3.4.38 Consult specified nameservers rather than TCP/IP stack's choice
+ network 2.3.4.89 NETMBX privilege required for use
+ noaddlineaddrs 2.3.4.94 Only addresses processed by PMDF are included in headers for mail sent from VMS MAIL. (default)
  nobangoverpercent 2.3.4.2 Group A!B%C as (A!B)%C (default)
  noblocklimit 2.3.4.78 No limit specified for the number of PMDF blocks allowed per message
  nocache 2.3.4.13 Do not cache any connection information
  nochannelfilter 2.3.4.86 Do not perform channel filtering for outgoing messages; synonym for nodestinationfilter
  noconvert_octet_stream 2.3.4.54 Do not convert application/octet-stream material
  nodayofweek 2.3.4.73 Remove day of week from date/time specifications
  nodefaulthost 2.3.4.47 Do not specify a domain name to use to complete addresses
  nodeferred 2.3.4.19 Do not honor deferred delivery dates
  nodefragment 2.3.4.76 Do not perform special processing for message/partial messages
  nodestinationfilter 2.3.4.86 Do not perform channel filtering for outgoing messages
+ nodns 2.3.4.38 TCP/IP network does not support DNS (nameserver) lookups
  nodropblank 2.3.4.49 Do not strip blank To:, Resent-To:, Cc:, or Resent-Cc: headers
  noehlo 2.3.4.32 Never use the SMTP EHLO command
  noexproute 2.3.4.3 No explicit routing for this channel's addresses
  noexquota 2.3.4.80 Return to originator any messages to users who are over quota
  nofileinto 2.3.4.86 Mailbox filter fileinto operator has no effect
  nofilter 2.3.4.86 Do not perform user mailbox filtering
+ noforeign 2.3.4.53 Do not use VMS MAIL's foreign message format
+ nogoldmail 2.3.4.26 Do not generate Gold-Mail compatible read receipts
  nogrey 2.3.4.83 Do not use Grey Book address formats
  noheaderread 2.3.4.59 Do not apply header trimming rules from option file upon message enqueue
  noheadertrim 2.3.4.59 Do not apply header trimming rules from options file
  noimproute 2.3.4.3 No implicit routing for this channel's addresses
  noinline 2.3.4.90 Do not do directory channel lookups immediately
  noinner 2.3.4.56 Do not rewrite inner message headers
  noinnertrim 2.3.4.59 Do not apply header trimming to inner message headers
  nolinelimit 2.3.4.78 No limit specified for the number of lines allowed per message
  nologging 2.3.4.84 Do not log message enqueues and dequeues into the log file
+ nologicaldisk 2.3.4.30 Store PMDF channel queues on a single disk
  nomailfromdnsverify 2.3.4.41 Do not perform DNS domain verification on the MAIL FROM: address
  nomaster_debug 2.3.4.85 Do not generate debugging output in the channel's master program output
  nomsexchange 2.3.4.46 Channel does not serve MS Exchange gateways
  nomultigate 2.3.4.82 Channel does not serve multiple BITNET gateways
  nomx 2.3.4.38 TCP/IP network does not support MX lookups
  nonrandommx 2.3.4.38 Do MX lookups; do not randomize returned entries with equal precedence
  nonurgentblocklimit 2.3.4.10 Force messages above this size to wait unconditionally for a periodic job
  nonurgentnotices 2.3.4.20 Specify the amount of time which may elapse before notices are sent and messages returned for messages of non-urgent priority
+ nonurgentqueue 2.3.4.18 Specify the queue for master channel program processing of nonurgent messages
  noreceivedfor 2.3.4.62 Do not include envelope to address in Received: header
  noreceivedfrom 2.3.4.62 Do not include the envelope From: address when constructing Received: header
  norelaxheadertermination 2.3.4.93 Don't consider a line with just spaces and tabs to be a header terminator.
  noremotehost 2.3.4.47 Use local host's domain name as the default domain name to complete addresses
  norestricted 2.3.4.57 Do not apply RFC 1137 restricted encoding to addresses
  noreturnaddress 2.3.4.63 Use the RETURN_ADDRESS option value
  noreturnpersonal 2.3.4.63 Use the RETURN_PERSONAL option value
  noreverse 2.3.4.55 Do not apply reverse database to addresses
  normalblocklimit 2.3.4.10 Force messages above this size to nonurgent priority
  normalnotices 2.3.4.20 Specify the amount of time which may elapse before notices are sent and messages returned for messages of normal priority
+ normalqueue 2.3.4.18 Specify the queue for master channel program processing of normal messages
  norules 2.3.4.6 Do not do channel-specific rewrite rule checks
  nosasl 2.3.4.43 SASL authentication not attempted or permitted
  nosaslclient 2.3.4.43 SMTP client does not attempt SASL authentication
  nosaslserver 2.3.4.43 SMTP server does not permit SASL authentication
  nosaslswitchchannel 2.3.4.43 Do not allow switching to this channel upon successful SASL authentication
  nosendetrn 2.3.4.33 Do not send SMTP ETRN command
  nosendpost 2.3.4.21 Do not send copies of failures to the postmaster
  noserviceall 2.3.4.12 Immediate delivery jobs process only the messages they were queued to process
  noslave_debug 2.3.4.85 Do not generate debugging output in the channel's slave program output
  nosmtp 2.3.4.31 Channel does not use SMTP
  nosourcefilter 2.3.4.86 Do not perform channel filtering for incoming messages
  noswitchchannel 2.3.4.42 Stay with the server channel; do not switch to the channel associated with the originating host; do not permit being switched to
  notices 2.3.4.20 Specify the amount of time which may elapse before notices are sent and messages returned
§ notls 2.3.4.45 SMTP client and server neither attempt nor allow TLS use
§ notlsclient 2.3.4.45 SMTP client does not attempt TLS use when sending messages
§ notlsserver 2.3.4.45 SMTP server does not offer or allow TLS use when receiving messages
  novrfy 2.3.4.35 Do not issue SMTP VRFY commands
  nowarnpost 2.3.4.22 Do not send copies of warnings to the postmaster
  nox_env_to 2.3.4.61 Do not add X-Envelope-to: header lines while enqueuing
  percents 2.3.4.1 Use % routing in the envelope; synonymous with 733
  period 2.3.4.9 Specify periodicity of periodic channel service
  periodic 2.3.4.9 Channel is serviced only periodically; immediate delivery processing is never done
  personalinc 2.3.4.68 Leave personal names in message header lines intact
  personalomit 2.3.4.68 Remove personal name fields from message header lines
  personalstrip 2.3.4.68 Strip problematic characters from personal name fields in message header lines
  port 2.3.4.37 Send to the specified TCP/IP port
  postheadbody 2.3.4.23 Both the message's header and body are sent to the postmaster when a delivery failure occurs
  postheadonly 2.3.4.23 Only the message's header is sent to the postmaster when a delivery failure occurs
  queue 2.3.4.18 Specify queue master channel programs run in
  randommx 2.3.4.38 Do MX lookups; randomize returned entries with equal precedence
  readreceiptmail 2.3.4.25 Ignore read receipt requests when delivering to VMS MAIL, rather than "downgrading" them to delivery receipt requests; leave it up to user agents to act upon the read receipt request
  receivedfor 2.3.4.62 Include envelope to address in Received: header
  receivedfrom 2.3.4.62 Include the envelope From: address when constructing Received: header
  relaxheadertermination 2.3.4.93 Consider a line with just spaces and tabs to be a header terminator.
  remotehost 2.3.4.47 Use remote host's name as the default domain name to complete addresses
  reportboth 2.3.4.24 Generate both header and NOTARY delivery receipt requests from "foreign" delivery receipt requests
  reportheader 2.3.4.24 Generate only header delivery receipt requests from "foreign" delivery receipt requests
  reportnotary 2.3.4.24 Generate only NOTARY delivery receipt requests from "foreign" delivery receipt requests
  reportsuppress 2.3.4.24 Suppress delivery receipt requests from "foreign" delivery receipt requests
  restricted 2.3.4.57 Apply RFC 1137 restricted encoding to addresses
  returnaddress 2.3.4.63 Set the return address for the local Postmaster
  returnenvelope 2.3.4.64 Control use of blank envelope return addresses
  returnpersonal 2.3.4.63 Set the personal name for the local Postmaster
  reverse 2.3.4.55 Apply reverse database or REVERSE mapping to addresses
  routelocal 2.3.4.4 Rewriting should shortcircuit routing addresses
  rules 2.3.4.6 Do channel-specific rewrite rule checks
  saslswitchchannel 2.3.4.43 Switch to another channel when SASL authentication is successful
  sendetrn 2.3.4.33 Send SMTP ETRN command
  sendpost 2.3.4.21 Send copies of failures to the postmaster
  sensitivitycompanyconfidential 2.3.4.88 Allow messages of any sensitivity
  sensitivitynormal 2.3.4.88 Reject messages whose sensitivity is higher than normal
  sensitivitypersonal 2.3.4.88 Reject messages whose sensitivity is higher than personal
  sensitivityprivate 2.3.4.88 Reject messages whose sensitivity is higher than private
  serviceall 2.3.4.12 Immediate delivery jobs process all messages (queued for the channel)
  sevenbit 2.3.4.50 Channel does not support eight bit characters; eight bit characters must be encoded
  silentetrn 2.3.4.34 Honor SMTP client ETRN commands, without echoing channel information
  single 2.3.4.15 Only one envelope To: address per message copy
  single_sys 2.3.4.15 Each message copy must be for a single destination system
  slave 2.3.4.7 Channel is serviced only by a slave program
  slave_debug 2.3.4.85 Generate debugging output in the channel's slave program output
  smtp 2.3.4.31 Channel uses SMTP
  smtp_cr 2.3.4.31 Accept CR as an SMTP line terminator
  smtp_crlf 2.3.4.31 Require CRLF as the SMTP line terminator
  smtp_crorlf 2.3.4.31 Allow any of CR, LF, or CRLF as the SMTP line terminator
  smtp_lf 2.3.4.31 Accept LF as an SMTP line terminator
  sourceblocklimit 2.3.4.78 Maximum number of PMDF blocks allowed per incoming message
  sourcecommentinc 2.3.4.67 Leave comments in incoming message header lines intact
  sourcecommentomit 2.3.4.67 Remove comments from incoming message header lines
  sourcecommentstrip 2.3.4.67 Remove problematic characters from comment field in incoming message header lines
  sourcecommenttotal 2.3.4.67 Strip comments (material in parentheses) everywhere in incoming messages
  sourcefilter 2.3.4.86 Specify the location of channel filter file for incoming messages
  sourcepersonalinc 2.3.4.68 Leave personal names in incoming message header lines intact
  sourcepersonalomit 2.3.4.68 Remove personal name fields from incoming message header lines
  sourcepersonalstrip 2.3.4.68 Strip problematic characters from personal name fields in incoming message header lines
  sourceroute 2.3.4.1 Use source routes in the message envelope; synonymous with 822
  streaming 2.3.4.28 Specify degree of protocol streaming for channel to use
  subaddressexact 2.3.4.71 Alias must match exactly, including exact subaddress match
  subaddressrelaxed 2.3.4.71 Alias without subaddress may match
  subaddresswild 2.3.4.71 Alias with subaddress wildcard may match
  subdirs 2.3.4.17 Use multiple subdirectories
  submit 2.3.4.8 Mark the channel as a submit-only channel
  suppressfinal 2.3.4.27 Include only original form of address in notification messages
  switchchannel 2.3.4.42 Switch from the server channel to the channel associated with the originating host
  threaddepth 2.3.4.29 Number of messages triggering new thread with multithreaded SMTP client
§ tlsswitchchannel 2.3.4.45 Switch to specified channel upon successful TLS negotiation
  unrestricted 2.3.4.57 Do not apply RFC 1137 restricted encoding to addresses
  urgentblocklimit 2.3.4.10 Force messages above this size to normal priority
  urgentnotices 2.3.4.20 Specify the amount of time which may elapse before notices are sent and messages returned for messages of urgent priority
+ urgentqueue 2.3.4.18 Specify the queue for master channel program processing of urgent messages
  user <REFERENCE>(HEAD2_CHANNELORIGINATORTAG\VALUE) Specify account under which to run the pipe channel or specify Message Router mailbox name
  usereplyto 2.3.4.65 Specify mapping of Reply-to: header
  useresent 2.3.4.66 Specify mapping of Resent- headers for non RFC 822 environments
  uucp 2.3.4.1 Use UUCP ! routing in the envelope; synonymous with bangstyle
  validatelocalmsgstore 2.3.4.70 Enqueuing channels check that the local part of addresses they enqueue to this channel matches a PMDF Message Store account
  validatelocalnone 2.3.4.70 Enqueuing channels perform no validatation check on the local part of addresses they enqueue to this channel
  validatelocalsystem 2.3.4.70 Enqueuing channels check that the local part of addresses they enqueue to this channel matches an account on the system
  vrfyallow 2.3.4.36 Provide informative responses to SMTP VRFY command
  vrfydefault 2.3.4.36 Default responses to SMTP VRFY command, according to channel's HIDE_VERIFY option setting
  vrfyhide 2.3.4.36 Provide obfuscatory responses to SMTP VRFY command
  warnpost 2.3.4.22 Send copies of warnings to the postmaster
  x_env_to 2.3.4.61 Add X-Envelope-to: header lines while enqueuing


+Supported only on OpenVMS.
§Supported only for PMDF-TLS sites.


Previous Next Contents Index