Avidemux kann man unter Ubuntu mit

sudo aptitude install avidemux

installieren .

Für andere Betriebssysteme kann man es hier :

http://avidemux.sourceforge.net/download.html

downloaden.

So nun ein Beispiel wie man Werbung aus einer Tv-Aufnahme entfernt :

Avidemux starten

In Ubuntu findet man es unter Anwendungen -> Unterhaltungsmedien -> Avidemux(GTK+)

oder per Kommandozeile :

avidemux2_gtk

Mit Datei-> öffnen laden wir die Datei die wir bearbeiten wollen:

Bei vielen Dateien wird man gefragt ob man eine VBR-Zeitkarte erstellen will:Dies sollte man mit Ja bestätigen .

Unten ist eine Zeitleiste mit der man durch die den Film spulen kann, indem man sie mit der Maus bewegt.

um präziser eine Stelle zu erreichen kann man mit einen Klick auf den < Bottom ein Bild zurück und mit  dem >- Bottom eins vor spulen. mit >>  bzw<< spult man mehrer Sekunden vor/zurück .

mit <ll und ll> sucht man das nächste schwarze Bild und mit <D unf D> (ganz rechts) spult man zum Anfang und Ende des Videos.Bei der Tv Auf nahmen sind meist einige Minuten Vorprogramm drauf , das entfernen wir ein den wir den Anfang des Films suchen. Hier klicken wir unten auf “B” .

Dann klicken wir auf Bearbeiten->Entfernen (oder drücken die ENF-Taste).

Nun suchen wir den Anfang der Werbepause (Orientierungshilfe: In der Werbung senden die Sender kein Senderlogo)

Den Anfang markieren wir in der Zeitleiste mit dem “A” Bottom und das Ende mit B. Der Abschnitt ist dann wie im Bild oben markiert, entfernen  wir die Werbung. Mit jeder Werbepause machen wir das gleiche.

Das Ende des Films markieren wir mit A und löschen dann letzten Minuten die in der Datei sind.

Danach klicken wir auf speichern:

Vorsicht nicht die Originaldatei überscheiben , da es sonst Probleme gibt.

Danach erscheinen einige Fragen die man mit JA bzw OK beantwortet.:

Danach wird der geschnittene Film geschrieben ( kann je nach Rechenleistung ein paar Minuten dauern. )

Nun kann die Datei mit dem bevorzugten Videoplayer getestet werden.

Hier meine Exim4 Konfiguration auf Debian Lenny (5.0) mit folgenden Merkmalen :
-Der Server nutzt Veschlüsselung
- Der Server verlangt SMTP Auth für Versand ( Passwörter von PAM bezogen)
- Der Server legt Mails im Maildirformat ab ( Nutzung mit Courier IMAP)
- Je nach Absender werden die Mails über verschiedene Mailserver versendet.

Folgende Pakete werden benötigt:
exim4
libsasl2-modules
sasl2-bin

Exim muss in der sasl Gruppe sein:
Dazu folgender Befehl:

adduser debian-exim sasl

Datei /etc/exim4/exim4.conf

######################################################################
#                  Runtime configuration file for Exim               #
######################################################################

# This is a default configuration file which will operate correctly in
# uncomplicated installations. Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file. There are many more than are mentioned here. The
# manual is in the file doc/spec.txt in the Exim distribution as a plain
# ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
# from the Exim ftp sites. The manual is also online at the Exim web sites.

# This file is divided into several parts, all but the first of which are
# headed by a line starting with the word "begin". Only those parts that
# are required need to be present. Blank lines, and lines starting with #
# are ignored.

########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
#                                                                          #
# Whenever you change Exim's configuration file, you *must* remember to    #
# HUP the Exim daemon, because it will not pick up the new configuration   #
# until you do. However, any other Exim processes that are started, for    #
# example, a process started by an MUA in order to send a message, will    #
# see the new configuration as soon as it is in place.                     #
#                                                                          #
# You do not need to HUP the daemon for changes in auxiliary files that    #
# are referenced from this file. They are read every time they are used.   #
#                                                                          #
# It is usually a good idea to test a new configuration for syntactic      #
# correctness before installing it (for example, by running the command    #
# "exim -C /config/file.new -bV").                                         #
#                                                                          #
########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########

######################################################################
#                    MAIN CONFIGURATION SETTINGS                     #
######################################################################

# Specify your host's canonical name here. This should normally be the fully
# qualified "official" name of your host. If this option is not set, the
# uname() function is called to obtain the name. In many cases this does
# the right thing and you need not set anything explicitly.

# primary_hostname =
local_interfaces = 0.0.0.0.25

# The next three settings create two lists of domains and one list of hosts.
# These lists are referred to later in this configuration using the syntax
# +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
# are all colon-separated lists:

domainlist local_domains = localhost : meinhost.name

domainlist relay_to_domains =
hostlist   relay_from_hosts = 127.0.0.1

# Most straightforward access control requirements can be obtained by
# appropriate settings of the above options. In more complicated situations, you
# may need to modify the Access Control List (ACL) which appears later in this
# file.

# The first setting specifies your local domains, for example:
#
#   domainlist local_domains = my.first.domain : my.second.domain
#
# You can use "@" to mean "the name of the local host", as in the default
# setting above. This is the name that is specified by primary_hostname,
# as specified above (or defaulted). If you do not want to do any local
# deliveries, remove the "@" from the setting above. If you want to accept mail
# addressed to your host's literal IP address, for example, mail addressed to
# "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
# list. You also need to uncomment "allow_domain_literals" below. This is not
# recommended for today's Internet.

