Another thought would be, just another filter thats reporting wrong. Have you sent your self the same message and checked the message size>? Just to be sure it was too big? What size do you have your list set for? Should be enough for a normal digest, are your message that big? I have people who write so much its like a book, near onto 20K and post. Dan On 04/14/2018 11:16 AM, David E. Cann wrote: > Lynne, > > > > I use Outlook 2016 (part of MS Office 365) as an email client, and email is downloaded to it from my ISP. To post to any RW list I FIRST convert the blank new message TO PLAIN TEXT first before writing the first word. I may be wrong here, but isn't THAT KIND OF TEXT MESSAGE rather "bloated" in size compared to one that has always been plain text "from birth." Like many of you, I am now following these steps to send "welcome" messages to ALL of my lists as Anne has requested, but so far 100% of them, EVERY ONE OF THEM WITHOUT EXCEPTION,

Not all email works the same. Not all members have that savvy. List members should be notified that ( before ) replying to the digest, to make the proper subject line >reason.date>place or what complies, thus snipping out  the pertaining part of the topic. This was one of the reasons that in the past we tried to set incoming size to about 20 K so those with out savvy would not get posted.    Members should ( never ) post subject line ( digest) I have always notified those that did and nicely explained how to post from digest Your right about snipping and posting, but it don't work on the masses. BTW I had a post with a perfect digest in tact and as it should be this moring. Dan On 04/14/2018 11:13 AM, Marleen Van Horne wrote: > In most e-mail software, if you highlight the passage you are replying > to before you open the Write box, the highlighted passage will appear > in the write box. > > Quoting entire digest message over and over again is rude and > inconsiderate. > > Most subscribers when they see the subject is digest, just delete it > without reading it. > > Marleen Van Horne [snip]

Lynne, First of all, let me preface my comments by saying I IN NO WAY, SHAPE NOR FORM CLAIMING TO BE AN EXPERT on IT work or anything at all remotely knowledgeable about what I am talking about. I am simply an old (75) geezer who has been a List Owner for 20 years now (or whatever else the title was at any given time). WITHOUT any training, what little I have learned in two decades of doing this was learned through osmosis. A chimpanzee could have learned as much in the same time if you get him to repeat it enough times. Now then, all that said in my background, please let me tell you why I think I can tell you "YES" that I may well be one of those people who has had (and continues to have) messages rejected due to size despite changing my list settings per Anne's precise directions. I use Outlook 2016 (part of MS Office 365) as an email client, and email is downloaded to it from my ISP. To post to any RW list I FIRST convert the blank new message TO PLAIN TEXT first before writing the first word. I may be wrong here, but isn't THAT KIND OF TEXT MESSAGE rather "bloated" in size compared to one that has always been plain text "from birth." Like many of you, I am now following these steps to send "welcome" messages to ALL of my lists as Anne has requested, but so far 100% of them, EVERY ONE OF THEM WITHOUT EXCEPTION, has require me to then go to the Held Messages filter despite the fact I am a subscriber just like everyone else is despite the fact my filters are set to allow all subscribers through freely. If all of my assumptions are correct, and my "bloated Outlook plain text" messages THAT HAVE GOTTEN THROUGH PRIOR TO THE CURRENT MAILMAN 3 was installed to gum up the works including UNDER MAILMAN 2.17, then something in the current filters needs to be fixed or tweaked to make it DO WHAT ALL OF IT'S PREDECESSORS WERE ABLE TO DO? Now then, how do we get someone at RW to at least "take off the blinders" long enough to stop blaming us for setting the tweaks wrong or otherwise causing the problem long enough to examine the issue and resolve it one way or another without any more guesswork, hmmmmm? ☹ David -----Original Message----- From: Lynne <[email protected]> Sent: Saturday, April 14, 2018 1:01 PM To: Listowners list for Rootsweb list admins and moderators <[email protected]> Subject: [LO]Re: na and subscriber posts Thanks, Dan, but I'm really curious to know if Janet or anyone else has had a message rejected because of size. Lynne On 4/14/2018 11:44 AM, DJ wrote: > https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/modera > tion.html > > Lots of help here. If you can find it. > > > On 04/14/2018 06:53 AM, Lynne wrote: >> Janet, are you saying that with the new system you are getting >> notifications of posts that are too large to post? If that's the >> case, where are the settings in MailMan to change the size of >> acceptable posts? The only notifications I've received are N/A or >> not a member. >>

