[Mailman-Users] Meaning of "Postfix SMTP server: errors from dd11328.otherdomain.tld[ip.ip.ip.ip]"
Dear List-Members, today we ran our first mailing over our new Mailman instance. We received a few bounces and the following email which left me clueless. Please, what is this message trying to tell me? Is this us sending out, or is this someone trying to answer to our mailing (and failing to log in via TLS)? I checked my /var/log/mail logs - to no avail. Thanks for your answers! Cordially, KB Transcript of session follows. Out: 220 lists.domain.tld ESMTP Postfix (Ubuntu) In: EHLO dd11328.otherdomain.tld Out: 250-lists.domain.tld Out: 250-PIPELINING Out: 250-SIZE 1024 Out: 250-VRFY Out: 250-ETRN Out: 250-STARTTLS Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: STARTTLS Out: 454 4.7.0 TLS not available due to local problem In: MAIL FROM:<> SIZE=236 Out: 250 2.1.0 Ok In: RCPT TO: ORCPT=rfc822;list-boun...@lists.domain.tld Out: 250 2.1.5 Ok In: RSET Out: 250 2.0.0 Ok In: QUIT Out: 221 2.0.0 Bye For other details, see the local mail logfile -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Meaning of "Postfix SMTP server: errors from dd11328.otherdomain.tld[ip.ip.ip.ip]"
Dear Mark, thank you for your helpful reply although your answer shows that my question was off the list topic. Am 10.05.2016 um 17:24 schrieb Mark Sapiro: > On 5/9/16 2:04 PM, Kala Balik wrote: >> >> today we ran our first mailing over our new Mailman instance. We >> received a few bounces and the following email which left me clueless. >> >> Please, what is this message trying to tell me? Is this us sending out, >> or is this someone trying to answer to our mailing (and failing to log >> in via TLS)? I checked my /var/log/mail logs - to no avail. > > > This apparently has nothing directly to do with Mailman on your server. > > >> Transcript of session follows. >> >> Out: 220 lists.domain.tld ESMTP Postfix (Ubuntu) >> In: EHLO dd11328.otherdomain.tld >> Out: 250-lists.domain.tld >> Out: 250-PIPELINING >> Out: 250-SIZE 1024 >> Out: 250-VRFY >> Out: 250-ETRN >> Out: 250-STARTTLS >> Out: 250-ENHANCEDSTATUSCODES >> Out: 250-8BITMIME >> Out: 250 DSN >> In: STARTTLS >> Out: 454 4.7.0 TLS not available due to local problem >> In: MAIL FROM:<> SIZE=236 >> Out: 250 2.1.0 Ok >> In: RCPT TO: >> ORCPT=rfc822;list-boun...@lists.domain.tld >> Out: 250 2.1.5 Ok >> In: RSET >> Out: 250 2.0.0 Ok >> In: QUIT >> Out: 221 2.0.0 Bye > > > It looks to me like the server that identifies itself as > dd11328.otherdomain.tld started to send a message (probably a legitimate > bounce of a list message) to . It send > the RCPT TO:, was sent an OK in reply and then instead of sending the > DATA, reset the connection and quit. Possibly this is because the > sending server requires TLS which your Postfix says is not available. > > Why your Postfix decided to notify you of this is a Postfix question. > > I suggest you set both > > smtp_tls_security_level = may > > and > > smtpd_tls_security_level = may > > in your Postfix main.cf so that you accept incoming TLS if offered and > offer outgoing TLS. You will also need to set smtpd_tls_cert_file and > smtpd_tls_key_file and maybe others. See > <http://www.postfix.org/TLS_README.html>. > Will implement these postfix changes as soon as possible. Cordially, KB -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Bounces threshold never reached
Dear list members, two weeks ago we sent out a mailing through our six new mailman lists with roughly 6.000 subscribers. We expected to get a number of bounces, however, while the bounces log shows that about 600 subscribers did get a bounce score of 1.0 or 2.0, not a single address reached the threshold of 5.0 (or anything above 2.0) and, consequently, the admins did not get notice about any disables or removals. Here is my bouncing configuration: bounce_processing: yes bounce_score_threshold: 5.0 bounce_info_stale_after: 7 bounce_you_are_disabled_warnings: 3 bounce_you_are_disabled_warnings_interval: 7 bounce_unrecognized_goes_to_list_owner: yes bounce_notify_owner_on_disable: yes bounce_notify_owner_on_removal: yes >From reading the information in the web interface my understanding of the bounces processing is that for "bad" (i.e. unreachable) addresses the bounces score increases EVERYDAY by 1.0 (hard bounces) or .5 (soft bounces). Since my bounces log only displays whole numbers (either 1.0 or 2.0) I assume that most of my bounces were hard bounces (scoring 1.0 each). Therefore, constantly unreachable addresses should have reached the threshold of 5.0 after 5 days. Yet my log reads as if the email providers of most (about 500) subscribers with bounces were unreachable on the day of the mailing (kind of plausible), while the others (about 100) were "down" for two days and then online again (not very plausible). Providers may be unreliable sometimes, but not that unreliable. And our address base may be good, but not that good (no permanent bouncees at all - or am I misunderstanding the concept of permanence here - and, consequently, no automatic unsubscribes at all). What am I missing here? And how do I "repair" bounce processing and automatic unsubscribe? Thanks for your help! Cordially, CK -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bounces threshold never reached
Am 07.06.2016 um 05:01 schrieb Mark Sapiro: > On 06/06/2016 01:48 AM, Kala Balik wrote: >> >> two weeks ago we sent out a mailing through our six new mailman lists >> with roughly 6.000 subscribers. We expected to get a number of bounces, >> however, while the bounces log shows that about 600 subscribers did get >> a bounce score of 1.0 or 2.0, not a single address reached the threshold >> of 5.0 (or anything above 2.0) and, consequently, the admins did not get >> notice about any disables or removals. > > > That's exactly what I would expect. > > >> Here is my bouncing configuration: >> >> bounce_processing: yes >> bounce_score_threshold: 5.0 >> bounce_info_stale_after: 7 >> bounce_you_are_disabled_warnings: 3 >> bounce_you_are_disabled_warnings_interval: 7 >> bounce_unrecognized_goes_to_list_owner: yes >> bounce_notify_owner_on_disable: yes >> bounce_notify_owner_on_removal: yes > > > Starting with Mailman 2.1.19, there is also a > bounce_notify_owner_on_bounce_increment setting which will notify the > owner any time the score is incremented. > > >> >From reading the information in the web interface my understanding of >> the bounces processing is that for "bad" (i.e. unreachable) addresses >> the bounces score increases EVERYDAY by 1.0 (hard bounces) or .5 (soft >> bounces). > > No. > > The score is incremented by 1.0 on the first received bounce of the day. > On a day that there are no posts and hence no bounces, the score isn't > changed. > > If there are no bounces for bounce_info_stale_after (in your case 7) > days, the next bounce will reset the score to 1.0. > > There aren't actually any 'soft' bounces so the score never increments > by 0.5. > > > Since my bounces log only displays whole numbers (either 1.0 >> or 2.0) I assume that most of my bounces were hard bounces (scoring 1.0 >> each). Therefore, constantly unreachable addresses should have reached >> the threshold of 5.0 after 5 days. > > > After 5 days on which new bounces were recorded. See above. > > >> Yet my log reads as if the email providers of most (about 500) >> subscribers with bounces were unreachable on the day of the mailing >> (kind of plausible), while the others (about 100) were "down" for two >> days and then online again (not very plausible). Providers may be >> unreliable sometimes, but not that unreliable. And our address base may >> be good, but not that good (no permanent bouncees at all - or am I >> misunderstanding the concept of permanence here - and, consequently, no >> automatic unsubscribes at all). > > > Your misunderstanding is that Mailman has no way to determine if a > bouncing address will bounce the next day without sending a post and > having it bounce. No post = no bounce for that day = no score increment. It seems that my real misunderstanding is even more fundamental. I was expecting Mailman to retry sending an email if it received a bounce for that adress. I thought it would retry until either no new bounce was received anymore or the bounces threshold was reached. But this really is a misunderstanding, right? Mailman does not retry sending emails, right? > > >> What am I missing here? And how do I "repair" bounce processing and >> automatic unsubscribe? > > > It's working as intended. If yo actually want member's delivery disabled > after one or two bounces, set bounce_score_threshold to 1 or 2. > > In general your settings which are the default are appropriate for lists > which receive several posts a week or at least never more than 7 days > between posts. If your list is lower volume than that, you may want to > decrease bounce_score_threshold and increase bounce_info_stale_after. > > Note that once a member's delivery is disabled by bounce_score_threshold > being reached, Mailman no longer looks for bounces for that member and > the bounce_you_are_disabled_warnings and > bounce_you_are_disabled_warnings_interval settings take over. > -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problem with SPF, DKIM or Mailman-DMARC settings
Dear Mailman-Users, I have a Mailman instance running on a vServer with Plesk, but am using email services from my provider (different IP and MX-Domain than the Mailman machine). Emails in the format n...@domain.tld generally seem to work. However, when I send an email from the same adress to one of my Mailman lists at subdomain.domain.tld, I get many bouncees who will eventually be removed from the list. My question is: What is wrong here, my SPF or DKIM settings OR my Mailman-DMARC settings? My Mailman-DMARC settings are the following: from_is_list: No anonymous_list: No dmarc_moderation_action: Munge from dmarc_quarantine_moderation_action: Yes dmarc_none_moderation_action: No From Google I received reports of which the following XML is a clipping: google.com noreply-dmarc-supp...@google.com ... subdomain.domain.tld r r reject reject 100 123.456.78.90 1 quarantine fail fail forwarded looks forwarded, downgrade to quarantine with phishing warning subdomain.domain.tld subdomain.domain.tld fail default subdomain.domain.tld softfail 123.456.789.0 1 quarantine fail fail forwarded looks forwarded, downgrade to quarantine with phishing warning subdomain.domain.tld subdomain.domain.tld fail default some.random.domain.name pass Thanks for your help! CK -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
