On Tuesday 03 January 2006 17:30, mouss wrote: >Gene Heskett a écrit : >> ------------- >> From [EMAIL PROTECTED] Sat Dec 31 23:16:57 2005 >> Return-Path: <[EMAIL PROTECTED]> >> Received: from localhost (localhost.localdomain [127.0.0.1]) >> by coyote.coyote.den (8.12.11/8.12.10) with ESMTP id >> k014Gv7g021793 >> for <[EMAIL PROTECTED]>; Sat, 31 Dec 2005 23:16:57 -0500 > >so this is the "after fetchmail" header > >> Received: from incoming.verizon.net [206.46.232.10] >> by localhost with POP3 (fetchmail-6.2.5.5) >> for [EMAIL PROTECTED] (single-drop); Sat, 31 Dec 2005 23:16:57 >> -0500 (EST) > >and this is the fetchmail header. > >- you should add 206.46.232.10 to your trusted_networks >- SA will recognize this as a fetchmail hop, and will "reinitialize" > its received parsing (This is my understanding, but I may be wrong. > But this is what I understand from -D output). > Yes, I put it into local.cf as 206.46.232/24 and I believe it has helped. Time will tell & its only been about 20 hrs so far, during which I built and rebooted to 2.6.15.
>> ------------ >> which is not the same message, and therefore a waste of bandwidth I >> think. > >what do you mean? > >> Too bad the /var/spool/mail/gene files contents are so ephemeral. > >what do you mean? -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
