Startseite » Forum » LiveConfig Forums (english) » Bugs and troubleshooting » Postfix / Greylist http://serverfault.com/questions/471581/postfix-warning-connect-to
Ergebnis 1 bis 2 von 2
  1. #1
    Erfahrener Benutzer
    Registriert seit
    09.07.2012
    Ort
    Spanien
    Beiträge
    273

    Ubuntu 12.04LTS Postfix / Postgrey delivery failure.

    Apparently since Ubuntu 12.04LTS postgrey service now exclusively listens to ipv6 and this needs to be corrected in the postfix settings. See this post. This manifested as failing local mail delivery logged as:
    Jan 11 22:00:03 rhodavm100 postfix/smtpd[5944]: warning: connect to 127.0.0.1:10023: Connection refused
    Jan 11 22:00:03 rhodavm100 postfix/smtpd[5944]: warning: problem talking to server 127.0.0.1:10023: Connection refused
    Jan 11 22:00:04 rhodavm100 postfix/smtpd[5944]: warning: connect to 127.0.0.1:10023: Connection refused
    Jan 11 22:00:04 rhodavm100 postfix/smtpd[5944]: warning: problem talking to server 127.0.0.1:10023: Connection refused
    Jan 11 22:00:04 rhodavm100 postfix/smtpd[5944]: NOQUEUE: reject: RCPT from srv1.nubelo.com[178.33.160.130]: 451 4.3.5 Server configuration problem; from=<info@nubelo.com> to=<myaddress@mydomain.como> proto=ESMTP helo=<srv1.nubelo.com>
    After changing the following line in /etc/postfix/main.cf, local mail delivery was recovered:

    greylist = check_policy_service inet:::1:10023
    After that I changed /usr/lib/liveconfig/lua/postfix.lua :
    if LC.distribution.family == "Debian" then
    fh:write("greylist = check_policy_service inet:::1:10023\n")
    In LUA I don't see distinction is made between Debian and Ubuntu. Since I don't use Debian, I cannot tell if the same setting would work there. Is so, please correct the LUA script like indicated in your next release.
    Geändert von ñull (15.01.2014 um 09:08 Uhr) Grund: i hoped to be able to remove the url from the title

  2. #2
    Erfahrener Benutzer
    Registriert seit
    09.07.2012
    Ort
    Spanien
    Beiträge
    273
    My attempt to correct this and the other issue with {SCRYPT} hash in a custom.lua, utterly failed. The simple override in the documentation is not sufficiently illustrative to teach me how to override a large function like this, without knowing all the in and outs of LUA. So for now I'll just put an chattr +i for the hacked lua file and wait until I see the fix in the changelog.

    If somebody else finds the right way to solve it in custom.lua, please feel free to post it here.

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •