"We can't screen an event involving some teams and riders under suspicion of doping."(That's strange. Of course they can. They have before and I bet they'll still show motorsport, football, horse-racing, golf, wrestling, and so on if they get them. They just don't want to show cycling.)
"We want to show by this gesture that we're ready to support cycling only if it's clean, that's to say without banned doping sustances."(That's actually quite a high standard: over 180 participants, none of them cheating. That's a lot harder than 20 drivers or 30 footballers all being clean - even then, they don't always manage it and I don't see ARD/ZDF dropping those sports every time one player is accused of doping. Never mind all the smaller cheating attempts which are easier in many other sports than cycling.)
"It's a warning to cycling and to every other sport,"It's a warning that ARD/ZDF's TV producers are short-sighted and don't care about the viewers. At least Eurosport Germany continues with live coverage every day! Let's keep watching and see how the chips fall for Sinkewitz. Are ARD/ZDF fee-payers raising hell about this absurd decision? I hope so.
I cannot understand why this can be considered fascist by reading the lyrics. But listening to it I have felt again that we need lyrics. We cannot go out at the world mumbling our athem, as we cannot sign it. Recently, Spanish Olimpic Comitee requested lyrics to be written. I strongly think that they will be some king of "flower power" lyrics, to avoid hurting anyone (which is impossible)
I cannot understand why this can be considered fascist by reading the lyrics. But listening to it I have felt again that we need lyrics. We cannot go out at the world mumbling our athem, as we cannot sign it. Recently, Spanish Olimpic Comitee requested lyrics to be written. I strongly think that they will be some king of "flower power" lyrics, to avoid hurting anyone (which is impossible)
There is/was a street musician here in Boston who played the most amazing slide guitar I have ever heard. He is also filthy, unkempt, rude, and generally angry at the commuters who he clearly feels owe him more of their attention. It would be wrong to assume that his failure to draw crowds is due solely to the public's inability to appreciate music.Right on! My point exactly.
local_part_suffix = +*
local_part_suffix_optional
The first option defines the suffix; normal practice appears to be to use both “+” and “-“, but since I’d previously used “-” with qmail I opted to use “+” only so that I didn’t confuse myself during the transition.
The second option allows the suffix to be optional, so that mail to “scott” is still delivered normally.
Now mail to “scott+canonical” will be delivered to the “scott” user.
Forwarding configuration
The next task is to ensure that mail is actually forwarded to this address; for me this was a configuration performed by the Canonical sysadmins to ensure that my work e-mail is actually delivered to scott+canonical on my own mail server.
Filtering configuration
Since both personal and work e-mail are now both being delivered to the same user account on my home mail server, I need to filter the mail into separate folders.
This can be done by checking the $localpartsuffix variable in Exim filter .forward files, e.g.:
# Exim filter
if $local_part_suffix is "+canonical"
then
save Maildir/Canonical/
endif
Now incoming work e-mail is filtered into a different mail folder, while personal mail is delivered into the primary one.
I’ve used similar filter instructions for mailing lists, mailman messages, Launchpad mails, etc. to filter into appropriate folders.
Where the mail is personal, it is filtered into (e.g.) Maildir/.Lists/upstart-devel/
Where the mail is for work, I add /Canonical/ to the path, (e.g.) Maildir/Canonical/.Lists/linux-hotplug-devel/
This means that the Maildir/ directory is my personal INBOX, with sub-folders immediately under that and beginning with a period; and the Maildir/Canonical/ directory is my work INBOX, with sub-folders immediately under that and beginning with a period.
This defines two trees in a manner compatible with dovecot. There’s no particular reason that Maildir/Canonical/ has to be under Maildir/, it could have been Maildir-Canonical/ and this would still work. I simply wanted them in one place to ease backups.
Dovecot configuration
Now we need to configure dovecot to permit login by a fake (“virtual”) user, with a different Maildir tree, so that I can configure them as two separate accounts.
The first set of changes is to dovecot.conf to add an additional authentication source. Modify the “auth default” block to add a new “passwd-file” passdb in addition to the “pam” passdb (or whatever your system is using).
passdb passwd-file
args = /etc/dovecot/passwd
This lets us authenticate virtual users, but we also want to set their attributes, so we can use the same file as a userdb in the same “auth” block.
userdb passwd-file
args = /etc/dovecot/passwd
Dovecot will now check both PAM and this file for user information.
We now simply need to add a line to this file to specify the virtual user and set up the alternate Maildir tree.
scott+canonical:PASSWORD:1000:1000::/home/scott::userdb_mail=maildir:/home/scott/Maildir/Canonical
The format is that of an ordinary passwd file; the first two parts give the passdb authentication credentials and the rest give the userdb information.
I’ve set this user to have the same uid, gid and home directory as my real “scott” user.
The final part changes the mail environment for this virtual user, instead rooting it at Maildir/Canonical/
Client configuration
The mail client will need two accounts adding; one for “scott” and the other for “scott+canonical”. It will see two separate folder trees for each account.
An unexpected bonus is that the reply account is now automatically set for me, since I’m replying from the specific account rather than from a single general one.
$ bzr branch http://people.debian.org/~zack/bzr/pkg-python-debian/
Here are some examples to wet your
appetite:
It is already a proposed addition to python-debian, feel free to
comment about the API ... before it's too late
Next.