GPG sign error-message
When I sign a mail with GPG I get the following error-message: gpg: skipped `my-secret-key-ID': this is a PGP generated ElGamal key which is not secure for signatures! Press any key to continue... However, the recipient sees nothing wrong: [-- PGP output follows (current time: Tue Jan 2 07:51:37 2001) --] gpg: Signature made Tue Jan 02 06:26:09 2001 EST using DSA key ID my-public-key-ID gpg: Good signature from "Russell Hoover [EMAIL PROTECTED]" [-- End of PGP output --] This is with: set pgp_sign_as=my-secret-key-ID in my gpg.rc. But when I put in my gpg.rc: set pgp_sign_as=my-PUBLIC-key-ID I get no error message, but the recipient sees: [-- PGP output follows (current time: Tue Jan 2 07:51:37 2001) --] gpg: can't handle these multiple signatures [-- End of PGP output --] What am I dong wrong? -- // [EMAIL PROTECTED] //
Mutt and *nix clients and Qmail server
I have no problem setting up Windows/OS/2 clients to connect to the Qmail server to relay the messages. The problem I am facing now is *nix clients. It looks like the *nix clients (with the exception of Pine) do require a local SMTP server to relay to the main SMTP server. One of the clients, I am using is mutt. It doesn't look like Mutt can send the message directly to the relaying SMTP server. Is there a Qmail solution to secure the *nix clients? I prefer not to run sendmail on the local clients for their mail to go out. Are there any work arounds for the Mutt client? Thank you in advance for any info or ideas. -- Subba Rao [EMAIL PROTECTED] http://pws.prserv.net/truemax/
Re: Mutt and *nix clients and Qmail server
Subba Rao proclaimed on mutt-users that: I have no problem setting up Windows/OS/2 clients to connect to the Qmail server to relay the messages. The problem I am facing now is *nix clients. It looks like the *nix clients (with the exception of Pine) do require a local SMTP server to relay to the main SMTP server. One of the clients, I am using is mutt. It doesn't look like Mutt can send the message directly to the relaying SMTP server. Use something like masqmail / nullmailer and such on the local unix clients. --suresh -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Mutt and *nix clients and Qmail server
On Tue, Jan 02, 2001 at 07:53:54PM +0530, Suresh Ramasubramanian wrote: Subba Rao proclaimed on mutt-users that: I have no problem setting up Windows/OS/2 clients to connect to the Qmail server to relay the messages. The problem I am facing now is *nix clients. It looks like the *nix clients (with the exception of Pine) do require a local SMTP server to relay to the main SMTP server. One of the clients, I am using is mutt. It doesn't look like Mutt can send the message directly to the relaying SMTP server. Use something like masqmail / nullmailer and such on the local unix clients. The point is, Unix mail clients do not require a local SMTP server per se; they require a sendmail-like *program* to.. well.. to send mail :) It's much easier - and less error-prone - for mail clients to know they have to execute such-and-such program and pass such-and-such parameters to it, than to make all mail clients actually network-aware SMTP clients (with all the subtleties of SMTP and any network protocol - response parsing and such..) So, just as Suresh suggested, look into some mail delivery agents that act like the sendmail *program*, not SMTP server, and take care of all the SMTP talk. G'luck, Peter -- I've heard that this sentence is a rumor.
Re: GPG sign error-message
On Tue 01/02/01 at 08:24 AM -0500, Russell Hoover [EMAIL PROTECTED] wrote: When I sign a mail with GPG I get the following error-message: gpg: skipped `my-secret-key-ID': this is a PGP generated ElGamal key which is not secure for signatures! Press any key to continue... I commented-out the "set pgp_sign_as" setting in my gpg.rc, and that solved the problem, though I don't know that this might adversely affect other things. Anyone know if it will? -- // [EMAIL PROTECTED] //
