That is canonicalized for use with the Python email API. Given a MailBase message, this will construct a MIMEPart Writes a canonicalized message to the given file. If you need to make thisĬheck different, then change this. To check if a header value has an email address. It’s a simple lambda returning True/False Normally this works fine, but in Librelist, we need to “obfuscate” emailĪddresses by changing the to ‘-AT-’. Have weird special formatting rules, we have to check for it. Since random headers could have an email address, and email addresses To do a fast check to see if the header value has an email address in The only thing special (weird) about this function is that it tries properly_encode_header ( value, encoder, not_email ) ¶ properly_decode_header ( header ) ¶ĭecodes headers from their ASCII-safe representation salmon.encoding. parse_parameter_header ( message, header ) ¶ salmon.encoding. normalize_header ( header ) ¶ salmon.encoding. header_to_mime_encoding ( value, not_email = False ) ¶ salmon.encoding. header_from_mime_encoding ( header ) ¶ salmon.encoding. guess_encoding_and_decode ( original, data, errors = 'strict' ) ¶ salmon.encoding. Takes a string, and tries to clean it up into a clean MailBase. If it can’t then it raises a EncodingError. Will canonicalize it and give you back a pristine MailBase. Given a MIMEBase or similar Python email API message object, this from_message ( message, parent = None ) ¶ Reads an email and cleans it up to make a MailBase. attempt_decoding ( charset, dec ) ¶Īttempts to decode bytes into unicode, calls guess_encoding_and_decode > print ( apply_charset_to_header ( 'utf-8', 'Q', '=142ukasz' )) łukaszĮncoding is case insensitive and must be one of B or Q salmon.encoding. Given a charset and encoding, decode data into unicode, e.g. apply_charset_to_header ( charset, encoding, data ) ¶ VALUE_IS_EMAIL_ADDRESS ( v ) ¶ salmon.encoding.

property body ¶ get_all ( key ) ¶ items ( ) ¶ keys ( ) ¶ This attaches a simpler text encoded part, which doesn’t have aįilename.

Like _set_item_, but won’t replace header values attach_file ( filename, data, ctype, disposition ) ¶Ī file attachment is a raw attachment with a disposition that You actually can do all your email processing with thisĬlass, but it’s more raw. MailBase is used as the basis of salmon.mail and contains the basics ofĮncoding an email.

MailBase ( mime_part_or_headers = None, parent = None ) ¶ add_text ( content, charset = None ) ¶ extract_payload ( mail ) ¶ class salmon.encoding. Thing you’d encode, there’s just this one, and it figures out how toĮncode what you ask it. MIMEPart ( type_, ** params ) ¶Ī reimplementation of nearly everything in email.mime to be more usefulįor actually attaching things. Will raise EncodingError if you try to access a header that isn’t inĬONTENT_ENCODING_KEYS get ( key, default = None ) ¶ keys ( ) ¶ exception salmon.encoding. content_encoding > print ( value ) ('text/html', ) MailRequest objects are happily Unicode enabled and ready to go. Once Salmon has done this, your Python handler can now assume that all If it can’t detect the codec, and the codec lies, then the email is bad.Īll text bodies and attachments are then converted to Python str in the sameĪll other attachments are converted to raw strings as-is. It does this by decoding all codecs, and if the codec is wrong, then it willĪttempt to detect the codec using chardet. Internally, and cleaning all email addresses. Salmon will therefore try to “upgrade” all email it receives to Unicode Will be canonicalized and properly encoded. In Python 3, that means str.Īny email that cannot become Unicode, cannot be processed by Salmon orĮmail addresses are essential to Salmon’s routing and security, and therefore Python wants Unicode, it will get Unicode. No encoding is trusted, no language is sacred, all are suspect. To accomplish these tasks, Salmon goes back to basics and assert a few simple Some fictional world), but this generally frowned upon. It is possible to use other encodings (Salmon doesn’t live in To that end, Salmon will canonicalizeĪll email it sends to be ascii or utf-8 (whichever is simpler and works toĮncode the data). That’s the receiving end, but on the sending end Salmon wants to make the worldīetter by not increasing the suffering. Regular Python programmer can work with: Unicode. These are turned into something nice and clean that a Using bizarre pre-Unicode formats that are irrelevant and unnecessary in Salmon takes the policy that email it receives is most likely complete garbage

Email obfuscator ascii