Operation   : Linux premium131.web-hosting.com 4.18.0-553.44.1.lve.el8.x86_64 #1 SMP Thu Mar 13 14:29:12 UTC 2025 x86_64
Software     : Apache
Server IP    : 162.0.232.56 | Your IP: 216.73.216.111
Domains      : 1034 Domain(s)
Permission   : [ 0755 ]

�
e fJ$�@s�dZd
dl
mZmZmZmZ
d
dlmZ
d
dlm	Z	
d
dl
mZ
dddd	d
ddd
gZeGdd	�d	e��
Z
e
�Ze`ejdd�
Zejdd�
Zejdddd�ZdS)zcThis will be the home for the policy that hooks in the new
code that adds all the email6 features.
�)�Policy�Compat32�compat32�_extend_docstrings)
�_has_surrogates)
�HeaderRegistry)
�raw_data_managerrrr�EmailPolicy�default�strict�SMTP�HTTPcs�eZ
dZd
ZdZe�ZeZ�f
dd�Z	dd�Z
dd�Zd	d
�Zdd�Z
d
d�Zdd�Zddd�
Z�S)r	a�
+
    PROVISIONAL

    The API extensions enabled by this policy are currently provisional.
    Refer to the documentation for details.

    This policy adds new header parsing and folding algorithms.  Instead of
    simple strings, headers are custom objects with custom attributes
    depending on the type of the field.  The folding algorithm fully
    implements RFCs 2047 and 5322.

    In addition to the settable attributes listed above that apply to
    all Policies, this policy adds the following additional attributes:

    refold_source       -- if the value for a header in the Message object
                           came from the parsing of some source, this attribute
                           indicates whether or not a generator should refold
                           that value when transforming the message back into
                           stream form.  The possible values are:

                           none  -- all source values use original folding
                           long  -- source values that have any line that is
                                    longer than max_line_length will be
                                    refolded
                           all  -- all values are refolded.

                           The default is 'long'.

    header_factory      -- a callable that takes two arguments, 'name' and
                           'value', where 'name' is a header field name and
                           'value' is an unfolded header field value, and
                           returns a string-like object that represents that
                           header.  A default header_factory is provided that
                           understands some of the RFC5322 header field types.
                           (Currently address fields and date fields have
                           special treatment, while all other fields are
                           treated as unstructured.  This list will be
                           completed before the extension is marked stable.)

    content_manager     -- an object with at least two methods: get_content
                           and set_content.  When the get_content or
                           set_content method of a Message object is called,
                           it calls the corresponding method of this object,
                           passing it the message object as its first argument,
                           and any arguments or keywords that were passed to
                           it as additional arguments.  The default
                           content_manager is
                           :data:`~email.contentmanager.raw_data_manager`.

    �longc
s9d
|
kr%tj
|d
t��
nt�j|
�
dS)N�header_factory)�object�__setattr__r�super�__init__)�self�kw)
�	__class__��1/opt/alt/python34/lib64/python3.4/email/policy.pyrOs

zEmailPolicy.__init__cCs|j|
j
S)
z�+
        The implementation for this class returns the max_count attribute from
        the specialized header class that would be used to construct a header
        of type 'name'.
        )rZ	max_count)r�namerrr�header_max_countVszEmailPolicy.header_max_countcCsU|
d
jdd�\}}|j
d�
dj|
dd��
}||jd�
fS)ac
+
        The name is parsed as everything up to the ':' and returned unmodified.
        The value is determined by stripping leading whitespace off the
        remainder of the first line, joining all subsequent lines together, and
        stripping any trailing carriage return or linefeed characters.  (This
        is the same as Compat32).

        r
�
:�
z 	�Nz
)�split�lstrip�join�rstrip)rZsourcelinesr�valuerrr�header_source_parsehs	
&
zEmailPolicy.header_source_parsecCs�t|d
�r4|j
j�|
j�kr4|
|fSt|t�rjt|j��
dkrjtd�
�
n|
|j|
|�fS)a�
+
        The name is returned unchanged.  If the input value has a 'name'
        attribute and it matches the name ignoring case, the value is returned
        unchanged.  Otherwise the name and value are passed to header_factory
        method, and the resulting custom header object is returned as the
        value.  In this case a ValueError is raised if the input value contains
        CR or LF characters.

        rrzDHeader values may not contain linefeed or carriage return characters)	�hasattrr�lower�
isinstance�str�len�
splitlines�
ValueErrorr)rrr"rrr�header_store_parseus

*


'
zEmailPolicy.header_store_parsecCs2t|d
�r|S|j
|
dj|j��
�S)ai
+
        If the value has a 'name' attribute, it is returned to unmodified.
        Otherwise the name and the value with any linesep characters removed
        are passed to the header_factory method, and the resulting custom
        header object is returned.  Any surrogateescaped bytes get turned
        into the unicode unknown-character glyph.

        rr)r$rr r))rrr"rrr�header_fetch_parse�s	

zEmailPolicy.header_fetch_parsecCs|j|
|d
d�
S)a+
        Header folding is controlled by the refold_source policy setting.  A
        value is considered to be a 'source value' if and only if it does not
        have a 'name' attribute (having a 'name' attribute means it is a header
        object of some sort).  If a source value needs to be refolded according
        to the policy, it is converted into a custom header object by passing
        the name and the value with any linesep characters removed to the
        header_factory method.  Folding of a custom header object is done by
        calling its fold method with the current policy.

        Source values are split into lines using splitlines.  If the value is
        not to be refolded, the lines are rejoined using the linesep from the
        policy and returned.  The exception is lines containing non-ascii
        binary data.  In that case the value is refolded regardless of the
        refold_source setting, which causes the binary data to be CTE encoded
        using the unknown-8bit charset.

        �
refold_binaryT)
�_fold)rrr"rrr�fold�szEmailPolicy.foldcCs1|j|
|d
|j
dk�
}|jdd�S)a�
+
        The same as fold if cte_type is 7bit, except that the returned value is
        bytes.

        If cte_type is 8bit, non-ASCII binary data is converted back into
        bytes.  Headers with binary data are not refolded, regardless of the
        refold_header setting, since there is no way to know whether the binary
        data consists of single byte characters or multibyte characters.

        r-Z7bit�ascii�surrogateescape)r.Zcte_type�encode)rrr"Zfoldedrrr�fold_binary�s!
zEmailPolicy.fold_binaryFcs
t|d
�r|j
d|�
S|jr1|jn	td�
�|j�}|jdkp�|jdko�|r�t|d�
t|
�
d�kp�t�f
dd	�|d
d�D�
�
}|s�|r�t|�
r�|j	|
dj
|�
�j
d|�
S|
d|jj
|�
|jS)
NrZpolicy�inf�allrr
�c
3s!|]}
t|
�
�kV
qdS)
N)
r()�.0�
x)
�maxlenrr�	<genexpr>�sz$EmailPolicy._fold.<locals>.<genexpr>rrz: )r$r/�max_line_length�floatr)�
refold_sourcer(�anyrrr �linesep)rrr"r-�linesZrefoldr)
r9rr.�s






*
)

%
zEmailPolicy._fold)�__name__�
__module__�__qualname__�__doc__r=rrrZcontent_managerrrr#r+r,r/r3r.rr)
rrr	s4
	


Zraise_on_defectTr?z
r;N)rDZemail._policybaserrrrZemail.utilsrZemail.headerregistryrZemail.contentmanagerr�__all__r	r
rZclonerrr
rrrr�<module>s&"









	