# The second setting specifies domains for which your host is an incoming relay.
# If you are not doing any relaying, you should leave the list empty. However,
# if your host is an MX backup or gateway of some kind for some domains, you
# must set relay_to_domains to match those domains. For example:
#
# domainlist relay_to_domains = *.myco.com : my.friend.org
#
# This will allow any host to relay through your host to those domains.
# See the section of the manual entitled "Control of relaying" for more
# information.

# The third setting specifies hosts that can use your host as an outgoing relay
# to any other host on the Internet. Such a setting commonly refers to a
# complete local network as well as the localhost. For example:
#
# hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
#
# The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
# have to include 127.0.0.1 if you want to allow processes on your host to send
# SMTP mail by using the loopback address. A number of MUAs use this method of
# sending mail.

# All three of these lists may contain many different kinds of item, including
# wildcarded names, regular expressions, and file lookups. See the reference
# manual for details. The lists above are used in the access control list for
# incoming messages. The name of this ACL is defined here:

acl_smtp_rcpt = acl_check_rcpt

# You should not change that setting until you understand how ACLs work.

# Specify the domain you want to be added to all unqualified addresses
# here. An unqualified address is one that does not contain an "@" character
# followed by a domain. For example, "caesar@rome.example" is a fully qualified
# address, but the string "caesar" (i.e. just a login name) is an unqualified
# email address. Unqualified addresses are accepted only from local callers by
# default. See the recipient_unqualified_hosts option if you want to permit
# unqualified addresses from remote sources. If this option is not set, the
# primary_hostname value is used for qualification.

# qualify_domain =

# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.

# qualify_recipient =

# The following line must be uncommented if you want Exim to recognize
# addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
# (an IP address) instead of a named domain. The RFCs still require this form,
# but it makes little sense to permit mail to be sent to specific hosts by
# their IP address in the modern Internet. This ancient format has been used
# by those seeking to abuse hosts by using them for unwanted relaying. If you
# really do want to support domain literals, uncomment the following line, and
# see also the "domain_literal" router below.

# allow_domain_literals

# No deliveries will ever be run under the uids of these users (a colon-
# separated list). An attempt to do so causes a panic error to be logged, and
# the delivery to be deferred. This is a paranoic safety catch. There is an
# even stronger safety catch in the form of the FIXED_NEVER_USERS setting
# in the configuration for building Exim. The list of users that it specifies
# is built into the binary, and cannot be changed. The option below just adds
# additional users to the list. The default for FIXED_NEVER_USERS is "root",
# but just to be absolutely sure, the default here is also "root".

# Note that the default setting means you cannot deliver mail addressed to root
# as if it were a normal user. This isn't usually a problem, as most sites have
# an alias for root that redirects such mail to a human administrator.

never_users = root

# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.

host_lookup = *

# The settings below, which are actually the same as the defaults in the
# code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP
# calls. You can limit the hosts to which these calls are made, and/or change
# the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
# are disabled. RFC 1413 calls are cheap and can provide useful information
# for tracing problem messages, but some hosts and firewalls have problems
# with them. This can result in a timeout instead of an immediate refused
# connection, leading to delays on starting up an SMTP session.

rfc1413_hosts = *
rfc1413_query_timeout = 30s

# By default, Exim expects all envelope addresses to be fully qualified, that
# is, they must contain both a local part and a domain. If you want to accept
# unqualified addresses (just a local part) from certain hosts, you can specify
# these hosts by setting one or both of
#
# sender_unqualified_hosts =
# recipient_unqualified_hosts =
#
# to control sender and recipient addresses, respectively. When this is done,
# unqualified addresses are qualified using the settings of qualify_domain
# and/or qualify_recipient (see above).

# If you want Exim to support the "percent hack" for certain domains,
# uncomment the following line and provide a list of domains. The "percent
# hack" is the feature by which mail addressed to x%y@z (where z is one of
# the domains listed) is locally rerouted to x@y and sent on. If z is not one
# of the "percent hack" domains, x%y is treated as an ordinary local part. This
# hack is rarely needed nowadays; you should not enable it unless you are sure
# that you really need it.
#
# percent_hack_domains =
#
# As well as setting this option you will also need to remove the test
# for local parts containing % in the ACL definition below.

# When Exim can neither deliver a message nor return it to sender, it "freezes"
# the delivery error message (aka "bounce message"). There are also other
# circumstances in which messages get frozen. They will stay on the queue for
# ever unless one of the following options is set.

# This option unfreezes frozen bounce messages after two days, tries
# once more to deliver them, and ignores any delivery failures.

ignore_bounce_errors_after = 2d

# This option cancels (removes) frozen messages that are older than a week.

timeout_frozen_after = 7d

#system_filter = /etc/exim4/exim_system_filter.conf
#system_filter_user = Debian-exim

smtp_accept_max_per_connection = 150
smtp_accept_queue_per_connection = 150
############tls
tls_certificate = /etc/ssl/certs/ssl-cert-snakeoil.pem
tls_privatekey = /etc/ssl/private/ssl-cert-snakeoil.key
#tls_verify_certificates = /etc/ssl/certs
tls_advertise_hosts = *
#tls_try_verify_hosts = *
log_selector = +tls_peerdn
received_header_text = "Received: \
    ${if def:sender_rcvhost {from ${sender_rcvhost}\n\t}\
    {${if def:sender_ident {from ${sender_ident} }}\
    ${if def:sender_helo_name {(helo=${sender_helo_name})\n\t}}}}\
    by ${primary_hostname} \
    ${if def:received_protocol {with ${received_protocol}}} \
    ${if def:tls_cipher {($tls_cipher)\n\t}}\
    ${if def:tls_peerdn {($tls_peerdn)(verified=$tls_certificate_verified)\n\t}} \
    (Exim ${version_number} #${compile_number})\n\t\
    id ${message_id}\
    ${if def:received_for {\n\tfor $received_for}}"

