-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/07 04:28, Chris Bannister wrote:
> On Wed, Feb 07, 2007 at 12:12:08PM -0600, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 02/07/07 11:19, Dan H. wrote:
>>> Ron Johnson wrote:
>>>
It's called the "Unsent"
On Wed, Feb 07, 2007 at 12:12:08PM -0600, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/07/07 11:19, Dan H. wrote:
> > Ron Johnson wrote:
> >
> >> It's called the "Unsent" folder.
> >
> > I know. But after I hit "Cancel" on the "Sending message" dialog (which
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/07 11:19, Dan H. wrote:
> Ron Johnson wrote:
>
>> It's called the "Unsent" folder.
>
> I know. But after I hit "Cancel" on the "Sending message" dialog (which
> had been on the screen for minutes), my messages appeared neither in
> "Sent" no
On Wed, 2007-02-07 at 10:00 -0600, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/07/07 09:49, Roberto C. Sanchez wrote:
> > On Wed, Feb 07, 2007 at 09:41:35AM -0600, Ron Johnson wrote:
> >> No. It's *all* text. SMTP *only* handles text.
> >>
> >> The function of
Ron Johnson wrote:
> It's called the "Unsent" folder.
I know. But after I hit "Cancel" on the "Sending message" dialog (which
had been on the screen for minutes), my messages appeared neither in
"Sent" nor in "Unsent", which is why I called it a "secret queue".
>> The SMTP server seems to prefer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/07 09:49, Roberto C. Sanchez wrote:
> On Wed, Feb 07, 2007 at 09:41:35AM -0600, Ron Johnson wrote:
>> No. It's *all* text. SMTP *only* handles text.
>>
>> The function of base64 (which MIME uses), uuencode and yenc is to
>> convert binary da
On Wed, Feb 07, 2007 at 09:41:35AM -0600, Ron Johnson wrote:
>
> No. It's *all* text. SMTP *only* handles text.
>
> The function of base64 (which MIME uses), uuencode and yenc is to
> convert binary data into text.
>
I know it's all text. What I was trying to say (perhaps not clearly
enough)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/07 09:06, Roberto C. Sanchez wrote:
> On Wed, Feb 07, 2007 at 08:01:24AM -0600, Ron Johnson wrote:
>> On 02/07/07 04:46, Dan H. wrote:
>>
>>> The SMTP server seems to preferentially choke on GPG signed messages.
>>> Don't know why.
>> That's "
On Wed, Feb 07, 2007 at 08:01:24AM -0600, Ron Johnson wrote:
> On 02/07/07 04:46, Dan H. wrote:
>
> > The SMTP server seems to preferentially choke on GPG signed messages.
> > Don't know why.
>
> That's "impossible". It's all text.
>
Unless it has a problem with attachments (IIRC, enigmail defa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/07 04:46, Dan H. wrote:
> Sorry for posting the same message over and over again. Thunderbird
> alias Icedove keeps complaining about not being able to send to the SMTP
> server, and I keep changing things trying to help, and of course keep
>
Thanks for the note, And I just recieved a letter about my BIOS. I did
check it, and I know they are not disabled, however, I wanted to check to
make sure the IO Ports are matching.
--Jay
At 3/19/99 07:04 AM +0100, you wrote:
>Dear Jay,
>
>I have seen this discussion on the Debian users mailingl
t;
>-Original Message-
>From: Jay Barbee [SMTP:[EMAIL PROTECTED]
>Sent: Thursday, March 18, 1999 5:12 AM
>To:Person, Roderick; debian-user@lists.debian.org
>Subject: RE: grrr, No response from modem
>
>At 3/18/99 09:35 AM -0500, Person, Roderick wrote:
>>
Jay Barbee wrote:
>
> At 3/18/99 11:28 AM +0100, Nils Rennebarth wrote:
> >ioports and interrupts look ok. What about the cable? Does it work on
> >another computer? Wiring could be wierd. Does the serial port work at all?
> >Sometimes when I assemble a computer I put the little plug on the mainbo
At 3/18/99 09:35 AM -0500, Person, Roderick wrote:
> >>> First modem is MultiTech ZDX 19.2k bps and the second is a USR
>Courier
> >>> v.everything 33.6k bps.
> >>Are they set to different settings. If they are on the same
>setting you will
> >>get
> >>nothing.
>
At 3/18/99 11:28 AM +0100, Nils Rennebarth wrote:
>ioports and interrupts look ok. What about the cable? Does it work on
>another computer? Wiring could be wierd. Does the serial port work at all?
>Sometimes when I assemble a computer I put the little plug on the mainboard
>on only half of the pins
AIL PROTECTED]
> Sent: Thursday, March 18, 1999 9:27 AM
> To: debian-user@lists.debian.org
> Subject: Re: grrr, No response from modem
>
> >At 3/17/99 07:58 PM -0800, Shanta McBain wrote:
> >>Jay Barbee wrote:
> >>> First modem is MultiTech ZDX 19.2k b
>At 3/17/99 07:58 PM -0800, Shanta McBain wrote:
>>Jay Barbee wrote:
>>> First modem is MultiTech ZDX 19.2k bps and the second is a USR Courier
>>> v.everything 33.6k bps.
>>Are they set to different settings. If they are on the same setting you will
>>get
>>nothing.
>
Hummm, are you talking about
ioports and interrupts look ok. What about the cable? Does it work on
another computer? Wiring could be wierd. Does the serial port work at all?
Sometimes when I assemble a computer I put the little plug on the mainboard
on only half of the pins, or in the wrong orientation,... It is an external
mo
Jay Barbee writes:
> Modem should be in the first serial port.
You mean /dev/ttyS0? What does setserial say about /dev/ttyS0 and
/dev/ttyS1?
> $ setserial /dev/ttyS2
> /dev/ttyS2, UART: 16550A, Port: 0x03e8, IRQ: 4
> $ setserial /dev/ttyS3
> /dev/ttyS3, UART: 16550A, Port: 0x02e8, IRQ: 3
Looks
At 3/17/99 05:53 PM +0100, Nils Rennebarth wrote:
>On Wed, Mar 17, 1999 at 11:48:39AM -0500, Jay Barbee wrote:
>> Never on tried using a modem on this debain box.
>>
>> First modem is MultiTech ZDX 19.2k bps and the second is a USR Courier
>> v.everything 33.6k bps.
>What does cat /proc/interrupts
On Wed, Mar 17, 1999 at 11:48:39AM -0500, Jay Barbee wrote:
> Never on tried using a modem on this debain box.
>
> First modem is MultiTech ZDX 19.2k bps and the second is a USR Courier
> v.everything 33.6k bps.
What does cat /proc/interrupts and cat /proc/ioports say?
Nils
--
Plug-and-Play is r
; debian-user@lists.debian.org
>> Subject: RE: grrr, No response from modem
>>
>> At 3/17/99 11:18 AM -0500, Person, Roderick wrote:
>> >In minicom you need to make your modem either:
>> > /dev/ttyS2
>> >
What kind of modems are they. Did they ever work in Debian.
> -Original Message-
> From: Jay Barbee [SMTP:[EMAIL PROTECTED]
> Sent: Wednesday, March 17, 1999 11:42 AM
> To: Person, Roderick; debian-user@lists.debian.org
> Subject: RE: grrr, No response from modem
>
At 3/17/99 11:18 AM -0500, Person, Roderick wrote:
>In minicom you need to make your modem either:
> /dev/ttyS2
>or
> /dev/ttyS3
>Depending on which modem your using.
>
>BTW, /dev/ttyS2 would be your 3rd serial
In minicom you need to make your modem either:
/dev/ttyS2
or
/dev/ttyS3
Depending on which modem your using.
BTW, /dev/ttyS2 would be your 3rd serial port, /dev/ttyS0 being the first
serial port and so on..
At 3/16/99 08:07 PM -0600, John Hasler wrote:
>Jay Barbee writes:
>
>> Mar 16 16:49:16 torch kernel: tty02 at 0x03e8 (irq = 4) is a 16550A
>> Mar 16 16:49:16 torch kernel: tty03 at 0x02e8 (irq = 3) is a 16550A
>
>> Modem should be in the first serial port. Any ideas how I can get this
>> thing to
Jay Barbee writes:
> Mar 16 16:49:16 torch kernel: tty02 at 0x03e8 (irq = 4) is a 16550A
> Mar 16 16:49:16 torch kernel: tty03 at 0x02e8 (irq = 3) is a 16550A
> Modem should be in the first serial port. Any ideas how I can get this
> thing to talk?
What do 'setserial /dev/ttyS2' and 'setserial
> From [EMAIL PROTECTED] Wed Dec 18 22:25:06 1996
>
> On Wed, 18 Dec 1996, David Lutz wrote:
>
> > of Debian Packages. I would like to know how I can fix the problem
> > however. Dselect swears that the binutils package is up-to-date and
> > refuses to attempt to reload it. Does anybody have an
David Lutz writes:
> I am upgrading my mostly Debian 1.1 system to Debian 1.2. According
> to symlinks I have these dangling links:
>
> dangling: /usr/lib/libbfd.so.2.7.0.3 -> libbfd.so.2.7.0.3.dpkg-tmp
> dangling: /usr/lib/libopcodes.so.2.7.0.3 -> libopcodes.so.2.7.0.3.dpkg-tmp
This is a hold
On Wed, 18 Dec 1996, David Lutz wrote:
> of Debian Packages. I would like to know how I can fix the problem
> however. Dselect swears that the binutils package is up-to-date and
> refuses to attempt to reload it. Does anybody have any suggestions?
Reinstalling might indeed be a good thing. Get
30 matches
Mail list logo