bon je me suis attaquer a devcot
et quand j’ai du modifier son fichier son fichier de configuration:
a savoir rajouter
socket listen {
client {
path = /var/spool/postfix/private/auth
group = postfix
mode = 0660
}
quand je redemrre devcot:
/etc/init.d/dovecot restart
Restarting IMAP/POP3 mail server: dovecotError: Error in configuration file /etc/dovecot/dovecot.conf line 894: Unknown section type (section changed in /etc/dovecot/dovecot.conf at line 888)
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
failed!
un extrait du fichier original:
cat /etc/dovecot/dovecot.conf |grep "auth default {" -A 30
auth default {
# Space separated list of wanted authentication mechanisms:
# plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi otp skey
# gss-spnego
# NOTE: See also disable_plaintext_auth setting.
mechanisms = plain
#
# Password database is used to verify user's password (and nothing more).
# You can have multiple passdbs and userdbs. This is useful if you want to
# allow both system users (/etc/passwd) and virtual users to login without
# duplicating the system users into virtual database.
#
# </usr/share/doc/dovecot-common/wiki/PasswordDatabase.txt>
#
# By adding master=yes setting inside a passdb you make the passdb a list
# of "master users", who can log in as anyone else. Unless you're using PAM,
# you probably still want the destination user to be looked up from passdb
# that it really exists. This can be done by adding pass=yes setting to the
# master passdb. </usr/share/doc/dovecot-common/wiki/Authentication.MasterUsers.txt>
# Users can be temporarily disabled by adding a passdb with deny=yes.
# If the user is found from that database, authentication will fail.
# The deny passdb should always be specified before others, so it gets
# checked first. Here's an example:
#passdb passwd-file {
# File contains a list of usernames, one per line
#args = /etc/dovecot/dovecot.deny
#deny = yes
#}
On peux y voir:
mechanisms = plain
mai a quoi sa sert ? sa remplace peut etre déja le cote cité ?
sinon le truc qui me derange c’est que n’importe qui peux envoiye un mail de cette manière
root@mondomaine.com
(en gros tout utilisateur systeme)
comment empecher que root ce prenne des mail depuis l’exterieur, mai autoriser ceux en local generer par d’autre application par exemple apache ?
[/quote]
M$ y a pas, donc pas de risque de ce coter.
[/quote]