######################################################################
#                       ACL CONFIGURATION                            #
#         Specifies access control lists for incoming SMTP mail      #
######################################################################

begin acl

# This access control list is used for every RCPT command in an incoming
# SMTP message. The tests are run in order until the address is either
# accepted or denied.

acl_check_rcpt:

  # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
  # testing for an empty sending host field.

  accept  hosts = :

  #############################################################################
  # The following section of the ACL is concerned with local parts that contain
  # @ or % or ! or / or | or dots in unusual places.
  #
  # The characters other than dots are rarely found in genuine local parts, but
  # are often tried by people looking to circumvent relaying restrictions.
  # Therefore, although they are valid in local parts, these rules lock them
  # out, as a precaution.
  #
  # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
  # allows them because they have been encountered. (Consider local parts
  # constructed as "firstinitial.secondinitial.familyname" when applied to
  # someone like me, who has no second initial.) However, a local part starting
  # with a dot or containing /../ can cause trouble if it is used as part of a
  # file name (e.g. for a mailing list). This is also true for local parts that
  # contain slashes. A pipe symbol can also be troublesome if the local part is
  # incorporated unthinkingly into a shell command line.
  #
  # Two different rules are used. The first one is stricter, and is applied to
  # messages that are addressed to one of the local domains handled by this
  # host. It blocks local parts that begin with a dot or contain @ % ! / or |.
  # If you have local accounts that include these characters, you will have to
  # modify this rule.

  deny    message       = Restricted characters in address
          domains       = +local_domains
          local_parts   = ^[.] : ^.*[@%!/|]

  # The second rule applies to all other domains, and is less strict. This
  # allows your own users to send outgoing messages to sites that use slashes
  # and vertical bars in their local parts. It blocks local parts that begin
  # with a dot, slash, or vertical bar, but allows these characters within the
  # local part. However, the sequence /../ is barred. The use of @ % and ! is
  # blocked, as before. The motivation here is to prevent your users (or
  # your users' viruses) from mounting certain kinds of attack on remote sites.

  deny    message       = Restricted characters in address
          domains       = !+local_domains
          local_parts   = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
  #############################################################################

  # Accept mail to postmaster in any local domain, regardless of the source,
  # and without verifying the sender.

  accept  local_parts   = postmaster
          domains       = +local_domains

  # Deny unless the sender address can be verified.

  require verify        = sender

  #############################################################################
  # There are no checks on DNS "black" lists because the domains that contain
  # these lists are changing all the time. However, here are two examples of
  # how you could get Exim to perform a DNS black list lookup at this point.
  # The first one denies, while the second just warns.
  #
  # deny    message       = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
  #         dnslists      = black.list.example
  #
  # warn    message       = X-Warning: $sender_host_address is in a black list at $dnslist_domain
  #         log_message   = found in $dnslist_domain
  #         dnslists      = black.list.example
  #############################################################################

  # Accept if the address is in a local domain, but only if the recipient can
  # be verified. Otherwise deny. The "endpass" line is the border between
  # passing on to the next ACL statement (if tests above it fail) or denying
  # access (if tests below it fail).

  accept  domains       = +local_domains
          endpass
          verify        = recipient

  # Accept if the address is in a domain for which we are relaying, but again,
  # only if the recipient can be verified.

  accept  domains       = +relay_to_domains
          endpass
          verify        = recipient

  # If control reaches this point, the domain is neither in +local_domains
  # nor in +relay_to_domains.

  # Accept if the message comes from one of the hosts for which we are an
  # outgoing relay. Recipient verification is omitted here, because in many
  # cases the clients are dumb MUAs that don't cope well with SMTP error
  # responses. If you are actually relaying out from MTAs, you should probably
  # add recipient verification here.

  accept  hosts         = +relay_from_hosts

  # Accept if the message arrived over an authenticated connection, from
  # any host. Again, these messages are usually from MUAs, so recipient
  # verification is omitted.

  accept  authenticated = *

  # Reaching the end of the ACL causes a "deny", but we might as well give
  # an explicit message.

  deny    message       = relay not permitted

warn  log_message = verified peer dn $tls_peerdn
        condition = $tls_certificate_verified

  accept condition = $tls_certificate_verified

#deny  message = This message contains an unwanted file extension ($found_extension)
#        demime = scr:vbs:bat:lnk:pif:exe

######################################################################
#                      ROUTERS CONFIGURATION                         #
#               Specifies how addresses are handled                  #
######################################################################
#     THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT!       #
# An address is passed to each router in turn until it is accepted.  #
######################################################################

begin routers

# This router routes to remote hosts over SMTP by explicit IP address,
# when an email address is given in "domain literal" form, for example,
# . The RFCs require this facility. However, it is
# little-known these days, and has been exploited by evil people seeking
# to abuse SMTP relays. Consequently it is commented out in the default
# configuration. If you uncomment this router, you also need to uncomment
# allow_domain_literals above, so that Exim can recognize the syntax of
# domain literal addresses.

# domain_literal:
#   driver = ipliteral
#   domains = ! +local_domains
#   transport = remote_smtp

