On 12 Feb 2015, at 08:25 , Noel Jones wrote:
> On 2/12/2015 12:43 AM, LuKreme wrote:
>>
>>> On Feb 11, 2015, at 6:20 PM, Wietse Venema wrote:
>>>
>>> LuKreme:
Received: from thenewestsecret.net (unknown [170.130.246.215])
by mail.covisp.net (Postfix) with ESMTP id 00E42212DC0
>>
On 2/12/2015 12:43 AM, LuKreme wrote:
>
>> On Feb 11, 2015, at 6:20 PM, Wietse Venema 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:5
> On Feb 11, 2015, at 6:20 PM, Wietse Venema 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: *bob*@covis
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
> 998S7h4.
On Feb 6, 2015, at 3:43 PM, LuKreme wrote:
> On 06 Feb 2015, at 15:05 , Wietse Venema 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 h
On 06 Feb 2015, at 15:05 , Wietse Venema 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, right. I’ve added
LuKreme:
>
> > On 05 Feb 2015, at 15:53 , Wietse Venema wrote:
> >
> > LuKreme:
> >> On 05 Feb 2015, at 05:07 , Wietse Venema 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 Postf
Only other thing I can think of is that this is somehow related to always_bcc?
--
A dyslexic walks into a bra...
> On 05 Feb 2015, at 15:53 , Wietse Venema wrote:
>
> LuKreme:
>> On 05 Feb 2015, at 05:07 , Wietse Venema 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
wie...@porcupine.org (Wietse Venema) wrote:
LuKreme:
On 05 Feb 2015, at 05:07 , Wietse Venema 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.
LuKreme:
> On 05 Feb 2015, at 05:07 , Wietse Venema 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:
/^Delivered-To:
On 05 Feb 2015, at 05:07 , Wietse Venema 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 these files (with onl
LuKreme:
>
> > On Feb 4, 2015, at 9:20 AM, Miles Fidelman
> > 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 postfix/local[441
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,
On 04 Feb 2015, at 07:38 , Wietse Venema 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:
>> to=<*bob*@covisp.ne
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
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 (
17 matches
Mail list logo
