Displaying 20 results from an estimated 107 matches for "hopps".
Did you mean:
hopes
2018 Apr 20
5
Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
Hi (Stephan?),
is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of
a redirected mail or simply a bug ?
A sends mail to B, B redirects to C
C sees B (not A!) as envelope sender.
It is not a problem if C gets the mail but if that mail bounces
for various reasons it goes back to B and A will never know about this.
I thick this is came
2020 Apr 04
2
replication and spam removal ("doveadm expunge")
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Can you provide doveconf -n and try turning on mail_debug=yes on both ends and try doveadm -Dv expunge ....
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote type="cite">
<div>
2020 Mar 30
2
replication and spam removal ("doveadm expunge")
Hello everybody,
since now I did no replication and spam is delivered into users folder "spambox"
Every night there is a cronjob which deletes spam older than 30 days via something like
"find .... -ctime +30 -delete"
Now I'm going to set up replication (two way) and I thought that
doing "rm" is not a good idea.
So I modified the job to something like
2018 Apr 20
2
Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
OK, I found a solution:
trusted_users = exim:dovecot
in my exim.conf fixed it.
Anyway this is an important change of behavour between 2.2 und 2.3
In 2.2 the "dovecot" under exims "trusted_users" was not necessary.
Olaf
On 04/20/2018 02:53 PM, Olaf Hopp wrote:
> On 04/20/2018 02:01 PM, Olaf Hopp wrote:
>> Hi (Stephan?),
>> is it a new feature of dovecot 2.3
2018 Apr 23
2
Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
On 04/23/2018 03:22 PM, Stephan Bosch wrote:
>
>
> Op 20-4-2018 om 14:01 schreef Olaf Hopp:
>> Hi (Stephan?),
>> is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of
>> a redirected mail or simply a bug ?
>>
>> A sends mail to B, B redirects to C
>> C sees B (not A!) as envelope sender.
2018 May 09
2
lmtp panic with many recipients
On 05/09/2018 11:10 AM, Stephan Bosch wrote:
>
>
> Op 09/05/2018 om 10:17 schreef Ralf Hildebrandt:
>> * Stephan Bosch <stephan at rename-it.nl>:
>>>
>>> Op 08/05/2018 om 10:34 schreef Olaf Hopp:
>>>> Hi,
>>>>
>>>> I had an email with 58 recipients in the "To" and 13 in the "CC"
>>>>
2015 Jul 01
4
dovecot-lmtp
...'m running Debian
Wheezy. I've got runit configured to execute postfix and dovecot, which
may be the source of the problem (runit executes /usr/sbin/dovecot -F).
I've got mail_debug turned on and there is nothing in the mail log about
lmtp.
Any help would be appreciated.
--
Steven Hopps || shopps at pridetechdesign.com
424-888-0443 || http://www.pridetechdesign.com
= Ask about my Security Tune-Up & 24/7 Server Monitoring! =
2017 Jul 26
1
under another kind of attack
Olaf Hopp <Olaf.Hopp at kit.edu> wrote:
> And I have a new one just for "unknown user" and here my bantime and findtime
> are much bigger and the retries are just '2'. So here I'm much harsher.
> I'll keep an eye on my logs and maybe some more twaeking is necessary.
Just be careful about typos (like twaeking!): users could simply misspell
their username,
2015 Dec 18
2
autoexpunge problems
Hello,
I tried to use the new autoexpunge for my Trash folders
I had in 15-mailboxes.conf
mailbox Trash {
special_use = \Trash
auto = subscribe
}
(dovecot -n of the original config is below)
and added just the line
autoexpunge = 1h
Just a short period on my test system.
But it failed. In the log I see
Dec 18 10:54:07 irams2 dovecot: imap(ms2test): Error: Failed to autoexpunge
2009 May 20
2
zfs raidz questions
Hi there,
i''m building a small NAS with 5x1TB Disks. The disks contains at the moment some data, ntfs as the fs and aren''t a raid.
Now my im wondering if its possible to add the parity later. So that i add step by step one disk to the pool. And when i add the last disk, i enable the parity.
(i have only one another 1 tb disk to backup the files)
Thank you for you replies and
2010 Feb 07
2
predicting with stl() decomposition
Hi mailinglist members,
I’m actually working on a time series prediction and my current approach is
to decompose the series first into a trend, a seasonal component and a
remainder. Therefore I’m using the stl() function. But I’m wondering how to
get the single components in order to predict the particular fitted series’.
This code snippet illustrates my problem:
series <-
2017 Jun 06
3
v2.2.30.1 released
On 06/05/2017 11:05 AM, Angel L. Mateo wrote:
> I have updated my dovecot proxy servers from 2.2.28 to 2.2.30. Since the upgrade I'm having the error:
>
> Jun 5 10:54:51 musio12 dovecot: auth: Fatal: master: service(auth): child 63632 killed with signal 11 (core not dumped)
>
>
Me too, with
# 2.2.30.1 (eebd877): /opt/dovecot/etc/dovecot/dovecot.conf
# Pigeonhole
2015 Mar 12
2
Why is Sieve trying to re-compile global scripts?
On 3/12/2015 11:56 AM, Olaf Hopp wrote:
> On 03/12/2015 12:02 AM, Stephan Bosch wrote:
>> On 3/11/2015 11:10 AM, Olaf Hopp wrote:
>>> Please see the thread with subject
>>> "Sieve permissions issue following update"
>>> I tested sucessfully a developper issue last month
>>> on the hint of Stephan. Yesterday I started to test the currenr RCs.
2017 Jul 27
1
under another kind of attack
> On 26 Jul 2017, at 7:57 pm, Olaf Hopp <Olaf.Hopp at kit.edu> wrote:
>
> Dear collegues,
>
> many thanks for your valuable input.
>
> Since we are an university GEO-IP blocking is not an option for us.
> Somestimes I think it should ;-)
>
> My "mistake" was that I had just *one* fail2ban filter for both cases:
> "wrong password" and
2018 Apr 21
1
Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
On 4/20/2018 8:53 AM, Olaf Hopp wrote:
> On 04/20/2018 02:01 PM, Olaf Hopp wrote:
>> Hi (Stephan?),
>> is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of
>> a redirected mail or simply a bug ?
>>
>> A sends mail to B, B redirects to C
>> C sees B (not A!) as envelope sender.
>> It is not a
2020 Apr 06
0
replication and spam removal ("doveadm expunge")
Hi Aki,
On 4/4/20 8:12 PM, Aki Tuomi wrote:
> Can you provide doveconf -n and try turning on mail_debug=yes on both ends and try doveadm -Dv expunge ....
mail_debug=yes
is on on both ends and dovecot was restarted but anyway nothing is logged when I issue "doveadm -Dv expunge "
In the shell where I issue the "expunge" I see the following:
# /usr/bin/doveadm -Dv expunge
2018 May 09
2
lmtp panic with many recipients
* Stephan Bosch <stephan at rename-it.nl>:
>
>
> Op 08/05/2018 om 10:34 schreef Olaf Hopp:
> > Hi,
> >
> > I had an email with 58 recipients in the "To" and 13 in the "CC"
> > Delivering it from exim to dovecot lmtp panics (see below)
> > Panic: file smtp-address.c: line 533 (smtp_address_write): assertion
> > failed:
2005 Aug 25
4
Sipura spa-2000 / 3000: surge protection
I am located in the UK, and I am using Sipura spa-2000 adapters to
connect analog phones to a voip network. The network connects to the
PSTN as well via the Sipura spa-3000 adapter.
I would like to provide surge protection for the spa-2000 and the
spa-3000 adapters.
1. For spa-2000, fxs port: What is the maximum tip-to-ring voltage
before damage to the the adapter occurs?
2. For spa-2000,
2004 Sep 13
2
Problem with mle in stats4 (R 1.9.1)
Hi!
This is a repost of an earlier message (with a clearer example
demonstrating the problem I ran into). If you run the mle example in
stats4
library(stats4)
x <- 0:10
y <- c(26, 17, 13, 12, 20, 5, 9, 8, 5, 4, 8)
ll <- function(ymax=15, xhalf=6)
-sum(stats::dpois(y, lambda=ymax/(1+x/xhalf), log=TRUE))
(fit <- mle(ll))
plot(profile(fit),
2015 Mar 11
4
Why is Sieve trying to re-compile global scripts?
On 3/11/2015 11:10 AM, Olaf Hopp wrote:
> Please see the thread with subject
> "Sieve permissions issue following update"
> I tested sucessfully a developper issue last month
> on the hint of Stephan. Yesterday I started to test the currenr RCs.
>
> First I was disappointed, because the error seems to persist.
> So I double checked everything, recreated / recompiled