On 2018-10-16 15:40, Graeme Fowler via Exim-users wrote:
> > I agreed that systemd should allow exim to work on current rules. But I
> > don know how can I argue to Lennart Poettering to change his mind.
>
> You can't :)
>
> What you've shown us is (in my opinion) an incredibly niche case which
On 2018-10-15, Brent Clark via Exim-users wrote:
> Good day Guys
>
> I would just like to double check something with the community.
>
> I would like to ask, how do you guys handle outgoing SPAM queue?
We have one of the early routers check for a flag agaisnt the user-id that
sent the mail
On 16/10/2018 20:42, Jasen Betts via Exim-users wrote:
> We have one of the early routers check for a flag agaisnt the user-id that
> sent the mail (condition=${lookup...}), when something bad happens
> we set the flag and exim delivers all that user-id's mail to >/dev/null
In similar vein, one
On 16/10/2018 21:58, Christian K via Exim-users wrote:
> What about freezing all or the messages in question to pick them apart
> and thaw every "good" mail?
That works, though it doesn't scale quite so well.
--
Cheers,
Jeremy
--
## List details at
What about freezing all or the messages in question to pick them apart
and thaw every "good" mail?
Am Di., 16. Okt. 2018 um 22:44 Uhr schrieb Jeremy Harris via
Exim-users :
>
> On 16/10/2018 20:42, Jasen Betts via Exim-users wrote:
> > We have one of the early routers check for a flag agaisnt the
On 2018-10-16, Christian K via Exim-users wrote:
> What about freezing all or the messages in question to pick them apart
> and thaw every "good" mail?
Usually we have a few thousand emails from the bad account in the
queue, and a few thousand from good users and some of them are
locked by
Jeremy Harris via Exim-users writes:
[..]
> It does seem somewhat... arrogant of systemd to assume that
> when a process it has started terminates, any of its children
Ahem. :)
https://github.com/systemd/systemd/issues/10299
KJ
--
http://wolnelektury.pl/wesprzyj/teraz/
P-K4
--
## List
On 16/10/2018 12:44, Kamil Jońca via Exim-users wrote:
> Jeremy Harris via Exim-users writes:
>
> [..]
>> It does seem somewhat... arrogant of systemd to assume that
>> when a process it has started terminates, any of its children
> Ahem. :)
>
> https://github.com/systemd/systemd/issues/10299
On 15/10/2018 11:59, Brent Clark via Exim-users wrote:
> The problem is, when Exim is stopped, then other clients app that need
> to send mail, cant.
>
> The question I would like to ask is, what is the correct way to manage
> mail in the queue, or if someone can give a suggestion, of removing
On 16 Oct 2018, at 14:56, Kamil Jońca via Exim-users
wrote:
> I do not know if it is clear: this is not my words, neither I agreed
> with them (please note, that I opened this issue on github.)
...and you have a workaround in systemd via the KillMode switch, or the various
timeout options. Or
Jeremy Harris via Exim-users writes:
> On 16/10/2018 12:44, Kamil Jońca via Exim-users wrote:
>> Jeremy Harris via Exim-users writes:
>>
>> [..]
>>> It does seem somewhat... arrogant of systemd to assume that
>>> when a process it has started terminates, any of its children
>> Ahem. :)
>>
>>
Good day Guys
I would just like to double check something with the community.
I would like to ask, how do you guys handle outgoing SPAM queue?
So what happens is, we may have a client that runs a website (shared
hosting), and say it gets compromised (not the server itself), just the app.
On Tue, 16 Oct 2018 at 17:12, Brent Clark via Exim-users <
exim-users@exim.org> wrote:
> Good day Guys
>
> I would just like to double check something with the community.
>
> I would like to ask, how do you guys handle outgoing SPAM queue?
>
> So what happens is, we may have a client that runs a
13 matches
Mail list logo
