Hi,
That’s interesting. Is it a script that can be called from the command line? If
so, maybe Exim could call it directly, instead of using an LMTP callout.
On 20 Mar 2014, at 17:10, Jim Popovitch jim...@gmail.com wrote:
On Thu, Mar 20, 2014 at 9:17 AM, Ian Eiloart i...@sussex.ac.uk wrote:
On Tue, Mar 25, 2014 at 12:34 PM, Ian Eiloart i...@sussex.ac.uk wrote:
Hi,
That's interesting. Is it a script that can be called from the command line?
It is exactly a script that is called from the command line. Postfix
spawn service listens on an IP and spawns a process, and returns the
On Mar 20, 2014, at 01:17 PM, Ian Eiloart wrote:
For me, the big win for spam prevention with mailing lists is the restriction
on posters: it’s what keeps mailing lists relatively spam free. Most sites
don’t like to bounce messages that they’ve previously accepted, so that means
that the spam
On 18 Mar 2014, at 19:12, Barry Warsaw ba...@list.org wrote:
I see this was a private reply. Feel free to forward this on to the list if
you want.
Thanks, Barry. I’ll have a go at that if I get time.
For me, the big win for spam prevention with mailing lists is the restriction
on posters:
On Thu, Mar 20, 2014 at 9:17 AM, Ian Eiloart i...@sussex.ac.uk wrote:
For me, the big win for spam prevention with mailing lists is the restriction
on posters: it's what keeps mailing lists relatively spam free. Most sites
don't like to bounce messages that they've previously accepted, so
On Thu, Mar 20, 2014 at 1:10 PM, Jim Popovitch jim...@gmail.com wrote:
On Thu, Mar 20, 2014 at 9:17 AM, Ian Eiloart i...@sussex.ac.uk wrote:
For me, the big win for spam prevention with mailing lists is the
restriction on posters: it's what keeps mailing lists relatively spam free.
Most
On Mar 17, 2014, at 02:34 PM, Stephen J. Turnbull wrote:
I don't understand what you're trying to say here. Are you saying
that rules should not have a rules_to_run_before_this_rule field,
but it's OK if a chain rule_B, rule_A is buggy because rule_A should
be run before rule_B? Of course we
Barry Warsaw writes:
I feel quite strongly that rules should be self-contained and
unordered, with ordering imposed by the chain of links that rules
are associated with.
I don't understand what you're trying to say here. Are you saying
that rules should not have a
On Mar 13, 2014, at 05:06 PM, Stephen J. Turnbull wrote:
I expressed myself poorly. The parameters of the decision logic given
the list of senders are different for the two rules so both rules are
needed. But I really think that determining the sender should be done
in one place by one set of
Barry Warsaw writes:
I'm having a hard time right now seeing how we could continue to
support these types of operations with a combined member and
non-member rule.
I expressed myself poorly. The parameters of the decision logic given
the list of senders are different for the two rules so
OK, I've opened a bug on Launchpad to attach my very basic
implementation (plus a unit test). It's just 3 lines, it does not
implement Stephen's suggestion (which is probably better but involves
some refactoring). Here is the ticket:
https://bugs.launchpad.net/mailman/+bug/1291452
I've tested it
On Mar 12, 2014, at 01:43 PM, Stephen J. Turnbull wrote:
Offhand I'd say that having both a Member rule and a NonMember rule is
a bad idea. There should be one conceptual test: can we identify a
member as the originator of this post? Having Member and NonMember
rules that can both succeed is
Hey!
I'd like to discuss what happens when an email is sent by both a
member and a nonmember in Mailman3. How is that possible? Very easy,
here's my use case : I have my own domain, say example.com, and for
convenience and portability I choose to use Gmail as a
server/storage/interface. My main
On Mar 11, 2014, at 06:25 PM, Aurelien Bompard wrote:
What do you think about all that? Do you agree there's actually an
issue there? Any idea how to solve it? For example, make the NonMember
rule exit if a member is found amongst the senders (which would simply
be equivalent to making it yield
On 03/11/2014 03:14 PM, Barry Warsaw wrote:
On Mar 11, 2014, at 06:25 PM, Aurelien Bompard wrote:
What do you think about all that? Do you agree there's actually an
issue there? Any idea how to solve it? For example, make the NonMember
rule exit if a member is found amongst the senders
Aurelien Bompard writes:
I'd like to discuss what happens when an email is sent by both a
member and a nonmember in Mailman3. How is that possible? Very easy,
here's my use case : I have my own domain, say example.com, and for
convenience and portability I choose to use Gmail as a
16 matches
Mail list logo
