Iredmail smtp ошибка 451 невозможно добавить получателя

Skip to forum content

iRedMail

Works on CentOS, Rocky, Debian, Ubuntu, FreeBSD, OpenBSD

You are not logged in. Please login or register.

May 23, 2023: iRedMail-1.6.3 has been released.



  • Spider Email Archiver: Lightweight on-premises email archiving software, developed by iRedMail team.
  • Join our Telegram group (@iredmail_chat) to get help from other iRedMail users.

[ Closed ] [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

Pages 1

You must login or register to post a reply

1 2011-07-08 02:47:45

  • blason
  • Member
  • Offline
  • Registered: 2011-07-08
  • Posts: 4

Topic: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

Hi Folks,

I am trying iRedOS and just insatlled the same. Installation was pretty smooth but when I try to send email to others I keep getting below error in maillog.

Jul  8 00:08:35 mx1 roundcube: Invalid response code received from server (451):
Jul  8 00:08:35 mx1 roundcube: [08-Jul-2011 00:08:35 -0400]: SMTP Error: SMTP error: Failed to add recipient ‘xxx@xxx.xxx’ in /var/www/roundcubemail-0.3.1/program/steps/mail/func.inc on line 1365 (POST /webmail/?_task=mail&_action=send)

Any clue why?

—-

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Stable release is out.

2 Reply by ZhangHuangbin 2011-07-08 08:01:58

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,319

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

Please paste related postfix log in /var/log/maillog, not just log of roundcube.

3 Reply by blason 2011-07-08 15:26:43

  • blason
  • Member
  • Offline
  • Registered: 2011-07-08
  • Posts: 4

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

ZhangHuangbin wrote:

Please paste related postfix log in /var/log/maillog, not just log of roundcube.

Ok here are the logs from maillog file

Jul  8 02:44:09 mx1 postfix/smtpd[2831]: connect from mx1.isn.net[127.0.0.1]
Jul  8 02:44:09 mx1 postfix/smtpd[2831]: warning: connect to 127.0.0.1:7777: Connection refused
Jul  8 02:44:09 mx1 postfix/smtpd[2831]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Jul  8 02:44:10 mx1 postfix/smtpd[2831]: warning: connect to 127.0.0.1:7777: Connection refused
Jul  8 02:44:10 mx1 postfix/smtpd[2831]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Jul  8 02:44:10 mx1 postfix/smtpd[2831]: NOQUEUE: reject: RCPT from mx1.isn.net[127.0.0.1]: 451 4.3.5 Server configuration problem; from=<xxx@isn.net> to=<xxx@isn.net> proto=ESMTP helo=<192.168.1.203>
Jul  8 02:44:10 mx1 roundcube: Invalid response code received from server (451):
Jul  8 02:44:10 mx1 roundcube: [08-Jul-2011 02:44:10 -0400]: SMTP Error: SMTP error: Failed to add recipient ‘blason@isn.net’ in /var/www/roundcubemail-0.3.1/program/steps/mail/func.inc on line 1365 (POST /webmail/?_task=mail&_action=send)
Jul  8 02:44:10 mx1 postfix/smtpd[2831]: disconnect from mx1.isn.net[127.0.0.1]

4 Reply by blason 2011-07-08 15:37:12

  • blason
  • Member
  • Offline
  • Registered: 2011-07-08
  • Posts: 4

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

It seems there is some issue with iRedAPD. I have gone through the documents and didnt find any files for iRedAPD in iRedOS.
is it not included with iRedOS?

5 Reply by ZhangHuangbin 2011-07-08 22:58:26

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,319

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

blason wrote:

Jul  8 02:44:09 mx1 postfix/smtpd[2831]: warning: connect to 127.0.0.1:7777: Connection refused

iRedAPD service is not running.
Please start it immediately:

# /etc/init.d/iredapd restart

It will log in file /var/log/iredapd.log, If it doesn’t work, please check its log file first.

6 Reply by blason 2011-07-09 03:50:52

  • blason
  • Member
  • Offline
  • Registered: 2011-07-08
  • Posts: 4

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

Great ..Thnks a ton..I just resolved the issue and mail routing is working as it should be. I appeared to be ireapd issue only.

7 Reply by sriram.r153 2018-04-30 02:12:05

  • sriram.r153
  • Member
  • Offline
  • Registered: 2018-04-30
  • Posts: 4

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

same issue iam facing
Apr 29 17:49:09 mail postfix/submission/smtpd[1894]: disconnect from localhost[127.0.0.1]
Apr 29 17:55:34 mail clamd[1408]: SelfCheck: Database status OK.
Apr 29 17:58:40 mail postfix/postfix-script[2529]: stopping the Postfix mail system
Apr 29 17:58:40 mail postfix/master[1279]: terminating on signal 15
Apr 29 17:58:40 mail postfix/postfix-script[2614]: warning: /var/spool/postfix/etc/hosts and /etc/hosts differ
Apr 29 17:58:40 mail postfix/postfix-script[2640]: starting the Postfix mail system
Apr 29 17:58:40 mail postfix/master[2643]: daemon started — version 2.10.1, configuration /etc/postfix
Apr 29 17:58:40 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/submission/smtpd[2755]: connect from localhost[127.0.0.1]
Apr 29 17:59:44 mail postfix/submission/smtpd[2755]: Anonymous TLS connection established from localhost[127.0.0.1]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/proxymap[2646]: warning: pgsql:/etc/postfix/pgsql/transport_maps_user.cf is unavailable. unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/trivial-rewrite[2757]: warning: proxy:pgsql:/etc/postfix/pgsql/transport_maps_user.cf lookup error for «*»
Apr 29 17:59:44 mail postfix/proxymap[2646]: warning: pgsql:/etc/postfix/pgsql/transport_maps_user.cf is unavailable. unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/trivial-rewrite[2757]: warning: proxy:pgsql:/etc/postfix/pgsql/transport_maps_user.cf lookup error for «*»
Apr 29 17:59:44 mail postfix/proxymap[2646]: warning: pgsql:/etc/postfix/pgsql/virtual_mailbox_domains.cf is unavailable. unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/trivial-rewrite[2757]: warning: proxy:pgsql:/etc/postfix/pgsql/virtual_mailbox_domains.cf: table lookup problem
Apr 29 17:59:44 mail postfix/trivial-rewrite[2757]: warning: virtual_mailbox_domains lookup failure
Apr 29 17:59:44 mail postfix/proxymap[2646]: warning: pgsql:/etc/postfix/pgsql/virtual_mailbox_domains.cf is unavailable. unsupported dictionary type: pgsql
Apr 29 17:59:44 mail postfix/trivial-rewrite[2757]: warning: proxy:pgsql:/etc/postfix/pgsql/virtual_mailbox_domains.cf: table lookup problem
Apr 29 17:59:44 mail postfix/trivial-rewrite[2757]: warning: virtual_mailbox_domains lookup failure
Apr 29 17:59:44 mail postfix/submission/smtpd[2755]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 <postmaster@tradesocio.lan>: Temporary lookup failure; from=<postmaster@tradesocio.lan> to=<sriram.r153@gmail.com> proto=ESMTP helo=<_>
Apr 29 17:59:44 mail roundcube: <6bqgt9g5> SMTP Error: Failed to add recipient ‘sriram.r153@gmail.com’. 4.3.0 <postmaster@tradesocio.lan>: Temporary lookup failure (Code: 451) in /var/www/roundcubemail-1.3.0/program/lib/Roundcube/rcube.php on line 1665 (POST /mail/?_task=mail&_unlock=loading1525024784127&_lang=en_US&_framed=1&_action=send)
Apr 29 17:59:44 mail postfix/submission/smtpd[2755]: disconnect from localhost[127.0.0.1]
Apr 29 18:05:34 mail clamd[1408]: SelfCheck: Database status OK.

8 Reply by ZhangHuangbin 2018-04-30 07:07:46

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,319

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

sriram.r153 wrote:

Apr 29 17:58:40 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql

Please make sure package ‘postfix-pgsql’ is installed on server.

9 Reply by sriram.r153 2018-04-30 13:17:27

  • sriram.r153
  • Member
  • Offline
  • Registered: 2018-04-30
  • Posts: 4

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

ZhangHuangbin wrote:

sriram.r153 wrote:

Apr 29 17:58:40 mail postfix/proxymap[2646]: error: unsupported dictionary type: pgsql

Please make sure package ‘postfix-pgsql’ is installed on server.

Thanks for reply,

checking.

10 Reply by sriram.r153 2018-04-30 13:35:29 (edited by sriram.r153 2018-04-30 13:36:54)

  • sriram.r153
  • Member
  • Offline
  • Registered: 2018-04-30
  • Posts: 4

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

Hi package ‘postfix-pgsql’ instaled
i don’t have luck sad same issue facing

please help me on this
Thanks in advance:)

