Your message, Port 6000/X11 Won't Close!,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
--- Begin Message ---
I use debian 2.2 (woody/unstable) with kernal 2.4.7, i use login.app to login
to X.
I use debian 2.2 (woody/unstable) with kernal 2.4.7, i use login.app to login
to X. I believe i have the --no-listen command set. However, no madder what i
do port 6000 still remains open. I really want to close this port for security
reasons! can someone please help me?! - Thank you!
--
vexat
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
--- Begin Message ---
Hi Martin!
On Thu, 09 Aug 2001, Martin Domig wrote:
> Is there a way to make mutt sen
Hi Martin!
On Thu, 09 Aug 2001, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Although there is a way to tell mutt not to use PGP/MIME, Don't Do It. Mutt
will mistype the message as application/pgp and royally screw up the
readab
Your message, Port 6000/X11 Won't Close!,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
I use debian 2.2 (woody/unstable) with kernal 2.4.7, i use login.app to login
to X. I believe i have the --no-listen command set. However, no madder what i
do port 6000 still remains open. I really want to close this port for security
reasons! can someone please help me?! - Thank you!
--
vexa
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
--- Begin Message ---
On Thu, Aug 09, 2001 at 03:51:14PM -0500, Rob VanFleet wrote:
> On Thu, Aug 09, 2001 a
On Thu, Aug 09, 2001 at 03:51:14PM -0500, Rob VanFleet wrote:
> On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> > option "pgp_create_traditional". That option might help you very much,
> > but instead I would suggest that the other MUA's get fixed.
>
> Um, wouldn't that be every
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
Hi Martin!
On Thu, 09 Aug 2001, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Although there is a way to tell mutt not to use PGP/MIME, Don't Do It. Mutt
will mistype the message as application/pgp and royally screw up the
reada
-. Alberto Cortés (2001-08-09) :
| I have a little problem with apt-get, i think i am not doing it the
| proper way.
|
|When there is a announce that certain package has a bug, (like
| gnupg v1.0.5) you can read in www.debian.org that there is a new
| package to download (1.0.6-0pota
Hi
On Thu, Aug 09, 2001 at 11:51:30PM +0200, Alberto Cort?s wrote:
>
> deb http://http.us.debian.org/debian stable main contrib non-free
> deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free
>
> What are the official sources if you want to have an up to date,
> sec
Your message, Re: Mutt and inline gpg,
was not delivered to the following recipient:
[EMAIL PROTECTED]
Reason: System error: Please re-send your message later.
Recipient: [EMAIL PROTECTED]
On Thu, Aug 09, 2001 at 03:51:14PM -0500, Rob VanFleet wrote:
> On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> > option "pgp_create_traditional". That option might help you very much,
> > but instead I would suggest that the other MUA's get fixed.
>
> Um, wouldn't that be every
I have a little problem with apt-get, i think i am not doing it the
proper way.
When there is a announce that certain package has a bug, (like
gnupg v1.0.5) you can read in www.debian.org that there is a new
package to download (1.0.6-0potato1). Thats OK, but i can't download it
with my apt
Marko Kreen writes:
> On Thu, Aug 09, 2001 at 12:38:52PM -0700, Dale Southard wrote:
> > Marko Kreen writes:
> > > Well, we have basically one init script per package. Now I want
> > > state, that _nothing_ from this package gets started. Do I need
> > > examine the init script then one-by-one
On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> option "pgp_create_traditional". That option might help you very much,
> but instead I would suggest that the other MUA's get fixed.
Um, wouldn't that be every other MUA asid from mutt and maybe one or two
others?
-Rob
On Thu, Aug 09, 2001 at 12:38:52PM -0700, Dale Southard wrote:
> Marko Kreen writes:
> > Well, we have basically one init script per package. Now I want
> > state, that _nothing_ from this package gets started. Do I need
> > examine the init script then one-by-one disable all vars?
>
> Nope, yo
-. Alberto Cortés (2001-08-09) :
| I have a little problem with apt-get, i think i am not doing it the
| proper way.
|
|When there is a announce that certain package has a bug, (like
| gnupg v1.0.5) you can read in www.debian.org that there is a new
| package to download (1.0.6-0pot
Hi
On Thu, Aug 09, 2001 at 11:51:30PM +0200, Alberto Cort?s wrote:
>
> deb http://http.us.debian.org/debian stable main contrib non-free
> deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free
>
> What are the official sources if you want to have an up to date,
> se
Marko Kreen writes:
> > If the ``do I run service X'' check is done in rcS it means that each
> > init.d script is either on or off. This would eliminate the
> > possibility of having more than one check in a script -- for example,
> > it would be logical to configure the existing Debian network
I have a little problem with apt-get, i think i am not doing it the
proper way.
When there is a announce that certain package has a bug, (like
gnupg v1.0.5) you can read in www.debian.org that there is a new
package to download (1.0.6-0potato1). Thats OK, but i can't download it
with my ap
On Wed, Aug 08, 2001 at 05:17:33PM -0700, Dale Southard wrote:
> Marko Kreen writes:
> > I think this
> > is not good, it takes away flexibility. IMHO it would be better
> > if only /etc/init.d/rc (& rcS) checks whether a service should be
> > auto-started on boot. That way the responsibility is
Christian Kurz <[EMAIL PROTECTED]> writes:
> That option might help you very much, but instead I would suggest
> that the other MUA's get fixed.
I'd like to see all mailers complying with RFC2822 first.
--
Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors!
If at first you don't succeed,
On Thu, Aug 09, 2001 at 05:26:50PM +0200, Christian Kurz wrote:
> option "pgp_create_traditional". That option might help you very much,
> but instead I would suggest that the other MUA's get fixed.
Um, wouldn't that be every other MUA asid from mutt and maybe one or two
others?
-Rob
--
To U
On 01-08-09 Martin Domig wrote:
> On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
> [...]
> > : When my friends (2 differnt ones, one of which is planning to switch
> > : to mutt) get the mails, they get it in an attachment, have to save it
> > : and decode it manually (apparently kmail
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Well, this is a little kludgy, but it works. Put this in your .muttrc:
# Inline encryption
macro compose \CE "Fgpg -ea\ny"
# C
On Thu, Aug 09, 2001 at 11:55:49AM +0200, Marc Leeman wrote:
> kmail sends the gpg messages inline, and upon arrival decodes them
> immediately. In my config, mutt sends them as attachments.
> When I get a kmail message, I have to save it to file and manually
> decode it (not that difficult, but an
On Thu, Aug 09, 2001 at 06:05:38PM +0200, Viljo Marrandi wrote:
>
> Hello,
>
> I'm not sure this is aan security issue, but i could be exploitable...
> >From time to time one of my nic's just dies and in /var/log/messages i
> have stuff like this:
>
> Aug 9 16:08:59 server kernel: eth1: Oversiz
Viljo,
actually I can´t help with the error you posted.
But to complete the collection here´s an error that I see frequently on the
external interfaces of our routers.
Suspect short first fragment.
eth0 PROTO=6 213.13.177.121:0 217.29.8.82:0 L=20 S=0x00 I=63073 F=0x6000
T=102 (#0)
They do not h
Christian Kurz <[EMAIL PROTECTED]> writes:
> That option might help you very much, but instead I would suggest
> that the other MUA's get fixed.
I'd like to see all mailers complying with RFC2822 first.
--
Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors!
If at first you don't succeed
Hello,
I'm not sure this is aan security issue, but i could be exploitable...
>From time to time one of my nic's just dies and in /var/log/messages i
have stuff like this:
Aug 9 16:08:59 server kernel: eth1: Oversized Ethernet frame c7f9f460 vs
c7f9f460.
Aug 9 16:08:59 server kernel: eth1: Over
It sounds like the real fix for this is to change kmail's behavior
If none of the involved parties is willing to, I volunteer to take
it to the kmail mailing list at:
subscribe:
mailto:[EMAIL PROTECTED]
archive:
http://lists.kde.org/?l=kmail&r=1&w=2
I did notice that there is a bu
On 01-08-09 Martin Domig wrote:
> On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
> [...]
> > : When my friends (2 differnt ones, one of which is planning to switch
> > : to mutt) get the mails, they get it in an attachment, have to save it
> > : and decode it manually (apparently kmail
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
>
> I am using the same procmail filter and can say that it works
> perfectly for incoming pgp/gpg mails. However, this does not solve the
> problem with other mail clients that want to have inline PGP messages, and
> those are many.
>
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
> Is there a way to make mutt send inline PGP messages instead of the
> MIME attachment form?
Well, this is a little kludgy, but it works. Put this in your .muttrc:
# Inline encryption
macro compose \CE "Fgpg -ea\ny"
#
On Thu, Aug 09, 2001 at 11:55:49AM +0200, Marc Leeman wrote:
> kmail sends the gpg messages inline, and upon arrival decodes them
> immediately. In my config, mutt sends them as attachments.
> When I get a kmail message, I have to save it to file and manually
> decode it (not that difficult, but a
On Thu, Aug 09, 2001 at 06:05:38PM +0200, Viljo Marrandi wrote:
>
> Hello,
>
> I'm not sure this is aan security issue, but i could be exploitable...
> >From time to time one of my nic's just dies and in /var/log/messages i
> have stuff like this:
>
> Aug 9 16:08:59 server kernel: eth1: Oversi
Viljo,
actually I can´t help with the error you posted.
But to complete the collection here´s an error that I see frequently on the
external interfaces of our routers.
Suspect short first fragment.
eth0 PROTO=6 213.13.177.121:0 217.29.8.82:0 L=20 S=0x00 I=63073 F=0x6000
T=102 (#0)
They do not
Hello,
I'm not sure this is aan security issue, but i could be exploitable...
>From time to time one of my nic's just dies and in /var/log/messages i
have stuff like this:
Aug 9 16:08:59 server kernel: eth1: Oversized Ethernet frame c7f9f460 vs
c7f9f460.
Aug 9 16:08:59 server kernel: eth1: Ove
It sounds like the real fix for this is to change kmail's behavior
If none of the involved parties is willing to, I volunteer to take
it to the kmail mailing list at:
subscribe:
mailto:[EMAIL PROTECTED]
archive:
http://lists.kde.org/?l=kmail&r=1&w=2
I did notice that there is a b
Hello list
On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
[...]
> : When my friends (2 differnt ones, one of which is planning to switch
> : to mutt) get the mails, they get it in an attachment, have to save it
> : and decode it manually (apparently kmail is expecting inline messages).
On Thu, Aug 09, 2001 at 03:19:42PM +0200, Martin Domig wrote:
>
> I am using the same procmail filter and can say that it works
> perfectly for incoming pgp/gpg mails. However, this does not solve the
> problem with other mail clients that want to have inline PGP messages, and
> those are many.
Hello list
On Thu, Aug 09, 2001 at 08:03:15PM +1000, Matt Hope wrote:
[...]
> : When my friends (2 differnt ones, one of which is planning to switch
> : to mutt) get the mails, they get it in an attachment, have to save it
> : and decode it manually (apparently kmail is expecting inline messages)
On Thu, 09 Aug 2001, Marc Leeman <[EMAIL PROTECTED]> wrote...
: kmail sends the gpg messages inline, and upon arrival decodes them
: immediately. In my config, mutt sends them as attachments.
: When I get a kmail message, I have to save it to file and manually
: decode it (not that difficult, but
This is about the 4th time in as many years that I changed my e-mail client
and every time I feel I have gained.
I'm now using mutt now and am still in the process of finetuning. However,
I have the following problem, of which I didn't find a solution yet.
I am using gpg and in communication with
On Thu, 09 Aug 2001, Marc Leeman <[EMAIL PROTECTED]> wrote...
: kmail sends the gpg messages inline, and upon arrival decodes them
: immediately. In my config, mutt sends them as attachments.
: When I get a kmail message, I have to save it to file and manually
: decode it (not that difficult, but
This is about the 4th time in as many years that I changed my e-mail client
and every time I feel I have gained.
I'm now using mutt now and am still in the process of finetuning. However,
I have the following problem, of which I didn't find a solution yet.
I am using gpg and in communication with
Hello,
First, you should (keep cool and ... ;o) ) know which dns server you are
running. Look in the processes (ps -ax) if there is something like bind or
djbdns, or anything that could be a dns server. The lsof command can help
(look at what listens to port 53), as the dpkg and apt-get command
49 matches
Mail list logo
