On 2017-01-25 17:49, Daniel J. Luke wrote:
> On Jan 25, 2017, at 9:41 AM, Rainer Müller wrote:
>> Before being handed off to mailman, postfix already adds an
>> Approved header with the corresponding list post password to the mail.
>> This is apparently not enough to circumvent/pass the spam filte
On 2017-01-26 02:40, Joshua Root wrote:
> On 2017-1-26 01:41 , Rainer Müller wrote:
>> Your message was held for moderation because SpamAssassin gave the
>> message a score of 6.2 for the following reasons:
>>
>> HEADER_FROM_DIFFERENT_DOMAINS, HEADER_SPAM, HTML_MESSAGE,
>> HTML_MIME_NO_HTML_TAG, MI
On 2017-1-26 01:41 , Rainer Müller wrote:
Your message was held for moderation because SpamAssassin gave the
message a score of 6.2 for the following reasons:
HEADER_FROM_DIFFERENT_DOMAINS, HEADER_SPAM, HTML_MESSAGE,
HTML_MIME_NO_HTML_TAG, MIME_HTML_ONLY, NO_RELAYS, TO_NO_BRKTS_HTML_ONLY,
URIBL_
On Jan 25, 2017, at 9:41 AM, Rainer Müller wrote:
> Your message was held for moderation because SpamAssassin gave the
> message a score of 6.2 for the following reasons:
>
> HEADER_FROM_DIFFERENT_DOMAINS,
0.001 0.001 0.001 0.001
> HEADER_SPAM,
2.499 2.499 1.994 0.585
> HTML_MESSAGE,
0.001
On 2017-01-25 13:50, John Patrick wrote:
> I'm getting these emails too for pull requests I created that have
> been approved.
>
> Is someone able to whitelist github sending emails to the
> macport-changes list...
Sorry for the inconvenience, these mails are certainly not intended to
go out to y
I'm getting these emails too for pull requests I created that have
been approved.
Is someone able to whitelist github sending emails to the
macport-changes list...
John
On 25 January 2017 at 09:26, Ivan Larionov wrote:
> I started to get the same emails for every pull request opened by me when
I started to get the same emails for every pull request opened by me when
someone merges it.
On Wed, Jan 25, 2017 at 1:23 AM, Zero King wrote:
> On 1/25/17 7:50 AM, macports-changes-ow...@lists.macports.org wrote:
>
>> Your mail to 'macports-changes' with the subject
>>
>> [macports-ports]
On 1/25/17 7:50 AM, macports-changes-ow...@lists.macports.org wrote:
Your mail to 'macports-changes' with the subject
[macports-ports] branch master updated: miredo: adopt and update
to 1.2.6
Is being held until the list moderator can review it for approval.
The reason it is being held:
> On Dec 2, 2016, at 7:55 AM, Rainer Müller wrote:
>
> HTML was a request for the new commit mails. I was not able to find
> anything better than git-multimail [3], but it only supports either text
> or HTML. Unfortunately, It does not support sending both as MIME
> multi-part alternatives as th
On 2016-12-02 14:55, Rainer Müller wrote:
> Yes, this is a problem on our end, probably occurring since I deployed
> the From: addresses [1] after the discussion in [2].
>
> After this, some mails were rejected by mailman, which we only
> discovered a few days ago. To avoid losing any change mails
On 2016-12-03 08:53, Mojca Miklavec wrote:
> On 2 December 2016 at 14:55, Rainer Müller wrote:
>> On 2016-12-02 12:28, Mojca Miklavec wrote:
>>
>>> But there might be some issues. Looking at a random commit email:
>>>
>>> https://lists.macports.org/pipermail/macports-changes/2016-December/14472
On 2 December 2016 at 14:55, Rainer Müller wrote:
> On 2016-12-02 12:28, Mojca Miklavec wrote:
>
>> But there might be some issues. Looking at a random commit email:
>>
>> https://lists.macports.org/pipermail/macports-changes/2016-December/144725.html
>> saying
>>An HTML attachment was scru
On 2016-12-02 12:28, Mojca Miklavec wrote:
> On 2 December 2016 at 12:13, Zero King wrote:
>> I didn't write to that list, my commit was merged into master and so I've
>> got this mail.
>
> In that case it's a problem with our scripts or mailman configuration
> and Rainer should be able to answer
On 2 December 2016 at 12:13, Zero King wrote:
> I didn't write to that list, my commit was merged into master and so I've
> got this mail.
In that case it's a problem with our scripts or mailman configuration
and Rainer should be able to answer you.
I guess that the idea was to use the committer
he first place? Isn't
the discussion about changes usually done on this (= developer)
mailing list?
Mojca
Forwarded Message ----
Subject: Your message to macports-changes awaits moderator approval
Date: Fri, 02 Dec 2016 11:50:39 +0100
From: macports-changes-ow...@lists.macports.org
T
ed Message ----
> Subject: Your message to macports-changes awaits moderator approval
> Date: Fri, 02 Dec 2016 11:50:39 +0100
> From: macports-changes-ow...@lists.macports.org
> To: l...@icloud.com
>
>
> Your mail to 'macports-changes' with the subject
>
&g
I don't want to receive such mail but would prefer not to subscribe to
the macports-changes list either. What should I do?
Forwarded Message
Subject: Your message to macports-changes awaits moderator approval
Date: Fri, 02 Dec 2016 11:50:39 +0100
From: mac
17 matches
Mail list logo
