RE: Sturman Industries Alerts

From: Rizzuto, Alan (ARizzuto_at_SturmanIndustries.com)
Date: 10/14/03

  • Next message: Toralf Lund: "Re: C++ lib compatibility between Red Hat 9 and 7.3"
    To: <redhat-list@redhat.com>
    Date: Tue, 14 Oct 2003 08:50:00 -0600
    
    

    I am the admin and on vacation - someone turned on the alerts while I am
    gone - I will get it fixed - OK.
    Alan Rizzuto

    -----Original Message-----
    From: redhat-list-admin@redhat.com [mailto:redhat-list-admin@redhat.com]
    On Behalf Of David C. Hart
    Sent: Monday, October 13, 2003 8:19 AM
    To: Redhat General List
    Subject: Re: Sturman Industries Alerts

    On Mon, 2003-10-13 at 09:19, Michael Schwendt wrote:

    > Inline (aka "clear text") signatures are the old and deprecated form.
    > S/MIME PGP detached signatures would be the right way to go. But using
    > new features, which are not [fully] supported by all mail user agents
    > and list management software, usually has side effects. Such as
    > unreadable Base64 encoded message bodies in list archives or
    > signatures, which verify as bad because the mailing-list software
    > modifies the mesage body content.
    >
    I think that the bottom line is that signing messages is a matter of
    personal preference. I keep it on by default and encourage clients to do
    the same. In line or by attachment may be a function of the mail client.
    Evolution creates attachments by default. On the recipient end, I prefer
    the attachment since it "decodes" automatically. Again, that's related
    to the client.

    The most disturbing issue is that Symantec sells a product that is
    incapable of distinguishing between PGP and executable attachments.
    Reliance on this product might bounce more valid mail than SPEWS ever
    did. Microsoft's mail server is broken enough without adding more
    impediments to communications.

    Moreover, this is an issue that has been discussed with respect to
    Sturman as recently as last July. It's hard to believe that they would
    not correct this issue by now given the implications.

    Some nitwit suggested that, by posting this matter to the list (from
    which the problem originates), it is - somehow - spam. I disagree.

    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: Toralf Lund: "Re: C++ lib compatibility between Red Hat 9 and 7.3"

    Relevant Pages

    • gray, its making me; 2007
      ... as a client for Exchange Server off a SBS box. ... "Rules and Alerts" is grayed out. ... email accounts. ...
      (microsoft.public.outlook)
    • Rules and Alerts" is grayed out in Outlook
      ... as a client for Exchange Server off an SBS box. ... "Rules and Alerts" is grayed out. ... email accounts. ...
      (microsoft.public.exchange.clients)
    • SSPI - use of ApplyControlToken
      ... The SSPI constant SCHANNEL_SHUTDOWN is used with the API function ... client request for renegotiation, and then send the resulting output to the ... tokens in other situations where TLS would use alerts? ...
      (microsoft.public.platformsdk.security)
    • Global Alerts on Lists and Document Libraries
      ... I have a client that wishes to allow users to set a Global Alerts on ... any changes on the site (for Lists and Document Libraries). ... But the client would like to set a global change alert. ...
      (microsoft.public.sharepoint.portalserver.development)
    • Horribly frustrating email alerts
      ... How come Outlooks alerts are so intrusive? ... It doesn't matter if I am typing in Outlook or ...
      (microsoft.public.outlook.general)