• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Kmail, Mail nach verschieben in Unterordner wieder im Postei

OpenSuse 13.1
KDE-Plattform-Version 4.11.5
kmail 4.11.5
Ordnertyp Maildir
verwende pop3

hallo,
ich habe keine Ahnung wie ich folgendes Problem gelöst bekomme:
wenn Mails vom Provider, hier Arcor, abgeholt wurden, landen diese im Ordner Posteingang und es starten Filterregel.
Im wesentlichen werden die Mails nach Absender gefiltert, und wenn Filterbedingung erfüllt, in entsprechende Unterordner verschoben. Der Ordner Posteingang ist dann leer.
Aber nur für wenige Sekunden.
Denn dann taucht die zuvor verschobene Mail wieder im Ordner Posteingang auf, und durchläuft die Regel erneut und wird wieder verschoben. Somit komme ich in kürzester Zeit auf jede Menge doppelte Mails.
Fehler im Filterprogramm, oder Filterregel? Nein.
Gleiches passiert wenn ich eine Mail von Hand in ein anderen Ordner verschiebe. Sie ist in wenigen Sekunden wieder im Posteingang und im Unterordner.
Ich kann die Mail auch mit Rechtsklick in den Papierkorb bringen: gleiches Ergebnis.
Fehler beim Provider? Nein.
Ich lasse im Normalfall die Mails 3 Tage beim Provider. Aber wenn ich auch die Mail sofort nach dem herunterladen lösche, vervielfältigt sich diese auf wunderbarer Weise, wenn sie den Ordner Posteingang verläßt um in ein anderen Unterordner landet.

Nachtrag:
Selbsttest des Akonadi-Servers ergab:
1. Eine angepasste Konfiguration des MySQL-Server wurde nicht gefunden, sie ist aber auch nicht vorgeschrieben.
2. Der Akonadi-Server hat während des aktuellen Starts Fehler gemeldet. Das Protokoll kann hier gefunden werden:
das Fehlerprotokoll:
Akonadi Server Self-Test Report
===============================

Test 1: SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/horst/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-horst.tIMpw9/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2: SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3: SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4: SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.5.33-MariaDB for Linux on i686 (openSUSE package)


Test 5: SUCCESS
--------

MySQL server log contains no errors.
Details: The MySQL server log file &apos;<a href='/home/horst/.local/share/akonadi/db_data/mysql.err'>/home/horst/.local/share/akonadi/db_data/mysql.err</a>&apos; does not contain any errors or warnings.

File content of '/home/horst/.local/share/akonadi/db_data/mysql.err':
140302 17:14:42 InnoDB: The InnoDB memory heap is disabled
140302 17:14:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140302 17:14:42 InnoDB: Compressed tables use zlib 1.2.8
140302 17:14:42 InnoDB: Using Linux native AIO
140302 17:14:42 InnoDB: Initializing buffer pool, size = 80.0M
140302 17:14:42 InnoDB: Completed initialization of buffer pool
140302 17:14:42 InnoDB: highest supported file format is Barracuda.
140302 17:14:43 InnoDB: Waiting for the background threads to start
140302 17:14:44 Percona XtraDB (http://www.percona.com) 5.5.33-MariaDB-31.1 started; log sequence number 24318647
140302 17:14:44 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.33-MariaDB' socket: '/tmp/akonadi-horst.tIMpw9/mysql.socket' port: 0 openSUSE package


Test 6: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

[client]
default-character-set=utf8


Test 7: SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8: SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/horst/.local/share/akonadi/mysql.conf'>/home/horst/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/horst/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

[client]
default-character-set=utf8


Test 9: SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.10.3


Test 10: SUCCESS
--------

Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.

Test 11: SUCCESS
--------

Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.

Test 12: SUCCESS
--------

Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.

Test 13: SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

Test 14: SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 15: SUCCESS
--------

Resource agents found.
Details: At least one resource agent has been found.

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/etc/opt/kde3/share:/opt/kde3/share'

Test 16: SUCCESS
--------

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

Test 17: ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/horst/.local/share/akonadi/akonadiserver.error.old'>/home/horst/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/horst/.local/share/akonadi/akonadiserver.error.old':
Control process died, committing suicide!


Test 18: SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 19: SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

Wo kann ich den Fehler suchen?
Oder hat jemand ein Lösung für mich?

Auf jeden Fall schon einmal vielen Dank für Hilfe und Tips.
 

P6CNAT

Advanced Hacker
Hallo Horst,

Die Meldung "The Akonadi server reported errors during its previous startup." aus Test 17 ist Unsinn. Bei mir steht da auch "Control process died, committing suicide!" drin, aber zu einer Uhrzeit als ich den Rechner herunter gefahren hatte. Nach einem "kill" Kommando ist das durchaus plausibel. Merkwürdigerweise kann ich auch nirgendwo eine Datei "akonadiserver.error" finden. :???:

Den Effekt, dass verschobene Mails wieder im Posteingang auftauchen hatte ich auch schon. Aber nur sporadisch und seit der Installation von openSUSE 13.1 ist das nicht mehr vorgekommen. Ich hatte auch einen Verdacht woran es liegen könnte, komme aber nicht mehr auf das Ergebnis. :nosmile:

Hast du zufällig MariaDB/MySQL installiert und kennst SQL Kommandos? Dann könntest du die Akonadi Datenbank manuell auf Auffälligkeiten prüfen. Eine Anleitung habe ich in Linupedia geschrieben, allerdings wird die Grafik mit dem Datenmodell nicht mehr angezeigt. Bei Interesse könnte ich es hier posten.

Grüße
Georg
 
Oben