Thanks for the help. Should we take this off list, since this seems unique, or do you think the list would be interested?
On 5/10/2011 9:15 AM, Ralf Hildebrandt wrote: > * Dennis Putnam <d...@bellsouth.net>: >> I have gotten some feedback from my list members. It seems no one got >> the message although the log shows they all were accepted by my ISP. I'm >> stuck. > So you'll have to got the bcc route and find out WHAT PHRASE EXACTLY > causes the mail to be stuck. > > I can help, since I find this highly interesting :) >> On 5/10/2011 5:08 AM, Ralf Hildebrandt wrote: >>> * Dennis Putnam <d...@bellsouth.net>: >>>> As a followup, there is something definitely weird going on but I am >>>> pretty sure it is not a mailman problem per se. I am still waiting for >>>> some feedback from my list members but it appears that the problem is my >>>> own email address. >>> Very very odd. Meaning you're the only person NOT to receive the mails? >>> >>>> I can and do get other messages as both the list owner and a member but >>>> not this particular one. However, as I said before, the message is >>>> definitely being accepted by my ISP's mail server. This is probably >>>> going to be one of those unsolvable problems with my ISP unless there >>>> are other list members that did not receive the reminder. >>>> >>>> Thanks for your help. >>>> >>>> On 5/5/2011 10:05 AM, Ralf Hildebrandt wrote: >>>>>>> Well, you can use: >>>>>>> >>>>>>> recipient_bcc_maps = hash:/etc/postfix/recipient_bcc_maps >>>>>>> >>>>>>> containing >>>>>>> d...@bellsouth.net someaccount@localhost >>>>>>> then "postmap /etc/postfix/recipient_bcc_maps" >>>>>>> >>>>>>> which would then deliver a copy of EVERY mail sent to >>>>>>> d...@bellsouth.net in copy to someaccount@localhost >>>>>> Ohhhh! You meant in Postfix. I thought you were talking about mailman. >>>>>> Interesting idea, I'll give it a try. >>>>> All you THEN have to do is to coax mailman into actually sending such >>>>> a mail :) >>>>> >>>>>>> Once you have a copy of the faulty mail at the mailbox for >>>>>>> someaccount@localhost you can always do stuff like: >>>>>>> >>>>>>> cat themail.txt | sendmail -i -f mailman-boun...@bellsouth.net >>>>>>> d...@bellsouth.net >>>>>> Another good idea I didn't think of that I can try with any text. That >>>>>> would at least confirm if from is the culprit. >>>>> You can then use an editor to remove portions from, the email UNTIL it >>>>> arrives at bellsouth! >>>>> >>>>>> Thanks for the suggestions. I'll try them and get back if nothing >>>>>> definitive shows up. >>>>> Just let me know if you encounter any problems. I find this highly >>>>> interesting :) >>>>> >>> >> > >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------ 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