In most e-mail software, if you highlight the passage you are replying to before you open the Write box, the highlighted passage will appear in the write box. Quoting entire digest message over and over again is rude and inconsiderate. Most subscribers when they see the subject is digest, just delete it without reading it. Marleen Van Horne

No, don't do that. Let them snip, but don't turn off the part that tells us what they are replying to, just makes a mess. wrong idea.   The footers set up for all lists are a problem tho, too big, too many links. Dan On 04/14/2018 10:57 AM, Marleen Van Horne wrote: > I have had several messages held for size.  They are usually replies > to digests that have been quoted over and over again.  The default > size is 40k which is plenty big enough.  I think it is rude of > subscribers to quote entire messages over and over when replying. I > warn my subscribers not to do it, and when it happens I do not post > the messages. > > You can actually click on the message and see what it is. > > This happens because most e-mail software comes set to quote messages > being replied to and has to be turned off.  I alert my subscriber to > this, and if they do not turn it off, I do not post these excessive > messages for them. > > Also, I have not changed any of the options that came with the new > software, and I am not having any of the troubles the rest of you are > having.  My lists that actually have active subscribers are working > like they are supposed to work. > > Marleen Van Horne  [snip]

X-MailFrom: pjroots(a)att.net X-Mailman-Rule-Hits: max-size X-Mailman-Rule-Misses: dmarc-mitigation; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; news-moderation; no-subject; suspicious-header On 04/14/2018 10:44 AM, Lynne wrote: > Pat, I don't see in your archived post where you say the message was > held for being too large or that you received a "too large" > notification.  I just see that it was another N/A.  What am I missing? > > Thanks. > > Lynne > > On 4/14/2018 1:33 PM, Pat Asher wrote: >> At 01:00 PM 4/14/2018, Lynne wrote: >>> Thanks, Dan, but I'm really curious to know if Janet or anyone else >>> has had a message rejected because of size. >>> >>> Lynne >> >> Yes. See >> https://lists.rootsweb.ancestry.com/hyperkitty/list/[email protected]/thread/AANY6BW7VHKE4GCS5ZGMRCNUHM6MUUV7/ >> > > _______________________________________________ > > _______________________________________________ > You are receiving this email because you have registered with RootsWeb > Mailing Lists.  Manage your email preferences at: > https://lists.rootsweb.ancestry.com/postorius/accounts/subscriptions/ > > To unsubscribe send an email to > mailto:[email protected]?subject=unsubscribe&body=unsubscribe > > View the archives for this list at: > https://lists.rootsweb.ancestry.com/hyperkitty/list/[email protected]/ > > Your privacy is important to us.  View our Privacy Statement at > https://www.ancestry.com/cs/legal/privacystatement for more > information.  Use of RootsWeb is subject to our Terms and Conditions > https://www.ancestry.com/cs/legal/termsandconditions > > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community >

I have had several messages held for size. They are usually replies to digests that have been quoted over and over again. The default size is 40k which is plenty big enough. I think it is rude of subscribers to quote entire messages over and over when replying. I warn my subscribers not to do it, and when it happens I do not post the messages. You can actually click on the message and see what it is. This happens because most e-mail software comes set to quote messages being replied to and has to be turned off. I alert my subscriber to this, and if they do not turn it off, I do not post these excessive messages for them. Also, I have not changed any of the options that came with the new software, and I am not having any of the troubles the rest of you are having. My lists that actually have active subscribers are working like they are supposed to work. Marleen Van Horne

Pat, I don't see in your archived post where you say the message was held for being too large or that you received a "too large" notification. I just see that it was another N/A. What am I missing? Thanks. Lynne On 4/14/2018 1:33 PM, Pat Asher wrote: > At 01:00 PM 4/14/2018, Lynne wrote: >> Thanks, Dan, but I'm really curious to know if Janet or anyone else >> has had a message rejected because of size. >> >> Lynne > > Yes. See > https://lists.rootsweb.ancestry.com/hyperkitty/list/[email protected]/thread/AANY6BW7VHKE4GCS5ZGMRCNUHM6MUUV7/ >

