Search K
Appearance
Appearance
doveadm [GLOBAL OPTIONS] [-f formatter] fetch [-S socket_path] -A fields search_query
doveadm [GLOBAL OPTIONS] [-f formatter] fetch [-S socket_path] -F file fields search_query
doveadm [GLOBAL OPTIONS] [-f formatter] fetch [-S socket_path] --no-userdb-lookup fields search_query
doveadm [GLOBAL OPTIONS] [-f formatter] fetch [-S socket_path] -u user fields search_query
doveadm fetch can be used to fetch messages' contents and metadata. This can be useful for scripts and for debugging. If you want to fetch messages one at a time, see doveadm-search(1)
.
Global doveadm(1)
options:
Enables verbosity and debug messages.
Do not read any config file, just use defaults. The dovecot_storage_version
defaults to the latest version, but can be overridden with -o.
Preserve entire environment for doveadm, not just import_environment
.
Enables verbosity, including progress counter.
If using multiple Dovecot instances, choose the config file based on this instance name.
See instance_name
for more information.
Read configuration from the given config-file. By default it first reads config socket, and then falls back to /etc/dovecot/dovecot.conf. You can also point this to config socket of some instance running compatible version.
Overrides the configuration setting from /etc/dovecot/dovecot.conf and from the userdb with the given value. In order to override multiple settings, the -o option may be specified multiple times.
Specifies the formatter for formatting the output. Supported formatters are:
This command uses by default the output formatter pager.
If the -A option is present, the command will be performed for all users. Using this option in combination with system users from userdb { driver = passwd } is not recommended, because it contains also users with a lower UID than the one configured with the first_valid_uid
setting.
When the SQL userdb module is used make sure that the iterate_query setting in /etc/dovecot/dovecot-sql.conf.ext matches your database layout. When using the LDAP userdb module, make sure that the iterate_attrs and iterate_filter settings in /etc/dovecot/dovecot-ldap.conf.ext match your LDAP schema. Otherwise doveadm(1)
will be unable to iterate over all users.
Execute the command for all the users in the file. This is similar to the -A option, but instead of getting the list of users from the userdb, they are read from the given file. The file contains one username per line.
Do not perform userdb lookup. Use the USER
environment variable to specify the username.
The option's argument is either an absolute path to a local UNIX domain socket, or a hostname and port (hostname:port), in order to connect a remote host via a TCP socket.
This allows an administrator to execute doveadm(1)
mail commands through the given socket.
Run the command only for the given user. It's also possible to use '*' and '?' wildcards (e.g. -u *@example.org).
One or more result field names to display, if the search_query matches any messages. In order to specify multiple fields, enclose them in single or double quotes.
Date and time of final delivery, when the message was delivered to a user's mailbox for the first time.
The internal date and time of the source message, when the message was copied by the IMAP COPY command.
The date-time attribute when present, otherwise the current time, when the message was saved by the IMAP APPEND command.
Fetch messages matching this search query. See doveadm-search-query(1)
for details.
This example based on the first example from doveadm-search(1)
. We are fetching the fields mailbox and date.sent from user bob's mailbox with the guid "3a94c928d66ebe4bda04000015811c6a" for the messages with the UIDs 8, 25 and 45.
$ doveadm fetch -u bob "mailbox date.sent" mailbox-guid 3a94c928d66ebe4bda04000015811c6a uid 8,25,45
mailbox: dovecot/pigeonhole/2.0
date.sent: 2010-01-19 01:17:41 (+0100)
^L
mailbox: dovecot/pigeonhole/2.0
date.sent: 2010-01-28 09:38:49 (+0100)
^L
mailbox: dovecot/pigeonhole/2.0
date.sent: 2010-03-28 18:41:14 (+0200)
Report bugs, including doveconf -n output, to the Dovecot Mailing List dovecot@dovecot.org. Information about reporting bugs is available at: https://dovecot.org/bugreport.html