FaN&@s)dZddlmZddlmZddlmZddlmZGdddZGdd d Z Gd d d e Z d d Z GdddZ Gddde ZGdddZGdddeZGdddZGdddeZGdddeZGdddeZGdddZGd d!d!ZGd"d#d#eZGd$d%d%eZGd&d'd'Zd(ed)ed*ed+ed,ed-ed.ed/ed0ed1ed2ed3ed4ed5ed6ed7ed8ed9ed:eiZGd;d<d<Zd=S)>a;Representing and manipulating email headers via custom objects. This module provides an implementation of the HeaderRegistry API. The implementation is designed to flexibly follow RFC5322 rules. Eventually HeaderRegistry will be a public API, but it isn't yet, and will probably change some before that happens. )MappingProxyType)utils)errors)_header_value_parserc@seZdZddddddZeddZeddZed d Zed d Zd dZ ddZ ddZ dS)AddressNcCs|dk r|s|r$tdtj|\}}|rWtdj|||jrm|jd|j}|j}||_||_ ||_ dS)aCreate an object representing a full email address. An address can have a 'display_name', a 'username', and a 'domain'. In addition to specifying the username and domain separately, they may be specified together by using the addr_spec keyword *instead of* the username and domain keywords. If an addr_spec string is specified it must be properly quoted according to RFC 5322 rules; an error will be raised if it is not. An Address object has display_name, username, domain, and addr_spec attributes, all of which are read-only. The addr_spec and the string value of the object are both quoted according to RFC5322 rules, but without any Content Transfer Encoding. Nz=addrspec specified when username and/or domain also specifiedz6Invalid addr_spec; only '{}' could be parsed from '{}'r) TypeErrorparserZ get_addr_spec ValueErrorformat all_defects local_partdomain _display_name _username_domain)self display_nameusernamer addr_specZa_srestr*/usr/lib/python3.5/email/headerregistry.py__init__s          zAddress.__init__cCs|jS)N)r)rrrrr7szAddress.display_namecCs|jS)N)r)rrrrr;szAddress.usernamecCs|jS)N)r)rrrrr?szAddress.domaincCsrt|j}t|t|tjkrCtj|j}n |j}|jrd|d|jS|sndS|S)zThe addr_spec (username@domain) portion of the address, quoted according to RFC 5322 rules, but with no Content Transfer Encoding. @z<>)setrlenr Z DOT_ATOM_ENDS quote_stringr)rnamesetZlprrrrCs  zAddress.addr_speccCs%dj|jj|j|j|jS)Nz1{}(display_name={!r}, username={!r}, domain={!r}))r __class____name__rrr)rrrr__repr__Ss zAddress.__repr__cCst|j}t|t|tjkrCtj|j}n |j}|r|jdkrgdn|j}dj||S|jS)Nz<>rz{} <{}>)rrrr SPECIALSrrr )rrdisprrrr__str__Xs zAddress.__str__cCsPt|t|krdS|j|jkoO|j|jkoO|j|jkS)NF)typerrr)rotherrrr__eq__cs zAddress.__eq__) r __module__ __qualname__rpropertyrrrrr!r$r'rrrrrs %  rc@sjeZdZddddZeddZeddZdd Zd d Zd d Z dS)GroupNcCs+||_|rt|nt|_dS)aCreate an object representing an address group. An address group consists of a display_name followed by colon and a list of addresses (see Address) terminated by a semi-colon. The Group is created by specifying a display_name and a possibly empty list of Address objects. A Group can also be used to represent a single address that is not in a group, which is convenient when manipulating lists that are a combination of Groups and individual Addresses. In this case the display_name should be set to None. In particular, the string representation of a Group whose display_name is None is the same as the Address object, if there is one and only one Address object in the addresses list. N)rtuple _addresses)rr addressesrrrrms zGroup.__init__cCs|jS)N)r)rrrrrszGroup.display_namecCs|jS)N)r-)rrrrr.szGroup.addressescCsdj|jj|j|jS)Nz${}(display_name={!r}, addresses={!r})r rr rr.)rrrrr!s zGroup.__repr__cCs|jdkr5t|jdkr5t|jdS|j}|dk rt|}t|t|tjkrtj|}djdd|jD}|rd|n|}dj ||S)Nrz, css|]}t|VqdS)N)str).0xrrr sz Group.__str__.. z{}:{};) rrr.r0rr r"rjoinr )rr#rZadrstrrrrr$s$   z Group.__str__cCs>t|t|krdS|j|jko=|j|jkS)NF)r%rr.)rr&rrrr'sz Group.__eq__) r r(r)rr*rr.r!r$r'rrrrr+ks   r+c@s|eZdZdZddZddZeddZedd Zd d Z e d d Z ddZ dS) BaseHeadera|Base class for message headers. Implements generic behavior and provides tools for subclasses. A subclass must define a classmethod named 'parse' that takes an unfolded value string and a dictionary as its arguments. The dictionary will contain one key, 'defects', initialized to an empty list. After the call the dictionary must contain two additional keys: parse_tree, set to the parse tree obtained from parsing the header, and 'decoded', set to the string value of the idealized representation of the data from the value. (That is, encoded words are decoded, and values that have canonical representations are so represented.) The defects key is intended to collect parsing defects, which the message parser will subsequently dispose of as appropriate. The parser should not, insofar as practical, raise any errors. Defects should be added to the list instead. The standard header parsers register defects for RFC compliance issues, for obsolete RFC syntax, and for unrecoverable parsing errors. The parse method may add additional keys to the dictionary. In this case the subclass must define an 'init' method, which will be passed the dictionary as its keyword arguments. The method should use (usually by setting them as the value of similarly named attributes) and remove all the extra keys added by its parse method, and then use super to call its parent class with the remaining arguments and keywords. The subclass should also make sure that a 'max_count' attribute is defined that is either None or 1. XXX: need to better define this API. cCswdgi}|j||tj|drFtj|d|d parse_treer7rrrr<s  zBaseHeader.initcCs|jS)N)rA)rrrrr>szBaseHeader.namecCs t|jS)N)r,rC)rrrrr7szBaseHeader.defectscCs+t|jj|jjt|f|jfS)N)_reconstruct_headerrr __bases__r0__dict__)rrrr __reduce__s    zBaseHeader.__reduce__cCstj||S)N)r0r;)r=r?rrr _reconstructszBaseHeader._reconstructcCsmtjtjtj|jdtjddgtjtjddg|jg}|jd|S)atFold header according to policy. The parsed representation of the header is folded according to RFC5322 rules, as modified by the policy. If the parse tree contains surrogateescaped bytes, the bytes are CTE encoded using the charset 'unknown-8bit". Any non-ASCII characters in the parse tree are CTE encoded using charset utf-8. XXX: make this a policy setting. The returned value is an ASCII-only string possibly containing linesep characters, and ending with a linesep character. The string includes the header name and the ': ' separator. z header-name:z header-sepr4Zfwspolicy) r ZHeaderZ HeaderLabelZ ValueTerminalr>ZCFWSListZWhiteSpaceTerminalrBfold)rrKheaderrrrrLszBaseHeader.foldN) r r(r)__doc__r;r<r*r>r7rH classmethodrIrLrrrrr6s   r6cCst||ij|S)N)r%rI)Zcls_namebasesr?rrrrEsrEc@s7eZdZdZeejZeddZ dS)UnstructuredHeaderNcCs+|j||dUs z'AddressHeader.parse..__iter__cSs7g|]-}t|ds-td|gn|qS)r.N)hasattrr+)r1itemrrrrd^s groupsr7z, cSsg|]}t|qSr)r0)r1rgrrrrdds r8) rZr0rRr.rYr+rZ all_mailboxeslistr rfr5)r=r?r@rcrhZaddrr7rrrr9Ls$        zAddressHeader.parsecs8t|jd|_d|_tj||dS)Nrh)r,r[_groupsr-r]r<)rr^r_)rrrr<hs zAddressHeader.initcCs|jS)N)rj)rrrrrhmszAddressHeader.groupscCs5|jdkr.tdd|jD|_|jS)NcSs&g|]}|jD] }|qqSr)r.)r1groupaddressrrrrdts z+AddressHeader.addresses..)r-r,rj)rrrrr.qszAddressHeader.addresses) r r(r)rSrTrRrOr9r<r*rhr.rr)rrraBs rac@seZdZdZdS)UniqueAddressHeaderr/N)r r(r)rSrrrrrmys rmc@s"eZdZeddZdS)SingleAddressHeadercCs8t|jdkr-tdj|j|jdS)Nr/z9value of single address header {} is not a single addressr)rr.r r r>)rrrrrls zSingleAddressHeader.addressN)r r(r)r*rlrrrrrn~s rnc@seZdZdZdS)UniqueSingleAddressHeaderr/N)r r(r)rSrrrrros rocseZdZdZeejZeddZ fddZ e ddZ e dd Z e d d ZS) MIMEVersionHeaderr/cCs|j||d<}t||d<|dj|j|jdkrPdn|j|d<|j|d<|jdk rdj|d|d|dr?rrr s z1ParameterizedMIMEHeader.parse..)rRr0rtr ry)r=r?r@rDrrrr9s  zParameterizedMIMEHeader.parsecs)|jd|_tj||dS)Nry)r[_paramsr]r<)rr^r_)rrrr<szParameterizedMIMEHeader.initcCs t|jS)N)rr|)rrrrryszParameterizedMIMEHeader.params) r r(r)rSrOr9r<r*ryrr)rrrxs  rxcsgeZdZeejZfddZeddZ eddZ eddZ S) ContentTypeHeadercsGtj||tj|jj|_tj|jj|_dS)N) r]r<rr:rBmaintype _maintypesubtype_subtype)rr^r_)rrrr<szContentTypeHeader.initcCs|jS)N)r)rrrrr~szContentTypeHeader.maintypecCs|jS)N)r)rrrrrszContentTypeHeader.subtypecCs|jd|jS)N/)r~r)rrrr content_typeszContentTypeHeader.content_type) r r(r)rTr Zparse_content_type_headerrRr<r*r~rrrr)rrr}s r}csCeZdZeejZfddZeddZ S)ContentDispositionHeadercsGtj|||jj}|dkr1|n tj||_dS)N)r]r<rBcontent_dispositionrr:_content_disposition)rr^r_Zcd)rrrr<s zContentDispositionHeader.initcCs|jS)N)r)rrrrrsz,ContentDispositionHeader.content_disposition) r r(r)rTr Z parse_content_disposition_headerrRr<r*rrr)rrrs rcs[eZdZdZeejZeddZ fddZ e ddZ S)ContentTransferEncodingHeaderr/cCs?|j||d<}t||d<|dj|jdS)NrDr8r7)rRr0rtr )r=r?r@rDrrrr9sz#ContentTransferEncodingHeader.parsecs/tj||tj|jj|_dS)N)r]r<rr:rBcte_cte)rr^r_)rrrr<sz"ContentTransferEncodingHeader.initcCs|jS)N)r)rrrrrsz!ContentTransferEncodingHeader.cte) r r(r)rSrTr Z&parse_content_transfer_encoding_headerrRrOr9r<r*rrr)rrrs rZsubjectZdatez resent-datez orig-dateZsenderz resent-senderZtoz resent-toZccz resent-ccZbccz resent-bccfromz resent-fromzreply-toz mime-versionz content-typezcontent-dispositionzcontent-transfer-encodingc@sOeZdZdZeedddZddZddZd d Z d S) HeaderRegistryz%A header_factory and header registry.TcCs5i|_||_||_|r1|jjtdS)aCreate a header_factory that works with the Policy API. base_class is the class that will be the last class in the created header class's __bases__ list. default_class is the class that will be used if "name" (see __call__) does not appear in the registry. use_default_map controls whether or not the default mapping of names to specialized classes is copied in to the registry when the factory is created. The default is True. N)registry base_class default_classupdate_default_header_map)rrrZuse_default_maprrrr$s   zHeaderRegistry.__init__cCs||j|jr=rrr map_to_type6szHeaderRegistry.map_to_typecCs>|jj|j|j}td|j||jfiS)N_)rgetrzrr%r r)rr>r=rrr __getitem__<szHeaderRegistry.__getitem__cCs||||S)aCreate a header instance for header 'name' from 'value'. Creates a header instance by creating a specialized class for parsing and representing the specified header by combining the factory base_class with a specialized class from the registry or the default_class, and passing the name and value to the constructed class's constructor. r)rr>r?rrr__call__@s zHeaderRegistry.__call__N) r r(r)rNr6rQrrrrrrrrr s   rN)rNtypesrZemailrrrr rr+r0r6rErQrVrWr`rarmrnrorprxr}rrrrrrrr sR[6a  '7 %