Re: [Mailman-Users] Problems sending to prodigy.net mail server addresses
On Tue, Feb 5, 2019 at 1:07 AM Richard Johnson wrote: > I run a small mailman server for our historical recreation group. Lately, > I've been seeing messages like: > > : host al-ip4-mx-vip1.prodigy.net[144.160.235.143] said: > 550 5.7.1 Connections not accepted from servers without a valid sender > domain.alph733 Fix reverse DNS for 149.28.67.38 (in reply to MAIL FROM > command) > host 149.28.67.38 38.67.28.149.in-addr.arpa domain name pointer peacock.place. > host peacock.place peacock.place has address 149.28.67.38 The DNS records look perfect to me. If you're going through a time warp to Prodigy maybe the new top-levels like .place don't work yet? You get the error after MAIL FROM because that's the earliest point when a server is allowed to 550. The thing that puzzles me is that "domain.alph733" in there. I don't know what that is. If you're sending that in the HELO / EHLO then that is an error. Joe Brennan Columbia University -- 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] gmail
I don't have a Mailman recommendation, but the situation is worth some comment: Notice Gmail "blocks" with a 4xx temp fail, for a message they will never accept. That's a protocol violation. It's abusive. I've been seeing the same temp fail abuse for some messages received from Mailchimp and forwarded by our users to external addresses, and also a message from princeton.edu forwarded through us to gmail. The fake temp fails clutter up the mail queue and slow down queue runs. To cope, I've started a separate queue runner to bounce on a short timeout for recipients @gmail. The 800 pound gorilla makes up its own rules. On Tue, Sep 11, 2018 at 10:10 PM Bernie Cosell wrote: > I've gotten buried by 80 bounce messages, thanks to gmail's new policy > [that was, > apparently, put into effect yesterday]. The bounces say: > > <@gmail.com>: host alt1.gmail-smtp-in.l.google.com[74.125.129.26] > said: > 421-4.7.0 This message does not have authentication information or > fails to > pass 421-4.7.0 authentication checks. To best protect our users from > spam, > the 421-4.7.0 message has been blocked. Please visit 421-4.7.0 > https://support.google.com/mail/answer/81126#authentication for more > 421- 4.7.0 information. 128-v6si11952705iti.109 - gsmtp (in reply to end of > DATA command) > > I looked at their 'answer' and mostly found it to be unhelpful. i > certainly can't get > any server anywhere to change their their system configuration, nor can I > mess > with mailman [all suggestions about python-esque tweaks to mailman presume > that you have access to the server, which I don't]. Is there something I > can do > [just as a list owner] to deal with this mess? > > /Bernie\_ > > > Bernie Cosell > ber...@fantasyfarm.com > -- Too many people; too few sheep -- > > -- > 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/brennan%40columbia.edu > -- Joseph Brennan Lead, Email and Systems Applications -- 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] non-subscribers getting through--email address in "Real Name"
On Tue, Jul 24, 2018 at 8:20 PM Grant Taylor via Mailman-Users < mailman-users@python.org> wrote: > > > Right, thereby causing a great deal of entirely legitimate mail that > > DMARC cannot describe to go missing, along with a certain amount of spam. > > "legitimate mail that DMARC cannot describe" That sounds distinctly > like a problem with the DMARC specification, /not/ with use there of. Well it is. The problem is that DMARC's notion of "alignment" contradicts RFC 822, 2822, 5322, namely '''The "From:" field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message.''' and contradicts RFC 821, 2821, 5321 that describes the MAIL FROM address as the address used "to report errors". Mailing lists fully comply with the standard by keeping the writer's address in the Header From and by putting the address to report errors in the MAIL FROM. Nothing in email standards stated or even implied that the two addresses need to be the same. Of course a system can reject any email message for any reason or no reason, so all I can do is point out that lack of "alignment" is a silly reason for rejecting list mail. For transactional mail from sources like financial institutions, where the sender can state that the two addresses should "align", then it makes a lot more sense. Joseph Brennan -- 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] ARC, was non-subscribers getting through--email address in "Real Name"
On Sun, Jul 22, 2018 at 3:18 PM Grant Taylor via Mailman-Users < mailman-users@python.org> wrote: > On 07/21/2018 02:24 PM, John Levine wrote: > > I know people working on whiteish lists to use with ARC, to say that > > these domain are known to host real mailing lists so you should believe > > their ARC assertions. > Why not just have that list, and a X-Trust-Me: YES header? It would be much simpler to implement than ARC. Joseph Brennan Columbia University I T -- 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] Correct Mailman setup (was: List adds information to sender's name)
> At Fri, 22 Sep 2017 17:57:36 +0200 lusche...@yahoo.de wrote: >> All lists are more or less working, but every now and then some people >> complain about something. The most annoying thing is that messages are >> processed but then queued for up to one hour before they go out. I think you mean the message for one user is delayed and the message for another is not. This could happen when sending to gmail servers for recipients in more than one domain. The gmail server will accept for only one domain at a time and temp fail the other recipients. If your mail transport re-tries every 30 minutes, you will have some sent at once, some delayed for 30 minutes, and maybe even some more delayed for multiples of 30 minutes. Access to the maillog would totally clarify whether this is the answer, but I take it you can't see that. You could have Mailman send to 1 recipient per message --which is what Gmail does!-- but it is so inefficient that it makes me cringe and I have not chosen to implement that yet on our systems. -- Joseph Brennan Columbia University -- 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] Authenticated Received Chain in Mailman?
On Tue, May 30, 2017 at 10:34 PM, Brett Delmage <br...@twobikes.ottawa.on.ca> wrote: > Will Mailman 2 or 3 be incorporating Authenticated Received Chain (ARC) > http://arc-spec.org/ ? Wonderful, another offering of "This document is not an Internet Standards Track specification; it is published for informational purposes" adding further complexity to email in a mad attempt to make up for the "potential" (?) problems that the previous "informational" one (DMARC) has done to mailing lists. It would be too easy for email-reading software to show me the address of the sender and the name of the system that handed the message to my system, and let me use my own common sense to decide whether it's spoofed. Well, we have to play the cards we're dealt. Onward. Joseph Brennan Columbia University -- 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] We lost a message
We had an odd situation yesterday where Mailman lost a message.
The list is one that includes other lists ("Other mailing lists on
this site whose members are included") rather than having its own
subscribers. The list has existed for several years and has been
used many times. The last previous time was a week earlier.
A message was sent to the list address, and held for moderator
approval, as configured. The moderator approved. The approval action
is logged, so we know the right button was used. But then the message
disappeared. No Mailman logs recorded an action after approval, and
Postfix had no log of the message.
As a test we changed it to include only one small list instead, sent a
message, and got the same result, that is, moderator approved the
message and again the last trace was the log that it was approved.
As a second test we made the list unmoderated, and sent a message.
Postfix log shows it being accepted and passed to Mailman, but there
is nothing in Mailman's logs for this one.
We checked carefully for any configuration that would discard messages
automatically.
We deleted the problem list, and created a new list of the same name
including the small list, and then it worked normally. To the best of
our knowledge only this one list had the problem. Many other lists
were sending mail successfully during the same time.
We can't figure out what happened here. We never saw this before and I
don't remember anyone reporting it on this list either. I realize that
by deleting the list we destroyed some possible evidence, but all the
logs are still intact. Two of our tech staff spent some time yesterday
looking for any place the messages could be without success. I keep
thinking we missed something.
Has anyone EVER seen this? Where would you look for clues?
Joseph Brennan
Columbia U I T
--
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] Archive looping
I must correct myself. First-- The monthly archive is 9,000 messages (137,000 is the total in the entire archive going back for years). Second-- Not all messages are getting rewritten one newline at a time. Only those with "An HTML attachment was scrubbed..." get the rewrite. Still happening Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- 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] Archive looping
We have a list with a very large archive, over 137,000 messages in a month.
It catches system alerts. This might just be a bad idea. Maybe we should
archive by day. But it's been all right for many months up to now.
I'm looking for ideas on how to solve a problem with the archives.
Yesterday the archive got into a weird state that I could not break by a
shutdown and fresh start. For each incoming message, it rewrites all of the
old messages with one extra newline. This useless activity takes quite a
while and has caused mail to accumulate in the in/ directory.
Inspection of a sample message in a backup from about 24 hours ago shows
hundreds of newlines added to the message in that time. The newlines are
always added at the same place, between this:---
-- next part --
An HTML attachment was scrubbed...
URL: https://lists.columbia.edu [detail omitted]
and this:---
Below is a 'truss' (it's solaris!) showing the read and write for one
message. It reads 8192 and 2187 bytes, and writes out the same file with
8192 and 2188 bytes. (List name changed to 'listname')
open64("/mailman/archives/private/listname/2015-August/130332.html",
O_RDONLY) = 9
fstat64(9, 0xFFBFEC40) = 0
fstat64(9, 0xFFBFEC80) = 0
fstat64(9, 0xFFBFEB28) = 0
ioctl(9, TCGETA, 0xFFBFEC0C)Err#25 ENOTTY
read(9, " < ! D O C T Y P E H T".., 8192)= 8192
read(9, "\n\n\n\n\n\n\n\n\n\n\n\n".., 8192) = 2187
llseek(9, 0xFD8D, SEEK_CUR) = 9752
close(9)= 0
umask(02) = 07
open64("/mailman/archives/private/listname/2015-August/130332.html",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 9
fstat64(9, 0xFFBFEC40) = 0
umask(07) = 02
stat64("/opt/mailman-2.1.15/messages/en_US.ISO8859-1/LC_MESSAGES/mailman.mo",
0xFFBFE908) Err#2 ENOENT
stat64("/opt/mailman-2.1.15/messages/en_US/LC_MESSAGES/mailman.mo",
0xFFBFE908) Err#2 ENOENT
stat64("/opt/mailman-2.1.15/messages/en.ISO8859-1/LC_MESSAGES/mailman.mo",
0xFFBFE908) Err#2 ENOENT
stat64("/opt/mailman-2.1.15/messages/en/LC_MESSAGES/mailman.mo",
0xFFBFE908) Err#2 ENOENT
fstat64(9, 0xFFBFECC8) = 0
fstat64(9, 0xFFBFEB70) = 0
ioctl(9, TCGETA, 0xFFBFEC54)Err#25 ENOTTY
write(9, " < ! D O C T Y P E H T".., 8192) = 8192
write(9, "\n\n\n\n\n\n\n\n\n\n\n\n".., 2188) = 2188
close(9)= 0
Joseph Brennan
Columbia University Information Technology
--
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] Logo in posts
something tricky with an IFRAME element to hold the original message Thanks to spammer activity a few years ago I think iframe is inactive or even cause for rejection on various mail systems. Joseph Brennan Columbia University Information Technology -- 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] DMARC and Reply-To lines with from_is_list munging.
Stephen J. Turnbull step...@xemacs.org wrote: Honestly, they (one of the principal DMARC spec authors works for Yahoo) ignored their own advice, imagine how well that would go over in some other industries. Let's not overlook Agari, which has a financial stake in offering a solution to the problem they helped create. Notice how many dmarc domains direct the reports to agari, from which, for a fee, they will get nice reports and metrics for their CIO to show around, reports that will show how many times their domain was faked. Agari has an interest in making those numbers big, and mailing lists help them do it. The Agari web page boasts how many users they protect, and it features the kind of slick writing that impresses people who don't know nuts and bolts. One of the great failings on Yahoo's part was introducing a Change without notice to those affected, not even their own customers (to my knowledge). Even sloppy business owners should know not to do that. Agari introduced Agari PRO April 1. Dmarc was pulled from standards track April 2. Yahoo implemented dmarc April 4. What was the rush? Let's have some perspective: nobody died this time. So true. In 100 years who will know the difference. Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- 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] Add PayPal to DNs publishing DMARC p=reject
Stephen J. Turnbull step...@xemacs.org wrote: No, the point is that a phishing mail with From: Chase Bank Customer Service serv...@chase.com.invalid will sail right past DMARC, as currently set up It will sail past people using modern mail clients, too, by which I include web mail and Outlook, since those people will see some variation on this-- From: Chase Bank Customer Service --so that it hardly matters what address is in the From line. This rewrite-- From: Chase Bank Customer Service serv...@chase.com serv...@chase.com.invalid --would produce a more informative result, and just about honor RFC 5322 where it says the mailbox of the author of the message should be in the From: field. But this is the Mailman discussion list. Joseph Brennan Columbia University Information Technology -- 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] Excessive bounces to list members on my list
Lindsay Haisley fmo...@fmp.com wrote: They don't have to. All they have to do is respect AOL's and Yahoo's DMARC p=reject record and bounce non-aligning email from these ESPs accordingly. I think Gmail is doing the same. It's a touch evil to make mail from aol and yahoo less deliverable than your own... but it's what they asked for. Joseph Brennan Columbia University Information Technology -- 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] DMARC and Gmail
[DMARC's words] o A silent discard, wherein the SMTP server returns a 2xy reply code implying to the client that delivery (or, at least, relay) was successfully completed, but then simply discarding the message with no further action. Naturally the people who can't read RFC5322 and understand that the From header line represents the writer of the message also can't read RFC5321 and grasp that a 2xy code signifies a responsibility that is well defined (sec 4.2.5). They're just making stuff up. And companies that fall for it betray their cluelessness. Joseph Brennan Columbia University Information Technology (N.B. They were so proud of using wherein that they got lost later in the sentence-- s/b discards not discarding.) -- 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] Emails from yahoo members, are getting rejected by yahoo, Service Unavailable.
It finally occurred to me that this affects routine forwarding too. Even if you implement SRS on the envelope, the header From is left alone, as per RFC 5322. It also affects a message from any of our users who authenticates with our user and password but prefers to send with a yahoo.com From line. To sum it up, any message with a yahoo.com header From is poison unless you can deliver it locally to your own systems. This simplifies matters, since it means a milter should check for any outgoing message with /yahoo.com/ in the From. The simplest action to implement would be to bounce. I'm still pondering implementation. That some other domain might implement the same approach as yahoo is a good point. It is best to generalize a problem.* *unless you're selling updates to virus signatures! Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- 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] Best solution to fix the yahoo problem?
In any event, I'm a unclear about the best solution (if there is one). My inclination is to refuse postings from addresses @yahoo.com, since accepting them will interfere with everyone's use of our list system. The only issue for me is precisely how to implement it. Joseph Brennan Columbia University I T -- 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] Emails from yahoo members, are getting rejected by yahoo, Service Unavailable.
Jim Popovitch jim...@gmail.com wrote: DMARC works off of SPF as well. Not really. SPF does not check the From: header line, and that's where the troubles begin with DMARC. Joseph Brennan Columbia University IT -- 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] DMARC issues
They're breaking RFC 822 / 5322. The From: field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message. [...] In all cases, the From: field SHOULD NOT contain any mailbox that does not belong to the author(s) of the message. I don't think we should compound that by changing the From line. Joseph Brennan Columbia University Information Technology -- 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] DMARC issues
Lindsay Haisley fmo...@fmp.com wrote: SPF inherently breaks mailing lists No, it doesn't. SPF checks the envelope sender, and when the list host is, say, lists.example.com, the envelope sender is something like listname-boun...@lists.example.com, and that can pass SPF. Mailman, Listserv, etc, all write their envelope sender that way. Joseph Brennan Columbia University Information Technology -- 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] Google Groups Migration API?
I wonder if anyone on this list can share a script to migrate Mailman archives to a Google group using the Groups Migration API announced about a year ago. I'm actually looking to move mbox files made by 2 or 3 other software packages, but, same solution should work. Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- 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] Rejected or bounced messages.
These three were stopped after RCPT, so the problem is not about content. Most likely the recipient address is not deliverable. m...@me.com: host mx6.me.com.akadns.net[17.158.8.114] said: 550 5.1.1 unknown or illegal alias: usern...@me.com (in reply to RCPT TO command) m...@cgocable.ca: host mx2.cgocable.ca[216.221.81.40] said: 550 #5.1.0 Address rejected. (in reply to RCPT TO command) m...@msn.com: host mx2.hotmail.com[65.55.92.168] said: 550 Requested action not taken: mailbox unavailable (in reply to RCPT TO command) The first one is the unusual case. m...@epdot.com: host mx1.megamailservers.com[216.251.32.71] said: 550 5.7.1 s01D0qcI004613 This message does not comply with required standards. (in reply to end of DATA command) I've never seen this error before. Google This message does not comply with required standards to find a lot of people speculating about what it means, going back to 2006. They all relate it to Exchange or Outlook, but mx1.megamailservers.com says it is running Sendmail 8.13.6, and this is not a standard sendmail error message. So it's a custom filter on megamailservers.com. Here's an example involving Mailman and megamailservers.com from 2007! http://list.web.net/archives/getsmart-l/2007-December/002525.html ... with complete message attached. I don't see anything wrong with it. Joseph Brennan Columbia University IT -- 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] Folding whitespace
Happy New Year (almost)! Archives show me that this topic went around a while back but I did not find a complete answer. It's not really a Mailman bug, but a Mailman choice between correct options. When the Subject is folded into more than 1 line, Mailman inserts whitespace in the form of a TAB character, at the start of the continuation lines. Outlook, when unfolding, removes the CR LF but leaves whatever whitespace is there, in this case a TAB, so people tell me it looks ugly. Microsoft, Microsoft... I noticed that in Mailman/Handlers/CookHeaders.py, we go out of our way to change email.header's continuation_ws from the default of one space to be one tab. Both are correct, since the standard just says whitespace, but if we used one space it would trick Outlook into doing the right thing. Why the tab? CookHeaders.py gets pretty hairy so I feel like I'm missing something. Joseph Brennan Columbia University Information Technology -- 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] Mailman reusing message-id, leads to duplicate message suppression
--On November 5, 2013 10:25:20 AM +0100 Ralf Hildebrandt ralf.hildebra...@charite.de wrote: Who's to blame? Mailman for re-using the message-id? Exchange for dropping the second mail on the floor? The messages are duplicates, so they should have the same Message-ID. Whether to suppress delivery of duplicates is the choice of an end user, or a system administrator, or a software designer. I don't know which applies to Exchange. But in order to allow the choice, which is correctly a choice to be made at the receiving end, the dups have to be sent with the same Message-ID. I wouldn't say 'blame'. Joseph Brennan Columbia University I T -- 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] Performance issues with 12K subscribers and 14K subscribers and personalized footers.
Worth noting, Mailman is a lot faster if you don't send to 1 at a time. If they're all at the same domain, like our mass mail to staff and students, it is really fast: smtp to for 25570 recips, completed in 39.777 seconds smtp to for 41153 recips, completed in 84.754 seconds Even if they are at many different domains it does well: smtp to for 2016 recips, completed in 158.363 seconds smtp to for 2199 recips, completed in 701.392 seconds Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- 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] mails without MIME delimiter break when sent through mailman
--On May 16, 2013 10:48:31 +0200 Jan Lausch jan.lau...@gmx.de wrote: Some MUAs send picture-attachments not seperated by MIME-delimiters, but by begin and end. That's an ancient pre-MIME encoding called uuencode. I am amazed that any modern software would create it. Joseph Brennan Columbia University Information Technology -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] receive your own posts problem
I think he is saying that his mailing list subscribers subscribed to gmail do not receive a copy of they own mail. fir this we do not have any solution :-) The solution, or workaround I would say, is to change the Message-ID. Possibly, a milter could do this on the way in on the Mailman host. Maybe add a fixed string to what's already there. However this might have some impact on non Gmail users that does not come to mind immediately, so I am NOT saying to do this. Joseph Brennan Columbia University Information Technology -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Hide sender but keep reply-to sender address?
- Andrei - tucsonand...@gmail.com wrote: I would like members to receive email with From: Mailing List Name How will people know who wrote each message? Joseph Brennan Columbia University Information Technology -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Google mail servers reply Multiple destination domains per transaction is unsupported
Mark Sapiro m...@msapiro.net wrote: I am curious. As a Google Apps for Edu customer using Google servers to relay outgoing mail, do you see the From: header and envelope sender rewriting I report at http://mail.python.org/pipermail/mailman-users/2013-February/074748.html ? The Mailman host uses localhost as its smtp server. No problem! The problem described there is relevant to small organizations that do not have their own infrastructure. Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Google mail servers reply Multiple destination domains per transaction is unsupported
Stephen J. Turnbull step...@xemacs.org wrote: I bet they think it's an anti-spam measure. None of the big services likes to talk much about that. That's what frontline helpdesk told me, but no one could explain how it reduces spam. It beats me why, say, 6 recipients at one domain is less spammy than 6 recipients at two domains. The reverse might even even be true, since spammers seem to sort by domain not by mx server. but they confirmed it is not considered a bug, it was done deliberately. Can you confirm that this is happening at your outgoing MTA (ie, the first Google MX you encounter when submitting as a Google customer)? We run our own smtp servers. They determine where each user's mail goes. Some users are on Google Apps, so we re-send their mail to Google's MX address. That's when the fun begins. What I demonstrated is what happens when any host anywhere connects to Google's MX address and tries to send to addresses at two domains both hosted by Google. These are the hosts: $ host -t mx gmail.com gmail.com mail is handled by 5 gmail-smtp-in.l.google.com. gmail.com mail is handled by 30 alt3.gmail-smtp-in.l.google.com. gmail.com mail is handled by 10 alt1.gmail-smtp-in.l.google.com. gmail.com mail is handled by 40 alt4.gmail-smtp-in.l.google.com. gmail.com mail is handled by 20 alt2.gmail-smtp-in.l.google.com. I'm just guessing, but in practice is this issue restricted to mailing lists and other software that automatically mails to several users? Did they perhaps say you should be using the submission protocol (port 587) No, it was just a non-Google host trying to send mail to two addresses hosted on Google. That's all it takes to get that response. The reason I ask is that surely academic users regularly send mail personally to recipients at multiple domains. Of course! I used columbia.edu and barnard.edu as an example because the two schools are very closely affiliated. We first noticed this when an undergrad club president wanted to know why the members at one school got their mail right away and the others were delayed about 20 minutes. The answer is more or less because Google is weird. Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Google mail servers reply Multiple destination domains per transaction is unsupported
Max Pyziur p...@brama.com wrote: We received the following while sending out a newsletter/notification to a 6,000+ email list: 451 4.3.0 try again. ac8si27848234obc.211 - gsmtp Deferred: 451-4.3.0 Multiple destination domains per transaction is unsupported. Please ... while talking to aspmx.l.google.com This reads like a configuration issue on the those businesses and educational institutions who rely on Google mail servers. Is there a way for the sender (us) to be whitelisted, or is this matter handled at the receivers' end? I reported this a few months ago, as a Google Apps for Edu customer, and Google refuses to fix it. I spent a couple of weeks back and forth with several people, and I got beyond the first line helpdesk. None of them could give me a good explanation, but they confirmed it is not considered a bug, it was done deliberately. It means that if you send to two domains, both hosted at Google, they will accept only the first domain. To spell it out: rcpt to:n...@columbia.edu 250 2.1.5 OK k17si2328403qct.207 - gsmtp rcpt to:n...@barnard.edu 451-4.3.0 Multiple destination domains per transaction ... The lucky domain named first gets their messages right away, and the others have to wait until you run the queue. Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Need to see sender of post to my list
How can I find out, while maintaining privacy so that addresses are not exposed to the list at large? The system administrator can see it in /var/log/maillog or syslog. Joseph Brennan -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
--On Saturday, February 16, 2013 8:08 AM -0500 Tanstaafl
tansta...@libertytrek.org wrote:
On 2013-02-15 10:25 AM, Joseph Brennan bren...@columbia.edu wrote:
elsif
(/^from:.*+(bounce|do-not-reply|facebook|linkedin|list-|myspace|twitter)
/i) { $logger-debug(Multi-string From header matching $1: $2 found;
exiting); exit (0); }
This 'if' block is just a bunch of separate one line tests that, if any
of them match, result in the vacation response not being sent, so it
doesn't really matter what is above them (they are all the defaults, this
is the only line I am modifying)...
Not exactly. If you chain them with elsif then the conditions are tested
in order until one matches, and any after that are not tested. If one of
the earlier conditions matched then your rule would never match.
Remove the + mark (and learn what .* means) and you're probably done.
In the debug statement, $1 will be the string in ( ) that matched, but
$2 is not defined since there is no other ( ) string.
Joe Brennan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
elsif
(/^from:.*+(bounce|do-not-reply|facebook|linkedin|list-|myspace|twitter)/i)
{ $logger-debug(Multi-string From header matching $1: $2 found;
exiting); exit (0); }
Examine the logic of the 'if' and any 'elsif' above this line.
I am uncertain what /.*+/ would do. Remove either * or +.
Otherwise this looks reasonable to me.
Joseph Brennan
Columbia University Information Technology
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Amazon SES and Verified Senders
This is not a practical comment, but... I am amazed Amazon is checking the header From instead of the header Sender and envelope sender... and recommending breaking standards to get around what they are doing. They not only break mailing lists but the types of forwarding that preserve the original From header. RFC 2822: The From: field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message. The Sender: field specifies the mailbox of the agent responsible for the actual transmission of the message. The latter, and the envelope sender, is what they should care about. All right, enough, back to real life where you just have to deal with crazy stuff you can't control... Joseph Brennan Columbia University Information Technology -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
