�
�(�g) � �P � d Z ddlZddlZddlmZmZmZmZ ddlm Z ddl
m Z ddl m
Z
ddlmZ g d�Z ej" d � Ze G d
� d e� � Z e� Ze`ej- d �
� Zej- d�� Zej- dd�� Zej- d �� Zy)zcThis will be the home for the policy that hooks in the new
code that adds all the email6 features.
� N)�Policy�Compat32�compat32�_extend_docstrings)�_has_surrogates)�HeaderRegistry)�raw_data_manager)� EmailMessage)r r r � EmailPolicy�default�strict�SMTP�HTTPz\n|\rc �l � � e Zd ZdZeZdZdZ e� Z e
Z � fd�Z d� Z
d� Zd� Zd� Zd � Zd
� Zd d �Z� xZS )
r aQ +
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:
utf8 -- if False (the default) message headers will be
serialized as ASCII, using encoded words to encode
any non-ASCII characters in the source strings. If
True, the message headers will be serialized using
utf8 and will not contain encoded words (see RFC
6532 for more on this serialization format).
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`.
F�longc �j �� d|vr t j | dt � � t �| � di |�� y )N�header_factory� )�object� __setattr__r �super�__init__)�self�kw� __class__s ��#/usr/lib/python3.12/email/policy.pyr zEmailPolicy.__init__] s3 �� � �2� %� � � �t�%5�~�7G� H�
��� �2� � c �4 � | 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'.
)r � max_count)r �names r �header_max_countz EmailPolicy.header_max_countd s � � �"�"�4�(�2�2�2r c � � |d j dd� \ }}|j d� dj |dd � z }||j d� 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 � N�
)�split�lstrip�join�rstrip)r � sourcelinesr �values r �header_source_parsez EmailPolicy.header_source_parsev sT � � "�!�n�*�*�3��2� ��e�� � �U�#�b�g�g�k�!�"�o�&>�>���e�l�l�6�*�+�+r c � � t |d� r/|j j � |j � k( r||fS t |t � r't |j
� � dkD r t d� �|| 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.
r r$ zDHeader values may not contain linefeed or carriage return characters) �hasattrr �lower�
isinstance�str�len�
splitlines�
ValueErrorr �r r r, s r �header_store_parsez EmailPolicy.header_store_parse� s} � � �5�&� !�e�j�j�&6�&6�&8�D�J�J�L�&H��%�=� � �e�S� !�c�%�*:�*:�*<�&=�a�&?� � =� >�
>��d�)�)�$��6�7�7r c � � t |d� r|S dj t j |� � }| 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.
r r% )r/ r) �linesep_splitterr' r r6 s r �header_fetch_parsez EmailPolicy.header_fetch_parse� s@ � � �5�&� !��L����(�.�.�u�5�6���"�"�4��/�/r c �* � | j ||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.
T��
refold_binary)�_foldr6 s r �foldzEmailPolicy.fold� s � �& �z�z�$��T�z�:�:r c � � | j ||| j dk( �� }| j rdnd}|j |d� 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.
If utf8 is true, headers are encoded to utf8, otherwise to ascii with
non-ASCII unicode rendered as encoded words.
�7bitr< �utf8�ascii�surrogateescape)r> �cte_typerB �encode)r r r, �folded�charsets r � fold_binaryzEmailPolicy.fold_binary� s@ � � ���D�%�t�}�}�f�7L��M�� �I�I�&�7���}�}�W�&7�8�8r c � �� t |d� r|j | �� S | j r | j nt j �|j � }| j dk( xsN | j dk( xr= |xr t |d � t |� z dz �kD xs t �fd�|dd D � � }|s+| j s|j � }n
|r t |� }|r1| j |d j |� � j | �� S |d
z | j j |� z | j z S ) Nr )�policy�allr r � c 3 �: �K � | ] }t |� �kD �� � y �w)N)r3 )�.0�x�maxlens �r � <genexpr>z$EmailPolicy._fold.<locals>.<genexpr>� s �� �� �<�Q��Q��&� �<�s �r$ r% z: )r/ r? �max_line_length�sys�maxsizer4 �
refold_sourcer3 �anyrB �isasciir r r) �linesep)r r r, r= �lines�refoldrQ s @r r> zEmailPolicy._fold� s& �� � �5�&� !��:�:�T�:�*� *�)-�)=�)=��%�%�3�;�;��� � �"���$�$��-� >��$�$��.� >��A�s�5��8�}�S��Y� 6�q� 8�6� A� =��<�%���)�<�<� �
��9�9� "�]�]�_�,�� �(��/�� ��&�&�t�R�W�W�U�^�<�A�A��A�N� N��d�{�T�\�\� .� .�u� 5�5�� � �D�Dr )F)�__name__�
__module__� __qualname__�__doc__r
�message_factoryrB rV r r r �content_managerr r! r- r7 r: r? rI r> �
__classcell__)r s @r r r sP �� �8�t #�O� �D��M�#�%�N�&�O� �3�$ ,�8�&
0� ;�*9�$Er r T)�raise_on_defectr& )rY )rY rS )rB )r_ �rerT �email._policybaser r r r � email.utilsr �email.headerregistryr �email.contentmanagerr �
email.messager
�__all__�compiler9 r r r �cloner
r r �SMTPUTF8r r r �<module>rn s� ���
�
� L� L� '� A� 1� &� �� �2�:�:�h�'� ��CE�&� CE� �CE�L �-�� �� � � �t� � ,���}�}�V�}�$���}�}�V�T�}�:�� �:�:�4�:� �r |