comes in over the list.
HTH!
--
Heiko Wundram
hackerkey://v4sw7CHJLSUY$hw5ln5pr7FOP$ck2ma9u7FL$w3DVWXm0l7GL$i65e6t3EMRSXb7ADORen5a26s5MSr2p-6.62/-6.56g5AORZ
f our suppliers,
who doesn't seem to be able to unsubscribe us from his mailings. For the
latter, you could use a Header-Check inside the
smtpd_end_of_data_restrictions from Postfix.
Those would be at least two _sensible_ routes to try, I'd say.
* http://spambayes.sourceforge.net/
--
Heiko
Hey all!
As the title says: is there a possibility to set different
smtpd_sasl_security_options depending on the connecting IP (or rather
subnet) of the client that tries to do authentication?
I've looked at the access maps documentation of postfix, but can't see
how that relates to setting
Am 06.09.2011 11:24, schrieb Patrick Ben Koetter:
* Heiko Wundram:
As the title says: is there a possibility to set different
smtpd_sasl_security_options depending on the connecting IP (or
rather subnet) of the client that tries to do authentication?
No, you can't. Which problem ar
Am 06.09.2011 12:29, schrieb Patrick Ben Koetter:
You can offer a different SASL policy on a different port on the Postfix
server side.
Clone the "smtp ... smtpd" service line and configure it to listen on a
different port e.g. 2525. Then add "-o
smtpd_sasl_security_options=noanonymous" and let
Am 06.09.2011 13:42, schrieb Noel Jones:
Or use firewall rules to redirect connections from that client to a
different port with different smtpd_sasl_security_options.
Thanks, after an off-list reply suggesting just that I tried that out,
and that works like a charm. Adding the client to mynet
Am 07.09.2011 19:06, schrieb Jeroen Geilman:
On 2011-09-06 13:58, Heiko Wundram wrote:
Am 06.09.2011 13:42, schrieb Noel Jones:
Or use firewall rules to redirect connections from that client to a
different port with different smtpd_sasl_security_options.
Thanks, after an off-list reply
Hey!
I'm currently working up a patch for Postfix which implements support
for libsrs2 functionality in the Postfix core.
I've gotten to some "design" decisions I'm currently somewhat...
undecided about:
1) Rewriting the recipient
Basically, rewriting the recipient (in case of a valid SRS
Am 21.10.2011 16:52, schrieb Jack Fredrikson:
That error appears to come from a file called
/etc/postfix/mysql_virtual_alias_maps.cf that has this line:
SELECT goto FROM alias WHERE address = ‘%s’ AND active = 1
Therefore, the address has question marks in it. Looks like a hacker, no?
No, the
Am 23.10.2011 19:13, schrieb Jack Fredrikson:
I may be dreaming, but this could be my last problem with my installation.
After following all your good advice, I still have this one problem and it is
pervasive in all emails:
Oct 23 09:50:58 myserver postfix/pipe[30578]: BB2BB5790262: to=,
rela
Hey!
My searching through the Postfix documentation didn't turn up anything
relevant, so I thought I'd ask on the list: which parameter(s) control
whether (and if possible: how many/more than one?) warning messages are
sent in the case that a mail can't be delivered for a specified amount
of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 20.08.2013 11:48, schrieb Sebastian Wiesinger:
> This error ONLY occurs with their servers. My question is if
> anyone has an idea what could cause this error. My first guess is
> that they check certificates for validity and I only have an CACert
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 20.08.2013 12:12, schrieb Sebastian Wiesinger:
> * Heiko Wundram [2013-08-20 12:09]:
>> Still delivers fine for me (and my mail-server) running Postfix
>> 2.10.1:
>>
>> Received: from mout.web.de (mout.web.de [212.22
hem as SPAM and then do server/client-side
filtering. From what you tell, the amount of SPAM that gets through is so
miminal (25 messages a day for I guess quite a lot of users), that explicitly
moving them to a spam folder for the user to decide what to do should be a
perfectly acceptable polic
d as such
the order in the input file does not matter at all, as the keys are reordered
anyway when creating the map.
--
Heiko Wundram
hackerkey://v4sw7CHJLSUY$hw5ln5pr7FOP$ck2ma9u7FL$w3DVWXm0l7GL$i65e6t3EMRSXb7ADORen5a26s5MSr2p-6.62/-6.56g5AORZ
15 matches
Mail list logo
