Synology-Forum.nl
Packages => Officiële Packages => Mail Server => Topic gestart door: Robert Koopman op 24 mei 2019, 13:34:45
-
Toch een vreemd probleempje met Mailserver vanmorgen.
De complete aliassen lijst was leeg. Toch onhandig als er 30+ aliassen instonden?
Via Hyperbackup Mailserver teruggezet op een andere nas waar Mailserver niet op stond.
Een backup van eergisteren, daar stond alles nog in.
Deze lijst teruggezet en alles weer in orde.
Blijft toch de vraag waarom was dit weg/leeg?
-
Hier gelukkig niet. Er staan hier een stuk of 20 in die ik ook niet allen terug zou kunnen zetten.
Tip voor de toekomst: Bij elke aanpassing het bestand exporteren. De lijst is platte tekst in het formaat:
MAILER-DAEMON: postmaster
postmaster: root
alias: account
Deze eerste twee staan er altijd in en daarna komt je eigen alias.
-
Heb het bestandje nu inderdaad even veilig gesteld.
Maar kan nergens vinden hoe het heeft kunnen verdwijnen.
-
En vandaag de aliassen lijst wederom leeg?
Zo draai je van 2012 tot 14 dagen terug zonder dit probleem en nu al voor de tweede keer fout.
Vreemd.
Maar bestandje teruggezet en alles is er weer.
-
En hedenmorgen weer leeg.
-
Heeft dat iets met een automatische update te maken? Er was woensdag of donderdag een update van MailServer.
Of zit er een heel gekke alias in waar hij over struikelt en dan alles maar wist? In elk geval vreemd omdat het bestand eigenlijk alleen hoeft te veranderen bij aanpassen van een alias.
-
Die update gedaan van de week en gaf geen problemen.
Ik mail naar een alias elke ochtend om 10 uur het rapport van de mailserver.
Krijg ik om 10:01 een mailtje van mijn SMTP provider dat die mail onbestelbaar is.
Ik weet zo dat de alias tabel weer leeg is 8)
Dacht eerst even dat het steeds op zaterdag gebeurde, ik maak in deze nacht een backup van mijn Directory Server, maar dat is dus niet zo.
-
Nu wel weer op zaterdag.
Volgende week vrijdagvond kijken of de lijst er nog staan en dan zaterdagmorgen weer na de backup van de Directory Server.
Ik gebruik LDAP en Mail Server heeft daar natuurlijk ook wel iets me te maken.
-
Ik heb eens bij postfix gekeken en vond daar het volgende document. In het begin staat een verwijzing naar LDAP. Daar maak ik uit op dat ook LDAP de aliaslijst kan aanleveren. Daar zal het bij jou dan misschien mis gaan. Is daar dan ook een aliaslijst aan te maken? Ik zie het niet. Ik zie bij LDAP gebruikers wel een optie om de gegevens te updaten. Was als je die knop gebruikt? is dan de alias tabel weer leeg?
Uit het onderstaande verhaal maak ik op dat de alias tabel een tekstfile is. Na editen wordt de binary "newaliasses' aangeroepen, die dit omzet in het db formaat voor snellere toegang door postfix. Mocht je dus met de hand in die aliasfile editen, dan moet je daarna "/var/packages/MailServer/target/bin/newaliases" aanroepen.
# ALIASES(5) ALIASES(5)
#
# NAME
# aliases - Postfix local alias database format
#
# SYNOPSIS
# newaliases
#
# DESCRIPTION
# The aliases(5) table provides a system-wide mechanism to
# redirect mail for local recipients. The redirections are
# processed by the Postfix local(8) delivery agent.
#
# Normally, the aliases(5) table is specified as a text file
# that serves as input to the postalias(1) command. The
# result, an indexed file in dbm or db format, is used for
# fast lookup by the mail system. Execute the command
# newaliases in order to rebuild the indexed file after
# changing the Postfix alias database.
#
# When the table is provided via other means such as NIS,
# LDAP or SQL, the same lookups are done as for ordinary
# indexed files.
#
# Alternatively, the table can be provided as a regu-
# lar-expression map where patterns are given as regular
# expressions. In this case, the lookups are done in a
# slightly different way as described below under "REGULAR
# EXPRESSION TABLES".
#
# Users can control delivery of their own mail by setting up
# .forward files in their home directory. Lines in per-user
# .forward files have the same syntax as the right-hand side
# of aliases(5) entries.
#
# The format of the alias database input file is as follows:
#
# o An alias definition has the form
#
# name: value1, value2, ...
#
# o Empty lines and whitespace-only lines are ignored,
# as are lines whose first non-whitespace character
# is a `#'.
#
# o A logical line starts with non-whitespace text. A
# line that starts with whitespace continues a logi-
# cal line.
#
# The name is a local address (no domain part). Use double
# quotes when the name contains any special characters such
# as whitespace, `#', `:', or `@'. The name is folded to
# lowercase, in order to make database lookups case insensi-
# tive.
#
# In addition, when an alias exists for owner-name, this
# will override the envelope sender address, so that deliv-
# ery diagnostics are directed to owner-name, instead of the
# originator of the message (for details, see
# owner_request_special, expand_owner_alias and
# reset_owner_alias). This is typically used to direct
# delivery errors to the maintainer of a mailing list, who
# is in a better position to deal with mailing list delivery
# problems than the originator of the undelivered mail.
#
# The value contains one or more of the following:
#
# address
# Mail is forwarded to address, which is compatible
# with the RFC 822 standard.
#
# /file/name
# Mail is appended to /file/name. See local(8) for
# details of delivery to file. Delivery is not lim-
# ited to regular files. For example, to dispose of
# unwanted mail, deflect it to /dev/null.
#
# |command
# Mail is piped into command. Commands that contain
# special characters, such as whitespace, should be
# enclosed between double quotes. See local(8) for
# details of delivery to command.
#
# When the command fails, a limited amount of command
# output is mailed back to the sender. The file
# /usr/include/sysexits.h defines the expected exit
# status codes. For example, use "|exit 67" to simu-
# late a "user unknown" error, and "|exit 0" to
# implement an expensive black hole.
#
# :include:/file/name
# Mail is sent to the destinations listed in the
# named file. Lines in :include: files have the same
# syntax as the right-hand side of alias entries.
#
# A destination can be any destination that is
# described in this manual page. However, delivery to
# "|command" and /file/name is disallowed by default.
# To enable, edit the allow_mail_to_commands and
# allow_mail_to_files configuration parameters.
#
# ADDRESS EXTENSION
# When alias database search fails, and the recipient local-
# part contains the optional recipient delimiter (e.g.,
# user+foo), the search is repeated for the unextended
# address (e.g., user).
#
# The propagate_unmatched_extensions parameter controls
# whether an unmatched address extension (+foo) is propa-
# gated to the result of table lookup.
#
# CASE FOLDING
# The local(8) delivery agent always folds the search string
# to lowercase before database lookup.
#
# REGULAR EXPRESSION TABLES
# This section describes how the table lookups change when
# the table is given in the form of regular expressions. For
# a description of regular expression lookup table syntax,
# see regexp_table(5) or pcre_table(5). NOTE: these formats
# do not use ":" at the end of a pattern.
#
# Each regular expression is applied to the entire search
# string. Thus, a search string user+foo is not broken up
# into user and foo.
#
# Regular expressions are applied in the order as specified
# in the table, until a regular expression is found that
# matches the search string.
#
# Lookup results are the same as with indexed file lookups.
# For security reasons there is no support for $1, $2 etc.
# substring interpolation.
#
# SECURITY
# The local(8) delivery agent disallows regular expression
# substitution of $1 etc. in alias_maps, because that would
# open a security hole.
#
# The local(8) delivery agent will silently ignore requests
# to use the proxymap(8) server within alias_maps. Instead
# it will open the table directly. Before Postfix version
# 2.2, the local(8) delivery agent will terminate with a
# fatal error.
#
# CONFIGURATION PARAMETERS
# The following main.cf parameters are especially relevant.
# The text below provides only a parameter summary. See
# postconf(5) for more details including examples.
#
# alias_database (see 'postconf -d' output)
# The alias databases for local(8) delivery that are
# updated with "newaliases" or with "sendmail -bi".
#
# alias_maps (see 'postconf -d' output)
# The alias databases that are used for local(8)
# delivery.
#
# allow_mail_to_commands (alias, forward)
# Restrict local(8) mail delivery to external com-
# mands.
#
# allow_mail_to_files (alias, forward)
# Restrict local(8) mail delivery to external files.
#
# expand_owner_alias (no)
# When delivering to an alias "aliasname" that has an
# "owner-aliasname" companion alias, set the envelope
# sender address to the expansion of the
# "owner-aliasname" alias.
#
# propagate_unmatched_extensions (canonical, virtual)
# What address lookup tables copy an address exten-
# sion from the lookup key to the lookup result.
#
# owner_request_special (yes)
# Enable special treatment for owner-listname entries
# in the aliases(5) file, and don't split owner-list-
# name and listname-request address localparts when
# the recipient_delimiter is set to "-".
#
# recipient_delimiter (empty)
# The set of characters that can separate a user name
# from its extension (example: user+foo), or a .for-
# ward file name from its extension (example: .for-
# ward+foo).
#
# Available in Postfix version 2.3 and later:
#
# frozen_delivered_to (yes)
# Update the local(8) delivery agent's idea of the
# Delivered-To: address (see prepend_deliv-
# ered_header) only once, at the start of a delivery
# attempt; do not update the Delivered-To: address
# while expanding aliases or .forward files.
#
# STANDARDS
# RFC 822 (ARPA Internet Text Messages)
#
# SEE ALSO
# local(8), local delivery agent
# newaliases(1), create/update alias database
# postalias(1), create/update alias database
# postconf(5), configuration parameters
#
# README FILES
# Use "postconf readme_directory" or "postconf html_direc-
# tory" to locate this information.
# DATABASE_README, Postfix lookup table overview
#
# LICENSE
# The Secure Mailer license must be distributed with this
# software.
#
# AUTHOR(S)
# Wietse Venema
# IBM T.J. Watson Research
# P.O. Box 704
# Yorktown Heights, NY 10598, USA
#
# Wietse Venema
# Google, Inc.
# 111 8th Avenue
# New York, NY 10011, USA
#
# ALIASES(5)
-
Sinds de update van 6.2.2-24922-2 is het niet meer voorgekomen dat deze lijst opeens leeg is.
Heeft er misschien mee te maken gehad.