From: Starodumoff Ilya <sendmeforever@mail.ru>
To: sysadmins@lists.altlinux.org
Subject: Re: [Sysadmins] postfix и авторизация на провайдерском smtp
Date: Mon, 15 Oct 2007 17:20:04 +0600
Message-ID: <200710151720.05056.sendmeforever@mail.ru> (raw)
In-Reply-To: <20071015140128.2cc7d5fa.dolgov@mail.zp.ua>
В сообщении от Понедельник 15 октября 2007 Oleg Dolgov написал(a):
> Здравствуйте.
>
> Перекочевал тут на ОГО! от Укртелекома. Переустановил сервер. Поставил
> 4.0
> Теперь затык с почтой. Нимогу никак расчехлить postfix.
> Вроде все восстановил из бэкапа (после Мастера 2.4), подправил на что
> ругался, но вот теперь низадача:
>
> defer_transports = smtp
> relayhost = smtp сервер, требующий авторизацию.
>
> как и куда ее прописать, дабы постфикс нормально выталкивал почту из
> офиса?
>
> Заранее благодарен.
Лень "выжимать", цитирую полностью :) :
12.5 SMTP Client Authentication
You may want your Postfix server to relay through other servers that require
SMTP authentication. In addition to requiring passwords on your own server,
you can configure Postfix to provide login names and passwords when relaying
mail through other SMTP servers.
You have to provide Postfix with a password file that contains the credentials
it should use when authenticating to other servers. Entries in the password
file contain a domain or hostname, username, and password in the form: domain
username:password. For the domain or hostname, Postfix first checks for the
destination domain from the recipient address. If it doesn't find the domain,
it then checks for the hostname it is connecting to. This allows Postfix to
work easily with sites that have multiple MX hosts that share the same user
database. Use smtp_sasl_password_maps parameter to specify where your
password file is.
The client smtp_sasl_security_options parameter works just like server
smtpd_sasl_security_options (discussed earlier in the chapter) for the SMTP
servers. If you don't specify any options, the default allows all available
mechanisms including plaintext but not anonymous logins.
12.5.1 Procedure to Enable SMTP Client Authentication
Use the following steps to configure Postfix to provide a login and password
when relaying mail. In this example, you'll set up two different passwords
for Postfix to authenticate when relaying through any server for the domain
ora.com and through a host called mail.postfix.org:
Create a file called /etc/postfix/sasl_passwd with entries for each host,
login, and password combination you need. Your file should resemble the
following:
ora.com kdent:Rumpelstiltskin
mail.postfix.org kyle:quixote
Execute postmap on the file:
# postmap /etc/postfix/sasl_passwd
Edit main.cf to turn on client authentication. Notice that you are now setting
smtp_sasl_auth_enable instead of smtpd_sasl_auth_enable as you did to turn on
authentication at the server. You must also set smtp_sasl_password_maps to
point to the password file you created:
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
Reload Postfix so that it recognizes the changes in its main.cf configuration
file:
# postfix reload
Now, when the Postfix SMTP client attempts to relay messages through any of
the domains or hosts listed in /etc/postfix/sasl_passwd, it will offer the
corresponding authentication credentials. For example, if your Postfix smtp
client connects to the server mail.ora.com, it authenticates with the
username kdent and the password Rumpelstiltskin.
--
С уважением,
Стародумов Илья
next prev parent reply other threads:[~2007-10-15 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 11:01 Oleg Dolgov
2007-10-15 11:20 ` Starodumoff Ilya [this message]
2007-10-15 11:53 ` Oleg Dolgov
2007-10-15 12:43 ` Oleg Dolgov
2007-10-16 6:03 ` Vladimir V. Kamarzin
2007-10-15 11:20 ` Oleg Dolgov
2007-10-16 8:54 ` Oleg Dolgov
2007-10-16 12:21 ` Oleg Dolgov
2007-10-16 12:54 ` Vladimir V. Kamarzin
2007-10-16 13:03 ` Oleg Dolgov
2007-10-17 5:21 ` Vladimir V. Kamarzin
2007-10-17 7:16 ` Oleg Dolgov
2007-10-17 9:45 ` Vladimir V. Kamarzin
2007-10-17 10:12 ` Oleg Dolgov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710151720.05056.sendmeforever@mail.ru \
--to=sendmeforever@mail.ru \
--cc=sysadmins@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux sysadmins discussion
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sysadmins/0 sysadmins/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sysadmins sysadmins/ http://lore.altlinux.org/sysadmins \
sysadmins@lists.altlinux.org sysadmins@lists.altlinux.ru sysadmins@lists.altlinux.com
public-inbox-index sysadmins
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sysadmins
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git