# This router routes addresses that are not in local domains by doing a DNS
# lookup on the domain name. Any domain that resolves to 0.0.0.0 or to a
# loopback interface address (127.0.0.0/8) is treated as if it had no DNS
# entry. Note that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated
# as the local host inside the network stack. It is not 0.0.0.0/0, the default
# route. If the DNS lookup fails, no further routers are tried because of
# the no_more setting, and consequently the address is unrouteable.
#amavis:
#        driver = manualroute
#        condition = "${if eq {$interface_port}{10025} {0}{1}}"
#        # if scanning incoming mails, uncomment the following line and
#        # change local_domains accordingly
#        #domains = +local_domains
#        transport = amavis
#        #route_list = "* localhost byname"
#	route_list = "* 127.0.0.1"
#	no_verify
 #       self = send

#fax:
#driver = manualroute
#transport = fax
#route_list ="*fax"

smarthost_auto:
    domains = ! +local_domains
    condition = "${extract{3}{:}{${lookup{$sender_address}lsearch*\
                {/etc/exim4/passwd.user}{$value}fail}}}"
    driver = manualroute
    transport = remote_smtp
    route_list = "* ${extract{3}{:}{${lookup{$sender_address}lsearch*\
                {/etc/exim4/passwd.user}{$value}fail}}}"
    host_find_failed = defer
    same_domain_copy_routing = yes
   ignore_target_hosts = 192.168.0.0/16 :\
                       172.16.0.0/12 : 10.0.0.0/8 : 169.254.0.0/16 : ext.mond.myhome
   # no_more

dnslookup:
  debug_print = "R: dnslookup for $local_part@$domain"
  driver = dnslookup
  domains = ! +local_domains
  transport = remote_smtp
  same_domain_copy_routing = yes
  ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :\
                        172.16.0.0/12 : 10.0.0.0/8 : 169.254.0.0/16
  no_more

# The remaining routers handle addresses in the local domain(s).

# This router handles aliasing using a linearly searched alias file with the
# name /etc/aliases. When this configuration is installed automatically,
# the name gets inserted into this file from whatever is set in Exim's
# build-time configuration. The default path is the traditional /etc/aliases.
# If you install this configuration by hand, you need to specify the correct
# path in the "data" setting below.
#
##### NB  You must ensure that the alias file exists. It used to be the case
##### NB  that every Unix had that file, because it was the Sendmail default.
##### NB  These days, there are systems that don't have it. Your aliases
##### NB  file should at least contain an alias for "postmaster".
#
# If any of your aliases expand to pipes or files, you will need to set
# up a user and a group for these deliveries to run under. You can do
# this by uncommenting the "user" option below (changing the user name
# as appropriate) and adding a "group" option if necessary. Alternatively, you
# can specify "user" on the transports that are used. Note that the transports
# listed below are the same as are used for .forward files; you might want
# to set up different ones for pipe and file deliveries from aliases.

system_aliases:
 debug_print = "R: system_aliases for $local_part@$domain"
  driver = redirect
  allow_fail
  allow_defer
  data = ${lookup{$local_part}lsearch{/etc/aliases}}
# user = exim
  file_transport = address_file
  pipe_transport = address_pipe

# This router handles forwarding using traditional .forward files in users'
# home directories. If you want it also to allow mail filtering when a forward
# file starts with the string "# Exim filter" or "# Sieve filter", uncomment
# the "allow_filter" option.

# If you want this router to treat local parts with suffixes introduced by "-"
# or "+" characters as if the suffixes did not exist, uncomment the two local_
# part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
# in the same way as xxxx@your.domain by this router. You probably want to make
# the same change to the localuser router.

# The no_verify setting means that this router is skipped when Exim is
# verifying addresses. Similarly, no_expn means that this router is skipped if
# Exim is processing an EXPN command.

# The check_ancestor option means that if the forward file generates an
# address that is an ancestor of the current one, the current one gets
# passed on instead. This covers the case where A is aliased to B and B
# has a .forward file pointing to A.

# The three transports specified at the end are those that are used when
# forwarding generates a direct delivery to a file, or to a pipe, or sets
# up an auto-reply, respectively.

#userforward:
#  driver = redirect
#  check_local_user
# local_part_suffix = +* : -*
# local_part_suffix_optional
#  file = $home/.forward
# allow_filter
#  no_verify
#  no_expn
#  check_ancestor
#  file_transport = address_file
#  pipe_transport = address_pipe
#  reply_transport = address_reply

userforward:
  debug_print = "R: userforward for $local_part@$domain"
  driver = redirect
  domains = +local_domains
  check_local_user
  file = $home/.forward
  no_verify
  no_expn
  check_ancestor
  allow_filter
  directory_transport = address_directory
  file_transport = address_file
  pipe_transport = address_pipe
  reply_transport = address_reply
  skip_syntax_errors
  syntax_errors_to = real-$local_part@$domain
  syntax_errors_text = \
    This is an automatically generated message. An error has\n\
    been found in your .forward file. Details of the error are\n\
    reported below. While this error persists, you will receive\n\
    a copy of this message for every message that is addressed\n\
    to you. If your .forward file is a filter file, or if it is\n\
    a non-filter file containing no valid forwarding addresses,\n\
    a copy of each incoming message will be put in your normal\n\
    mailbox. If a non-filter file contains at least one valid\n\
    forwarding address, forwarding to the valid addresses will\n\
    happen, and those will be the only deliveries that occur.

# This router matches local user mailboxes. If the router fails, the error
# message is "Unknown user".

