Bitbucket channel

As the name itself suggests, the bitbucket channel simply deletes any message enqueued to it. Indeed, messages that match the bitbucket channel are instantly deleted, without even being written to a bitbucket disk area. (In particular, note that no   (or equivalently  )  message files are created---a message is simply discarded immediately once the MTA sees that it matches the bitbucket channel.   However, if logging is enabled then the MTA does write  MTA transaction log entries for the bitbucket channel as if it actually ran, for monitoring/statistics purposes.   (Note that the bitbucket channel " " supposed "dequeue" record is in fact written by the enqueueing process at the same time as it writes its " " supposed "enqueue" record: note the identical time stamps and, if the MTA option    is set, the  identical process id corresponding to the enqueuing process.)

Note that Sieve filter  " " and " " actions  are, depending upon the setting of the    and    MTA options,  potential sources of purported "enqueues" to the bitbucket channel, as are matches of an attempted poster&#x27;s envelope From address to the value of an   or   LDAP attribute (more precisely to the value of whatever LDAP attributes are named by the   or   MTA options),  as well as    mapping table ,  ,  , or   flag effects.

See also:
 * Channels
 * Available channels
 * MTA transaction logging
 * log_process MTA Option
 * Sieve discard and jettison actions
 * filter_discard MTA Option
 * filter_jettison MTA Option
 * ldap_jettison_domain MTA Option
 * ldap_jettison_url MTA Option
 * Recipient access mapping tables
 * Bitbucket channel configuration