Pegasus Mail & Mercury

Welcome to the Community for Pegasus Mail and
The Mercury Mail Transport System, the Internet's longest-serving PC e-mail system!
Welcome to Pegasus Mail & Mercury Sign in | Join | Help
in
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview

Commandline too short in Policy

Last post 03-24-2008, 21:29 by Barius. 6 replies.
Sort Posts: Previous Next
  •  12-10-2007, 21:20

    • Barius is not online. Last active: 12-31-2008, 2:56 Barius
    • Top 25 Contributor
    • Joined on 05-15-2007
    • Member
    • Points 1,080

    Commandline too short in Policy

    Configuration->Mercury core module...->Policy->"Commandline".  The number of characters is too short (128?).  I'm sure this is a remnant from Win98 days, but it is far too restrictive today.  Many virus scanners have longer command line parameters than they used to (likely because they have moved on from Win98 days).  The result is that I cannot run mine (nod32) directly using this setting in Mercury, I have had to create a batch file and run using a sentinel file.  This should not be necessary and is likely beyond many novice users.

    Ideally, Mercury would set the length of this parameter based on the detected OS, but I'd settle for a hard-coded limit based on the NT 5+ kernel (Win2k+) which is 2046 characters (WinXP+ = 8191 chars).

     

  •  12-11-2007, 6:12

    Re: Commandline too short in Policy

    Most admins use virprot when calling nod32
  •  12-11-2007, 22:06

    • Barius is not online. Last active: 12-31-2008, 2:56 Barius
    • Top 25 Contributor
    • Joined on 05-15-2007
    • Member
    • Points 1,080

    Re: Commandline too short in Policy

    Great, but I shouldn't have to use an external 'pipe' to do what Mercury should be able to do internally.  The command line length is a problem, regardless of workarounds.  This is a suggestion/wish, not a request for help.

     

  •  12-12-2007, 5:23

    Re: Commandline too short in Policy

    As long as Mercury supports Windows 98 it wouldn't be a good idea to have a command line that exceeds the maximum length for that OS. But if it would be possible to detect the OS and set the length accordingly without extensive code changes that certainly sounds like an improvement.

    /Rolf 

  •  12-13-2007, 21:33

    • Barius is not online. Last active: 12-31-2008, 2:56 Barius
    • Top 25 Contributor
    • Joined on 05-15-2007
    • Member
    • Points 1,080

    Re: Commandline too short in Policy

    I think the minimal 'fix' that would work is to set the length to 2048 chars, but if the user enters more than 128 chars, have a popup warning letting the user know that their command may not work if they use Win98/95/ME.  Nice and simple.

    Still, OS detection is *not* difficult.  It's a simple registry lookup...
     

  •  03-20-2008, 15:27

    • fojtik is not online. Last active: 01-05-2009, 20:17 fojtik
    • Top 150 Contributor
    • Joined on 05-28-2007
    • Member
    • Points 290

    Re: Commandline too short in Policy

    There should be no problem to enter shortened path:

    dir c:\progra~1\

    15355\ Webcam\ Live
    MySQL
    7-Zip
    NX\ Client\ for\ Windows

     

    do you see how to short the file path. This works even on Windows XP. 

  •  03-24-2008, 21:29

    • Barius is not online. Last active: 12-31-2008, 2:56 Barius
    • Top 25 Contributor
    • Joined on 05-15-2007
    • Member
    • Points 1,080

    Re: Commandline too short in Policy

    @fojtik 

    Yes, I already use dos command format, sometimes it is still not short enough.  In these cases I resort to .bat files.  However, this is the 'Suggestion & Wishlist' forum, which is why I am posting a request for a feature, which in my opinion, should have been implemented years ago.

View as RSS news feed in XML

Copyright © 2007 David Harris / Peter Strömblad. All Rights Reserved. | Terms of Use | Privacy Statement
Questions/Problems with community.pmail.com? | Visit our Hoster: PraktIT | Pegasus Mail Home Page