# If you want this router to treat local parts with suffixes introduced by "-"
# or "+" characters as if the suffixes did not exist, uncomment the two local_
# part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
# in the same way as xxxx@your.domain by this router.

#procmail:
#  debug_print = "R: procmail for $local_part@$domain"
#  driver = accept
#  domains = +local_domains
#  check_local_user
#  transport = procmail_pipe
  # emulate OR with "if exists"-expansion
#  require_files = ${local_part}:\
#                  ${if exists{/etc/procmailrc}\
#                    {/etc/procmailrc}{${home}/.procmailrc}}:\
#                  +/usr/bin/procmail
#  no_verify
#  no_expn

local_user:
  debug_print = "R: local_user for $local_part@$domain"
  driver = accept
  domains = +local_domains
  check_local_user
  local_parts = ! root
  transport = local_delivery

#maildrop:
#  debug_print = "R: maildrop for $local_part@$domain"
#  driver = accept
#  domains = +local_domains
#  check_local_user
#  transport = maildrop_pipe
#  require_files = ${local_part}:${home}/.mailfilter:+/usr/bin/maildrop
#  no_verify
#  no_expn

real_local:
  debug_print = "R: real_local for $local_part@$domain"
  driver = accept
  domains = +local_domains
  local_part_prefix = real-
  check_local_user
  transport = local_delivery

mail4root:
  debug_print = "R: mail4root for $local_part@$domain"
  driver = redirect
  domains = +local_domains
  data = /var/mail/mail
  file_transport = address_file
  local_parts = root
  user = tobias
  group = mail
#######################################

shared_folders:
  local_parts = "shared"
  driver = accept
  transport = maildir_shared_folder

######################################################################
#                      TRANSPORTS CONFIGURATION                      #
######################################################################
#                       ORDER DOES NOT MATTER                        #
#     Only one appropriate transport is called for each delivery.    #
######################################################################

# A transport is used only when referenced from a router that successfully
# handles an address.

begin transports
#amavis:
#      driver = smtp
#      port = 10024
#      allow_localhost

#fax:
#driver = pipe
#user = exim
#command ="/usr/local/bin/faxmail -d -n ${local_part}"
#home_directory = /tmp

# This transport is used for delivering messages over SMTP connections.

#remote_smtp:
#  driver = smtp
remote_smtp:
    debug_print = "T: remote_smtp for $local_part@$domain"
    driver = smtp

    hosts_try_auth = "${extract{3}{:}{${lookup{$sender_address}lsearch*\
                        {/etc/exim4/passwd.user}{$value}fail}}}"

# This transport is used for local delivery to user mailboxes in traditional
# BSD mailbox format. By default it will be run under the uid and gid of the
# local user, and requires the sticky bit to be set on the /var/mail directory.
# Some systems use the alternative approach of running mail deliveries under a
# particular group instead of using the sticky bit. The commented options below
# show how this can be done.

#local_delivery:
#  driver = appendfile
#  file = /var/mail/$local_part
#  delivery_date_add
#  envelope_to_add
#  return_path_add
# group = mail
# mode = 0660

local_delivery:
  driver = appendfile
  directory = $home/Maildir
  delivery_date_add
  envelope_to_add
  return_path_add
  maildir_format
  mode = 0600
  mode_fail_narrower = false

# This transport is used for handling pipe deliveries generated by alias or
# .forward files. If the pipe generates any standard output, it is returned
# to the sender of the message as a delivery error. Set return_fail_output
# instead of return_output if you want this to happen only when the pipe fails
# to complete normally. You can set different transports for aliases and
# forwards if you want to - see the references to address_pipe in the routers
# section above.

address_directory:
  debug_print = "T: address_directory for $local_part@$domain"
  driver = appendfile
  envelope_to_add = true
  return_path_add = true
  check_string = ""
  escape_string = ""
  maildir_format

address_pipe:
debug_print = "T: address_pipe for $local_part@$domain"
  driver = pipe
  return_output

# This transport is used for handling deliveries directly to files that are
# generated by aliasing or forwarding.

address_file:
  debug_print = "T: address_file for $local_part@$domain"
  driver = appendfile
  delivery_date_add
  envelope_to_add
  return_path_add

# This transport is used for handling autoreplies generated by the filtering
# option of the userforward router.

address_reply:
  debug_print = "T: autoreply for $local_part@$domain"
 driver = autoreply

# procmail_pipe:
 # debug_print = "T: procmail_pipe for $local_part@$domain"
#   driver = pipe
#  path = "/bin:/usr/bin:/usr/local/bin"
#   command = "/usr/bin/procmail -t -d ${local_part}"
#   #from_hack
#   return_path_add
#   delivery_date_add
#   envelope_to_add
#   check_string = "From "
#   escape_string = ">From "
#   user = $local_part
#   group = mail

maildir_home:
  debug_print = "T: maildir_home for $local_part@$domain"
  driver = appendfile
  directory = $home/Maildir
  delivery_date_add
  envelope_to_add
  return_path_add
  maildir_format
  mode = 0600
  mode_fail_narrower = false

#maildrop_pipe:
#  debug_print = "T: maildrop_pipe for $local_part@$domain"
#  driver = pipe
#  path = "/bin:/usr/bin:/usr/local/bin"
#  command = "/usr/bin/maildrop"
#  return_path_add
#  delivery_date_add
#  envelope_to_add

# This transport is used for local delivery to user mailboxes in traditional
# BSD mailbox format.
#
#mail_spool:
#  debug_print = "T: appendfile for $local_part@$domain"
#  driver = appendfile
#  file = /var/mail/$local_part
#  delivery_date_add
#  envelope_to_add
#  return_path_add
#  group = mail
#  mode = 0660
#  mode_fail_narrower = false

 # This transport saves messages in shared folders for special mail
# addresses defined in the 'shared_folders' router - to allow workgroup
# style mail handling with Courier IMAP server (and clients which
# support shared folders)

maildir_shared_folder:
  driver = appendfile
  maildir_format = true
  directory = /srv/courier/.${local_part}/
  create_directory = true
  check_string = ""
  escape_string = ""
  delivery_date_add
  envelope_to_add
  return_path_add
  mode = 0777
  no_mode_fail_narrower
  user = Debian-exim
  group = Debian-exim
######################################################################
#                      RETRY CONFIGURATION                           #
######################################################################

begin retry

# This single retry rule applies to all domains and all errors. It specifies
# retries every 15 minutes for 2 hours, then increasing retry intervals,
# starting at 1 hour and increasing each time by a factor of 1.5, up to 16
# hours, then retries every 6 hours until 4 days have passed since the first
# failed delivery.

# Address or Domain    Error       Retries
# -----------------    -----       -------

*                      *           F,2h,15m; G,16h,1h,1.5; F,4d,6h

######################################################################
#                      REWRITE CONFIGURATION                         #
######################################################################

# There are no rewriting specifications in this default configuration file.

begin rewrite

*@+local_domains ${lookup{${local_part}}lsearch{/etc/exim4/email-addresses}\
                   {$value}fail} Ffrs

######################################################################
#                   AUTHENTICATION CONFIGURATION                     #
######################################################################

# There are no authenticator specifications in this default configuration file.

begin authenticators
#cram_md5:
#    driver = cram_md5
##    public_name = CRAM-MD5
#    client_name = "${extract{4}{:}{${lookup{$sender_address}lsearch*\
#                    {/etc/exim4/passwd.user}{$value}fail}}}"
 ##   client_secret = "${extract{5}{:}{${lookup{$sender_address}lsearch*\
#                    {exim4/passwd.user}{$value}fail}}}"

plain:
    driver = plaintext
    public_name = PLAIN
    client_send = "^${extract{4}{::}\
                    {${lookup{$sender_address}lsearch*\
                    {/etc/exim4/passwd.user}{$value}fail}}}\
                    ^${extract{5}{::}\
                    {${lookup{$sender_address}lsearch*\
                    {/etc/exim4/passwd.user}{$value}fail}}}"

login:
    driver = plaintext
    public_name = LOGIN
    client_send = ": ${extract{4}{::}\
                    {${lookup{$sender_address}lsearch*\
                    {/etc/exim4/passwd.user}{$value}fail}}}\
                    : ${extract{5}{::}\
                    {${lookup{$sender_address}lsearch*\
                    {/etc/exim4/passwd.user}{$value}fail}}}"

 plain_saslauthd_server:
   driver = plaintext
   public_name = PLAIN
   # don't send system passwords over unencrypted connections
   server_advertise_condition = ${if eq{$tls_cipher}{}{0}{1}}
   server_condition = ${if saslauthd{{$2}{$3}}{1}{0}}
   server_set_id = $2
   server_prompts = :

 login_saslauthd_server:
   driver = plaintext
   public_name = LOGIN
   server_prompts = "Username:: : Password::"
   # don't send system passwords over unencrypted connections
   server_advertise_condition = ${if eq{$tls_cipher}{}{0}{1}}
   server_condition = ${if saslauthd{{$1}{$2}}{1}{0}}
   server_set_id = $1

 cram_md5_server:
   driver = cram_md5
   public_name = CRAM-MD5
   server_secret = ${extract{2}{:}{${lookup{$1}lsearch{CONFDIR/passwd}{$value}fail}}}
   server_set_id = $1

######################################################################
#                   CONFIGURATION FOR local_scan()                   #
######################################################################

# If you have built Exim to include a local_scan() function that contains
# tables for private options, you can define those options here. Remember to
# uncomment the "begin" line. It is commented by default because it provokes
# an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
# set in the Local/Makefile.

# begin local_scan

# End of Exim configuration file 

#######################################################################
#####################################################################
/etc/exim4/passwd.user

###########################################################################
### Example for /etc/exim4/passwd.user
###########################################################################
###
### Last Update: Sat, 22 May 2004 16:14:08 +0200
###
### Die E-Mailadresse steht zweimal am Anfang (sehr wichtig fuer die
### Fehlerbehandlung!). Danach steht der lokale Username, gefolgt vom
### entsprechenden Smarthost. Am Ende stehen Benutzerkennung und Passwort
### vom Provider. Alle Eintraege werden mit einfachen Doppelpunkt getrennt.
###
### Die Raute '#' ist in dieser Datei das Kommentarzeichen.
###
###########################################################################
mail_adresse@gmx.net:mail_adresse@gmx.net:ocaler_gmx_nutzer:mail.gmx.net:1234567:passwort
mail2_adresse@web.de:mail2_adresse@web.de:localer_webde_nutzer:smtp.web.de:mail2_adresse:passwort

############################################################
/etc/default/saslauthd:

#
# Settings for saslauthd daemon
# Please read /usr/share/doc/sasl2-bin/README.Debian for details.
#

# Should saslauthd run automatically on startup? (default: no)
START=yes

# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"

# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
NAME="saslauthd"

