Differences between revisions 26 and 33 (spanning 7 versions)
Revision 26 as of 2015-04-16 11:43:34
Size: 5511
Editor: CordBeermann
Comment:
Revision 33 as of 2021-03-25 01:27:43
Size: 5547
Editor: PaulWise
Comment: missing comma
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
1. to let you know that something is wrong on the way between us and your mailsystem.
2. To let you know that you may be unsubscribed for bouncing.
 1. to let you know that something is wrong on the way between us and your mail system.
 1. to let you know that you may be unsubscribed for bouncing.
Line 14: Line 14:
= But the mail you got a bounce for was Spam! = = But the mail you got a bounce for was spam! =
Line 16: Line 16:
Mail should never be bounced because of its content. Our mails are tagged with a 'Precedence: list' so if you decide to not receive mails for which you subscribed drop them silently. Mail should never be bounced because of its content. Our mails are tagged with a 'Precedence: list' so if you decide to not receive mails for which you subscribed, drop them silently.
Line 19: Line 19:
You can use the [[http://www.infodrom.org/projects/majorsmart/|MajorSmart]]-interface to get a list.
Line 21: Line 20:
MajorSmart provides these commands: You can use the [[https://www.infodrom.org/projects/majorsmart/|MajorSmart]] interface to get a list.

!MajorSmart provides these commands:
Line 30: Line 31:
= I'm a Gmail-User and don't get the messages back I send to a list =
Gmail hides mails that look like they are from the Gmailuser until there is a reply to it.
= I'm a Gmail user and don't get the messages back I send to a list =
Line 33: Line 33:
= I suspect that a mail I sent has been caught by Spamfiltering =
First check on http://lists.debian.org if the mail shows up there. If it does, the mail has been successfully distributed to the list.
Gmail hides mails that look like they are from the Gmail user until there is a reply to it.

= I suspect that a mail I sent has been caught by spam filtering =

First check on https://lists.debian.org if the mail shows up there. If it does, the mail has been successfully distributed to the list.
Line 38: Line 41:
 * Mailadress of sender and receipient
 * Date and Time of sending, with Timezone information.
 * Mail address of sender and recipient
 * Date and Time of sending, with timezone information.
Line 45: Line 48:
Your mailaddress is coded in the Return-Path. Example:
Your mail address is coded in the Return-Path. Example:
Line 50: Line 54:
Line 55: Line 60:
= I have been unsubscribed from a list, because my Mailsystem refused to accept Listmail containing Spam = = I have been unsubscribed from a list, because my mail system refused to accept list mail containing spam =
Line 59: Line 65:
 * If you bounce back such mails, you worsen the spam problem, as most spam uses mailaddresses of innocents, and bounces are then returned to those.  * If you bounce back such mails, you worsen the spam problem, as most spam uses mail addresses of innocents, and bounces are then returned to those.
Line 64: Line 70:
We run heavy filters on the lists, which reduces the incoming mail-amount of ~50000 mails/day down to 2500 mails/day of which 10-50 mails/day are spam (depending on new spamwaves, which aren't known yet). On the other hand we have less than one False Positive per day. This is a pretty impressive outcome for a system carrying 180 Mailing lists of which 150 are unrestricted.
We run heavy filters on the lists, which reduces the incoming mail-amount of ~50000 mails/day down to 2500 mails/day of which 10-50 mails/day are spam (depending on new spam waves, which aren't known yet). On the other hand we have less than one False Positive per day. This is a pretty impressive outcome for a system carrying 180 Mailing lists of which 150 are unrestricted.
Line 68: Line 75:
Our spamassassin-configuration is also available at svn://svn.debian.org/svn/pkg-listmaster/trunk/spamassassin_config Our spamassassin configuration is also available at svn://svn.debian.org/svn/pkg-listmaster/trunk/spamassassin_config
Line 71: Line 78:
Line 74: Line 82:
Line 77: Line 86:
That depends on your removal score and the traffic-rate of the certain list. As start value we begin with 80% bounces for unmoderated lists and 60% bounces for moderated lists. That value will be lowered depending on the count of forced removals in the last 90 days. The timerange taken into account ranges from 1 day for high traffic lists over 1 week, 1 month up to 90 days for very-low-traffic-lists.
That depends on your removal score and the traffic-rate of the certain list. As start value we begin with 80% bounces for unmoderated lists and 60% bounces for moderated lists. That value will be lowered depending on the count of forced removals in the last 90 days. The time range taken into account ranges from 1 day for high traffic lists over 1 week, 1 month up to 90 days for very-low-traffic-lists.

I got a bounce notification, but bouncing it was correct because it was spam

Please do not bounce list mail (it is clearly marked as such). If you do not want to receive it, just drop it. We do appreciate suggestions for improvements to our spam filters (see below) and are well aware that there still is spam coming through. On the other hand, we have to be more careful to not incur too many false positives, so there is a very fine balance to take and your pet filtering mechanism might not work for us. As such, our appreciation for your mere expression of displeasure with our spam filtering might not justify the time you take to find wordings to convey your rage.

Why do you notify me about a single bounce?

The mails we send out are never unsolicited. You have signed up for them. So we notify you when a delivery goes wrong, for two reasons:

  1. to let you know that something is wrong on the way between us and your mail system.
  2. to let you know that you may be unsubscribed for bouncing.

But the mail you got a bounce for was spam!

Mail should never be bounced because of its content. Our mails are tagged with a 'Precedence: list' so if you decide to not receive mails for which you subscribed, drop them silently.

How can I get a list of all my subscriptions?

You can use the MajorSmart interface to get a list.

MajorSmart provides these commands:

  • un/subscribe -- subscribe / unsubscribe
  • which -- to which list is somebody subscribed to
  • help -- a comprehensive help
  • lists -- list of available lists
  • approve -- commands for the listmaster

send your commands to majordomo@lists.debian.org

I'm a Gmail user and don't get the messages back I send to a list

Gmail hides mails that look like they are from the Gmail user until there is a reply to it.

I suspect that a mail I sent has been caught by spam filtering

First check on https://lists.debian.org if the mail shows up there. If it does, the mail has been successfully distributed to the list.

If it doesn't show up then contact listmaster@lists.debian.org and provide as much information about the missing mail, especially information about

  • Mail address of sender and recipient
  • Date and Time of sending, with timezone information.
  • the Message-Id
  • the sending IP

is extremely helpful.

I want to unsubscribe but I can't remember with which address I'm subscribed

Your mail address is coded in the Return-Path. Example:

Return-Path:<bounce-debian-devel=cord=debian.org@lists.debian.org>

Show full message header in Gmail

  • Open the message.
  • Click on "More options"
  • Click on "Show original"
  • New window opens containing the message with complete header and body. Select all, copy, select destination window, paste.

I have been unsubscribed from a list, because my mail system refused to accept list mail containing spam

It is bad behaviour to refuse incoming mail because of the content, because:

  • RfC 2821 discourages in such practices Chapter 3.3 Server SMTP systems SHOULD NOT reject messages based on perceived defects in the RFC 822 or MIME [12] message header or message body.

  • If you bounce back such mails, you worsen the spam problem, as most spam uses mail addresses of innocents, and bounces are then returned to those.
  • You double-opted-in to our lists, so you should accept (or discard if you please) all mails that comes through it.

If you want to help us against spam, see the next chapter.

The lists are spam-laden, I want to help you

We run heavy filters on the lists, which reduces the incoming mail-amount of ~50000 mails/day down to 2500 mails/day of which 10-50 mails/day are spam (depending on new spam waves, which aren't known yet). On the other hand we have less than one False Positive per day. This is a pretty impressive outcome for a system carrying 180 Mailing lists of which 150 are unrestricted.

To filter we use procmail and spamassassin, so if you want to help us, you can send us recipes for those two systems to listmaster@lists.debian.org. You can also help us by bouncing (as in mutt) spam to report-listspam@lists.debian.org. (Don't automagically bounce spam to that address that your system thinks is spam. You are personally responsible that mail to that address IS spam. Also don't use that address to contact us.)

Our spamassassin configuration is also available at svn://svn.debian.org/svn/pkg-listmaster/trunk/spamassassin_config

I got an odd mail that send me here

lists.debian.org sends those mails automatically to notify users about problems with mail-delivery. Please see the other link provided in the mail, to find out what went wrong.

Will I be notified if I'm unsubscribed?

Yes, A Notification will be send out immediately when a forced unsubscription happens. There also will be a reminder after every seven days up to thirty days after the removal.

What is 'a certain threshold' after which forced removal happens?

That depends on your removal score and the traffic-rate of the certain list. As start value we begin with 80% bounces for unmoderated lists and 60% bounces for moderated lists. That value will be lowered depending on the count of forced removals in the last 90 days. The time range taken into account ranges from 1 day for high traffic lists over 1 week, 1 month up to 90 days for very-low-traffic-lists.