Benny Pedersen wrote on 4/07/16 9:47 AM:
> On 2016-07-03 23:34, Groach wrote:
>> On 03/07/2016 23:29, Reindl Harald wrote:
It turns out that this mailing list software gives me only a bigger hammer
than I wanted to use. I cannot place individuals under moderation so I can
review their posts before
Am 03.07.2016 um 23:47 schrieb Benny Pedersen:
On 2016-07-03 23:34, Groach wrote:
On 03/07/2016 23:29, Reindl Harald wrote:
sorry, but when i see Benny after 5 years experience on several
lists i just have enough, mouth wide often but technical still a
noob
http://geekologie.com/2011/08/08
On 2016-07-03 23:34, Groach wrote:
On 03/07/2016 23:29, Reindl Harald wrote:
sorry, but when i see Benny after 5 years experience on several
lists i just have enough, mouth wide often but technical still a
noob
http://geekologie.com/2011/08/08/mad-on-the-internet-cut.jpg
http://ipv6bingo.co
On 03/07/2016 23:29, Reindl Harald wrote:
sorry, but when i see Benny after 5 years experience on several lists
i just have enough, mouth wide often but technical still a noob
http://geekologie.com/2011/08/08/mad-on-the-internet-cut.jpg
Am 03.07.2016 um 23:24 schrieb Alex:
whitelist_from *@pm.sprintpcs.com
does not work.. Why?
It's because the mail has a Resent-From which overrides any other from type
header.
From the documentation Mail::SpamAssassin::Conf
"The headers checked for whitelist addresses are as follows: if Re
Hi,
whitelist_from *@pm.sprintpcs.com
does not work.. Why?
>
> It's because the mail has a Resent-From which overrides any other from type
> header.
>
> From the documentation Mail::SpamAssassin::Conf
>
> "The headers checked for whitelist addresses are as follows: if Resent-From is
On Sun, 3 Jul 2016 14:18:38 -0400
Alex wrote:
> Hi,
>
> >>> since they are fucking too stupid for SPF on their subdomains
> >>> whitelist_from_rcvd *@pm.sprint.com sprintpcs.com
> >>
> >> all headers begin with x- is pr defination forged header
> >>
>
> > when there is no SPF/DKIM you need t
On 03/07/2016 22:43, Sidney Markowitz wrote:
whitelist_from *@pm.sprintpcs.com
does not work.. Why?
It's because the mail has a Resent-From which overrides any other from type
header.
From the documentation Mail::SpamAssassin::Conf
"The headers checked for whitelist addresses are as follow
Alex wrote on 4/07/16 6:48 AM:
> Hi,
>
> On Sun, Jul 3, 2016 at 2:29 PM, Benny Pedersen wrote:
>> On 2016-07-03 20:18, Alex wrote:
>>
>>> whitelist_from *@pm.sprintpcs.com
>>>
>>> does not work.. Why?
It's because the mail has a Resent-From which overrides any other from type
header.
>From the
Am 03.07.2016 um 20:36 schrieb Benny Pedersen:
On 2016-07-03 20:26, Reindl Harald wrote:
Envelope-Sender
Resent-Sender
X-Envelope-From
From
please tell me what mta add this headers as envelope_sender header ?
obviously enough otherwise it would no exist
ma
Hi,
On Sun, Jul 3, 2016 at 2:29 PM, Benny Pedersen wrote:
> On 2016-07-03 20:18, Alex wrote:
>
>> whitelist_from *@pm.sprintpcs.com
>>
>> does not work.. Why?
>
> DSN is not possible to whitelist, its a rfc to accept always DSN
Strictly speaking, it was a quarantined message, not a DSN.
I also
On 2016-07-03 20:26, Reindl Harald wrote:
Envelope-Sender
Resent-Sender
X-Envelope-From
From
please tell me what mta add this headers as envelope_sender header ?
maybe you after that could tell who is idiot ?
On 2016-07-03 20:18, Alex wrote:
whitelist_from *@pm.sprintpcs.com
does not work.. Why?
DSN is not possible to whitelist, its a rfc to accept always DSN
Return-Path: <>
whats envelope_sender_header have you in local.cf ?
Am 03.07.2016 um 20:23 schrieb Benny Pedersen:
On 2016-07-03 20:16, Reindl Harald wrote:
when there is no SPF/DKIM you need to rely on headers
keep away from using x- headers for whitelist still
its forged
again you are an idiot and should RTFM before play smart-ass
http://spamassassin.
Am 03.07.2016 um 20:21 schrieb Benny Pedersen:
On 2016-07-03 20:17, Reindl Harald wrote:
what about shut up?
...
the subdomain has no SPF and so there is not much than headers
since the subdomain has no SPF there is no SPF test at all
its irelevaant
you are an idiot
"pm.sprint.com" ha
Am 03.07.2016 um 20:18 schrieb Alex:
Hi,
since they are fucking too stupid for SPF on their subdomains
whitelist_from_rcvd *@pm.sprint.com sprintpcs.com
all headers begin with x- is pr defination forged header
when there is no SPF/DKIM you need to rely on headers
omg, both of you guys
On 2016-07-03 20:16, Reindl Harald wrote:
when there is no SPF/DKIM you need to rely on headers
keep away from using x- headers for whitelist still
its forged
On 2016-07-03 20:17, Reindl Harald wrote:
what about shut up?
...
the subdomain has no SPF and so there is not much than headers
since the subdomain has no SPF there is no SPF test at all
its irelevaant
Hi,
>>> since they are fucking too stupid for SPF on their subdomains
>>> whitelist_from_rcvd *@pm.sprint.com sprintpcs.com
>>
>> all headers begin with x- is pr defination forged header
>>
> when there is no SPF/DKIM you need to rely on headers
omg, both of you guys. I didn't say anything about
Am 03.07.2016 um 20:15 schrieb Benny Pedersen:
On 2016-07-03 19:54, Alex wrote:
As I mentioned, all attempts to whitelist are ignored. I just don't
know why.
do not use x- headers for spf testing in spamassassin since its pr
defination forged
what about shut up?
the subdomain has no SPF
On 2016-07-03 19:54, Alex wrote:
As I mentioned, all attempts to whitelist are ignored. I just don't
know why.
do not use x- headers for spf testing in spamassassin since its pr
defination forged
Am 03.07.2016 um 20:14 schrieb Benny Pedersen:
On 2016-07-03 19:46, Reindl Harald wrote:
X-Envelope-From: <15556142...@pm.sprint.com>
From: 5556142...@pm.sprint.com
since they are fucking too stupid for SPF on their subdomains
whitelist_from_rcvd *@pm.sprint.com sprintpcs.com
all headers
On 2016-07-03 19:46, Reindl Harald wrote:
X-Envelope-From: <15556142...@pm.sprint.com>
From: 5556142...@pm.sprint.com
since they are fucking too stupid for SPF on their subdomains
whitelist_from_rcvd *@pm.sprint.com sprintpcs.com
all headers begin with x- is pr defination forged header
pay
Hi,
>>> whitelist_from_rcvd *@pm.sprint.com sprintpcs.com
>>
>>
>> As I mentioned, all attempts to whitelist are ignored. I just don't know
>> why
>
> you did not properly mention your attempts
> the above works, i have a long list of "whitelist_from_rcvd" for idiots too
> stupid for SPF or DKIM w
Am 03.07.2016 um 19:54 schrieb Alex:
Received: from lxnsmsomta04.localdomain (smtp4a.mo.sprintpcs.com
[66.1.208.13])
by mail01.example.com (Postfix) with ESMTP id 7FF846800CC30
for ; Sat, 25 Jun 2016 21:21:21 -0400 (EDT)
Received: from musreb31.nmcc.sprintspectrum.com (unknown [10.25.15
Hi,
>> Received: from lxnsmsomta04.localdomain (smtp4a.mo.sprintpcs.com
>> [66.1.208.13])
>> by mail01.example.com (Postfix) with ESMTP id 7FF846800CC30
>> for ; Sat, 25 Jun 2016 21:21:21 -0400 (EDT)
>> Received: from musreb31.nmcc.sprintspectrum.com (unknown [10.25.157.71])
>> by lxns
Am 03.07.2016 um 19:43 schrieb Alex:
I'm trying to whitelist mail from sprintpcs.com in the best way
possible, but it's ignoring attempts at even using whitelist_from and
I don't know why. Perhaps it's something with the way the mail is
formatted? No SPF or DKIM available to be used.
These mess
Hi,
I'm trying to whitelist mail from sprintpcs.com in the best way
possible, but it's ignoring attempts at even using whitelist_from and
I don't know why. Perhaps it's something with the way the mail is
formatted? No SPF or DKIM available to be used.
These messages are being quarantined because
28 matches
Mail list logo