11 Reply by ZhangHuangbin 2018-05-01 17:00:45

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,319

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

*) If ‘postfix-pgsql’ package is installed, did you restart Postfix service?
*) What’s the latest error message now?

12 Reply by sriram.r153 2018-05-02 03:28:34

  • sriram.r153
  • Member
  • Offline
  • Registered: 2018-04-30
  • Posts: 4

Re: [SOLVED] SMTP Error: SMTP error(451): Failed to add recipient

ZhangHuangbin wrote:

*) If ‘postfix-pgsql’ package is installed, did you restart Postfix service?
*) What’s the latest error message now?

Hi

Thanks for reply i have uninstalled and reinstalled with mariadb then the smtp issue is solved

Thanks you.

Posts: 12

Pages 1

You must login or register to post a reply

Generated in 0.011 seconds (57% PHP — 43% DB) with 9 queries

Источник

Errors you may see while maintaining iRedMail server

!!! attention

 Check out the lightweight on-premises email archiving software developed by iRedMail team: [Spider Email Archiver](https://spiderd.io/).

[TOC]

Postfix (SMTP)

Intended policy rejection, please try again later

Sample error message in Postfix log file:

Jul 24 06:43:08 mx0 postfix/smtpd[12719]: NOQUEUE: reject: RCPT from sender.com[xx.xx.xx.xx]: 451 4.7.1 recipient@my-domain.com: Recipient address rejected: Intentional policy rejection, please try again later{: .red }; from=sender@sender-domain.com to=recipient@my-domain.com proto=SMTP helo=<mx2.sender.com>

This error is caused by greylisting service, sender server will retry to
deliver the same email, and your server will accept it after few retries.

  • For more technical details about Greylisting, please visit:
    • Homepage: What is greylisting?
    • Articles about greylisting
  • To manage greylisting service, please read iRedAPD tutorial: Manage iRedAPD: Greylisting

Sender address rejected: not logged in

Sample error message in Postfix log file:

Jun 24 11:57:13 mx1 postfix/smtpd[2667]: NOQUEUE: reject: RCPT from
mail.mydomain.com[1.2.3.4]: 553 5.7.1 <sombody@my-domain.com>: Sender address
rejected: not logged in{: .red }; from=<sombody@my-domain.com>
to=<receipent@receipentdomain.com> proto=ESMTP helo=<client_helo.com>

This error is caused by incorrectly configured mail client application, not a
server issue.

All mail users are forced to perform SMTP auth before sending email, so you
must configure your mail client applications (Outlook, Thunderbird, …) to
enable SMTP authentication.

Sender address rejected: not owned by user user@domain.ltd

This error is caused by restriction rule reject_sender_login_mismatch in
Postfix parameter smtpd_recipient_restrictions, in file /etc/postfix/main.cf:

smtpd_recipient_restrictions =
    ...
    reject_sender_login_mismatch,
    ...

It will reject the request when $smtpd_sender_login_maps specifies an owner
for the MAIL FROM address, but the client is not (SASL) logged in as that MAIL
FROM address owner; or when the client is (SASL) logged in, but the client
login name doesn’t own the MAIL FROM address according to $smtpd_sender_login_maps.
Check manual page of Postfix configuration file for more details.

Removing reject_sender_login_mismatch and restarting Postfix service fixes
this issue.

!!! note

If you want to allow some users to send as other users, or allow all users
to send as their alias addresses, or allow member of mail list/alias to send
as mail list/alias, you should try iRedAPD plugin `reject_sender_login_mismatch`
instead (requires iRedAPD-1.4.4 or later releases).

Read comments in file `/opt/iredapd/plugins/reject_sender_login_mismatch.py`,
then enable it in iRedAPD config file `/opt/iredapd/settings.py` (`plugins = `),
restart iRedAPD service. That's all.

Recipient address rejected: SMTP AUTH is required for users under this sender domain

With old iRedAPD releases, the error messages may be one of below:

  • SMTP AUTH is required, or it is a spam with forged sender domain
  • Recipient address rejected: Policy rejection not logged in

This error message means sender domain is hosted locally on your iRedMail
server, but sender doesn’t perform SMTP AUTH to send email.

  1. If the email is not sent by a server or device under your control, most
    likely this email is spam with forged sender address, it’s safe to ignore it
    in this case.

  2. If the email is sent from your server, that means your MUA (Mail User Agent,
    e.g. Outlook, Thunderbird, etc) is not configured to perform SMTP
    authentication to send email. Enabling smtp auth will fix this automatically.

  3. If the email is sent from a server or device NOT under your control,
    you want to bypass the email sent from this sender address but not the whole
    server, please list this sender address in iRedAPD config file
    /opt/iredapd/settings.py, parameter ALLOWED_FORGED_SENDERS like below:

    # Single address.
ALLOWED_FORGED_SENDERS = ['user@domain.com']

# Or, whole domain.
ALLOWED_FORGED_SENDERS = ['domain.com']

    !!! warning

     With this setting, iRedAPD accepts all emails with this forged address
 from __ANY__ mail server.

    Notes:

    • This parameter doesn’t exist in /opt/iredapd/settings.py by default,
      feel free to add it manually. You can find detailed comments in file
      /opt/iredapd/libs/default_settings.py, read the comments to understand
      it better.
    • This parameter name must be in upper cases.

  4. If the email is sent by a server or device under your control and you want to
    trust this server/device and bypass all emails, you can whitelist the IP
    address of this server/device in iRedAPD config file /opt/iredapd/settings.py like below:

    MYNETWORKS = ['192.168.0.10', '192.168.0.20', '192.168.0.30']

    Notes:

    • This parameter doesn’t exist in /opt/iredapd/settings.py by default,
      feel free to add it manually. You can find detailed comments in file
      /opt/iredapd/libs/default_settings.py, read the comments to understand
      it better.
    • This parameter name must be in upper cases.

Recipient address rejected: Policy rejection due to null sender

Sample error message in Postfix log file:

Tue 15 16:00:17 mail postfix/submission/smtpd[412508]: NOQUEUE: reject: RCPT from unknown[119.12.37.112]: 554 5.7.1 user@domain.com: Recipient address rejected: Policy rejection due to null sender; from=<>{: .red } to=user@domain.com proto=ESMTP helo=<…>

If end user sends email with smtp authentication, but specify null sender
in SMTP session (from=<> in Postfix log), iRedAPD plugin reject_null_sender
will reject the email with above error message.

This behaviour looks like spamming, and null sender won’t trigger throttling.

The solution is making sure end user’s MUA is configured to send email with
SMTP authentication, and specify a sender address.

Recipient address rejected: Sender is not same as SMTP authenticate username

case #1

If the smtp authenticate username is different than the address in mail header
From: field, you will get this rejection (by iRedAPD).

Solutions:

  • If you don’t need to send as different sender, please update your mail
    composer (like Outlook, Thunderbird, webmail, your own script used to send
    email, etc) to use same address as smtp authenticate username and sender
    address in From:.
  • If you do need to send as different sender address (From:), please add one
    setting in iRedAPD config file /opt/iredapd/settings.py, then restart
    iRedAPD service:
ALLOWED_LOGIN_MISMATCH_SENDERS = ['user@mydomain.com']

Notes: user@mydomain.com is the email address you used for smtp authentication.

case #2

If you’re a member of mailing list or mail alias, and trying to send email with
the email address of mailing list/alias as sender address, you will get same
error. There’s another setting you can try (either one is ok):

ALLOWED_LOGIN_MISMATCH_LIST_MEMBER = True

It will allow all members of mailing list/alias to send email with the email
of mailing list/alias as the sender address.

unreasonable virtual_alias_maps map expansion size for user@domain.com

Sample error message in Postfix log file:

Feb 11 19:59:06 mail postfix/cleanup[30575]: warning: 23C334232FB3:
unreasonable virtual_alias_maps map expansion size{: .red } for
user@domain.com — deferring delivery

It means the maximal number of addresses that virtual alias expansion produces
from each original recipient exceeds hard limit, please either increase the
hard limit (default is 1000), or reduce alias members.

To increase the limit to, for example, 1500, please add below setting in
Postfix config file /etc/postfix/main.cf:

virtual_alias_expansion_limit = 1500

Reference: Postfix Configuration Parameters

Helo command rejected: need fully-qualified hostname

Sample error message in Postfix log file:

Sep 22 08:51:03 mail postfix/smtpd[22067]: NOQUEUE: reject: RCPT from
dslb-092-074-062-133.092.074.pools.vodafone-ip.de[92.74.62.133]: 504 5.5.2
<EHSGmbHLUCASPC>: Helo command rejected: need fully-qualified hostname;
from=user@domain-a.com to=user@domain-b.com proto=ESMTP helo=<EHSGmbHLUCASPC>

According to RFC document, HELO identity must be a FQDN (fully-qualified
hostname). Sender sends EHSGmbHLUCASPC as HELO hostname, but it’s not a FQDN.
It’s sender’s fault, not your mistake.

As a temporary solution, you can whitelist this HELO hostname
by adding a line like below at the top of file /etc/postfix/helo_access.pcre
(Linux/OpenBSD) or /usr/local/etc/postfix/helo_access.pcre (FreeBSD):

Helo command rejected: Host not found

Sample error message in Postfix log file:

Aug 13 08:07:14 mail postfix/smtpd[8606]: NOQUEUE: reject: RCPT from mta02.globetel.com.ph[120.28.49.114]: 450 4.7.1 <mta02.globetel.com>: Helo command rejected: Host not found; from=tcadd01@globetel.com.ph to=user@example.com proto=ESMTP helo=<mta02.globetel.com>

Postfix does DNS query to verify whether A type of DNS record of HELO domain
name mta02.globetel.com exists, if not, Postfix rejects the email.

As a temporary solution, you can whitelist this HELO hostname
by adding a line like below at the top of file /etc/postfix/helo_access.pcre
(Linux/OpenBSD) or /usr/local/etc/postfix/helo_access.pcre (FreeBSD):

/^mta02.globetel.com$/ OK

Helo command rejected: ACCESS DENIED. Your email was rejected because the sending mail server does not identify itself correctly (.local)

It means sender mail server uses a FQDN hostname which ends with .local as
HELO identity. .local is not a valid top level domain name, and all mail
servers should use a valid domain name which is resolvable from DNS query.

Two solutions:

  1. Temporarily remove this HELO check rule on YOUR server, in file
    /etc/postfix/helo_access.pcre (Linux/OpenBSD) or
    /usr/local/etc/postfix/helo_access.pcre (FreeBSD), then reload Postfix
    service.
  2. Ask sender server system administrator to correct their HELO identity, they
    will experience same issue while sending email to others.

warning: do not list domain mydomain.com in BOTH mydestination and virtual_mailbox_domains

Sample log in Postfix log file:

Feb 20 03:31:54 mail postfix/trivial-rewrite[2216]: warning: do not list
domain mydomain.com in BOTH mydestination and virtual_mailbox_domains

This error message means mail domain name mydomain.com is:

  • listed in Postfix parameter mydestination. Most probably, this domain name
    is value of Postfix parameter myhostname, and myhostname is value of
    mydestination.
  • a virtual mail domain name. Most probably, you added this domain with
    iRedAdmin.

To solve this, please either use a different myhostname or don’t use this
domain name as mail domain (remove it with iRedAdmin). To use a different value
for Postfix parameter myhostname, you must also
change server hostname.

Dovecot (IMAP / POP3)

Plaintext authentication not allowed without SSL/TLS

Error message in Dovecot log file:

[ALERT] Plaintext authentication not allowed without SSL/TLS, but your client
did it anyway. If anyone was listening, the password was exposed.

Dovecot is configured to force clients to use secure IMAP/POP3 connections,
but your client is trying to use plain and insecure connection without TLS or
SSL.

The BEST solution is updating IMAP/POP3 settings in the mail client
application (e.g. Outlook, Thunderbird) to enable secure connection. Please
check this link to see network port numbers and secure
connection types.

The NOT RECOMMENDED solution is updating Dovecot config file to allow
insecure connection, this is dangerous because your password is sent in plain
text, if someone can trace the network traffic with network gateway / firewall,
your password is explosed. if you clearly understand the risk and still want
to enable insecure connections, please check this document.

Amavisd

connect to 127.0.0.1[127.0.0.1]:10024: Connection refused

This error means Amavisd service is not running, please try to start it first.

  • RHEL/CentOS/FreeBSD: # service amavisd restart
  • Debian/Ubuntu: # service amavis restart
  • OpenBSD: # /etc/rc.d/amavisd restart or # rcctl restart amavisd

After restarted amavisd service, please check its
log file to make sure it’s running.

Notes:

  • 4 GB memory is recommended for a low traffic production mail server. If your
    server doesn’t have enough memory, Amavisd and ClamAV may be not able to
    start, or stop running automatically after running for a while. If it’s just
    a testing server, you can follow
    our tutorial to
    disable some features of Amavisd to keep it running, or disable it completely.

Есть такой почтовик — iRedMail-0.7.0.tar.bz2 http://www.iredmail.org/
Postfix+Dovecot+Spamassistent+Claim+amavis+RoundCube (набор скриптов по установке). Запускаешь скрипт — закачивается из портов, ставиться и… должно работать.
При установке ругнулось на Postfix —

Код: Выделить всё

Stop in /usr/ports/mail/postfix26/work/postfix-2.6.7/src/util.
*** Error code 1
Stop in /usr/ports/mail/postfix26/work/postfix-2.6.7.
*** Error code 1
Stop in /usr/ports/mail/postfix26
*** Error code 1
Stop in /usr/ports/mail/postfix26.
<ERROR> Port was not success installed, please fix it manually and then re-execute this script.

Решается установкой ручками из портов и правкой скрипта.

Код: Выделить всё

 iRedMail-0.6.1/.iRedMail.installation.status, append this line:

export status_install_port_mailpostfix26='DONE'

После чего все ставиться.
Все запускается и вроде работает…
Но: захожу на вебинтерфейс RoundCube и пытаюсь отправить письмо в локально (в этом же домене) — пишет:

Код: Выделить всё

SMTP Error (451): Невозможно добавить получателя "test@comp.my" (4.3.5 Server configuration problem)

В логах /var/log/maillog

Код: Выделить всё

Apr 14 12:44:23 mail postfix/smtpd[19149]: connect from mail.comp.my[127.0.0.1]
Apr 14 12:44:23 mail postfix/smtpd[19149]: warning: connect to 127.0.0.1:7777: Connection refused
Apr 14 12:44:23 mail postfix/smtpd[19149]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Apr 14 12:44:24 mail postfix/smtpd[19149]: warning: connect to 127.0.0.1:7777: Connection refused
Apr 14 12:44:24 mail postfix/smtpd[19149]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Apr 14 12:44:24 mail postfix/smtpd[19149]: NOQUEUE: reject: RCPT from mail.comp.my[127.0.0.1]: 451 4.3.5 Server configuration problem; from=<www@comp.my> to=<test@comp.my> proto=ESMTP helo=<mail.comp.my>
Apr 14 12:44:24 mail roundcube: Invalid response code received from server (451): 
Apr 14 12:44:24 mail roundcube: SMTP Error: SMTP error: Failed to add recipient 'test@comp.my' in /usr/local/www/roundcube/program/steps/mail/func.inc on line 1491 (POST /mail/?_unlock=loading1302774266302?_task=mail&_action=send)
Apr 14 12:44:24 mail postfix/smtpd[19149]: disconnect from mail.comp.my[127.0.0.1]

Отправляем письмо > cat let.txt | mail -s ‘test’ ‘www@comp.my’
Все нормально уходит.
На 127.0.0.1:7777 должно крутиться amavis
ps -ax | grep amavis

Код: Выделить всё

mail# ps -ax | grep amavis
19074  ??  Ss     0:01.46 amavisd (master) (perl)
19080  ??  I      0:00.01 amavisd (virgin child) (perl)
19081  ??  I      0:00.00 amavisd (virgin child) (perl)
19161   0  S+     0:00.00 grep amavis

т.е. amavis запущен
скан портов nmap не выдает открытый порт 7777.

Подскажите куда смотреть??

  • Печать

Страницы: 1 [2]  Все   Вниз

Тема: Настройка DKIM в iRedMail  (Прочитано 10556 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
Karl500

Слеши убрать. т.е.

mail._domainkey.mydomain.ru.  TXT     "v=DKIM1; k=rsa; t=s; p=MIGf.....NwIDAQAB"
all в строку

_adsp._domainkey.mydomain.ru. TXT "dkim=all"
если Вы все письма подписываете.

Оффлайн
golive

Слеши убрать. т.е. mail._domainkey.mydomain.ru.  TXT     "v=DKIM1; k=rsa; t=s; p=MIGf.....NwIDAQAB"
all в строку _adsp._domainkey.mydomain.ru. TXT "dkim=all"
если Вы все письма подписываете.

Сделал:
/etc/postfix/dkim/mail.txt

mail._domainkey IN TXT "v=DKIM1; k=rsa; g=*; p=MIGfMA0GCS......d6QTJdI9jVXka5rLU$Записи DNS:

mail._domainkey.mydomain.ru.  TXT     "v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEB......wIDAQAB"
_adsp._domainkey.mydomain.ru.  TXT     "dkim=all"
_domainkey.mydomain.  TXT     "t=s; o=~;"
default._domainkey.mydomain.ru  A       85.xxx.xxx.xxx

/etc/init.d/opendkim restart
sudo opendkim-testkey -d mydomain.ru -k /etc/postfix/dkim/mail.private -s mail

opendkim-testkey: /etc/postfix/dkim/mail.private: WARNING: unsafe permissions

Оффлайн
Karl500

Замечательно. И теперь что с почтой?

Оффлайн
golive

Замечательно. И теперь что с почтой?

в веб-интерфейсе ошибка «SMTP Error ($code): [451] 4.7.1 Service unavailable — try again later»
лог /var/log/mail.log

Jan 22 12:58:33 mail postfix/smtpd[22633]: connect from mail.mydomain.ru[127.0.0.1]
Jan 22 12:58:33 mail postfix/smtpd[22633]: 5CAD38E2927: client=mail.mydomain.ru[127.0.0.1], sasl_method=LOGIN, sasl_username=admin@mydomain.ru
Jan 22 12:58:33 mail postfix/cleanup[22637]: 5CAD38E2927: message-id=<fc5c3018ab954e4e35af6c85da47a890@mydomain.ru>
Jan 22 12:58:33 mail opendkim[22514]: 5CAD38E2927 error loading key `mail._domainkey.mydomain.ru'
Jan 22 12:58:33 mail postfix/cleanup[22637]: 5CAD38E2927: milter-reject: END-OF-MESSAGE from mail.mydomain.ru[127.0.0.1]: 4.7.1 Service unavailable - try again later$
Jan 22 12:58:33 mail roundcube: Invalid response code received from server (451):
Jan 22 12:58:33 mail roundcube: SMTP Error: SMTP error: Failed to send data in /usr/share/apache2/roundcubemail-0.5.4/program/steps/mail/func.inc on line 1501 (POST /m$
Jan 22 12:58:33 mail postfix/smtpd[22633]: disconnect from mail.mydomain.ru[127.0.0.1]
Jan 22 12:58:38 mail postfix/smtpd[22633]: connect from mail.mydomain.ru[127.0.0.1]
Jan 22 12:58:38 mail postfix/smtpd[22633]: 65EA08E2927: client=mail.mydomain.ru[127.0.0.1], sasl_method=LOGIN, sasl_username=admin@mydomain.ru
Jan 22 12:58:38 mail postfix/cleanup[22637]: 65EA08E2927: message-id=<25741be1891d7737daba0267e9236880@mydomain.ru>

Оффлайн
Karl500

Покажите

ls -al /etc/postfix/dkim/*

и

ps aux | grep opendkim

Оффлайн
golive

Покажите

ls -al /etc/postfix/dkim/*

и

ps aux | grep opendkim

ls -al /etc/postfix/dkim/*

-rw-r--r-- 1 root          root     522 2014-01-22 11:21 /etc/postfix/dkim/keytable
-rw-r----- 1 administrator mail     887 2014-01-21 15:43 /etc/postfix/dkim/mail.private
-rw-r----- 1 root          opendkim 301 2014-01-22 12:43 /etc/postfix/dkim/mail.txt
-rw-r--r-- 1 root          root     331 2014-01-21 15:57 /etc/postfix/dkim/signingtable
ps aux | grep opendkim

opendkim 22514  0.0  0.3 131152  5244 ?        Ssl  12:57   0:00 /usr/sbin/opendkim -x /etc/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid -p inet:8891@localhost
root     23544  0.0  0.0   7644   932 pts/0    S+   13:52   0:00 grep --color=auto opendkim

Оффлайн
Karl500

Сделайте

chown opendkim.opendkim /etc/postfix/dkim/mail.private
chmod 700 /etc/postfix/dkim/mail.private
/etc/init.d/opendkim restart

Оффлайн
golive

Сделайте

chown opendkim.opendkim /etc/postfix/dkim/mail.private
chmod 700 /etc/postfix/dkim/mail.private
/etc/init.d/opendkim restart

Добрый человек, спасибо Вам огромное! Все заработало! Исходящие письма подписываются! Ура! Еще раз спасибо!!!

P.S. Гугл собака все равно не пропускает от меня письма(( Думаю стоит подождать.

Оффлайн
Karl500

Не за что. А что в отлупе гугла?

Оффлайн
golive

Не за что. А что в отлупе гугла?

This is the mail system at host mail.mydomain.ru.

I’m sorry to have to inform you that your message could not
be delivered to one or more recipients. It’s attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<deenis.deep@gmail.com>: host gmail-smtp-in.l.google.com[74.125.143.27] said:
    550-5.7.1 [85.xxx.xxx.xxx       1] Our system has detected an unusual rate
    of 550-5.7.1 unsolicited mail originating from your IP address. To protect
    our 550-5.7.1 users from spam, mail sent from your IP address has been
    blocked. 550-5.7.1 Please visit
    http://www.google.com/mail/help/bulk_mail.html to review 550 5.7.1 our Bulk
    Email Senders Guidelines. 2si4879539laz.89 — gsmtp (in reply to end of DATA
    command)

Reporting-MTA: dns; mail.mydomain.ru
X-Postfix-Queue-ID: 02C6A8E29B6
X-Postfix-Sender: rfc822; admin@mydomain.ru
Arrival-Date: Wed, 22 Jan 2014 17:08:36 +0400 (SAMT)

Final-Recipient: rfc822; deenis.deep@gmail.com
Original-Recipient: rfc822;deenis.deep@gmail.com
Action: failed
Status: 5.7.1
Remote-MTA: dns; gmail-smtp-in.l.google.com
Diagnostic-Code: smtp; 550-5.7.1 [85.xxx.xxx.xxx       1] Our system has
    detected an unusual rate of 550-5.7.1 unsolicited mail originating from
    your IP address. To protect our 550-5.7.1 users from spam, mail sent from
    your IP address has been blocked. 550-5.7.1 Please visit
    http://www.google.com/mail/help/bulk_mail.html to review 550 5.7.1 our Bulk
    Email Senders Guidelines. 2si4879539laz.89 — gsmtp

Return-Path: <admin@mydomain.ru>
Received: from localhost (mail.mydomain.ru [127.0.0.1])
   by mail.mydomain.ru (Postfix) with ESMTP id 02C6A8E29B6
   for <deenis.deep@gmail.com>; Wed, 22 Jan 2014 17:08:36 +0400 (SAMT)
X-DKIM: OpenDKIM Filter v2.0.2 mail.mydomain.ru 02C6A8E29B6
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mydomain.ru;
   s=mail; t=1390396116;
   bh=1X4oPuVNlwps674Zm/7VZMk+3jPtLSnVhMmgDYDem50=;
   h=MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:
    Subject:Message-ID;
   b=ABKUD+YyRSUIv1dcxZyMyQocuwIaRYV06xyZXqfU63eIJ70rnH8FdWdxM+f70OtPA
    DP1m2ukKLBnZUB9cmYZuYDeRHibRcEr3esyQBrw/oJLWo6ihKgLToohCJpnkQO2EIf
    SKAzEge6Nirqsy1Emo4nLKV3hYxWuzhh2kB7NMho=
X-Virus-Scanned: Debian amavisd-new at mail.mydomain.ru
Received: from mail.mydomain.ru ([127.0.0.1])
   by localhost (mail.mydomain.ru [127.0.0.1]) (amavisd-new, port 10024)
   with ESMTP id AN3oryivlgHc for <deenis.deep@gmail.com>;
   Wed, 22 Jan 2014 17:08:35 +0400 (SAMT)
Received: from 192.168.0.85 (mail.mydomain.ru [127.0.0.1])
   (Authenticated sender: admin@mydomain.ru)
   by mail.mydomain.ru (Postfix) with ESMTPA id 323058E299B
   for <deenis.deep@gmail.com>; Wed, 22 Jan 2014 17:08:35 +0400 (SAMT)
X-DKIM: OpenDKIM Filter v2.0.2 mail.mydomain.ru 323058E299B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mydomain.ru;
   s=mail; t=1390396115;
   bh=1X4oPuVNlwps674Zm/7VZMk+3jPtLSnVhMmgDYDem50=;
   h=MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:
    Subject:Message-ID;
   b=FyXeLQn1qLxETNI8XzvpQokE7Hi05Bz987qcZ75lFX6u/TFNOMDEXOKbto94Lvy3n
    SI/G2dF6qPyywg8Vp3LFzTBpJJmE7S5d+Fv1bw3HpNbsa6It96boT453t4ivxlxyrE
    JxEyziUfoLiZBFCoOjc+VMRllqh7PyVnTJex2Ezs=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 22 Jan 2014 17:08:35 +0400
From: =?UTF-8?Q?=D0=98=D0=A2-=D0=9E=D1=82=D0=B4=D0=B5=D0=BB?=
 <admin@mydomain.ru>
To: <deenis.deep@gmail.com>
Subject: Test
Organization: =?UTF-8?Q?=D0=9E=D0=9E=D0=9E_=22=D0=9D=D0=B5=D0=B3=D0=BE?=
 =?UTF-8?Q?=D1=86=D0=B8=D0=B0=D0=BD=D1=82=22?=
Message-ID: <8b61d9d3000c8c85e969cbeae1a47bdf@trade-alco.ru>
X-Sender: admin@mydomain.ru
User-Agent: RoundCube WebMail

Оффлайн
Karl500

Оффлайн
golive

  • Печать

Страницы: 1 [2]  Все   Вверх

Источник

shystriknsk

Posts: 12
Joined: Sat Jun 15, 2019 6:25 am

Os: CentOS 6x
Web: apache + nginx
SMTP ошибка (451): Невозможно добавить получателя «delfin.lan@gmail.com» (Temporary local problem — please try later)

Доброго дня началась проблема с почтой. Вот ошибка

Code: Select all

SMTP ошибка (451): Невозможно добавить получателя "delfin.lan@gmail.com" (Temporary local problem - please try later)

Логи Rouncube

06-Jul-2020 11:43:21 +0000]: <rv6136ie> SMTP Error: Failed to add recipient ‘delfin.lan@gmail.com’. Temporary local problem — please try later (Code: 451) in /usr/share/roundcubemail/program/lib/Roundcube/rcube.php on line 1702 (POST /webmail/?_task=mail&_unlock=loading1594035807128&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:43:46 +0000]: <rv6136ie> PHP Error: Invalid response code received from server (POST /webmail/?_task=mail&_unlock=loading1594035832148&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:43:46 +0000]: <rv6136ie> SMTP Error: Failed to add recipient ‘delfin.lan@gmail.com’. Temporary local problem — please try later (Code: 451) in /usr/share/roundcubemail/program/lib/Roundcube/rcube.php on line 1702 (POST /webmail/?_task=mail&_unlock=loading1594035832148&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:45:21 +0000]: <rv6136ie> PHP Error: Invalid response code received from server (POST /webmail/?_task=mail&_unlock=loading1594035927235&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:45:21 +0000]: <rv6136ie> SMTP Error: Failed to add recipient ‘delfin.lan@gmail.com’. Temporary local problem — please try later (Code: 451) in /usr/share/roundcubemail/program/lib/Roundcube/rcube.php on line 1702 (POST /webmail/?_task=mail&_unlock=loading1594035927235&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:48:02 +0000]: <rv6136ie> PHP Error: Invalid response code received from server (POST /webmail/?_task=mail&_unlock=loading1594036088267&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:48:02 +0000]: <rv6136ie> SMTP Error: Failed to add recipient ‘delfin.lan@gmail.com’. Temporary local problem — please try later (Code: 451) in /usr/share/roundcubemail/program/lib/Roundcube/rcube.php on line 1702 (POST /webmail/?_task=mail&_unlock=loading1594036088267&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:51:51 +0000]: <rv6136ie> PHP Error: Invalid response code received from server (POST /webmail/?_task=mail&_unlock=loading1594036317830&_framed=1&_lang=ru&_action=send)
[06-Jul-2020 11:51:51 +0000]: <rv6136ie> SMTP Error: Failed to add recipient ‘delfin.lan@gmail.com’. Temporary local problem — please try later (Code: 451) in /usr/share/roundcubemail/program/lib/Roundcube/rcube.php on line 1702 (POST /webmail/?_task=mail&_unlock=loading1594036317830&_framed=1&_lang=ru&_action=send)

Логи Exim

020-07-06 14:36:15 Tainted filename for search: ‘/etc/exim/domains/msfleet.su/aliases’
2020-07-06 14:36:15 H=mail-qt1-f169.google.com [209.85.160.169] X=TLS1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<delfin.lan@gmail.com> temporarily rejected RCPT <test@msfleet.su>: failed to expand «${extract{1}{:}{${lookup{$local_part@$domain}lsearch{/etc/exim/domains/$domain/aliases}}}}»: NULL
2020-07-06 14:38:36 Tainted filename for search: ‘/etc/exim/domains/msfleet.su/aliases’
2020-07-06 14:38:36 H=mail-vk1-f182.google.com [209.85.221.182] X=TLS1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<delfin.lan@gmail.com> temporarily rejected RCPT <recruitment@msfleet.su>: failed to expand «${extract{1}{:}{${lookup{$local_part@$domain}lsearch{/etc/exim/domains/$domain/aliases}}}}»: NULL
2020-07-06 14:43:21 Tainted filename for search: ‘/etc/exim/domains/msfleet.su/aliases’
2020-07-06 14:43:21 H=localhost (msfleet.su) [127.0.0.1] sender verify defer for <test@msfleet.su>: failed to expand «${extract{1}{:}{${lookup{$local_part@$domain}lsearch{/etc/exim/domains/$domain/aliases}}}}»: NULL
2020-07-06 14:43:21 H=localhost (msfleet.su) [127.0.0.1] F=<test@msfleet.su> temporarily rejected RCPT <delfin.lan@gmail.com>: Could not complete sender verify
2020-07-06 14:43:32 exim 4.94 daemon started: pid=3837, -q1h, listening for SMTP on port 25 (IPv4) port 587 (IPv4) port 2525 (IPv4) and for SMTPS on port 465 (IPv4)
2020-07-06 14:43:32 Start queue run: pid=3841
2020-07-06 14:43:32 End queue run: pid=3841
2020-07-06 14:43:46 Tainted filename for search: ‘/etc/exim/domains/msfleet.su/aliases’
2020-07-06 14:43:46 H=localhost (msfleet.su) [127.0.0.1] sender verify defer for <test@msfleet.su>: failed to expand «${extract{1}{:}{${lookup{$local_part@$domain}lsearch{/etc/exim/domains/$domain/aliases}}}}»: NULL
2020-07-06 14:43:46 H=localhost (msfleet.su) [127.0.0.1] F=<test@msfleet.su> temporarily rejected RCPT <delfin.lan@gmail.com>: Could not complete sender verify
2020-07-06 14:45:21 Tainted filename for search: ‘/etc/exim/domains/msfleet.su/aliases’
2020-07-06 14:45:21 H=localhost (msfleet.su) [127.0.0.1] sender verify defer for <test@msfleet.su>: failed to expand «${extract{1}{:}{${lookup{$local_part@$domain}lsearch{/etc/exim/domains/$domain/aliases}}}}»: NULL
2020-07-06 14:45:21 H=localhost (msfleet.su) [127.0.0.1] F=<test@msfleet.su> temporarily rejected RCPT <delfin.lan@gmail.com>: Could not complete sender verify
2020-07-06 14:48:02 Tainted filename for search: ‘/etc/exim/domains/msfleet.su/aliases’
2020-07-06 14:48:02 H=localhost (msfleet.su) [127.0.0.1] sender verify defer for <test@msfleet.su>: failed to expand «${extract{1}{:}{${lookup{$local_part@$domain}lsearch{/etc/exim/domains/$domain/aliases}}}}»: NULL
2020-07-06 14:48:02 H=localhost (msfleet.su) [127.0.0.1] F=<test@msfleet.su> temporarily rejected RCPT <delfin.lan@gmail.com>: Could not complete sender verify

prmres

Posts: 55
Joined: Tue Feb 02, 2016 4:28 pm

Os: CentOS 7x
Web: apache + nginx
Re: SMTP ошибка (451): Невозможно добавить получателя «delfin.lan@gmail.com» (Temporary local problem — please try later

Post

by prmres » Tue Jul 07, 2020 9:50 pm

[s]/etc/exim/exim.conf
закоменти:
# require verify = sender[/s]

но принимать отказывается
на английкой теме форума активное обсуждение: viewtopic.php?t=19994
на первой странице пишут что помогает откат на раннюю версию, дальше пока не читал

Last edited by prmres on Thu Aug 06, 2020 8:07 pm, edited 1 time in total.

prmres

Posts: 55
Joined: Tue Feb 02, 2016 4:28 pm

Os: CentOS 7x
Web: apache + nginx
Re: SMTP ошибка (451): Невозможно добавить получателя «delfin.lan@gmail.com» (Temporary local problem — please try later

Post

by prmres » Wed Jul 08, 2020 4:58 pm

откатывать версию нет необходимости
там люди разобрались и на последней странцие конфмг exim-а с исправлениями выложили
я за пару минут все исправления с помощью Notepad++ с плагином compare внёс в свой конфиг, рестартанул эксима и почта пошла в обе стороны

делов реально на 5 минут с перекурами

grayfolk

Support team
Posts: 1111
Joined: Tue Jul 30, 2013 10:18 pm
Contact:

Os: CentOS 6x
Web: nginx + php-fpm
Re: SMTP ошибка (451): Невозможно добавить получателя «delfin.lan@gmail.com» (Temporary local problem — please try later

Post

by grayfolk » Thu May 27, 2021 12:51 pm

kaavain wrote: ↑

Thu May 27, 2021 10:01 am


Выложить-то выложили, да удалили. Не сохранилось правок?

Попробуйте в вебархиве поискать — может, сохранились снапшоты.

prmres

Posts: 55
Joined: Tue Feb 02, 2016 4:28 pm

Os: CentOS 7x
Web: apache + nginx
Re: SMTP ошибка (451): Невозможно добавить получателя «delfin.lan@gmail.com» (Temporary local problem — please try later

Post

by prmres » Wed Jun 02, 2021 9:04 am

могу рабочий конфиг выложить
чуть позже
если ещё актуально

Источник

Есть такой почтовик — iRedMail-0.7.0.tar.bz2 http://www.iredmail.org/
Postfix+Dovecot+Spamassistent+Claim+amavis+RoundCube (набор скриптов по установке). Запускаешь скрипт — закачивается из портов, ставиться и… должно работать.
При установке ругнулось на Postfix —

Код: Выделить всё

Stop in /usr/ports/mail/postfix26/work/postfix-2.6.7/src/util.
*** Error code 1
Stop in /usr/ports/mail/postfix26/work/postfix-2.6.7.
*** Error code 1
Stop in /usr/ports/mail/postfix26
*** Error code 1
Stop in /usr/ports/mail/postfix26.
<ERROR> Port was not success installed, please fix it manually and then re-execute this script.

Решается установкой ручками из портов и правкой скрипта.

Код: Выделить всё

 iRedMail-0.6.1/.iRedMail.installation.status, append this line:

export status_install_port_mailpostfix26='DONE'

После чего все ставиться.
Все запускается и вроде работает…
Но: захожу на вебинтерфейс RoundCube и пытаюсь отправить письмо в локально (в этом же домене) — пишет:

Код: Выделить всё

SMTP Error (451): Невозможно добавить получателя "test@comp.my" (4.3.5 Server configuration problem)

В логах /var/log/maillog

Код: Выделить всё

Apr 14 12:44:23 mail postfix/smtpd[19149]: connect from mail.comp.my[127.0.0.1]
Apr 14 12:44:23 mail postfix/smtpd[19149]: warning: connect to 127.0.0.1:7777: Connection refused
Apr 14 12:44:23 mail postfix/smtpd[19149]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Apr 14 12:44:24 mail postfix/smtpd[19149]: warning: connect to 127.0.0.1:7777: Connection refused
Apr 14 12:44:24 mail postfix/smtpd[19149]: warning: problem talking to server 127.0.0.1:7777: Connection refused
Apr 14 12:44:24 mail postfix/smtpd[19149]: NOQUEUE: reject: RCPT from mail.comp.my[127.0.0.1]: 451 4.3.5 Server configuration problem; from=<www@comp.my> to=<test@comp.my> proto=ESMTP helo=<mail.comp.my>
Apr 14 12:44:24 mail roundcube: Invalid response code received from server (451): 
Apr 14 12:44:24 mail roundcube: SMTP Error: SMTP error: Failed to add recipient 'test@comp.my' in /usr/local/www/roundcube/program/steps/mail/func.inc on line 1491 (POST /mail/?_unlock=loading1302774266302?_task=mail&_action=send)
Apr 14 12:44:24 mail postfix/smtpd[19149]: disconnect from mail.comp.my[127.0.0.1]

Отправляем письмо > cat let.txt | mail -s ‘test’ ‘www@comp.my’
Все нормально уходит.
На 127.0.0.1:7777 должно крутиться amavis
ps -ax | grep amavis

Код: Выделить всё

mail# ps -ax | grep amavis
19074  ??  Ss     0:01.46 amavisd (master) (perl)
19080  ??  I      0:00.01 amavisd (virgin child) (perl)
19081  ??  I      0:00.00 amavisd (virgin child) (perl)
19161   0  S+     0:00.00 grep amavis

т.е. amavis запущен
скан портов nmap не выдает открытый порт 7777.

Подскажите куда смотреть??

Источник

I am facing strange problem after today.

For months i am using iRedMail 0.9.2 and i have no problems at all. I received and send email all the way until today.

Today i install apt-get install sendmail and everything stopped working.

Now i can not receive and send emails.

So i menaged to remove sendmail and reinstall postfix but now in Roundcube when i try to send email i receive the following error:

SMTP Error (451): Failed to add recipient "theemail@gmail.com" (4.3.0 <office@superweb.bg>: Temporary lookup failure).

I removed sendmail and reinstalled postfix like this:

sudo apt-get purge sendmail
sudo apt-get install --reinstall postfix
sudo /etc/init.d/postfix restart

Here is what my mail.log says:

Oct  5 18:13:58 mail postfix/cleanup[3300]: warning: B8CB3A22AD7: sender_bcc_maps map lookup problem -- message not accepted, try again later
Oct  5 18:13:58 mail postfix/pickup[3297]: warning: maildrop/BAEC8A22ACD: error writing B8CB3A22AD7: queue file write error
Oct  5 18:14:41 mail postfix/smtpd[3318]: error: unsupported dictionary type: pcre
Oct  5 18:14:42 mail postfix/smtpd[3318]: connect from smtp-out.abv.bg[194.153.145.80]
Oct  5 18:14:42 mail postfix/proxymap[3303]: warning: mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf is unavailable. unsupported dictionary type: mysql
Oct  5 18:14:42 mail postfix/trivial-rewrite[3301]: warning: proxy:mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf: table lookup problem
Oct  5 18:14:42 mail postfix/trivial-rewrite[3301]: warning: virtual_mailbox_domains lookup failure
Oct  5 18:14:42 mail postfix/trivial-rewrite[3301]: warning: proxy:mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf: table lookup problem
Oct  5 18:14:42 mail postfix/trivial-rewrite[3301]: warning: virtual_mailbox_domains lookup failure
Oct  5 18:14:42 mail postfix/smtpd[3318]: warning: pcre:/etc/postfix/helo_access.pcre is unavailable. unsupported dictionary type: pcre
Oct  5 18:14:42 mail postfix/smtpd[3318]: warning: pcre:/etc/postfix/helo_access.pcre: table lookup problem
Oct  5 18:14:42 mail postfix/smtpd[3318]: NOQUEUE: reject: RCPT from smtp-out.abv.bg[194.153.145.80]: 451 4.3.5 <smtp-out.abv.bg>: Helo command rejected: Server configuration error;$
Oct  5 18:14:42 mail postfix/smtpd[3318]: disconnect from smtp-out.abv.bg[194.153.145.80]
Oct  5 18:14:58 mail postfix/pickup[3297]: B1974A22AD7: uid=0 from=<root>
Oct  5 18:14:42 mail postfix/proxymap[3303]: warning: mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf is unavailable. unsupported dictionary type: mysql
Oct  5 18:14:58 mail postfix/proxymap[3303]: warning: mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf is unavailable. unsupported dictionary type: mysql
Oct  5 18:14:58 mail postfix/cleanup[3300]: warning: proxy:mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf lookup error for "root@mail.vivashost.com"
Oct  5 18:14:58 mail postfix/cleanup[3300]: warning: B1974A22AD7: sender_bcc_maps map lookup problem -- message not accepted, try again later
Oct  5 18:14:58 mail postfix/pickup[3297]: warning: maildrop/BAEC8A22ACD: error writing B1974A22AD7: queue file write error
Oct  5 18:15:58 mail postfix/pickup[3297]: C0A32A22AD7: uid=0 from=<root>
Oct  5 18:15:58 mail postfix/cleanup[3300]: warning: proxy:mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf lookup error for "root@mail.vivashost.com"
Oct  5 18:15:58 mail postfix/cleanup[3300]: warning: C0A32A22AD7: sender_bcc_maps map lookup problem -- message not accepted, try again later
Oct  5 18:15:58 mail postfix/pickup[3297]: warning: maildrop/BAEC8A22ACD: error writing C0A32A22AD7: queue file write error
Oct  5 18:16:27 mail postfix/smtpd[3395]: error: unsupported dictionary type: pcre
Oct  5 18:16:27 mail postfix/smtpd[3395]: connect from localhost[127.0.0.1]
Oct  5 18:15:58 mail postfix/proxymap[3303]: warning: mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf is unavailable. unsupported dictionary type: mysql
Oct  5 18:16:27 mail postfix/proxymap[3303]: warning: mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf is unavailable. unsupported dictionary type: mysql
Oct  5 18:16:27 mail postfix/trivial-rewrite[3301]: warning: proxy:mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf: table lookup problem
Oct  5 18:16:27 mail postfix/trivial-rewrite[3301]: warning: virtual_mailbox_domains lookup failure
Oct  5 18:16:27 mail postfix/trivial-rewrite[3301]: warning: proxy:mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf: table lookup problem
Oct  5 18:16:27 mail postfix/trivial-rewrite[3301]: warning: virtual_mailbox_domains lookup failure
Oct  5 18:16:27 mail postfix/smtpd[3395]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 <office@superweb.bg>: Temporary lookup failure; from=<office@superweb.bg> to=<th$
Oct  5 18:16:27 mail roundcube: <65kuug0v> SMTP Error: Failed to add recipient 'thelex@abv.bg'. 4.3.0 <office@superweb.bg>: Temporary lookup failure (Code: 451) in /opt/www/roundcub$
Oct  5 18:16:27 mail postfix/smtpd[3395]: disconnect from localhost[127.0.0.1]
Oct  5 18:16:58 mail postfix/pickup[3297]: 508F3A22AD9: uid=0 from=<root>
Oct  5 18:16:27 mail postfix/proxymap[3303]: warning: mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf is unavailable. unsupported dictionary type: mysql
Oct  5 18:16:58 mail postfix/proxymap[3303]: warning: mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf is unavailable. unsupported dictionary type: mysql
Oct  5 18:16:58 mail postfix/cleanup[3300]: warning: proxy:mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf lookup error for "root@mail.vivashost.com"
Oct  5 18:16:58 mail postfix/cleanup[3300]: warning: 508F3A22AD9: sender_bcc_maps map lookup problem -- message not accepted, try again later
Oct  5 18:16:58 mail postfix/pickup[3297]: warning: maildrop/BAEC8A22ACD: error writing 508F3A22AD9: queue file write error

Can you help me out resolve this problem. I think i have wrong configuration for my postfix.

Can you help me out resolve the problem?

Thanks in advance!

Источник

Понравилась статья? Поделить с друзьями:
  • Iqos widget russia ошибка сервера
  • Iqos 3 duos коды ошибок
  • Iptv плеер ошибка воспроизведения канала
  • Iptv ошибка сети на приставке т2
  • Iptv ошибка воспроизведения канала на телевизоре