At 01:00 PM 4/14/2018, Lynne wrote: >Thanks, Dan, but I'm really curious to know if Janet or anyone else >has had a message rejected because of size. > >Lynne Yes. See https://lists.rootsweb.ancestry.com/hyperkitty/list/[email protected]/thread/AANY6BW7VHKE4GCS5ZGMRCNUHM6MUUV7/ Pat A.

A page I am reading. http://grokbase.com/t/python/mailman-users/09684zq6w7/approve-all-held Dan

Not me so far. Dan On 04/14/2018 10:00 AM, Lynne wrote: > Thanks, Dan, but I'm really curious to know if Janet or anyone else > has had a message rejected because of size. > > Lynne

Thanks, Dan, but I'm really curious to know if Janet or anyone else has had a message rejected because of size. Lynne On 4/14/2018 11:44 AM, DJ wrote: > https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/moderation.html > > Lots of help here. If you can find it. > > > On 04/14/2018 06:53 AM, Lynne wrote: >> Janet, are you saying that with the new system you are getting >> notifications of posts that are too large to post?  If that's the >> case, where are the settings in MailMan to change the size of >> acceptable posts?   The only notifications I've received are N/A or >> not a member. >>

t 10:44 AM 4/14/2018, DJ wrote: >https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/moderation.html >Lots of help here. If you can find it. I found it. The parameter max-size appears to be a universal setting. It may also be a setting for each user which is the reason some gets through and some don't. setting the value of this check parameter to 0 will allow all message to pass the filter. Message size The message-size rule matches when the posted message is bigger than a specified maximum. Generally this is used to prevent huge attachments from getting posted to the list. This value is calculated in terms of KB (1024 bytes). >>> mlist = create_list('[email protected]') >>> rule = config.rules['max-size'] >>> print(rule.name) max-size For example, setting the maximum message size to 1 means that any message bigger than that will match the rule. >>> mlist.max_message_size = 1 # 1024 bytes >>> one_line = 'x' * 79 >>> big_body = '\n'.join([one_line] * 15) >>> msg = message_from_string("""\ ... From: [email protected] ... To: [email protected] ... ... """ + big_body) >>> rule.check(mlist, msg, {}) True Setting the maximum message size to zero means no size check is performed. >>> mlist.max_message_size = 0 >>> rule.check(mlist, msg, {}) False Of course, if the maximum size is larger than the message���s size, then it���s still okay. >>> mlist.max_message_size = msg.original_size/1024.0 + 1 >>> rule.check(mlist, msg, {}) False At 10:44 AM 4/14/2018, DJ wrote: >https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/moderation.html >Lots of help here. If you can find it.

I am assuming. My address [email protected] ( is ) getting stuck in the filter since it has not posted any messages since yesterday early 827 am/ Dan

https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/moderation.html Lots of help here. If you can find it. On 04/14/2018 06:53 AM, Lynne wrote: > Janet, are you saying that with the new system you are getting > notifications of posts that are too large to post?  If that's the > case, where are the settings in MailMan to change the size of > acceptable posts?   The only notifications I've received are N/A or > not a member. > > Lynne > > > On 4/14/2018 6:43 AM, Janet Crawford wrote: >> Meryl, Often one can get a "too big" post when the sender is using Rich >> Text and not Plain Text. I just reject them and ask that they change >> it to >> Plain. It's easy. Just copy the message and post it to something like >> Notepad which will drop off the coding. Then recopy the message off >> Notepad >> and paste it to a Rootsweb message. Takes 5 seconds. >> >> Janet > > _______________________________________________ > > _______________________________________________ > You are receiving this email because you have registered with RootsWeb > Mailing Lists.  Manage your email preferences at: > https://lists.rootsweb.ancestry.com/postorius/accounts/subscriptions/ > > To unsubscribe send an email to > mailto:[email protected]?subject=unsubscribe&body=unsubscribe > > View the archives for this list at: > https://lists.rootsweb.ancestry.com/hyperkitty/list/[email protected]/ > > Your privacy is important to us.  View our Privacy Statement at > https://www.ancestry.com/cs/legal/privacystatement for more > information.  Use of RootsWeb is subject to our Terms and Conditions > https://www.ancestry.com/cs/legal/termsandconditions > > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community >

