Re: Tracking down a mail forwarding loop

2015-02-12 Thread Noel Jones
On 2/12/2015 12:43 AM, LuKreme wrote: On Feb 11, 2015, at 6:20 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Received: from thenewestsecret.net (unknown [170.130.246.215]) by mail.covisp.net (Postfix) with ESMTP id 00E42212DC0 for *bob*@covisp.net; Tue, 10 Feb 2015

Re: Tracking down a mail forwarding loop

2015-02-12 Thread LuKreme
On 12 Feb 2015, at 08:25 , Noel Jones njo...@megan.vbhcs.org wrote: On 2/12/2015 12:43 AM, LuKreme wrote: On Feb 11, 2015, at 6:20 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Received: from thenewestsecret.net (unknown [170.130.246.215]) by mail.covisp.net (Postfix) with

Re: Tracking down a mail forwarding loop

2015-02-11 Thread Wietse Venema
LuKreme: Received: from thenewestsecret.net (unknown [170.130.246.215]) by mail.covisp.net (Postfix) with ESMTP id 00E42212DC0 for *bob*@covisp.net; Tue, 10 Feb 2015 08:53:22 -0700 (MST) Delivered-To: *bob*@covisp.net Received: by 170.130.246.215 with SMTP id

Re: Tracking down a mail forwarding loop

2015-02-11 Thread LuKreme
On Feb 11, 2015, at 6:20 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Received: from thenewestsecret.net (unknown [170.130.246.215]) by mail.covisp.net (Postfix) with ESMTP id 00E42212DC0 for *bob*@covisp.net; Tue, 10 Feb 2015 08:53:22 -0700 (MST) Delivered-To:

Re: Tracking down a mail forwarding loop

2015-02-07 Thread LuKreme
On Feb 6, 2015, at 3:43 PM, LuKreme krem...@kreme.com wrote: On 06 Feb 2015, at 15:05 , Wietse Venema wie...@porcupine.org wrote: NORMALLY, that header is present AFTER mail is delivered to b...@covisp.net. If it is present BEFORE mail is delivered to b...@covisp.net, then you have a loop

Re: Tracking down a mail forwarding loop

2015-02-06 Thread Wietse Venema
LuKreme: On 05 Feb 2015, at 15:53 , Wietse Venema wie...@porcupine.org wrote: LuKreme: On 05 Feb 2015, at 05:07 , Wietse Venema wie...@porcupine.org wrote: Have you considered the possibility that the mail was sent with a bogus Delivered-To: header (i.e. the header is present, but

Re: Tracking down a mail forwarding loop

2015-02-06 Thread LuKreme
On 06 Feb 2015, at 15:05 , Wietse Venema wie...@porcupine.org wrote: NORMALLY, that header is present AFTER mail is delivered to b...@covisp.net. If it is present BEFORE mail is delivered to b...@covisp.net, then you have a loop (or the sender has added this header to trigger an error). Ah,

Re: Tracking down a mail forwarding loop

2015-02-06 Thread LuKreme
Only other thing I can think of is that this is somehow related to always_bcc? -- A dyslexic walks into a bra...

Re: Tracking down a mail forwarding loop

2015-02-06 Thread Miles Fidelman
wie...@porcupine.org (Wietse Venema) wrote: LuKreme: On 05 Feb 2015, at 05:07 , Wietse Venema wie...@porcupine.org wrote: Have you considered the possibility that the mail was sent with a bogus Delivered-To: header (i.e. the header is present, but not added by Postfix). Yes, but I'm unsure

Re: Tracking down a mail forwarding loop

2015-02-05 Thread Wietse Venema
LuKreme: On 05 Feb 2015, at 05:07 , Wietse Venema wie...@porcupine.org wrote: Have you considered the possibility that the mail was sent with a bogus Delivered-To: header (i.e. the header is present, but not added by Postfix). Yes, but I'm unsure how to diagnose that. header_checks:

Re: Tracking down a mail forwarding loop

2015-02-05 Thread LuKreme
On 05 Feb 2015, at 05:07 , Wietse Venema wie...@porcupine.org wrote: Have you considered the possibility that the mail was sent with a bogus Delivered-To: header (i.e. the header is present, but not added by Postfix). Yes, but I’m unsure how to diagnose that. Here is a full dump of one of

Re: Tracking down a mail forwarding loop

2015-02-05 Thread Wietse Venema
LuKreme: On Feb 4, 2015, at 9:20 AM, Miles Fidelman mfidel...@meetinghouse.net wrote: LuKreme wrote: I have a local user who is generating occasional mail forwarding loop errors, which are causing forged emails to cause NDNs and fill up mailq. Jan 30 13:46:08 mail

Re: Tracking down a mail forwarding loop

2015-02-04 Thread Miles Fidelman
LuKreme wrote: I have a local user who is generating occasional mail forwarding loop errors, which are causing forged emails to cause NDNs and fill up mailq. Jan 30 13:46:08 mail postfix/local[44147]: 7020950D4D4: to=*bob*@covisp.net, relay=local, delay=0.65, delays=0.59/0/0/0.06, dsn=5.4.6,

Tracking down a mail forwarding loop

2015-02-04 Thread LuKreme
I have a local user who is generating occasional mail forwarding loop errors, which are causing forged emails to cause NDNs and fill up mailq. Jan 30 13:46:08 mail postfix/local[44147]: 7020950D4D4: to=*bob*@covisp.net, relay=local, delay=0.65, delays=0.59/0/0/0.06, dsn=5.4.6, status=bounced

Re: Tracking down a mail forwarding loop

2015-02-04 Thread Wietse Venema
LuKreme: I have a local user who is generating occasional mail forwarding loop errors, which are causing forged emails to cause NDNs and fill up mailq. Jan 30 13:46:08 mail postfix/local[44147]: 7020950D4D4: to=*bob*@covisp.net, relay=local, delay=0.65, delays=0.59/0/0/0.06, dsn=5.4.6,

Re: Tracking down a mail forwarding loop

2015-02-04 Thread LuKreme
On 04 Feb 2015, at 07:38 , Wietse Venema wie...@porcupine.org wrote: LuKreme: I have a local user who is generating occasional mail forwarding loop errors, which are causing forged emails to cause NDNs and fill up mailq. Jan 30 13:46:08 mail postfix/local[44147]: 7020950D4D4: