Displaying 6 results from an estimated 6 matches for "wursti".
Did you mean:
wurst
2014 Jun 09
2
Subject tag is gone
I've actually been thinking about it almost since the beginning. It's just been annoying waste of space on my screen. And more importantly nowadays it's also breaking DKIM/DMARC signatures. So if somebody still uses Subject-based filtering it's about time to switch to List-ID header based filtering now.
Another thing I'm wondering about is if I should allow text/html parts,
2017 Dec 14
2
sieve filter move wrong email to Junk folder
....org
=====End of header=======
=======Maillog=========
Dec 14 02:54:51 mail postfix/postscreen[19236]: CONNECT from
[94.237.32.243]:40818 to [10.11.22.68]:25
Dec 14 02:54:52 mail postfix/postscreen[19236]: PASS OLD
[94.237.32.243]:40818
Dec 14 02:54:52 mail postfix/smtpd[19244]: connect from
wursti.dovecot.fi[94.237.32.243]
Dec 14 02:54:52 mail policyd-spf[19248]: None; identity=helo;
client-ip=94.237.32.243; helo=mail.dovecot.fi;
envelope-from=dovecot-bounces at dovecot.org; receiver=gao at pztop.com
Dec 14 02:54:52 mail policyd-spf[19248]: None; identity=mailfrom;
client-ip=94.237.32.243...
2019 Feb 09
2
offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]
...3
Hello Aki,
before updating to mailman3 consider an simpler update to latest mailman2.
you're using 2.1.15, current mailman2 is 2.1.29
Your missing an /significant amount/ of DMARC fixes!
and: more off-topic:
while my messages *to* the dovecot list are sent using STARTTLS,
messages *from* wursti.dovecot.fi are sent without encryption.
any reason to stay on unencrypted SMTP?
Andreas
2014 Mar 05
3
Still no emails since Feb. 6
I checked my settings on the dovecot mailman page, and although my
account was set to "disable" email, after changing it and attempting to
have the list resend my password, I'm still not seeing emails.
The last time I received emails, the outgoing server for the list was
sent from the IP 193.210.130.67. Is that still correct?
I've checked my logs to see if there's
2017 Aug 24
3
dmarc report faild ?
...ease i have new following Error, from DMARC Report, if i check my domain
on example mxtoolbox i dont see any problems.
Any from you know this Eror report, what i need to do to fix this issue?
C:\folder>nslookup 94.237.32.243
Server: dns204.data.ch
Address: 211.232.23.124
Name: wursti.dovecot.fi
Address: 94.237.32.243
--
I check also dkim and spif but i don't see the mistake, i dont want that me
Mailserver become seriussly mail problems.
Regards
Mauri
<?xml version="1.0" encoding="UTF-8" ?>...
2019 Feb 09
8
offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]
On 09/02/2019 10:44, Aki Tuomi via dovecot wrote:
> For some reason mailman failed to "munge from" for senders with dmarc policy ;(
>
> It's now configured to always munge to avoid this again.
I'd say, let Mailman throw all people off the list that have enabled DMARC
checking without using exceptions for the lists they are on. It's a known
fact that DMARC does not