$ cp -a /var/lib/mailman/archives/private/<listname>/* <backup_directory>

Remove the archives

$ rm -rf <listname>/*

Once it is removed recreate the html archive files

$ mailman/bin/arch <listname>

./arun

1. Edit Postfix Virtual Configuration:

Open and edit the Postfix virtual configuration file.

Add the following line, replacing email_address with the address you want to configure for autoresponding, and email_address@autoreply.nic.net.sa with the destination address for autoresponses:

For example:

2. Edit the Transport Configuration:

Open the transport configuration file and add the following line:

For example:

3. Create a Pipe for the Autoresponder in master.cf:

To execute the autoresponder script, create a pipe in the master.cf configuration. Open the master.cf file and add the following lines:

4. Create the Autoresponder Script:

Create the autoresponder script at the specified location, in this case, /usr/local/bin/autoreply.

Here’s an example of what the script could look like:

Customize the script with the appropriate sender address, subject, and content for your auto responses.

There are alternative methods for setting up autoresponders, such as using tools like Procmail, depending on your mail server setup. Postfix provides flexibility, and you can choose the method that best suits your needs.

HTML Fax Handling:

When it comes to processing HTML faxes with Unicode encoding, you can use the following script

#!/bin/bash
cp -pf $1 /tmp/email.html
/usr/bin/lynx -dump -display_charset=utf-8 /tmp/email.html > /tmp/html_txt
/usr/bin/uniprint -font /etc/hylafax/faxmail/Cyberbit.ttf -in /tmp/html_txt -out /tmp/html_txt.uni
cat /tmp/html_txt.uni | /etc/hylafax/faxmail/filter.pl
rm /tmp/email.html
rm /tmp/html_txt
rm /tmp/html_txt.uni

Here’s a breakdown of what this script does:

• It copies the incoming fax to a temporary file, /tmp/email.html.
• Using lynx, redirect the HTML content to plain text while specifying the UTF-8 character set for proper encoding.
• The uniprint utility is then used to apply the Cyberbit.ttf font to the converted text, saving it as /tmp/html_txt.uni.
• Finally, it pipes the content through filter.pl, a Perl script that processes the text.

Plain Text Fax Handling:

For plain text faxes with Unicode encoding, you can utilize this script

This script is more straightforward. It uses uniprint to apply the Cyberbit.ttf font to the plain text content, and then pipes it through filter.pl.

filter.pl:

The filter.pl Perl script is responsible for processing the text content, including stripping out any “showpage” directives.

This Perl script processes the text, counts the “showpage” occurrences, and removes the last “showpage” directive.

Cleaning Up with the Command Line:

The process of cleaning up held messages in Mailman is relatively straightforward, thanks to some handy command-line tools.

1. Navigating to the Mailman Directory:

First, open your terminal and navigate to the Mailman directory. You can usually find it at:

2. Using bin/discard:

To clean up held messages, you can typically use the bin/discard command. Run the following command, specifying the path to the held messages:

Cleaning Up a Long List of Held Messages:

In some cases, you might have a long list of held messages to deal with. In this situation, you can make use of a more efficient approach.

1. Navigating to the Appropriate Directory:

Navigate to the Mailman data directory where the held messages are stored. This is typically located at:

2. Using find and xargs:

The find command helps you locate all the held messages. It searches for files with the name pattern “heldmsg–*”. After finding them, it passes them as arguments to the discard command using xargs.

Execute the following command:

This approach efficiently processes a long list of held messages and gets your Mailman mailing list back in order