<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.qmailtoaster.org:80/index.php?action=history&amp;feed=atom&amp;title=Resolving_apparent_login_failures_with_SMTP_and_POP</id>
	<title>Resolving apparent login failures with SMTP and POP - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.qmailtoaster.org:80/index.php?action=history&amp;feed=atom&amp;title=Resolving_apparent_login_failures_with_SMTP_and_POP"/>
	<link rel="alternate" type="text/html" href="http://wiki.qmailtoaster.org:80/index.php?title=Resolving_apparent_login_failures_with_SMTP_and_POP&amp;action=history"/>
	<updated>2026-04-05T20:03:52Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>http://wiki.qmailtoaster.org:80/index.php?title=Resolving_apparent_login_failures_with_SMTP_and_POP&amp;diff=170&amp;oldid=prev</id>
		<title>Ebroch: Created page with &quot;Following upgrades or initial installations, you may find that your mail client is unable to connect successfully to your SMTP submission port or to the POP3 port. Some mail clients will report this as a password error; others may simply report a generic problem.  One possibility is that the &#039;vchkpw&#039; daemon does not have enough memory to run. You can test this by hand-simulating a POP session with, for example:          &#039;&#039;&#039;telnet yourhost.com pop3&#039;&#039;&#039;          Trying 1.2....&quot;</title>
		<link rel="alternate" type="text/html" href="http://wiki.qmailtoaster.org:80/index.php?title=Resolving_apparent_login_failures_with_SMTP_and_POP&amp;diff=170&amp;oldid=prev"/>
		<updated>2024-03-16T17:00:44Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Following upgrades or initial installations, you may find that your mail client is unable to connect successfully to your SMTP submission port or to the POP3 port. Some mail clients will report this as a password error; others may simply report a generic problem.  One possibility is that the &amp;#039;vchkpw&amp;#039; daemon does not have enough memory to run. You can test this by hand-simulating a POP session with, for example:          &amp;#039;&amp;#039;&amp;#039;telnet yourhost.com pop3&amp;#039;&amp;#039;&amp;#039;          Trying 1.2....&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Following upgrades or initial installations, you may find that your mail client is unable to connect successfully to your SMTP submission port or to the POP3 port. Some mail clients will report this as a password error; others may simply report a generic problem.&lt;br /&gt;
&lt;br /&gt;
One possibility is that the &amp;#039;vchkpw&amp;#039; daemon does not have enough memory to run. You can test this by hand-simulating a POP session with, for example:&lt;br /&gt;
&lt;br /&gt;
        &amp;#039;&amp;#039;&amp;#039;telnet yourhost.com pop3&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
        Trying 1.2.3.4...&lt;br /&gt;
&lt;br /&gt;
        Connected to yourhost.com.&lt;br /&gt;
&lt;br /&gt;
        Escape character is &amp;#039;^]&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
        +OK &amp;lt;21223.1390353263@yourhost.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;#039;&amp;#039;&amp;#039;USER &amp;lt;yourlogin&amp;gt;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
        +OK &lt;br /&gt;
&lt;br /&gt;
        &amp;#039;&amp;#039;&amp;#039;PASS &amp;lt;yourpass&amp;gt;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
(user input is shown in &amp;#039;&amp;#039;&amp;#039;bold&amp;#039;&amp;#039;&amp;#039;).&lt;br /&gt;
&lt;br /&gt;
The server should respond at this point with &amp;#039;+OK&amp;#039;. If it responds:&lt;br /&gt;
&lt;br /&gt;
        /home/vpopmail/bin/vchkpw: error while loading shared libraries: libresolv.so.2: failed to map segment from shared object: Cannot allocate memory&lt;br /&gt;
       -ERR authorization failed&lt;br /&gt;
&lt;br /&gt;
you have probably encountered a memory problem. To resolve this, do:&lt;br /&gt;
&lt;br /&gt;
        vi /var/qmail/supervise/*/run&lt;br /&gt;
&lt;br /&gt;
Step through the files one by one, checking each one for a line that resembles:&lt;br /&gt;
&lt;br /&gt;
        /usr/bin/softlimit -m 48000000&lt;br /&gt;
&lt;br /&gt;
In each such file, change the &amp;#039;48000000&amp;#039; to &amp;#039;64000000&amp;#039;. Then restart qmail with:&lt;br /&gt;
&lt;br /&gt;
        qmailctl stop&lt;br /&gt;
        qmailctl start&lt;br /&gt;
&lt;br /&gt;
and try your POP session again. If it now succeeds, the problem is probably resolved. If not, try raising the limit again.&lt;/div&gt;</summary>
		<author><name>Ebroch</name></author>
	</entry>
</feed>