Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

smtplib: LMTP broken in the case of multiple RCPT #76984

Open
jasenbetts mannequin opened this issue Feb 8, 2018 · 5 comments
Open

smtplib: LMTP broken in the case of multiple RCPT #76984

jasenbetts mannequin opened this issue Feb 8, 2018 · 5 comments
Labels
3.12 bugs and security fixes 3.13 bugs and security fixes 3.14 new features, bugs and security fixes stdlib Python modules in the Lib dir topic-email type-bug An unexpected behavior, bug, or error

Comments

@jasenbetts
Copy link
Mannequin

jasenbetts mannequin commented Feb 8, 2018

BPO 32803
Nosy @warsaw, @middagj
PRs
  • gh-76984: Handle DATA correctly for LMTP with multiple RCPT #18896
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = None
    created_at = <Date 2018-02-08.23:25:09.725>
    labels = ['type-bug', '3.8', '3.9', '3.10', '3.7', 'library']
    title = 'smtplib: LMTP broken in the case of multiple RCPT'
    updated_at = <Date 2020-11-13.23:14:47.716>
    user = 'https://bugs.python.org/jasenbetts'

    bugs.python.org fields:

    activity = <Date 2020-11-13.23:14:47.716>
    actor = 'middag'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2018-02-08.23:25:09.725>
    creator = 'jasen betts'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 32803
    keywords = ['patch']
    message_count = 4.0
    messages = ['311854', '311855', '369277', '380939']
    nosy_count = 3.0
    nosy_names = ['barry', 'jasen betts', 'middag']
    pr_nums = ['18896']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue32803'
    versions = ['Python 2.7', 'Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']

    @jasenbetts
    Copy link
    Mannequin Author

    jasenbetts mannequin commented Feb 8, 2018

    smtplib's LMTP support is broken,

    LMTP returns multiple responses at and of data if there have been multiple successful RCPT TO commands, but smtplib::data() only looks for a single response.

    see the example conversation on page 3 of RFC2033

    This makes LMTP unusable if there is more than one RCPT

    @jasenbetts jasenbetts mannequin added 3.8 (EOL) end of life 3.7 (EOL) end of life stdlib Python modules in the Lib dir type-bug An unexpected behavior, bug, or error labels Feb 8, 2018
    @warsaw
    Copy link
    Member

    warsaw commented Feb 8, 2018

    3.5 and 3.4 are in security fix only mode, so narrowing the relevant versions.

    @middagj
    Copy link
    Mannequin

    middagj mannequin commented May 18, 2020

    Could anyone take a look to the PR?

    @middagj
    Copy link
    Mannequin

    middagj mannequin commented Nov 13, 2020

    It would be nice if someone could take a look.

    @middagj middagj mannequin added 3.9 only security fixes 3.10 only security fixes labels Nov 13, 2020
    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    middagj added a commit to middagj/cpython that referenced this issue Nov 2, 2023
    Conform RFC 2033, the LMTP protocol gives for each successful recipient a reply.
    The smtplib only reads one. This gives problems sending more than one message
    with multiple recipients in a connection.
    middagj added a commit to middagj/cpython that referenced this issue Nov 2, 2023
    Conform RFC 2033, the LMTP protocol gives for each successful recipient a reply.
    The smtplib only reads one. This gives problems sending more than one message
    with multiple recipients in a connection.
    middagj added a commit to middagj/cpython that referenced this issue Nov 2, 2023
    …H-76984)
    
    Conform RFC 2033, the LMTP protocol gives for each successful recipient a reply.
    The smtplib only reads one. This gives problems sending more than one message
    with multiple recipients in a connection.
    middagj added a commit to middagj/cpython that referenced this issue Nov 2, 2023
    …H-76984)
    
    Conform RFC 2033, the LMTP protocol gives for each successful recipient a reply.
    The smtplib only reads one. This gives problems sending more than one message
    with multiple recipients in a connection.
    middagj added a commit to middagj/cpython that referenced this issue Jan 19, 2024
    …H-76984)
    
    Conform RFC 2033, the LMTP protocol gives for each successful recipient a reply.
    The smtplib only reads one. This gives problems sending more than one message
    with multiple recipients in a connection.
    middagj added a commit to middagj/cpython that referenced this issue Oct 11, 2024
    …H-76984)
    
    Conform RFC 2033, the LMTP protocol gives for each successful recipient a reply.
    The smtplib only reads one. This gives problems sending more than one message
    with multiple recipients in a connection.
    @jsbucy
    Copy link

    jsbucy commented Oct 16, 2024

    +1 ran into this today

    @picnixz picnixz removed 3.10 only security fixes 3.9 only security fixes 3.8 (EOL) end of life 3.7 (EOL) end of life labels Dec 3, 2024
    @picnixz picnixz added 3.12 bugs and security fixes 3.13 bugs and security fixes 3.14 new features, bugs and security fixes labels Dec 3, 2024
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    3.12 bugs and security fixes 3.13 bugs and security fixes 3.14 new features, bugs and security fixes stdlib Python modules in the Lib dir topic-email type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Development

    No branches or pull requests

    4 participants