![](https://secure.gravatar.com/avatar/9d2b2694f1f8fea795a902fa3a2bd3a3.jpg?s=120&d=mm&r=g)
Hi,
I recently sent an invite to an unknown third party. The invite came from my mailman list, we gave full particulars of who and where we are. We specifically advise that they are not at this stage subscribed to anything and will have to follow the detailed instructions (ie confirm) if they want to join the list. The third party is in the same trade as us, and deals with the same specialities, a third party customer had given me their address in good faith.
This week my ISP contacts me with an upstream request from the national backbone provider to in effect desist from sending spam.
Looking at the email returned, it was to an @yahoo address, spamcop seems to have detected spam on the basis of it being a mailman message, I am not certain that it was not initiated by the recipient but the official complaint originated from yahoo it seems (who should surely know better).
Subject: [196.26.208.190] Yahoo Abuse Report - FW:confirm 3a35c56b531368da533112d96a9cb24c17cf6961
As I said in my reply, this is hardly spam, I did not send it out to half a million addresses purchased on a cd. This makes a mockery of genuine spam prevention efforts when one email from a genuine address can be allowed to cause this. It
I don't want to make a mountain out of a molehill, but what can I do about this. Is this a common occurence? Are invites from mailman now considered fair game for spam detection software and humans alike?
bestest Anne
![](https://secure.gravatar.com/avatar/682b7115267957111b90d648ac5ab780.jpg?s=120&d=mm&r=g)
On Thu, 26 Apr 2012 09:39:44 +0200 Anne Wainwright <anotheranne@fables.co.za> wrote:
Hello Anne,
As I said in my reply, this is hardly spam, I did not send it out to
You sent out an Unsolicited Commercial Email (UCE) which, to most people, constitutes SPAM. Whether you sent it to one person or one million is irrelevant.
-- Regards _ / ) "The blindingly obvious is / _)rad never immediately apparent" The public gets what the public wants Going Underground - The Jam
![](https://secure.gravatar.com/avatar/2d8b084fbf3bb480d8a3b6233b498f4f.jpg?s=120&d=mm&r=g)
On 4/26/12 3:39 AM, Anne Wainwright wrote: person giving you their email address is normally NOT good enough of a reason for you to send them the invite. Protocol would be for that third party to contact the prospect directly (if they really did think that your list might be worthwhile for them) and point them to that list. One key factor here is that YOU are an "unknown" to the person you sent the invite to, and one should NEVER follow a link or reply to an email from an "unknown".
This sort of spam report tends to come because the person receiving the message has themselves hit the "this is spam" button, and them pressing it is a reasonable sign that you had over stepped the bounds by sending them the message. It is also quite possible that Yahoo has received multiple complaints (the one being quoted being an example), and this is what has prompted them to contact your ISP with the complaint.
-- Richard Damon
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On Apr 26, 2012, at 2:39 AM, Anne Wainwright wrote:
Okay, so first off, you did send the message unsolicited. That is generally considered to be one of the most basic hallmarks of spam -- the recipient got something that they never asked for.
If you had a prior direct business relationship with that recipient, and they had expressed interest in being on your mailing list at some point in time in the past, then you could potentially claim that the message was not spam. Outside of that scenario, you fail test #1 -- go straight to jail, do not pass "Go", do not collect $200.
That said, there are a lot of clueless Yahoo! customers, many of whom have actively asked to be on mailing lists that are hosted on python.org using Mailman, and yet they still do stupid stuff like clicking on the "THIS IS SPAM" button when the message in question was a regular message from the list that was posted as part of a discussion that they themselves were participating in -- clearly not spam.
If I were actively involved in the day-to-day operations of the python.org mail system, given the amount of complaints like this that we continue to get from Yahoo! on a daily basis, I would be strongly inclined to simply ban all subscriptions from addresses at yahoo.com -- just like many mailing list administrators used to do for aol.com. Yahoo is just too poorly administered, there are way too many clueless users, and the company doesn't begin to bother to educate their users as to when they should not click the "THIS IS SPAM" button.
However, the fact that Yahoo! is hopelessly clueless does not absolve you of the crime that you freely admit that you are guilty of.
If you wish to persist in your spammy ways, then we can make sure that your address gets unsubscribed from this list, and that your domain gets banned from sending e-mail to python.org.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
As an additional FYI in this thread, Mailman sends invitations with a "Precedence: bulk" header. This can only be changed by modifying code.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/334b870d5b26878a79b2dc4cfcc500bc.jpg?s=120&d=mm&r=g)
On Thu, Apr 26, 2012 at 4:39 PM, Anne Wainwright <anotheranne@fables.co.za> wrote:
I recently sent an invite to an unknown third party.
Normally I agree with Brad Knowles on this kind of thing, but this time I can't go 100%.
People regularly do make contacts with third parties that they have not previously met, with the intent of arranging mutually beneficial activities. Heck, if you think about it, that's what you're doing every time you make a first post to a mailing list. There is nothing wrong with that in general, and there is nothing (morally) wrong with that when done by email, to recipients carefully selected for high probability of getting some interest. (From this point of view, "double opt in" is just a useful, fail-safe litmus test for recipient interest, not the moral imperative some seem to think it is.) Obviously you think your mailing has passed that test.
That said, it's bad business IMO (except in cases like a double opt-in mailing list where every person has explicitly indicated interest in receiving list posts). What *you* think isn't what really matters. When done by mutual acquaintance, by phone, or even by form letter, there are significant costs to making such contacts, especially when you do the phoning yourself. You must really value the recipient to go to such expense, even if small.
There are no such costs to email, which means that using email as a medium puts you in company with some real scum, who send out unsolicited email indiscriminately, sometimes laden with malware or phishing URLs. It's unfair, I suppose, but I'm not surprised if you get classed with the scum on the basis of the only information the recipient has about you as a businessperson: an email that they didn't ask for.
There's another problem. The ISPs are a pretty quick-on-the-trigger bunch, too, as a couple of posters have noted. But if you're not running a double opt-in list, you're not going to be able to get them to change your minds about your list. Everything I know about them, they'd rather lose half their clients' mail than get a complaint about spam. And their customers are not well-informed enough to doubt the ISPs when they blame somebody else for any problems with mail. Except spam -- it's obvious to the customer that the spam is bogus, why is it so hard for the ISP? You see their incentive, I suppose, and it works against legitimate businesses unless they follow the ISPs' rules.
I conclude that for an honest business, anything is a better way than email to make first contact with a third party who doesn't know you.
Regards, Steve
![](https://secure.gravatar.com/avatar/9d2b2694f1f8fea795a902fa3a2bd3a3.jpg?s=120&d=mm&r=g)
Hi,
Have been offline for a goodly while hence tardy response to the thread that I started. comments lower down, but thanks to Brad, Richard, Mark, & Stephen for their input.
On Fri, May 04, 2012 at 12:33:24AM +0900, Stephen J. Turnbull wrote:
I have sinned and stand repentant. I hate spam as much as anyone and we get plenty to deal with. Somehow the Viagra and get rich emails didn't seem to stand on the same level as a once-off invite. But as pointed out clearly an unasked for email from an unknown party is just that.
In the light of the spam that we receive, which varies from worldwide mass mailings (viagra supplies from pharmacies in the USA, say) to lesser attempts (local suppliers of this & that product or service) there is no fuzzy line where the definition of spam rests, and much against my normal judgement where I see things in shades of grey, I am forced to make this a black and white decision on the basis of the definitions of spam made in the replies.
So will make sure that this doesn't occur again and will make clear the distinction to other staff handling these issues.
As an aside, I have to ask whether the 'invite' feature in Mailman has a function. If one has to have been in existing contact such that you can ask them if they would not object to an invite then one is in fact at the point where you can ask them point blank if you can subscribe them.
Typically someone may query whether we have a specific book title, or whether one listed on an online catalogue is still available. The usual drill if this is unavailable is to say so and then recommend that they join our mailing list for which we will send details (an 'invite') on the basis that it may show up on a future catalogue. I do not see this as sending spam. Maybe you differ?
I guess this may be considered a bit off-topic, comments welcome direct if you feel this is so.
bestest Anne
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
Anne Wainwright wrote:
My cycling club has a general discussion list for which subscription requires approval because it's limited to club members. If a new or renewing member checks the "I want to join the club's email list" box on the application form, we send an invitation. This avoids the problem of subscribing the wrong person or an invalid address to the list because of typos or unreadable handwriting (yes, we still accept snail-mailed forms with checks, although it's not our preferred method).
Even when a club member emails the list owners asking to join the list, we sometimes send an invitation rather than just subscribing if we think there's a possibility the email was spoofed.
I'm sure there are other use cases where invitations rather than direct subscriptions are appropriate/prudent.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/334b870d5b26878a79b2dc4cfcc500bc.jpg?s=120&d=mm&r=g)
Anne Wainwright writes:
They don't, from the point of view of the sender or society at large. But for the recipient....
As an aside, I have to ask whether the 'invite' feature in Mailman has a function.
Sure. As Mark points out, it confirms the intention of the user to join, which gives you the "double opt-in" property that gives a conservative litmus test for "not spam".
I think it might be a useful question to ask, "how can the invite feature be made more functional?"
In particular, if you've written a careful email, answering an inquiry, I see nothing spammy about adding a Mailman invite to that ... if it were possible, which currently it isn't, from any mail client I know of. OTOH, you could write that email using Mailman's "invite" interface, but I bet you'd get tired of that real quick.
![](https://secure.gravatar.com/avatar/9d2b2694f1f8fea795a902fa3a2bd3a3.jpg?s=120&d=mm&r=g)
Hi,
For the record the following URL is of interest
http://www.spamhaus.org/consumer/definition/
This clearly makes the point that spam is defined by two factors
"A message is Spam only if it is both Unsolicited and Bulk"
and being who they are their definition must carry some weight. In terms of their definition my mailing was not spam. Still, and I think Stephen made the point, there is also the consideration of good business practice to be considered.
over & out for tonight.
Anne
On Thu, Apr 26, 2012 at 09:39:44AM +0200, Anne Wainwright wrote:
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On May 18, 2012, at 5:14 PM, Anne Wainwright wrote:
Actually, if you go back to Mark's message where he said:
As an additional FYI in this thread, Mailman sends invitations
with a "Precedence: bulk" header. This can only be changed by
modifying code.
Then you will note that the message you sent does actually qualify on both counts -- it was most definitely unsolicited (by your own account), and unless you modified the source code then Mailman definitely marked those invitations as "bulk".
Even if Mailman hadn't marked the messages as bulk per se, if you sent out invitations to more than one person, then that could also be classified as essentially being "bulk".
There are features in Mailman that can be misused and abused in a wide variety of ways, and it is the responsibility of the Site Administrator(s) and the List Administrator(s) to make sure that they operate the software in an appropriate manner.
For example, if you were using Mailman internally to your company and could guarantee that no one could ever get on any list unless they were an employee, then by the terms of the employment contract you might be able to do things that might otherwise be considered of a "spammy nature", like requiring that all employees be subscribed to certain lists that they can't unsubscribe from, sending out invitations to join mailing lists that they did not request, etc….
We have to allow for these kinds of things because not everyone uses Mailman in the same way for the same user community. And some types of actions are appropriate for certain user communities but not for others. We can't just disable or remove features simply because they are not appropriate for a particular user community.
In essence, you're asking us to protect you against yourself, and there is a limit to how much of that we can do. At least, there is a limit to how much we can do if we want to keep the software usable for other people.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 5/19/2012 2:13 AM, Anne Wainwright wrote:
Why would this not be set to 'list' rather than 'bulk'?
List posts are sent with Precedence: list. Notices from Mailman, e.g. held message notices to an admin, invitations and welcome messages to users, password reminders, etc. are all sent with Precedence: bulk.
Prior to Mailman 2.1, everything was sent with Precedence: bulk, even list posts.
Comments in the Mailman 1.0 code say
# semi-controversial: some don't want this included at all, others # want the value to be `list'.
RFC 2076 (Feb 1997) says the Precedence: header is "non-standard, controversial, discouraged". See the RFC <http://www.rfc-editor.org/rfc/rfc2076.txt> for the precise definition of these terms.
We probably shouldn't be adding it at all, but as to why, other than the above code comment, some things are sent with Precedence: bulk you'd have to ask John Viega or someone with more knowledge of the history than I have.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On May 19, 2012, at 4:13 AM, Anne Wainwright wrote:
According to RFC 2076, the "Precedence:" header is "Non-standard, controversial, discouraged." RFC 3834 says:
and:
Historically, the "Precedence:" header has generally only had one standard value that I know of, if it was used at all -- and that value is "bulk". The original intent of this header (and this setting) was to help automated systems that receive mail messages to determine whether or not a message was originated by a human being or was perhaps automatically generated or handled through a mailing list -- at the time, there was no such negative connotation to the word "bulk" and no one would have distinguished between "bulk" mail and mail sent through a "list".
Over the years, things have changed, but the usage of this particular header has only gotten murkier. Mailman is one of the few programs on the Internet that has been fairly consistent in the way it has handled this header.
Of course, Mailman is only handling one end of the conversation, and it can't control what people on the other end do with the header. If we change the way Mailman works in this regard, we might break existing programs. If we don't change the way Mailman works in this regard, people on the other end might not understand what is really intended.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
![](https://secure.gravatar.com/avatar/2d8b084fbf3bb480d8a3b6233b498f4f.jpg?s=120&d=mm&r=g)
On 5/18/12 6:14 PM, Anne Wainwright wrote:
I will point out that from the recipients point of view, a mailman invite looks to be "Bulk", they have no way to know if you sent it specifically to them or to a large list.
A place like spamhaus can use "bulk" as part of their criteria, and see if essentially the same message is sent out repeatedly, an individual recipient generally can not, so their version of the "bulk" criteria is does it look like a mass mailing.
One way around this is rather than us the mailman invite feature, write a personal email where you "invite" the person to subscribe, giving the url of the subscription page as a pointer. While you can't prevent someone from pressing the "This is spam" button, if you have done some pre-vetting to be sure the person is likely interested, and made the message clearly personal and not bulk, will minimize the chances of them doing so.
-- Richard Damon
![](https://secure.gravatar.com/avatar/70dbe67e0eb08a96d695871292b27eef.jpg?s=120&d=mm&r=g)
<...> << On 5/19/2012 10:46 AM, Richard Damon wrote:
I will point out that from the recipients point of view, a mailman invite looks to be "Bulk", they have no way to know if you sent it specifically to them or to a large list.
<...>
One way around this is rather than us the mailman invite feature, write a personal email where you "invite" the person to subscribe, giving the url of the subscription page as a pointer.>>
Even tho I'm with a cPanel instal by serious "dumb" luck I having been doing exactly that for over a decade since I started my 1st List which was actually "begged" for ;-) by a bunch of folks on another Public List which did/does not allow attachments. I have no clue as to why I didn't just Mass Subscribe. I sent out Personal Invites with the Subscribe URL. Something about the Mass Sub. just didn't "feel" right.
<< While you can't prevent someone from pressing the "This is spam" button,>>
I have just about reached the "breaking point" and maybe one (1) more and I'm gonna ban AOL (Yahoo not far behind these days) users.
<< if you have done some pre-vetting to be sure the person is likely interested, and made the message clearly personal and not bulk, will minimize the chances of them doing so.>>
Absolutely agreed, Richard ! ! Thank you for posting something in this thread that applies to MM Users such as myself who ARE stuck behind cPanel :-[ :-) ! !
Ed Please visit MY site at: www.justbrits.com
PS: Anyone interested in a slow ( 3- 4 /day) "Joke List" by MM, please drop me a note :-) ! ! Ooops, and/or a small Political List (Poly Sci101).
![](https://secure.gravatar.com/avatar/682b7115267957111b90d648ac5ab780.jpg?s=120&d=mm&r=g)
On Thu, 26 Apr 2012 09:39:44 +0200 Anne Wainwright <anotheranne@fables.co.za> wrote:
Hello Anne,
As I said in my reply, this is hardly spam, I did not send it out to
You sent out an Unsolicited Commercial Email (UCE) which, to most people, constitutes SPAM. Whether you sent it to one person or one million is irrelevant.
-- Regards _ / ) "The blindingly obvious is / _)rad never immediately apparent" The public gets what the public wants Going Underground - The Jam
![](https://secure.gravatar.com/avatar/2d8b084fbf3bb480d8a3b6233b498f4f.jpg?s=120&d=mm&r=g)
On 4/26/12 3:39 AM, Anne Wainwright wrote: person giving you their email address is normally NOT good enough of a reason for you to send them the invite. Protocol would be for that third party to contact the prospect directly (if they really did think that your list might be worthwhile for them) and point them to that list. One key factor here is that YOU are an "unknown" to the person you sent the invite to, and one should NEVER follow a link or reply to an email from an "unknown".
This sort of spam report tends to come because the person receiving the message has themselves hit the "this is spam" button, and them pressing it is a reasonable sign that you had over stepped the bounds by sending them the message. It is also quite possible that Yahoo has received multiple complaints (the one being quoted being an example), and this is what has prompted them to contact your ISP with the complaint.
-- Richard Damon
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On Apr 26, 2012, at 2:39 AM, Anne Wainwright wrote:
Okay, so first off, you did send the message unsolicited. That is generally considered to be one of the most basic hallmarks of spam -- the recipient got something that they never asked for.
If you had a prior direct business relationship with that recipient, and they had expressed interest in being on your mailing list at some point in time in the past, then you could potentially claim that the message was not spam. Outside of that scenario, you fail test #1 -- go straight to jail, do not pass "Go", do not collect $200.
That said, there are a lot of clueless Yahoo! customers, many of whom have actively asked to be on mailing lists that are hosted on python.org using Mailman, and yet they still do stupid stuff like clicking on the "THIS IS SPAM" button when the message in question was a regular message from the list that was posted as part of a discussion that they themselves were participating in -- clearly not spam.
If I were actively involved in the day-to-day operations of the python.org mail system, given the amount of complaints like this that we continue to get from Yahoo! on a daily basis, I would be strongly inclined to simply ban all subscriptions from addresses at yahoo.com -- just like many mailing list administrators used to do for aol.com. Yahoo is just too poorly administered, there are way too many clueless users, and the company doesn't begin to bother to educate their users as to when they should not click the "THIS IS SPAM" button.
However, the fact that Yahoo! is hopelessly clueless does not absolve you of the crime that you freely admit that you are guilty of.
If you wish to persist in your spammy ways, then we can make sure that your address gets unsubscribed from this list, and that your domain gets banned from sending e-mail to python.org.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
As an additional FYI in this thread, Mailman sends invitations with a "Precedence: bulk" header. This can only be changed by modifying code.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/334b870d5b26878a79b2dc4cfcc500bc.jpg?s=120&d=mm&r=g)
On Thu, Apr 26, 2012 at 4:39 PM, Anne Wainwright <anotheranne@fables.co.za> wrote:
I recently sent an invite to an unknown third party.
Normally I agree with Brad Knowles on this kind of thing, but this time I can't go 100%.
People regularly do make contacts with third parties that they have not previously met, with the intent of arranging mutually beneficial activities. Heck, if you think about it, that's what you're doing every time you make a first post to a mailing list. There is nothing wrong with that in general, and there is nothing (morally) wrong with that when done by email, to recipients carefully selected for high probability of getting some interest. (From this point of view, "double opt in" is just a useful, fail-safe litmus test for recipient interest, not the moral imperative some seem to think it is.) Obviously you think your mailing has passed that test.
That said, it's bad business IMO (except in cases like a double opt-in mailing list where every person has explicitly indicated interest in receiving list posts). What *you* think isn't what really matters. When done by mutual acquaintance, by phone, or even by form letter, there are significant costs to making such contacts, especially when you do the phoning yourself. You must really value the recipient to go to such expense, even if small.
There are no such costs to email, which means that using email as a medium puts you in company with some real scum, who send out unsolicited email indiscriminately, sometimes laden with malware or phishing URLs. It's unfair, I suppose, but I'm not surprised if you get classed with the scum on the basis of the only information the recipient has about you as a businessperson: an email that they didn't ask for.
There's another problem. The ISPs are a pretty quick-on-the-trigger bunch, too, as a couple of posters have noted. But if you're not running a double opt-in list, you're not going to be able to get them to change your minds about your list. Everything I know about them, they'd rather lose half their clients' mail than get a complaint about spam. And their customers are not well-informed enough to doubt the ISPs when they blame somebody else for any problems with mail. Except spam -- it's obvious to the customer that the spam is bogus, why is it so hard for the ISP? You see their incentive, I suppose, and it works against legitimate businesses unless they follow the ISPs' rules.
I conclude that for an honest business, anything is a better way than email to make first contact with a third party who doesn't know you.
Regards, Steve
![](https://secure.gravatar.com/avatar/9d2b2694f1f8fea795a902fa3a2bd3a3.jpg?s=120&d=mm&r=g)
Hi,
Have been offline for a goodly while hence tardy response to the thread that I started. comments lower down, but thanks to Brad, Richard, Mark, & Stephen for their input.
On Fri, May 04, 2012 at 12:33:24AM +0900, Stephen J. Turnbull wrote:
I have sinned and stand repentant. I hate spam as much as anyone and we get plenty to deal with. Somehow the Viagra and get rich emails didn't seem to stand on the same level as a once-off invite. But as pointed out clearly an unasked for email from an unknown party is just that.
In the light of the spam that we receive, which varies from worldwide mass mailings (viagra supplies from pharmacies in the USA, say) to lesser attempts (local suppliers of this & that product or service) there is no fuzzy line where the definition of spam rests, and much against my normal judgement where I see things in shades of grey, I am forced to make this a black and white decision on the basis of the definitions of spam made in the replies.
So will make sure that this doesn't occur again and will make clear the distinction to other staff handling these issues.
As an aside, I have to ask whether the 'invite' feature in Mailman has a function. If one has to have been in existing contact such that you can ask them if they would not object to an invite then one is in fact at the point where you can ask them point blank if you can subscribe them.
Typically someone may query whether we have a specific book title, or whether one listed on an online catalogue is still available. The usual drill if this is unavailable is to say so and then recommend that they join our mailing list for which we will send details (an 'invite') on the basis that it may show up on a future catalogue. I do not see this as sending spam. Maybe you differ?
I guess this may be considered a bit off-topic, comments welcome direct if you feel this is so.
bestest Anne
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
Anne Wainwright wrote:
My cycling club has a general discussion list for which subscription requires approval because it's limited to club members. If a new or renewing member checks the "I want to join the club's email list" box on the application form, we send an invitation. This avoids the problem of subscribing the wrong person or an invalid address to the list because of typos or unreadable handwriting (yes, we still accept snail-mailed forms with checks, although it's not our preferred method).
Even when a club member emails the list owners asking to join the list, we sometimes send an invitation rather than just subscribing if we think there's a possibility the email was spoofed.
I'm sure there are other use cases where invitations rather than direct subscriptions are appropriate/prudent.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/334b870d5b26878a79b2dc4cfcc500bc.jpg?s=120&d=mm&r=g)
Anne Wainwright writes:
They don't, from the point of view of the sender or society at large. But for the recipient....
As an aside, I have to ask whether the 'invite' feature in Mailman has a function.
Sure. As Mark points out, it confirms the intention of the user to join, which gives you the "double opt-in" property that gives a conservative litmus test for "not spam".
I think it might be a useful question to ask, "how can the invite feature be made more functional?"
In particular, if you've written a careful email, answering an inquiry, I see nothing spammy about adding a Mailman invite to that ... if it were possible, which currently it isn't, from any mail client I know of. OTOH, you could write that email using Mailman's "invite" interface, but I bet you'd get tired of that real quick.
![](https://secure.gravatar.com/avatar/9d2b2694f1f8fea795a902fa3a2bd3a3.jpg?s=120&d=mm&r=g)
Hi,
For the record the following URL is of interest
http://www.spamhaus.org/consumer/definition/
This clearly makes the point that spam is defined by two factors
"A message is Spam only if it is both Unsolicited and Bulk"
and being who they are their definition must carry some weight. In terms of their definition my mailing was not spam. Still, and I think Stephen made the point, there is also the consideration of good business practice to be considered.
over & out for tonight.
Anne
On Thu, Apr 26, 2012 at 09:39:44AM +0200, Anne Wainwright wrote:
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On May 18, 2012, at 5:14 PM, Anne Wainwright wrote:
Actually, if you go back to Mark's message where he said:
As an additional FYI in this thread, Mailman sends invitations
with a "Precedence: bulk" header. This can only be changed by
modifying code.
Then you will note that the message you sent does actually qualify on both counts -- it was most definitely unsolicited (by your own account), and unless you modified the source code then Mailman definitely marked those invitations as "bulk".
Even if Mailman hadn't marked the messages as bulk per se, if you sent out invitations to more than one person, then that could also be classified as essentially being "bulk".
There are features in Mailman that can be misused and abused in a wide variety of ways, and it is the responsibility of the Site Administrator(s) and the List Administrator(s) to make sure that they operate the software in an appropriate manner.
For example, if you were using Mailman internally to your company and could guarantee that no one could ever get on any list unless they were an employee, then by the terms of the employment contract you might be able to do things that might otherwise be considered of a "spammy nature", like requiring that all employees be subscribed to certain lists that they can't unsubscribe from, sending out invitations to join mailing lists that they did not request, etc….
We have to allow for these kinds of things because not everyone uses Mailman in the same way for the same user community. And some types of actions are appropriate for certain user communities but not for others. We can't just disable or remove features simply because they are not appropriate for a particular user community.
In essence, you're asking us to protect you against yourself, and there is a limit to how much of that we can do. At least, there is a limit to how much we can do if we want to keep the software usable for other people.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 5/19/2012 2:13 AM, Anne Wainwright wrote:
Why would this not be set to 'list' rather than 'bulk'?
List posts are sent with Precedence: list. Notices from Mailman, e.g. held message notices to an admin, invitations and welcome messages to users, password reminders, etc. are all sent with Precedence: bulk.
Prior to Mailman 2.1, everything was sent with Precedence: bulk, even list posts.
Comments in the Mailman 1.0 code say
# semi-controversial: some don't want this included at all, others # want the value to be `list'.
RFC 2076 (Feb 1997) says the Precedence: header is "non-standard, controversial, discouraged". See the RFC <http://www.rfc-editor.org/rfc/rfc2076.txt> for the precise definition of these terms.
We probably shouldn't be adding it at all, but as to why, other than the above code comment, some things are sent with Precedence: bulk you'd have to ask John Viega or someone with more knowledge of the history than I have.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On May 19, 2012, at 4:13 AM, Anne Wainwright wrote:
According to RFC 2076, the "Precedence:" header is "Non-standard, controversial, discouraged." RFC 3834 says:
and:
Historically, the "Precedence:" header has generally only had one standard value that I know of, if it was used at all -- and that value is "bulk". The original intent of this header (and this setting) was to help automated systems that receive mail messages to determine whether or not a message was originated by a human being or was perhaps automatically generated or handled through a mailing list -- at the time, there was no such negative connotation to the word "bulk" and no one would have distinguished between "bulk" mail and mail sent through a "list".
Over the years, things have changed, but the usage of this particular header has only gotten murkier. Mailman is one of the few programs on the Internet that has been fairly consistent in the way it has handled this header.
Of course, Mailman is only handling one end of the conversation, and it can't control what people on the other end do with the header. If we change the way Mailman works in this regard, we might break existing programs. If we don't change the way Mailman works in this regard, people on the other end might not understand what is really intended.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
![](https://secure.gravatar.com/avatar/2d8b084fbf3bb480d8a3b6233b498f4f.jpg?s=120&d=mm&r=g)
On 5/18/12 6:14 PM, Anne Wainwright wrote:
I will point out that from the recipients point of view, a mailman invite looks to be "Bulk", they have no way to know if you sent it specifically to them or to a large list.
A place like spamhaus can use "bulk" as part of their criteria, and see if essentially the same message is sent out repeatedly, an individual recipient generally can not, so their version of the "bulk" criteria is does it look like a mass mailing.
One way around this is rather than us the mailman invite feature, write a personal email where you "invite" the person to subscribe, giving the url of the subscription page as a pointer. While you can't prevent someone from pressing the "This is spam" button, if you have done some pre-vetting to be sure the person is likely interested, and made the message clearly personal and not bulk, will minimize the chances of them doing so.
-- Richard Damon
![](https://secure.gravatar.com/avatar/70dbe67e0eb08a96d695871292b27eef.jpg?s=120&d=mm&r=g)
<...> << On 5/19/2012 10:46 AM, Richard Damon wrote:
I will point out that from the recipients point of view, a mailman invite looks to be "Bulk", they have no way to know if you sent it specifically to them or to a large list.
<...>
One way around this is rather than us the mailman invite feature, write a personal email where you "invite" the person to subscribe, giving the url of the subscription page as a pointer.>>
Even tho I'm with a cPanel instal by serious "dumb" luck I having been doing exactly that for over a decade since I started my 1st List which was actually "begged" for ;-) by a bunch of folks on another Public List which did/does not allow attachments. I have no clue as to why I didn't just Mass Subscribe. I sent out Personal Invites with the Subscribe URL. Something about the Mass Sub. just didn't "feel" right.
<< While you can't prevent someone from pressing the "This is spam" button,>>
I have just about reached the "breaking point" and maybe one (1) more and I'm gonna ban AOL (Yahoo not far behind these days) users.
<< if you have done some pre-vetting to be sure the person is likely interested, and made the message clearly personal and not bulk, will minimize the chances of them doing so.>>
Absolutely agreed, Richard ! ! Thank you for posting something in this thread that applies to MM Users such as myself who ARE stuck behind cPanel :-[ :-) ! !
Ed Please visit MY site at: www.justbrits.com
PS: Anyone interested in a slow ( 3- 4 /day) "Joke List" by MM, please drop me a note :-) ! ! Ooops, and/or a small Political List (Poly Sci101).
participants (7)
-
" Just Brits " Shop
-
Anne Wainwright
-
Brad Knowles
-
Brad Rogers
-
Mark Sapiro
-
Richard Damon
-
Stephen J. Turnbull