Beiträge von ñull

    Aren't you able to change / manage simple files?


    Looks like a rhetorical question. Of course I can't. That's why I use LiveConfig. I'm too lazy to maintain all these complex configuration files with their decentralised development and scattered documentation. My memory is limited and I cannot remember all the different configuration keywords and I am lazy enough that I like the idea that LiveConfig takes care of this.

    In my client's situation there is one contract or subscription with two domains. When I look at the access log I cannot distinguish between the two sites because it has entries of both and there is no domain name in the format.


    The bug is that there should be separate log for each domain, only combining www subdomain with it's domain. The same problem is when you use subdomains. The statistics should be different for each sub-domain. Only www. sub domain can share log-file with its domain.


    It is still in time for this client since the second site is still before release data. But as soon as it is released there will be a problem. Her statistics will be invalid and there is no way to see the statistics for the second domain. This option is not even offered by LC! May the statistics was switched off when the second domain was added? Because that was her initial complain that I try to solve now. Please fix this because there is no way to know what is what in a log, specially when the sites are of similar technology.

    Client discovers that her webaliser statistics was turned off, while it was working before. Not clear how that happened, but now she wants to see the stats of the last months.


    I sitll have the access logs compressed since May. Is there an easy way to run webaliser manually to recover the statistics for the missing months?

    Would be good when there is an easier way to identify the right mail folder (for administrators). May be a tool? A field to enter the mail address and it returns the path?


    would also be nice when the administrator you can temporary disable / block an mail account or all mail of a contract. Under domains there is a checkbox to disable email, but I don't know what it does. It might delete all mail folders for instance. When an mail account is abbused for sending Spam, it would be nice when you could disable SMTP still allowing reception and POP3/IMAP without deleting mailboxes.

    And when you are at it, why no make these all configurable:


    anvil_rate_time_unit = 1800s
    smtpd_client_connection_rate_limit = 50
    smtpd_client_recipient_rate_limit = 400
    smtpd_recipient_limit = 100


    Nice for SMAP damage limitation. This is specially important since the LUA configuration is difficult to custom override.

    On my VB test server I got it working. In /etc/postfix/main.cf:


    smtpd_sender_login_maps = hash:/etc/postfix/controlled_envelope_senders
    smtpd_sender_restrictions =
    reject_sender_login_mismatch,
    permit_sasl_authenticated,
    reject_unknown_address,
    reject_unknown_sender_domain,
    reject_non_fqdn_sender,
    check_sender_access hash:/etc/postfix/sender_access


    Apparently the reject_sender_login_mismatch, should come before any permit rules. After changes it should be compiled with:


    postmap /etc/postfix/main.cf


    This should be in /etc/postfix/controlled_envelope_senders (example, should be maintained by LUA):


    #box, alias or forwarded address sasl authenticated owner
    test@domain.com test@domain.com
    info@domain.com test@domain.com


    after changes it should be compiled with:


    postmap /etc/postfix/controlled_envelope_senders


    now only test@domain.com and info@domain.com are allowed from addresses when SASL authenticated as test@domain.com. Thunderbird errors with the message:


    An error occurred while sending mail. The mail server responded: 5.7.1 <anyaddress@gmail.com>: Sender address rejected: not owned by user test@domain.com. Please check the message recipient test@domain.com and try again.


    The last phrase is very confusing. I wonder why the recipient should be checked while the response clearly indicates a problem with the Sender address.

    Please include this in the postfix lua together with a fix for graylisting under Ubuntu. I don't know the correct implemantation. I tried this:


    smtpd_sender_restrictions =
    permit_mynetworks,
    reject_authenticated_sender_login_mismatch,
    reject_unknown_address,
    reject_unknown_sender_domain,
    reject_non_fqdn_sender,
    check_sender_access hash:/etc/postfix/sender_access


    But then I could not send at all any more. Please give this a higher priority, because it helps to identify a spamming mail account, a continuous problem with hosters.

    The Drupal installer is broken. I takes all information, downloads and installs all files, but then leaves me waiting. LC log tells me:


    [2014/07/17 08:54:45.188208] [5998|6003] Requesting installer file 'wai-drupal-7.28-1.php.gz'...
    [2014/07/17 08:54:59.984342] [5998|6003] Created database '<databasename>' (user '<databaseuser>')

    In an attempt to follow the example how to override a function in custom.lua, but when I run "liveconfig --diag" I get the error as indicated in the subject. All I do is include a minimally changed function LC.postfix.configure(cfg, opts).


    The same method of overriding worked with another function ( LC.users.addUser). What am i doing wrong here? In what is LC.postfix.configure different that it should fail?

    ... eine kleine Änderung in /usr/lib/liveconfig/lua/users.lua :


    Hallo Herr Strausmann,


    Wir lassen uns etwas einfallen, wie LiveConfig erkennen kann auf welchem IP- oder Unix-Socket nun Postgrey erreichbar ist, und Postfix entsprechend einrichtet.


    Wann werden Sie diesen Fehler beheben? Als ich gestern Whitelisting ausprobierte, wurden meine Kunden wiederum das Opfer dieser immer noch bestehenden Irritation, die meinen Mailserver lahm gelegt hatte.

    Hatte zu tun mit ufw. Einen fehlerhafte Foward Regel in before.rules wurde durch "ufw disable" oder "ufw reload" nicht deaktiviert. Das muss man Manual mit "iptables -t nat -F" tun.

    Heute vor einige Stunden funktionierte es noch aber jetzt scheint LC auf Port 8443 nicht mehr zu reagieren.
    Neustart usw. hat kein Erfolg. Im log sehe ich auch merkwürdige Fehlermeldungen. Kann ich ihnen das zuschicken? Was kann ich noch mehr tun?

    Ich entdekte die .res Dateien in /usr/share/liveconfig , anscheinend die Ressourcen mit auch die Sprachen. Ich arbeite hauptsächlich mit Linux und ich frage mich was ich mit diese Dateien anfangen muss für meine Spanisch und Holländisch Übersetzung? Soll ich resedit benützen unter Window$ in Virtualbox oder Wine?

    Meinen Patch für usr/lib/liveconfig/lua/postfix.lua seht so aus:

    Code
    709c709
    <         fh:write("greylist = check_policy_service inet:127.0.0.1:10023\n")
    ---
    >         fh:write("greylist = check_policy_service inet:::1:10023\n")


    Vorausgesetzt das Ubuntu und Debian in diesen Hinsicht ähnlich sind.