<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>e-mail &#8211; Arun&#8217;s blog</title>
	<atom:link href="https://arunns.net/category/communication/e-mail/feed/" rel="self" type="application/rss+xml" />
	<link>https://arunns.net</link>
	<description>Arun&#039;s blog</description>
	<lastBuildDate>Sat, 21 Oct 2023 14:08:48 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.2</generator>
	<item>
		<title>Setting Up Autoresponders with Postfix Virtual</title>
		<link>https://arunns.net/auto-responder-with-postfix/</link>
					<comments>https://arunns.net/auto-responder-with-postfix/#comments</comments>
		
		<dc:creator><![CDATA[Arun N.]]></dc:creator>
		<pubDate>Wed, 28 Oct 2009 18:59:38 +0000</pubDate>
				<category><![CDATA[e-mail]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[postfix]]></category>
		<guid isPermaLink="false">http://arunnsblog.com/blog/?p=80</guid>

					<description><![CDATA[One of the options to configure auto responder with Postfix 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: Copy code email_address recepient_lists, email_address@autoreply.nic.net.sa For example: Copy code [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>One of the options to configure auto responder with Postfix</p>
<p><strong>1. Edit Postfix Virtual Configuration:</strong></p>
<p>Open and edit the Postfix virtual configuration file.</p>
<p>Add the following line, replacing <code>email_address</code> with the address you want to configure for autoresponding, and <code>email_address@autoreply.nic.net.sa</code> with the destination address for autoresponses:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-plaintext">email_address recepient_lists, email_address@autoreply.nic.net.sa<br />
</code></div>
</div>
<p>For example:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-plaintext">wordpress@example.com recepient1@example.com, wordpress@google.com@autoreply.example.com<br />
</code></div>
</div>
<p><strong>2. Edit the Transport Configuration:</strong></p>
<p>Open the transport configuration file and add the following line:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-plaintext">autoreply.domain.com autoreply:<br />
</code></div>
</div>
<p>For example:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-plaintext">autoreply.example.com autoreply:<br />
</code></div>
</div>
<p><strong>3. Create a Pipe for the Autoresponder in master.cf:</strong></p>
<p>To execute the autoresponder script, create a pipe in the master.cf configuration. Open the master.cf file and add the following lines:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-plaintext">autoreply unix - n n - - pipe<br />
  flags= user=nobody argv=/usr/local/bin/autoreply $sender $recipient<br />
</code></div>
</div>
<p><strong>4. Create the Autoresponder Script:</strong></p>
<p>Create the autoresponder script at the specified location, in this case, <code>/usr/local/bin/autoreply</code>.</p>
<p>Here&#8217;s an example of what the script could look like:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash"><span class="hljs-meta">#!/bin/bash</span></p>
<p></code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">/usr/sbin/sendmail -oi -t &lt;&lt; <span class="hljs-string">EOF<br />
</span></code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash"><span class="hljs-string">From: nobody@example.com<br />
</span></code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash"><span class="hljs-string">To: $1<br />
</span></code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash"><span class="hljs-string">Subject: Auto Response from example.com<br />
</span></code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash"><span class="hljs-string">Content-Type: text/plain; charset=utf-8</p>
<p></span></code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash"><span class="hljs-string">This is an autoreponder email.<br />
</span></code></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash"><span class="hljs-string">EOF</span><br />
</code></div>
</div>
<p>Customize the script with the appropriate sender address, subject, and content for your auto responses.</p>
<p>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.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://arunns.net/auto-responder-with-postfix/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Cleanup mailman held messages</title>
		<link>https://arunns.net/cleanup-mailman-held-messages/</link>
					<comments>https://arunns.net/cleanup-mailman-held-messages/#respond</comments>
		
		<dc:creator><![CDATA[Arun N.]]></dc:creator>
		<pubDate>Wed, 21 Oct 2009 10:54:37 +0000</pubDate>
				<category><![CDATA[e-mail]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[mailman]]></category>
		<guid isPermaLink="false">http://arunnsblog.com/blog/?p=50</guid>

					<description><![CDATA[Occasionally, you might encounter a situation where messages get held up in mailman for various reasons, and it&#8217;s essential to know how to clean up these held messages. 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 [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Occasionally, you might encounter a situation where messages get held up in mailman for various reasons, and it&#8217;s essential to know how to clean up these held messages.</p>
<p><strong>Cleaning Up with the Command Line:</strong></p>
<p>The process of cleaning up held messages in Mailman is relatively straightforward, thanks to some handy command-line tools.</p>
<p><strong>1. Navigating to the Mailman Directory:</strong></p>
<p>First, open your terminal and navigate to the Mailman directory. You can usually find it at:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">$ <span class="hljs-built_in">cd</span> /usr/lib/mailman<br />
</code></div>
</div>
<p><strong>2. Using <code>bin/discard</code>:</strong></p>
<p>To clean up held messages, you can typically use the <code>bin/discard</code> command. Run the following command, specifying the path to the held messages:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">$ bin/discard /var/lib/mailman/data/heldmsg--*<br />
</code></div>
</div>
<p><strong>Cleaning Up a Long List of Held Messages:</strong></p>
<p>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.</p>
<p><strong>1. Navigating to the Appropriate Directory:</strong></p>
<p>Navigate to the Mailman data directory where the held messages are stored. This is typically located at:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">$ <span class="hljs-built_in">cd</span> /var/lib/mailman<br />
</code></div>
</div>
<p><strong>2. Using <code>find</code> and <code>xargs</code>:</strong></p>
<p>The <code>find</code> command helps you locate all the held messages. It searches for files with the name pattern &#8220;heldmsg&#8211;*&#8221;. After finding them, it passes them as arguments to the <code>discard</code> command using <code>xargs</code>.</p>
<p>Execute the following command:</p>
<div class="bg-black rounded-md mb-4">
<div class="flex items-center relative text-gray-200 bg-gray-800 gizmo:dark:bg-token-surface-primary px-4 py-2 text-xs font-sans justify-between rounded-t-md"><button class="flex ml-auto gizmo:ml-0 gap-2 items-center">Copy code</button></div>
<div class="p-4 overflow-y-auto"><code class="!whitespace-pre hljs language-bash">$ find data -name heldmsg--* -<span class="hljs-built_in">print</span> | xargs /usr/bin/discard<br />
</code></div>
</div>
<p>This approach efficiently processes a long list of held messages and gets your Mailman mailing list back in order</p>
]]></content:encoded>
					
					<wfw:commentRss>https://arunns.net/cleanup-mailman-held-messages/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>[Resolved] Postfix X-Authentication Warning</title>
		<link>https://arunns.net/resolved-postfix-x-authentication-warning/</link>
					<comments>https://arunns.net/resolved-postfix-x-authentication-warning/#respond</comments>
		
		<dc:creator><![CDATA[Arun N.]]></dc:creator>
		<pubDate>Sat, 03 Oct 2009 11:23:18 +0000</pubDate>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[e-mail]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[postfix]]></category>
		<guid isPermaLink="false">http://arunnsblog.com/blog/?p=29</guid>

					<description><![CDATA[It&#8217;s possible to see X-Authentication-Warning in the email header when the mail server doesn&#8217;t trust the user. This can sometimes cause emails to be marked as spam. To solve the problem, you can add the user to the /etc/mail/trusted-users file. If your system includes forms that are used to send email as the Apache user, [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>It&#8217;s possible to see X-Authentication-Warning in the email header when the mail server doesn&#8217;t trust the user. This can sometimes cause emails to be marked as spam. To solve the problem, you can add the user to the /etc/mail/trusted-users file. If your system includes forms that are used to send email as the Apache user, you need to add the &#8220;Apache&#8221; user to the trusted-users file.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://arunns.net/resolved-postfix-x-authentication-warning/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
