Community Discussions and Support
Inhibit POP3 deletion only for specific mailbox

Thomas it works perfectly !!!  Also other options are very interesting.

I have no words to say thank you ... Mercury/32 reserves allways a lot of nice surprises ... [:D]

Alex Bromo

<P>Thomas it works perfectly !!!  Also other options are very interesting. </P> <P>I have no words to say thank you ... Mercury/32 reserves allways <SPAN id=result_box lang=en class=short_text><SPAN title="" te="a lot of nice surprises" se="un sacco di belle sorprese" closure_uid_r3bdgd="76">a lot of nice surprises ... [:D]</SPAN></SPAN></P> <P><SPAN lang=en class=short_text><SPAN title="" te="a lot of nice surprises" se="un sacco di belle sorprese" closure_uid_r3bdgd="76">Alex Bromo</SPAN></SPAN></P>

In our Mercury/32 mailserver we have both POP3 and IMAP4 protocols actives, so users can choose to setup one or other protocol in their mail client.

Some days ago we created an "institutional" mailbox that we want to share with some users, so we want use it *only* with IMAP protocol, to avoid accidental POP3 deletion of incoming messages (i.e. due user's client miscofiguration).

Could be possible to inhibit the POP3 protocol (or POP3 deletion) only on a specific mailbox ?

Many thanks.

Alex.

<P>In our Mercury/32 mailserver we have both POP3 and IMAP4 protocols actives, so users can choose to setup one or other protocol in their mail client. </P> <P>Some days ago we created an "institutional" mailbox that we want to share with some users, so we want use it *only* with IMAP protocol, to avoid accidental POP3 deletion of incoming messages (i.e. due user's client miscofiguration). </P> <P>Could be possible to inhibit the POP3 protocol (or POP3 deletion) only on a specific mailbox ?</P> <P>Many thanks.</P> <P>Alex.</P>

Sorry, no built-in function to prevent POP3 access to individual mailboxes. That said, it would probably be possible to write a small event daemon to intercept POP3 logins and deny access for specific mailboxes. There is a daemon development kit in the downloads section, but it will require some programming experience.

/Rolf

<p>Sorry, no built-in function to prevent POP3 access to individual mailboxes. That said, it would probably be possible to write a small event daemon to intercept POP3 logins and deny access for specific mailboxes. There is a daemon development kit in the downloads section, but it will require some programming experience.</p><p>/Rolf </p>

> Could be possible to inhibit the POP3 protocol (or POP3 deletion) only on a specific mailbox ?

Yes, try using a POP3.PRO file in the new mail directory of the user to inhibit the POP3 deletes.  Each user on the server can have a file called POP3.PRO in his new mail directory which contains settings MercuryP will use when a POP3 connection is established. POP3.PRO is a simple text file, editable with any text editor (such as the DOS EDIT command). The following keywords can be used in it:

As well as user POP3 profiles (see the previous section) you can define a system-wide POP3 profile by creating a file using the same syntax, called SYS:SYSTEM/POP3.PRO. (mercury.exe directory) The system-wide profile is read first, and then the user profile (if any) is applied. Settings in the files are cumulative, so a setting applied in the system profile will remain after a user profile is read unless the user profile explicitly alters it.

   Mark read : <Y or N>
   If Y, then MercuryP will mark as having been read any  messages downloaded during a session but not deleted.

   Show read : <Y or N>
   If Y, then MercuryP will show all messages in the user's new mailbox when asked for a list by a POP3 client. If N,
   then only mail which has NOT been marked as read will be presented.

   Show status : <Y or N>
   If Y, then MercuryP will generate artificial "Status:" headers such as might be found in a Unix mailbox. Usually
   these headers are not present since neither Pegasus Mail nor Mercury relies on them for status information about
   the message, but other POP3 mailers (such as Eudora) rely on these headers to provide functionality.

   No delete : <Y or N>
   If Y, then MercuryP will not delete messages even when instructed to do so by the POP3 client. This is useful if
   you are using a POP3 client which cannot be configured to leave messages on the server, and you want to do so.


   Delete is final : <Y or N>
   If Y, then any mail deleted using the POP3 DELE command will be deleted if the connection to the server is lost.
   The default condition is for mail deleted using DELE to be recovered if the connection terminates abnormally. If
   you routinely access your mail across a slow or unreliable TCP/IP link (e.g, SLIP) you may prefer to set this to Y.

&amp;gt; Could be possible to inhibit the POP3 protocol (or POP3 deletion) only on a specific mailbox ? Yes, try using a POP3.PRO file in the new mail directory of the user to inhibit the POP3 deletes.&amp;nbsp; Each user on the server can have a file called POP3.PRO in his new mail directory which contains settings MercuryP will use when a POP3 connection is established. POP3.PRO is a simple text file, editable with any text editor (such as the DOS EDIT command). The following keywords can be used in it: As well as user POP3 profiles (see the previous section) you can define a system-wide POP3 profile by creating a file using the same syntax, called SYS:SYSTEM/POP3.PRO. (mercury.exe directory) The system-wide profile is read first, and then the user profile (if any) is applied. Settings in the files are cumulative, so a setting applied in the system profile will remain after a user profile is read unless the user profile explicitly alters it. &amp;nbsp;&amp;nbsp; Mark read : &amp;lt;Y or N&amp;gt; &amp;nbsp;&amp;nbsp; If Y, then MercuryP will mark as having been read any&amp;nbsp; messages downloaded during a session but not deleted. &amp;nbsp;&amp;nbsp; Show read : &amp;lt;Y or N&amp;gt; &amp;nbsp;&amp;nbsp; If Y, then MercuryP will show all messages in the user&#039;s new mailbox when asked for a list by a POP3 client. If N, &amp;nbsp;&amp;nbsp; then only mail which has NOT been marked as read will be presented. &amp;nbsp;&amp;nbsp; Show status : &amp;lt;Y or N&amp;gt; &amp;nbsp;&amp;nbsp; If Y, then MercuryP will generate artificial &quot;Status:&quot; headers such as might be found in a Unix mailbox. Usually &amp;nbsp;&amp;nbsp; these headers are not present since neither Pegasus Mail nor Mercury relies on them for status information about &amp;nbsp;&amp;nbsp; the message, but other POP3 mailers (such as Eudora) rely on these headers to provide functionality. &amp;nbsp;&lt;b&gt;&amp;nbsp; No delete : &amp;lt;Y or N&amp;gt; &amp;nbsp;&amp;nbsp; If Y, then MercuryP will not delete messages even when instructed to do so by the POP3 client. This is useful if &amp;nbsp;&amp;nbsp; you are using a POP3 client which cannot be configured to leave messages on the server, and you want to do so.&lt;/b&gt; &amp;nbsp;&amp;nbsp; Delete is final : &amp;lt;Y or N&amp;gt; &amp;nbsp;&amp;nbsp; If Y, then any mail deleted using the POP3 DELE command will be deleted if the connection to the server is lost. &amp;nbsp;&amp;nbsp; The default condition is for mail deleted using DELE to be recovered if the connection terminates abnormally. If &amp;nbsp;&amp;nbsp; you routinely access your mail across a slow or unreliable TCP/IP link (e.g, SLIP) you may prefer to set this to Y.
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft