Dear List

My mailman mail head have many users in it. Some ISP don?t accept my
messages. How can I solve it (one message to each user)


Thanks

Fl?vio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/mailman-users/attachments/20020917/28b8ca3e/attachment.html

Search Discussions

  • G. Armour Van Horn at Sep 17, 2002 at 9:32 pm
    So far, I've dealt with this entirely by getting my server whitelisted
    with the ISPs that are doing that. I believe that there is a setting for
    the number sent in a batch, but to go from 500 (default, I think) to 1
    would be an excruciating hit to your performance. I believe all of the
    discussion-list type servers (Mailman, listserv, Mercury, Majordomo, et
    al) use the same mechanism, so the ISPs that are using this technique
    for stopping spam will have to address legitimate list servers.

    Van

    Flavio wrote:
    Dear ListMy mailman mail head have many users in it. Some ISP don?t
    accept my messages. How can I solve it (one message to each
    user)ThanksFl?vio
    --
    ----------------------------------------------------------
    Sign up now for Quotes of the Day, a handful of quotations
    on a theme delivered every morning.
    Enlightenment! Daily, for free!
    mailto:twisted at whidbey.com?subject=Subscribe_QOTD

    For web hosting and maintenance,
    visit Van's home page: http://www.domainvanhorn.com/van/
    ----------------------------------------------------------

    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://mail.python.org/pipermail/mailman-users/attachments/20020917/1b334d83/attachment.html
  • J C Lawrence at Sep 18, 2002 at 4:15 pm

    On Tue, 17 Sep 2002 14:32:54 -0700 G Armour Van Horn wrote:

    I believe that there is a setting for the number sent in a batch, but
    to go from 500 (default, I think) to 1 would be an excruciating hit to
    your performance.
    See the FAQ.

    The sweet spot is typically in the range of 5 - 10.
    I believe all of the discussion-list type servers (Mailman, listserv,
    Mercury, Majordomo, et al) use the same mechanism, so the ISPs that
    are using this technique for stopping spam will have to address
    legitimate list servers.
    Sadly, nope.

    SMTP is an unreliable transport. ISPs have no especial obligation to
    deliver received mail to their addressed users (no matter that those
    users and we may feel differently). Further, the ISPs won't reveal the
    filter controls they are using as they don't want the SPAMmers working
    they're way around them (they also change them regularly as the SPAMmers
    empirically deduce the values).

    --
    J C Lawrence
    ---------(*) Satan, oscillate my metallic sonatas.
    claw at kanga.nu He lived as a devil, eh?
    http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
  • Alex wetmore at Sep 18, 2002 at 5:29 pm

    On Wed, 18 Sep 2002, J C Lawrence wrote:
    I believe all of the discussion-list type servers (Mailman, listserv,
    Mercury, Majordomo, et al) use the same mechanism, so the ISPs that
    are using this technique for stopping spam will have to address
    legitimate list servers.
    Sadly, nope.

    SMTP is an unreliable transport. ISPs have no especial obligation to
    deliver received mail to their addressed users (no matter that those
    users and we may feel differently).
    This is not accurate. SMTP is a reliable transport. It either deliveres
    the message or deliveres an NDR.
    From RFC2821:
    When the receiver-SMTP accepts a piece of mail (by sending a "250
    OK" message in response to DATA), it is accepting responsibility
    for delivering or relaying the message. It must take this
    responsibility seriously. It MUST NOT lose the message for
    frivolous reasons, such as because the host later crashes or
    because of a predictable resource shortage.

    If there is a delivery failure after acceptance of a message, the
    receiver-SMTP MUST formulate and mail a notification message.

    MTAs which don't accept this level of reliability aren't SMTP
    transports. Ones which bit bucket mail which has too many
    recipients are also not SMTP compliant.

    alex
  • Alex wetmore at Sep 17, 2002 at 10:02 pm

    On Tue, 17 Sep 2002, Flavio wrote:
    My mailman mail head have many users in it. Some ISP don?t accept my
    messages. How can I solve it (one message to each user)
    This is an MTA issue. Mailman just sends the message to your MTA,
    your MTA is responsible for talking to remote MTAs (such as at an
    ISP). The remote MTA should return a too many recipients error
    that your MTA sees, and that should trigger your MTA to send this
    message and start a new one for the rest of the recipients.

    What MTA are you using, and which ISPs are giving you this problem?
    How many recipients is your MTA trying to send?

    You could set SMTP_MAX_RCPTS = 1 in mm_cfg.py to force one recipient
    per message. That can make a noticable difference on your bandwidth
    usage though.

    alex

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedSep 17, '02 at 7:57p
activeSep 18, '02 at 5:29p
posts5
users4
websitelist.org

People

Translate

site design / logo © 2022 Grokbase