How to Install and Uninstall php-pear-Mail-Mime.noarch Package on Red Hat Enterprise Linux 9 (RHEL 9)

Last updated: November 24,2024

1. Install "php-pear-Mail-Mime.noarch" package

Please follow the instructions below to install php-pear-Mail-Mime.noarch on Red Hat Enterprise Linux 9 (RHEL 9)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                php-pear-Mail-Mime.noarch
            
                    
    
    Copied

2. Uninstall "php-pear-Mail-Mime.noarch" package

This guide let you learn how to uninstall php-pear-Mail-Mime.noarch on Red Hat Enterprise Linux 9 (RHEL 9):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                php-pear-Mail-Mime.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the php-pear-Mail-Mime.noarch package on Red Hat Enterprise Linux 9 (RHEL 9)

Last metadata expiration check: 0:01:17 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : php-pear-Mail-Mime
Version : 1.10.11
Release : 5.el9
Architecture : noarch
Size : 50 k
Source : php-pear-Mail-Mime-1.10.11-5.el9.src.rpm
Repository : epel
Summary : Classes to create MIME messages
URL : http://pear.php.net/package/Mail_Mime
License : BSD-3-Clause
Description : Mail_Mime provides classes to deal with the creation and manipulation
: of MIME messages. It allows people to create e-mail messages consisting of:
: * Text Parts
: * HTML Parts
: * Inline HTML Images
: * Attachments
: * Attached messages
:
: It supports big messages, base64 and quoted-printable encoding and
: non-ASCII characters in file names, subjects, recipients, etc. encoded
: using RFC2047 and/or RFC2231.