Lines Matching refs:recipient

528 		name of the sender and $2 is the name of the recipient.
729 		feature will cause recipient addresses to also masquerade
886 ldap_routing	Implement LDAP-based e-mail recipient routing according to
1009 		records of the host portion of an incoming recipient; that
1079 		recipient usernames, hostnames, or addresses.  For
1234 		Normally, if % addressing is used for a recipient, e.g.
1241 		Preserve the name of the recipient host if LUSER_RELAY is
1243 		recipient address will be replaced by the host specified as
1259 		with the Compat: tag --	Compat:sender<@>recipient -- in the
1261 			DISCARD	silently discard recipient
1302 		recipient.  Selection is done via entries in the
2169 portion of an incoming recipient address by using
2173 For example, if your server receives a recipient of user@domain.com
2176 if MX lookups for the recipient domain are slow or time out.  In that
2208 If source routing is used in the recipient address (e.g.,
2325 	To:		envelope recipient
2349 relaying, which is based on the recipient address, To: must be
2367 	REJECT		Reject the sender or recipient with a general
2371 			it affects only the designated recipient, not
2470 	To:user@other.my.TLD	ERROR:550 Mailbox disabled for this recipient
2472 This would prevent a recipient of badlocaluser in any of the local
2604 If such an argument is given, the recipient will be looked up in the
2608 skipped only if the recipient address is found and has RHS FRIEND.  If
2611 other two rulesets will be applied only if the recipient address is
2721 after a recipient address has been received, hence making these
2896 current recipient.  This ruleset is only defined if FEATURE(`access_db')
2897 is selected.  A recipient address user@domain is looked up in the access
3362 					default for bang-format recipient
3662 			RecipientFactor	[30000] Cost of each recipient.
3693 					recipient fields (To:, Cc: or Bcc:)
4214   2x	mailer rules (recipient qualification)
4216   4x	mailer rules (recipient header qualification)