# Which authentication mechanisms should saslauthd use? (default: pam)
#
# Available options in this Debian package:
# getpwent -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam -- use PAM
# rimap -- use a remote IMAP server
# shadow -- use the local shadow password file
# sasldb -- use the local sasldb database file
# ldap -- use LDAP (configuration is in /etc/saslauthd.conf)
#
# Only one option may be used at a time. See the saslauthd man page
# for more information.
#
# Example: MECHANISMS="pam"
MECHANISMS="pam"

# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS=""

# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
THREADS=5

# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
#
# WARNING: DO NOT SPECIFY THE -d OPTION.
# The -d option will cause saslauthd to run in the foreground instead of as
# a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish
# to run saslauthd in debug mode, please run it by hand to be safe.
#
# See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
# See the saslauthd man page and the output of 'saslauthd -h' for general
# information about these options.
#
# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
OPTIONS="-c -m /var/run/saslauthd"

Hier meine Postfix Konfiguration auf Ubuntu Jaunty Jackalope mit folgenden Merkmalen :
-Der Server nutzt Verschlüsselung
- Der Server verlangt SMTP Auth für Versand ( Passwörter von PAM bezogen)
- Der Server legt Mails im Maildirformat ab ( Nutzung mit Courier IMAP)
- Je nach Absender werden die Mails über verschiedene Mailserver Versendet.

Folgende Pakete werden benötigt:
postfix
libsasl2-modules
sasl2-bin

Postfix muss in der sasl Gruppe sein:
Dazu folgender Befehl:
adduser postfix sasl

/etc/default/saslauthd:

#
# Settings for saslauthd daemon
# Please read /usr/share/doc/sasl2-bin/README.Debian for details.
#

# Should saslauthd run automatically on startup? (default: no)
START=yes

# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"

# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
NAME="saslauthd"

# Which authentication mechanisms should saslauthd use? (default: pam)
#
# Available options in this Debian package:
# getpwent  -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam       -- use PAM
# rimap     -- use a remote IMAP server
# shadow    -- use the local shadow password file
# sasldb    -- use the local sasldb database file
# ldap      -- use LDAP (configuration is in /etc/saslauthd.conf)
#
# Only one option may be used at a time. See the saslauthd man page
# for more information.
#
# Example: MECHANISMS="pam"
MECHANISMS="pam"

# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS=""

# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
THREADS=5

# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
#
# WARNING: DO NOT SPECIFY THE -d OPTION.
# The -d option will cause saslauthd to run in the foreground instead of as
# a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish
# to run saslauthd in debug mode, please run it by hand to be safe.
#
# See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
# See the saslauthd man page and the output of 'saslauthd -h' for general
# information about these options.
#
# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
OPTIONS="-c -m /var/run/saslauthd"

######################################################################
/etc/postfix/sasl/smtpd.conf

pwcheck_method: saslauthd
mech_list: PLAIN LOGIN
saslauthd_path: /var/run/saslauthd/mux

#####################################################################
/etc/postfix/main.cf

# See /usr/share/postfix/main.cf.dist for a commented, more complete version

# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key

smtpd_tls_security_level=may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

myhostname = mond
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination =  localhost.localdomain, localhost, hostname.des.servers
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
home_mailbox = Maildir/
message_size_limit = 50000000
myorigin = /etc/mailname

inet_protocols = all

transport_maps = hash:/etc/postfix/transport

smtp_tls_security_level = may
smtp_sasl_security_options = noanonymous
smtp_sender_dependent_authentication = yes
smtp_sasl_auth_enable = yes
smtp_connection_cache_on_demand = no
smtp_sasl_password_maps = hash:/etc/postfix/sasl_password
sender_dependent_relayhost_maps = hash:/etc/postfix/sender_dependent
sender_canonical_maps = hash:/etc/postfix/sender_canonical

smtpd_sasl_auth_enable =yes
smtpd_sasl_path = smtpd
smtpd_tls_auth_only=yes
broken_sasl_auth_clients = yes

smtpd_recipient_restrictions =
    permit_mynetworks, permit_sasl_authenticated,reject

#########################################################################

/etc/postfix/master.cf

#
# Postfix master process configuration file.  For details on the format
# of the file, see the master(5) manual page (command: "man 5 master").
#
# Do not forget to execute "postfix reload" after editing this file.
#
# ==========================================================================
# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       n       -       -       smtpd
#submission inet n       -       -       -       -       smtpd
#  -o smtpd_tls_security_level=encrypt
#  -o smtpd_sasl_auth_enable=yes
#  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
#  -o milter_macro_daemon_name=ORIGINATING
#smtps     inet  n       -       -       -       -       smtpd
#  -o smtpd_tls_wrappermode=yes
#  -o smtpd_sasl_auth_enable=yes
#  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
#  -o milter_macro_daemon_name=ORIGINATING
#628      inet  n       -       -       -       -       qmqpd
pickup    fifo  n       -       -       60      1       pickup
cleanup   unix  n       -       -       -       0       cleanup
qmgr      fifo  n       -       n       300     1       qmgr
#qmgr     fifo  n       -       -       300     1       oqmgr
tlsmgr    unix  -       -       -       1000?   1       tlsmgr
rewrite   unix  -       -       -       -       -       trivial-rewrite
bounce    unix  -       -       -       -       0       bounce
defer     unix  -       -       -       -       0       bounce
trace     unix  -       -       -       -       0       bounce
verify    unix  -       -       -       -       1       verify
flush     unix  n       -       -       1000?   0       flush
proxymap  unix  -       -       n       -       -       proxymap
proxywrite unix -       -       n       -       1       proxymap
smtp      unix  -       -       -       -       -       smtp
# When relaying mail as backup MX, disable fallback_relay to avoid MX loops
relay     unix  -       -       -       -       -       smtp
	-o smtp_fallback_relay=
