https://tools.ietf.org/html/rfc5322#section-3.6.2

Originator Fields

The originator fields of a message consist of the from field, the
sender field (when applicable), and optionally the reply-to field.
The from field consists of the field name "From" and a comma-
separated list of one or more mailbox specifications. If the from
field contains more than one mailbox specification in the mailbox-
list, then the sender field, containing the field name "Sender" and a
single mailbox specification, MUST appear in the message. In either
case, an optional reply-to field MAY also be included, which contains
the field name "Reply-To" and a comma-separated list of one or more
addresses.

from = "From:" mailbox-list CRLF

sender = "Sender:" mailbox CRLF

reply-to = "Reply-To:" address-list CRLF

The originator fields indicate the mailbox(es) of the source of the
message. The "From:" field specifies the author(s) of the message,
that is, the mailbox(es) of the person(s) or system(s) responsible
for the writing of the message. The "Sender:" field specifies the
mailbox of the agent responsible for the actual transmission of the
message. For example, if a secretary were to send a message for
another person, the mailbox of the secretary would appear in the
"Sender:" field and the mailbox of the actual author would appear in
the "From:" field. If the originator of the message can be indicated by a single mailbox and the author and transmitter are identical, the "Sender:" field SHOULD NOT be used. Otherwise, both fields SHOULD appear.

Note: The transmitter information is always present. The absence
of the "Sender:" field is sometimes mistakenly taken to mean that
the agent responsible for transmission of the message has not been
specified. This absence merely means that the transmitter is
identical to the author and is therefore not redundantly placed
into the "Sender:" field.

The originator fields also provide the information required when
replying to a message. When the "Reply-To:" field is present, it
indicates the address(es) to which the author of the message suggests
that replies be sent. In the absence of the "Reply-To:" field,
replies SHOULD by default be sent to the mailbox(es) specified in the
"From:" field unless otherwise specified by the person composing the
reply.

In all cases, the "From:" field SHOULD NOT contain any mailbox that
does not belong to the author(s) of the message. See also section
3.6.3 for more information on forming the destination addresses for a
reply.

@black3dynamite said in Installing Zabbix 4 Agent on Fedora 29 Linux:

Fedora 30 repo provides version 4.0.5
http://repo.ialab.dsu.edu/fedora/linux/development/30/Everything/x86_64/os/Packages/z/zabbix-agent-4.0.5-1.fc30.x86_64.rpm

I'll wait for when Fedora 30 is released.

@scottalanmiller It's pretty mature now. The feature set is minimal but works fine compared to some other options I've played with. If they added a few more features it would be golden.

@Emad-R said in Download Windows Server 2019:

@scottalanmiller

https://software-download.microsoft.com/download/sg/17763.253.190108-0006.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso

Thanks @Emad-R with this link you don't have to go through all the paperwork.

@scottalanmiller said in Microsoft BCL or Bulk Complaint Level Values for Email:

Some sources call this an SCL or Spam Complaint Level.

Emails into O365 have both BCL and SCL.

@DustinB3403 said in Sound Eklin TruDR eSeries - Error Opening Receptor 106:

@scottalanmiller said in Sound Eklin TruDR eSeries - Error Opening Receptor 106:

@DustinB3403 We did 😉

Gotta check every now and then. 😄

Someone has to ask the stupid questions. It was me the other day.

@gjacobse said in Add a User to Remote Desktop Users in Windows Remotely:

I seem to remember doing this via ScreenConnect CMD

Only works if SC is installed, which if it was, we'd not need to do it 🙂

OSTicket is not a solution I can use, because I need time tracking also.

I never saw a plugin for that for OSTicket.

@black3dynamite said in Setting Up a Standard MySQL or MariaDB Database for an Application:

@JaredBusch said in Setting Up a Standard MySQL or MariaDB Database for an Application:

I like my approach to setting this up.

Obviously, install MySQL/MariaDB first as noted above.

Then do the following. This all needs done in the same SSH session, but otherwise things are simple.

Choose once of these exports for your DB root password.

The first one is for you to specify, the second generates a random one and echo's it back to you.

# Specify your own password for MariaDB root user export DB_ROOT_PASS="somebigpasswordgoeshere" # Generate a random password for MariaDB root user export DB_ROOT_PASS="$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 30)" echo "This is your MariaDB root password: $DB_ROOT_PASS" Specify the application database name and application user name # Database user to use for application export DB_USER='yourusername' # Database name to use for application export DB_NAME='yourdatabasename' Generate or specify a random password for the database user # Specify your own password for the application's database user export DB_PASS="somebigpasswordgoeshere" # Generate a random password for the application's database user export DB_PASS="$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 30)" echo "This is your password for the application user: $DB_PASS" Then create the application database, use, and grant access. mysql -e "CREATE DATABASE $DB_NAME;" mysql -e "CREATE USER '$DB_USER'@'localhost' IDENTIFIED BY '$DB_PASS';" mysql -e "GRANT ALL ON $DB_NAME.* TO '$DB_USER'@'localhost';" mysql -e "FLUSH PRIVILEGES;" Finally, lock down the system without the interactive requirement of mysql_secure_installation # Secure MariaDB (this does what mysql_secure_installation performs without interaction) mysql -e "UPDATE mysql.user SET Password=PASSWORD('$DB_ROOT_PASS') WHERE User='root';" mysql -e "DELETE FROM mysql.user WHERE User='root' AND Host NOT IN ('localhost', '127.0.0.1', '::1');" mysql -e "DELETE FROM mysql.user WHERE User='';" # Beginning on some version of MariaDB after Fedora 29 was released, the test DB is no longer there by defualt. mysql -e "DROP DATABASE test;" mysql -e "FLUSH PRIVILEGES;"

Your approach makes it easier to use as part of a script.

It also generates random passwords, which I prefer.

@LilAng said in Copy / Paste from Excel on Mac to Outlook Web Access Creates Image Rather than Table:

In Excel, use File > Save as web page, then attach the web page to your email message?

Yeah, we found that process. That's a pretty huge "fail" process.

@JaredBusch said in Upgrading to osTicket 1.11.0:

So what is the point of using OSTicket? There are solutions for that.

Time tracking would be nice. But lots of shops don't use it. MSPs do, but internal IT often does not.

@Dashrender said in Make an osTicket Database Backup:

Total DB Admin noob here - so bare with me.

Does this include the username/password setup for this DB? or does that need to be maintained separately?

i.e. you have to rebuild from this backup - do you just create a brand new SQL user and grant them rights to this DB upon import, then use that new account to give access to the app?

In typing out my question I kinda assume the answer is the second bit - you just create a new user and assign them rights.

Correct. The user and the database are separate things.

0.2.9-z is working for us here. Thanks!

I have a script that I wrote to do this.

https://gitlab.com/dafyre/powershell-utils/raw/master/export-O365Group.ps1

It gets you the person's DisplayName and their email address.

If you're exporting a Distribution List, just add the -distributionlist switch.

If you're exporting an Office 365 Group (Unified Group), then leave that switch out. Other parameters should be self explanatory.

Not yet.

@scottalanmiller said in EFI Pace Won't Start After Vault Configuration Change:

Had to deal with Fiery too.

I think they misspelled that name slightly. Fire that company (I know, you wish they would.)

The first time it is used, we have to manually type the domain\localadmin password.
995d4dcc-8f3f-428f-a56e-aafa241ca644-image.png
After that it is stored in credential manager.
e44ddd17-77ee-4318-a779-8edbc1471c2a-image.png