Posts by auanasgheps

    Those emails are sent as root because they are system emails (probably cron). If you want it to go to a different address, modify /etc/aliases and then run newaliases. Whether OMV should change this or not is a different question.

    Yes, cron jobs are sent with the 'root' sender, but it does not make sense in my opinion. And breaks my email provider.


    Postfix should already be configured to replace root with the configured email address.

    I encountered this issue about a month ago using whatever was the last version of OMV5. I can repeat the test if you want. By the way, as ryecoaaron mentioned, cron jobs are sent as "root".

    Hi people,


    During my testing with OMV (version 5) I discovered a behaviour that I really didn't like: majority of emails are sent with the sender root, only in rare occasions the email address is used.
    This can cause two issues:

    • OMV emails might go into spam. Also receiving emails from root it not nice.
    • Some provides simply do not support this configuration. One of them is Zoho Mail, which I use. When I configured this provider, I was not getting emails from OMV and logs were throwing errors about " Relaying disallowed error", a message received from the SMTP Server.

    That's what my provider says:


    Relaying disallowed error



    When the email address (or login credentials) you have provided in the application does not match the email address (or credentials) of your account's outgoing server, you will see a 'Relaying Disallowed' error when you attempt to send an email. The SMTP client will not be able to send the email because of the email address mismatch.
    This can happen when an email address is used as default in a coded program or when you have misspelled the email address while configuring your email inbox. You will receive emails without any issues. To resolve the 'Relaying Disallowed' error, you need to correct the email address provided.

    However there is no such option in OMV. I believe it should be added to the GUI, should be a basic change. Should I submit a product request?


    FIX
    I have found an easy fix for this issue.


    Connect to your server in SSH and edit the following file /etc/postfix/smtp_header_checks with the following:


    Code
    #Fix sender
    
    
    /^From: (.*)/ REPLACE From: SenderName <server@yourwebdomain>

    Save the file and restart postfix: service postfix restart
    From now on emails will be sent if your provider enforces/verifies the email address, and they will definitely appear better to your eyes.

    I checked my scheduled tasks and the report I attached to this thread was the report I was using. I think I was using the script unmodified but didn't remember because it has been so long since I used it.


    Looking at the script, all the output from the sync and scrub commands are directed to $TMP_OUTPUT variable which is included in the email. If it's possible to only include partial command output in the email, that might be beyond my bash capabilities.

    Thanks but don't worry, I found a better script in the meantime, you can get it in my previous posts. Works quite well.

    If you read the posts at the bottom of the page where the script is you'll see there are two reports (one mine) of it hanging at the end of the run on: 'python -m markdown /tmp/snapRAID.out'


    Today it ran fine, but yesterday it hung.

    lol, I did, and I am the other user, the one with another dog in the picture.


    I have found a good script which is not spammy at all, comes from here but these are the changes that I included


    - Adapted for standard parity (original script is made for split parity)
    - Integrated changes of user sburke to make it working with Debian 10 (original script does not work on Debian 10)


    I've tested it in my OMV5 VM and works fine.


    NOTES

    - You can configure sync rules, but by default it always forces a sync
    - It can pause Containers so they don't mess up, and restore them when finished. I disabled it but if you want to use this feature switch MANAGE_SERVICES=0 to 1 and in SERVICES= list all containers.
    - In OMV5 the script it self does send emails (you can specify your address in EMAIL_ADDRESS=). You might want to disable this feature or the one from the scheduled job on OMV.




    The output itself is quite nice. I've kept the whole output, it's not syncing any personal data.

    Yes, both BTRFS and ZFS have advanced features that are missing in EXT4. Things like snapshots, copy-on-write, checksums and more. But unless you intend to use these features, and know how to use them, they are useless. And you might just as well use EXT4.


    If you think that you need the advanced features, go ahead and learn how to use them.


    I think BTRFS and ZFS are not "ready", because they lack tools that makes it easy and safe for normal users to use the advanced features. Because of this, unless you really make an effort to learn how to use them safely, they might cause more problems than benefits.

    FYI I made the question because I'm coming from a Synology NAS, which uses BTRFS for their Hybrid RAID feature which is quite handy because allows different drives to be pooled together (a bit more flexible than classic RAID, but less than SnapRAID).


    I'm sure the Synology DSM OS does something in the background but I don't use any BTRFS advanced feature like snapshots. Synology really wants you to use BTRFS, but I have no idea why.


    Additionally, I already knew I didn't want to use ZFS due to impact on RAM/performance and the fact I can't extend pools.

    Here's the script I was using.

    Thanks buddy, will test it tonight.


    If works good I guess we (actually you, if it's your work) could make a merge request to have it updated for everybody.


    EDIT: Looks like it's just an older version of the official one, no edits at all. It exactly matches this version of the script. Are you sure you got yours?


    EDIT2:
    I am currently testing this script that seems to be less spammy and bit more structured, but the script does not terminate correctly and goes on even if it's done. I'm dumb in bash so I don't know how to fix it.
    Script comes from here, I only removed 'wait' instructions otherwise would not run on Debian 10/OMV5 (adviced by the author).
    If you want to test it, also install python-markdown.

    You would need to edit the diff script. Line 422 sends all output of the sync command to a variable and elsewhere in the script that output is included in the email.

    Code
    $SNAPRAID_BIN sync${prehash} >> $TMP_OUTPUT

    Line 444 includes all the scrub output.


    Code
    $SNAPRAID_BIN scrub -p $SCRUB_PERCENT -o $SCRUB_OLDER_THAN_DAYS >> $TMP_OUTPUT

    Could you describe in detail what could be done to reduce the spam with this script?
    By default emails produced by this script are unreadable, the email is so long that many applications can't even load it!
    Is there a way to write the output every X seconds or something similar?
    Ideally I would like to see a little progress or even none, but just having the total stats.


    I have commented these two lines, but as expected all the output gets removed and maybe breaks something else.


    The first part of the script is quite spammy too, because it lists all edited and updated files.


    If this script is too hard to edit, is anybody else using a nicer one? Thanks

    Hi guys,
    I am almost ready to build my first DIY server and have a basic question: should I choose EXT4 for my data drives or not?


    Is EXT4 still good enough or should I look for something more exotic like BTRFS or XFS?


    My scenario:

    • I do not want ZFS
    • I will be using SnapRAID
    • 4x4TB HDD for data, 1 NVMe SSD for docker/applications and one thumb drive for OMV.