#       -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq     unix  n       -       -       -       -       showq
error     unix  -       -       -       -       -       error
retry     unix  -       -       -       -       -       error
discard   unix  -       -       -       -       -       discard
local     unix  -       n       n       -       -       local
virtual   unix  -       n       n       -       -       virtual
lmtp      unix  -       -       -       -       -       lmtp
anvil     unix  -       -       -       -       1       anvil
scache    unix  -       -       -       -       1       scache
#
# ====================================================================
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# Many of the following services use the Postfix pipe(8) delivery
# agent.  See the pipe(8) man page for information about ${recipient}
# and other message envelope options.
# ====================================================================
#
# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
maildrop  unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient}
#
# See the Postfix UUCP_README file for configuration details.
#
uucp      unix  -       n       n       -       -       pipe
  flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
#
# Other external delivery methods.
#
ifmail    unix  -       n       n       -       -       pipe
  flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp     unix  -       n       n       -       -       pipe
  flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient
scalemail-backend unix	-	n	n	-	2	pipe
  flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension}
mailman   unix  -       n       n       -       -       pipe
  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
  ${nexthop} ${user}

##########################################################

/etc/postfix/sasl_passwort

#email servernutzername:passwort
meine_mail@gmx.net 123456:passwort
meine2_mail@web.de maine2_mail:passwort

##########################################################

/etc/postfix/sender_canonical

#localer_User externe Mail
user1 meine_mail@gmx.net
user2 meine2_mail@web.de

#######################################################

/etc/postfix/sender_dependent

#email mailserver
meine_mail@gmx.net mail.gmx.net
meine2_mail@web.de smtp.web.de

##########################################################

Zum Schluss müssen Datenbanken ins Postfixformat konvertiert werden:

sudo postmap /etc/postfix/sender_canonical
sudo postmap /etc/postfix/sender_dependent
sudo postmap /etc/postfix/sasl_password

Und ein Neustart von Postfix ist erforderlich :

sudo /etc/init.d/postfix restart

Ich hatte festgestellt , dass wenn PHP über CGI oder wie bei meinem Hoster über Fastcgi läuft die HTTP -Auth Funktionen nicht laufen (der Passwort-Dialog erscheint immer wieder).

Google lieferte mir Vorschläge wie ModfastCGI patchen oder FastCGI mit Parametern starten . Dies ist bei meinen Hoster nicht möglich , da ich keine Rootrechte hab.

Mit folgenden Anpassungen läuft es:

Datei .htaccess :

RewriteEngine on
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

Am Anfang der PHP Datei muss folgendes stehen:

// split the user/pass parts
list($_SERVER['PHP_AUTH_USER'], $_SERVER['PHP_AUTH_PW']) = explode(':', base64_decode(substr($_SERVER['Authorization'], 6)));

Hier eine Beispiel Testanwendung:

< ?php
// split the user/pass parts
list($_SERVER['PHP_AUTH_USER'], $_SERVER['PHP_AUTH_PW']) = explode(':', base64_decode(substr($_SERVER['Authorization'], 6)));

// open a user/pass prompt
if (!isset($_SERVER['Authorization'])) {
   header('WWW-Authenticate: Basic realm="My Realm"');
   header('HTTP/1.0 401 Unauthorized');
   echo 'Abrechen gedrückt ';

   exit;
 } else {
   echo "

Hallo, ".$_SERVER['PHP_AUTH_USER'];
   echo "

Dein Password: 

".$_SERVER['PHP_AUTH_PW'];
 }
?>

Als ich Gnucash mit der Postbank getestet hatte, bekam ich immer den Fehler:” No reply” in Aqbanking, und Gnucash emfang keine Umsätze .

Der Fehler war, dass in den Einstellungen” SSLv3 erzwingen” nicht aktiviert war.

Mit bcrypt geht das Verschlüsseln ähnlich wie mit mcrypt.

bcrypt Datei verschlüsselt  “Datei”

bcrypt Datei.bfe entschlüsselt sie wieder.

Der Vorteil von brypt gegenüber mcrypt ist, dass brypt auch unter Windows unterstützt wird.

Mit dem Programm mcypt kann man ganz einfach einzelne Dateien verschlüsseln.

mit  mrypt Datei verschlüsselt man “Datei” .

Mit mrypt  -d Datei.nc entschlüsselt man sie wieder.

Wenn man seinen Mailserver falsch konfiguriert kann er von Spammern benutzt werden um Spam zu verteilen. Solche Server nennt man Openrelay.

Unter http://www.dnsgoodies.com/ kann man seinen Server darauf testen.

Firefox Bug

Gestern hab ich festgestellt, dass die von mir verwendete Firefox Version (Ubuntu / 3.0.13) einen Bug  hat . Jedesmal wenn ich die Zertifikate exportieren wollte kam folgender Fehler:

Das Erstellen der PKCS#12-Backupdatei ist aus unbekannten Gründen fehlgeschlagen .

Das Problem konnte ich umgehen indem ich Firefox aus dem Terminal aus mit dem Parameter: -safe-mode gestartet hab .

Normalerweise kann man unter Linux sein Shell mit Rootrechten starten in den man su und danach sein Rootpasswort eingibt .

Bei Ubuntu gibt es leider kein Rootpasswort.

Hier kann man ein Rootshell mit

 sudo -s 

starten.
Benötigt wird dazu das Userpasswort.