Some notes or observations. note - When Anne posted to me in private - my red flag went off in thunderbird to check preferences.    Something in her message set off the warning.  None of my bouncing people have set off the flag. One thing to check; how high is your sending security and fire walls and anti virus?  Should be low level medium for what we use for email. We all have the same setting in our admin pages ( headers ) Some place in the caught headers, might be the real cause. Plenty to study in there. Mailman setup, radio and other settings and * and mail man and which mail man runs and was set to in setup. How ever I don't think that is the problem because I think it is personal. Log a note, what servers are caught, we all been through the black listing before. Most of us long time list admin, should be experienced enough to back up off all complaints and look for the real cause. Think about the above. I am using Linux, not microsoft, have no problems. Mailman and thunder bird and mozilla are linux products I was, a ms home consultant in my neighborhood helped many people with so many problems simple and complex.  Something tells me this is a simple solution, because we have people posting normally that no changes been made to their mailman settings by the admin.  So,it just looks like it is in one area, headers and that includes the fire walls and anti virus and security settings could be possible things to look over. Find out what the reasons in the headers mean. Dan M

On 04/14/2018 06:53 AM, Lynne wrote: > Janet, are you saying that with the new system you are getting > notifications of posts that are too large to post?  If that's the > case, where are the settings in MailMan to change the size of > acceptable posts?   The only notifications I've received are N/A or > not a member. > > Lynne  One thing to look for in na. bcc 'could' cause an implicit and catch as na. just one idea to look for. Dan

Janet, are you saying that with the new system you are getting notifications of posts that are too large to post? If that's the case, where are the settings in MailMan to change the size of acceptable posts? The only notifications I've received are N/A or not a member. Lynne On 4/14/2018 6:43 AM, Janet Crawford wrote: > Meryl, Often one can get a "too big" post when the sender is using Rich > Text and not Plain Text. I just reject them and ask that they change it to > Plain. It's easy. Just copy the message and post it to something like > Notepad which will drop off the coding. Then recopy the message off Notepad > and paste it to a Rootsweb message. Takes 5 seconds. > > Janet

Thats not happening.  I am set to send as received, I have seen little to no rich text messages, either in private or list. I write to people that cant post, only one replied in rich text. How ever one of my listowner address are set to rich, they still post. plain 2kb converted to rich don't add enough to hit 20 to 60 kb.  Not sure I plan to use reject either. Dan On 04/14/2018 03:43 AM, Janet Crawford wrote: > Meryl, Often one can get a "too big" post when the sender is using Rich > Text and not Plain Text. I just reject them and ask that they change it to > Plain. It's easy. Just copy the message and post it to something like > Notepad which will drop off the coding. Then recopy the message off Notepad > and paste it to a Rootsweb message. Takes 5 seconds. > > Janet > >

And was not max size.. I seen those. headers and message size don'y add that much. Still mainly in kb. Dan On 04/14/2018 05:58 AM, Gene Phillips wrote: > That was my thought 5 days ago after looking at the headers of a message that was held for N/A. > All the messages I've received for moderation for N/A all have the following line in the headers > > X-Mailman-Rule-Hits: max-size > > Gene > > > At 04:49 AM 4/14/2018, Meryl Yost wrote: > >> Are we getting messages held because they are too large? Do we need a >> setting to change the size? > _______________________________________________ > > _______________________________________________ > You are receiving this email because you have registered with RootsWeb Mailing Lists. Manage your email preferences at: https://lists.rootsweb.ancestry.com/postorius/accounts/subscriptions/ > > To unsubscribe send an email to mailto:[email protected]?subject=unsubscribe&body=unsubscribe > > View the archives for this list at: https://lists.rootsweb.ancestry.com/hyperkitty/list/[email protected]/ > > Your privacy is important to us. View our Privacy Statement at https://www.ancestry.com/cs/legal/privacystatement for more information. Use of RootsWeb is subject to our Terms and Conditions https://www.ancestry.com/cs/legal/termsandconditions > > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > . >