Bug#1012178: linux-image-5.17.0-3-amd64: cp210x driver problem

2022-05-31 Thread Michael Fischer
Package: src:linux
Version: 5.17.11-1
Severity: normal
X-Debbugs-Cc: mich...@webfischer.at

Dear Maintainer,

On trying to upload a program to an ESP32 attached via USB and a CP2102 USB to 
UART Bridge Controller the kernel log shows 
[  488.007479] usb 3-4: USB disconnect, device number 8
[  488.007697] cp210x ttyUSB0: failed set request 0x7 status: -19
[  488.007707] cp210x ttyUSB0: failed set request 0x12 status: -19
[  488.007710] cp210x ttyUSB0: failed set request 0x0 status: -19
[  488.007956] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[  488.007977] cp210x 3-4:1.0: device disconnected
and the esptool reports "OSError: [Errno 5] Input/output error"

May be related to 
https://lore.kernel.org/all/ymg+be220%2fsz4...@hovoldconsulting.com/t/

Greetings, MF

-- Package-specific info:
** Version:
Linux version 5.17.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.3.0-3) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 
5.17.11-1 (2022-05-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.17.0-3-amd64 
root=UUID=d547ee7b-d9f6-4996-9623-d67611b3f5f4 ro quiet

** Tainted: O (4096)
 * externally-built ("out-of-tree") module was loaded

** Kernel log:
[5.246128] Bluetooth: hci0: Waiting for firmware download to complete
[5.246657] Bluetooth: hci0: Firmware loaded in 1314757 usecs
[5.246822] Bluetooth: hci0: Waiting for device to boot
[5.274686] Bluetooth: hci0: Device booted in 27340 usecs
[5.274964] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-0041-0041.ddc
[5.274970] Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-0041-0041.ddc
[5.276592] Bluetooth: hci0: Applying Intel DDC parameters completed
[5.279721] Bluetooth: hci0: Firmware timestamp 2021.28 buildtype 1 build 
28502
[5.355772] NET: Registered PF_ALG protocol family
[5.384693] Bluetooth: RFCOMM TTY layer initialized
[5.384704] Bluetooth: RFCOMM socket layer initialized
[5.384711] Bluetooth: RFCOMM ver 1.11
[7.189564] wlp170s0: authenticate with 8a:2a:a8:87:18:1d
[7.189576] wlp170s0: bad VHT capabilities, disabling VHT
[7.189576] wlp170s0: 80 MHz not supported, disabling VHT
[7.196879] wlp170s0: send auth to 8a:2a:a8:87:18:1d (try 1/3)
[7.230888] wlp170s0: authenticated
[7.237804] wlp170s0: associate with 8a:2a:a8:87:18:1d (try 1/3)
[7.243564] wlp170s0: RX AssocResp from 8a:2a:a8:87:18:1d (capab=0x1431 
status=0 aid=12)
[7.260642] wlp170s0: associated
[7.435026] iwlwifi :aa:00.0: Unhandled alg: 0x707
[7.646790] IPv6: ADDRCONF(NETDEV_CHANGE): wlp170s0: link becomes ready
[8.570287] usb 3-9: reset full-speed USB device number 3 using xhci_hcd
[   10.293568] rfkill: input handler enabled
[   41.687387] usb 3-4: new full-speed USB device number 5 using xhci_hcd
[   41.940838] usb 3-4: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
[   41.940847] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   41.940850] usb 3-4: Product: CP2102 USB to UART Bridge Controller
[   41.940853] usb 3-4: Manufacturer: Silicon Labs
[   41.940856] usb 3-4: SerialNumber: 0001
[   41.978878] usbcore: registered new interface driver usbserial_generic
[   41.978892] usbserial: USB Serial support registered for generic
[   41.981532] usbcore: registered new interface driver cp210x
[   41.981549] usbserial: USB Serial support registered for cp210x
[   41.981570] cp210x 3-4:1.0: cp210x converter detected
[   41.982442] usb 3-4: cp210x converter now attached to ttyUSB0
[  156.658868] usb 3-4: USB disconnect, device number 5
[  156.659095] cp210x ttyUSB0: failed set request 0x7 status: -19
[  156.659104] cp210x ttyUSB0: failed set request 0x12 status: -19
[  156.659107] cp210x ttyUSB0: failed set request 0x0 status: -19
[  156.659344] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[  156.659383] cp210x 3-4:1.0: device disconnected
[  157.239531] usb 3-4: new full-speed USB device number 6 using xhci_hcd
[  157.487166] usb 3-4: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
[  157.487175] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  157.487178] usb 3-4: Product: CP2102 USB to UART Bridge Controller
[  157.487180] usb 3-4: Manufacturer: Silicon Labs
[  157.487182] usb 3-4: SerialNumber: 0001
[  157.497177] cp210x 3-4:1.0: cp210x converter detected
[  157.498094] usb 3-4: cp210x converter now attached to ttyUSB0
[  446.854106] usb 3-9: reset full-speed USB device number 3 using xhci_hcd
[  447.150142] usb 3-9: reset full-speed USB device number 3 using xhci_hcd
[  465.610619] usb 3-4: USB disconnect, device number 6
[  465.611043] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[  465.611081] cp210x 3-4:1.0: device disconnected
[  468.329897] usb 3-4: new full-speed USB device number 7 using xhci_hcd
[  468.579428] usb 3-4: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
[  

Bug#991797: the distributed ssh_config

2021-08-02 Thread Frank-Michael Fischer

looks like this:

*# Site-wide defaults for some commonly used options. * For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

#Include /etc/ssh/ssh_config.d/*.conf

Host *
#   ForwardAgent no
#   ForwardX11 no
#   ForwardX11Trusted yes
#   PasswordAuthentication yes
#   HostbasedAuthentication no
#   GSSAPIAuthentication no
#   GSSAPIDelegateCredentials no
#   GSSAPIKeyExchange no
#   GSSAPITrustDNS no
#   BatchMode no
#   CheckHostIP yes
#   AddressFamily any
#   ConnectTimeout 0
#   StrictHostKeyChecking ask
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa
#   IdentityFile ~/.ssh/id_ecdsa
#   IdentityFile ~/.ssh/id_ed25519
#   Port 22
#   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc
#   MACs hmac-md5,hmac-sha1,umac...@openssh.com
#   EscapeChar ~
#   Tunnel no
#   TunnelDevice any:any
#   PermitLocalCommand no
#   VisualHostKey no
#   ProxyCommand ssh -q -W %h:%p gateway.example.com
#   RekeyLimit 1G 1h
*#   UserKnownHostsFile ~/.ssh/known_hosts.d/%k*
    SendEnv LANG LC_*
    HashKnownHosts yes
    GSSAPIAuthentication yes

And without changing this default ssh looks into the non-existing 
directory *~/.ssh/known_hosts.d/%k!*


There is another bug in the default settings:

Without adding "hmac-sha2-256" this way "MACs 
hmac-md5,hmac-sha1,hmac-sha2-256,umac...@openssh.com" ssh does not 
connect to any of my own sshd servers on Debian 10, Ubuntu 18.04 and 
20.04 and Oracle Linux 8. This change I have to make for this 
openssh-client on Debian 11 only.


This bug needs to be reopened.

FMF
**



Bug#991797: openssh-client: UserKnownHostsFile default wrong

2021-08-01 Thread Frank-Michael Fischer

Package: openssh-client
Version: 1:8.4p1-5
Severity: important

Dear Maintainer,

The default setting of UserKnownHostsFile has changed in this version to:

~/.ssh/known_hosts.d/%k

But existing former versions have placed it in:

~/.ssh/known_hosts

This renders ssh connections impossible, unless I change it back to the 
former default by adding to ssh_config:


UserKnownHostsFile ~/.ssh/known_hosts ~/.ssh/known_hosts2

Regards,

FMF

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.20.9
ii  libc6 2.31-13
ii  libedit2  3.1-20191231-2+b1
ii  libfido2-1    1.6.0-2
ii  libgssapi-krb5-2  1.18.3-6
ii  libselinux1   3.1-3
ii  libssl1.1 1.1.1k-1
ii  passwd    1:4.8.1-1
ii  zlib1g    1:1.2.11.dfsg-2

Versions of packages openssh-client recommends:
ii  xauth  1:1.1-1

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh    
pn  monkeysphere  
pn  ssh-askpass   

-- Configuration Files:
/etc/ssh/ssh_config changed:
Include /etc/ssh/ssh_config.d/*.conf
Host *
UserKnownHostsFile ~/.ssh/known_hosts ~/.ssh/known_hosts2
    SendEnv LANG LC_*
    HashKnownHosts yes
    GSSAPIAuthentication yes


-- no debconf information



Bug#920957: workaround

2019-01-31 Thread Frank-Michael Fischer
The workaround for this display disturbing issue: unplug the USB mouse
while working in the command line console, plug it back  in when using
X. 

Regards, 

Michael

Bug#920957: linux-image-4.9.0-8-amd64: USB HID devices disconnect and reregister frequently - correction

2019-01-31 Thread Frank-Michael Fischer
After more testing here is my correction and additional info: 

* The issue shows with 4.19.0-0.bpo.1-amd64, too, just less often.
* With 4.19.0-0.bpo.1-amd64 it shows only when using command line.
Using keyboard and mouse with X produces no disconnects. Using a console
under X (CTRL-ALT-F1), however, gives me frequent disconnects again.
Annoying, because the disconnect messages pop up in the middle of text I
am keying into the console.
* With 4.19.0-0.bpo.1-amd64 the disconnect happens with mouse only,
never with the keyboard in use.

Regards, 

Michael

kern.log.gz
Description: GNU Zip compressed data


Bug#920957: linux-image-4.9.0-8-amd64: USB HID devices disconnect and reregister frequently

2019-01-31 Thread Frank-Michael Fischer
Yes, the issue remains with kernel version 4.9.144-2. 

Regards, 

FMF

Am 2019-01-30 23:35, schrieb Salvatore Bonaccorso:

> Hi Michael,
> 
> On Wed, Jan 30, 2019 at 11:02:30PM +0100, Michael Fischer wrote: 
> 
>> Package: src:linux
>> Version: 4.9.130-2
>> Severity: important
>> Tags: upstream
>> 
>> Dear Maintainer,
>> 
>> Having USB keyboard and/or USB mouse connected leads to the problem.
>> Same is true on three other systems, running 686-pae or 686 with the
>> same kernel version Installing linux-image-4.19.0-0.bpo.1-amd64
>> fixes the problem reliably. Also in case of 686 or 686-pae kernels
> 
> Can you confirm, does the issue still persist as well with the
> 4.9.144-2 version currently pending in proposed-updates (and to be
> included in the next point release)?
> 
> Regards,
> Salvatore

Bug#920957: linux-image-4.9.0-8-amd64: USB HID devices disconnect and reregister frequently

2019-01-30 Thread Michael Fischer
Package: src:linux
Version: 4.9.130-2
Severity: important
Tags: upstream

Dear Maintainer,

Having USB keyboard and/or USB mouse connected leads to the problem. Same is 
true on three other
systems, running 686-pae or 686 with the same kernel version
Installing linux-image-4.19.0-0.bpo.1-amd64 fixes the problem reliably. Also in 
case of 686 or
686-pae kernels


-- Package-specific info:
** Version:
Linux version 4.9.0-8-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.130-2 (2018-10-27)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-8-amd64 
root=UUID=746870cc-290f-4be3-aafa-d2749b200e8c ro bootdegraded=true

** Not tainted

** Kernel log:
[   12.970272] Bluetooth: HCI socket layer initialized
[   12.970340] Bluetooth: L2CAP socket layer initialized
[   12.970418] Bluetooth: SCO socket layer initialized
[   13.230396] Bluetooth: HCI UART driver ver 2.3
[   13.230471] Bluetooth: HCI UART protocol H4 registered
[   13.230537] Bluetooth: HCI UART protocol BCSP registered
[   13.230603] Bluetooth: HCI UART protocol LL registered
[   13.230668] Bluetooth: HCI UART protocol ATH3K registered
[   13.230794] Bluetooth: HCI UART protocol Intel registered
[   13.230900] Bluetooth: HCI UART protocol Broadcom registered
[   13.230968] Bluetooth: HCI UART protocol QCA registered
[   13.231033] Bluetooth: HCI UART protocol AG6XX registered
[   13.231099] Bluetooth: HCI UART protocol Marvell registered
[   13.259352] input: PC Speaker as /devices/platform/pcspkr/input/input9
[   13.451167] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   13.766482] [drm] Initialized
[   13.922180] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   13.922359] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   13.922534] sd 2:0:0:0: Attached scsi generic sg2 type 0
[   13.922702] sd 3:0:0:0: Attached scsi generic sg3 type 0
[   13.922877] sd 4:0:0:0: Attached scsi generic sg4 type 0
[   14.261987] [drm] Memory usable by graphics device = 2048M
[   14.262057] [drm] Replacing VGA console driver
[   14.262954] Console: switching to colour dummy device 80x25
[   14.263138] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   14.263146] [drm] Driver supports precise vblank timestamp query.
[   14.263664] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   14.383212] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[   14.383797] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
[   14.383981] snd_hda_intel :00:1b.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   14.384009] [drm] Initialized i915 1.6.0 20160919 for :00:02.0 on minor 0
[   14.498431] fbcon: inteldrmfb (fb0) is primary device
[   14.538301] Console: switching to colour frame buffer device 240x67
[   14.552978] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC892: 
line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[   14.552983] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   14.552987] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[   14.552990] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   14.552993] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   14.552995] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   14.553000] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[   14.553004] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[   14.553007] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[   14.567320] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   14.843919] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[   14.846110] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[   14.846217] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input13
[   14.846321] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card0/input14
[   14.846426] input: HDA Intel PCH Line Out Front as 
/devices/pci:00/:00:1b.0/sound/card0/input15
[   14.846531] input: HDA Intel PCH Line Out Surround as 
/devices/pci:00/:00:1b.0/sound/card0/input16
[   14.846638] input: HDA Intel PCH Line Out CLFE as 
/devices/pci:00/:00:1b.0/sound/card0/input17
[   14.846743] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input18
[   14.846849] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input19
[   14.846954] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1b.0/sound/card0/input20
[   16.346676] iTCO_vendor_support: vendor-support=0
[   16.435556] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   16.435742] iTCO_wdt: Found a Bay Trail SoC TCO device (Version=3, 
TCOBASE=0x0460)
[   16.436144] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   16.600133] 

Bug#770252: crond should use Auto-Submitted header in outbound mail

2014-11-19 Thread Michael Fischer v. Mollard
Package: cron
Version: 3.0pl1-127
Severity: wishlist

Dear Maintainer,

it would be nice if debian crond would set the Auto-Submitted header as
suggested in RFC 3834.
For the (rather trivial) patch see
https://bugzilla.redhat.com/show_bug.cgi?id=203746



-- Package-specific info:
--- EDITOR:


--- /usr/bin/editor:
/bin/nano

--- /usr/bin/crontab:
-rwxr-sr-x 1 root crontab 36008 2014-10-26 00:04 /usr/bin/crontab

--- /var/spool/cron:
drwxr-xr-x 5 root root 4096 2012-04-30 22:58 /var/spool/cron

--- /var/spool/cron/crontabs:
drwx-wx--T 2 root crontab 4096 2010-12-19 01:36 /var/spool/cron/crontabs

--- /etc/cron.d:
drwxr-xr-x 2 root root 4096 2014-11-09 12:32 /etc/cron.d

--- /etc/cron.daily:
drwxr-xr-x 2 root root 4096 2014-11-20 01:37 /etc/cron.daily

--- /etc/cron.hourly:
drwxr-xr-x 2 root root 4096 2014-11-09 12:32 /etc/cron.hourly

--- /etc/cron.monthly:
drwxr-xr-x 2 root root 4096 2014-11-09 12:32 /etc/cron.monthly

--- /etc/cron.weekly:
drwxr-xr-x 2 root root 4096 2014-11-09 17:26 /etc/cron.weekly


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cron depends on:
ii  adduser  3.113+nmu3
ii  debianutils  4.4+b1
ii  dpkg 1.17.21
ii  init-system-helpers  1.21
ii  libc62.19-13
ii  libpam-runtime   1.1.8-3.1
ii  libpam0g 1.1.8-3.1
ii  libselinux1  2.3-2
ii  lsb-base 4.1+Debian13+nmu1

Versions of packages cron recommends:
ii  exim4-daemon-heavy [mail-transport-agent]  4.84-3

Versions of packages cron suggests:
ii  anacron2.3-22
pn  checksecurity  none
ii  logrotate  3.8.7-1+b1

Versions of packages cron is related to:
pn  libnss-ldap   none
pn  libnss-ldapd  none
pn  libpam-ldap   none
pn  libpam-mount  none
pn  nis   none
pn  nscd  none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#741546: PAM misconfiguration for auditd results in audit trail loss

2014-03-13 Thread Michael Fischer
Package: auditd
Version: 1:1.7.18-1.1

The auditd package included in Debian Wheezy and Ubuntu 12.04 LTS (and
probably other Debian and Ubuntu releases as well) adds pam_loginuid.so to
the /etc/pam.d/common-session and /etc/pam.d/common-session-noninteractive
PAM sub-configuration files.  These sub-configuration files are in turn
included by reference in the /etc/pam.d/su and /etc/pam.d/sudo files.  This
results in pam_loginuid.so being included when the user context is switched
by running su or sudo.

The man page for pam_loginuid, however, warns us not to do that, as this
will cause the original user context to be lost in the audit logs (emphasis
mine):

The pam_loginuid module sets the loginuid process attribute for the
 process that was authenticated. This is necessary for applications to
be correctly audited. This PAM module should only be used for entry
 point applications like: login, sshd, gdm, vsftpd, crond and atd. There
are probably other entry point applications besides these.
 *You should not use it for applications like sudo or su as that defeats
 the**   purpose by changing the loginuid to the account they just
 switched to.*


The fix, of course, is never to add pam_loginuid.so to any common PAM
configuration file - or to exclude common-session and
common-session-noninteractive from /etc/pam.d/su and /etc/pam.d/sudo,
replacing it with the respective files' constituent lines, but without
pam_loginuid.so.


Bug#351500: See also #384221

2006-08-25 Thread Michael Fischer v. Mollard
The latest report seems to be about bug #384221. I've observed this bug, 
too. Simple (but slow) solution for spamassassin is to use 
Mail::SpamAssassin::BayesStore::SQL instead of 
Mail::SpamAssassin::BayesStore::MySQL


Michael


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#369888: First letter of From/To/Subject header is case sensitive

2006-06-01 Thread Michael Fischer v. Mollard

Package: vacation
Version: 3.3.0
Severity: normal
Tags: Patch

the current version of vaction needs an upper case first letter in mail 
headers. Although this is common practice there are rare examples of 
mails with all lowercase header field names. vacation won't recognize a 
'to:' header and won't answer the mail.


Solution is simple: Just add the lowercase case in the switch statement, 
as the function use strncasecomp anyway (not for 'From', why?):


# diff -c vacation.c.orig vacation.c
*** vacation.c.orig 2006-06-02 00:16:18.0 +0200
--- vacation.c  2006-06-02 00:26:14.0 +0200
***
*** 301,306 
--- 301,307 
cont = tome = 0;
while (fgets(buf, sizeof(buf), stdin)  *buf != '\n')
switch(*buf) {
+   case 'f':
case 'F':   /* From  */
cont = 0;
if (!strncmp(buf, From , 5)) {
***
*** 313,318 
--- 314,320 
discard_exit();
}
break;
+   case 'r':
case 'R':   /* Return-Path: */
/* EvB: this may use Name 
[EMAIL PROTECTED] */

cont = 0;
***
*** 328,333 
--- 330,336 
if (junkmail())
discard_exit();
break;
+   case 'p':
case 'P':   /* Precedence: */
cont = 0;
if (strncasecmp(buf, Precedence, 10) ||
***
*** 344,349 
--- 347,353 
!strncasecmp(p, list, 4))
discard_exit();
break;
+   case 's':
case 'S':   /* Subject */
cont = 0;
if (strncasecmp(buf, Subject:, 8) ||
***
*** 354,364 
--- 358,370 
if ((p = strchr(subj, '\n')))
*p = '\0';
break;
+   case 'c':
case 'C':   /* Cc: */
if (strncasecmp(buf, Cc:, 3))
break;
cont = 1;
goto findme;
+   case 't':
case 'T':   /* To: */
if (strncasecmp(buf, To:, 3))
break;



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]