It seems that the local delivery (pickup?) uses the content filter which
it shouldn't, AFAIK.
If that is the case, the following master.cf configuration taken from my
installation may help:
-- snip ---
ip:smtpinet n - n - - smtpd
-o
Pete:
I'm currently working on getting policyd rate limiting, and outbound spam
filtering put together, hopefully by the end of the week, but in the mean time
I'm hoping there is a way to limit sending auth sessions to a time limit to
help stop the bleeding.
In the past weeks I added support for a filter that can not only
change hard delivery errors into soft errors and vice versa, but
that can also change the (per recipient) explanatory text in
non-delivery notifications.
I'm thinking about making a minor change to enable text replacement
for
I have an application that sends and receives email. I don't want to have
it process bounces, though, so I'd like its dedicated Postfix relay to
forward all mailer-daemon messages to me rather than to the application.
In other words, I'd like to create a table that maps From or sender
addresses
Am 19.03.2014 15:19, schrieb Drew Mazurek:
I have an application that sends and receives email. I don't want to have it
process bounces, though, so I'd like
its dedicated Postfix relay to forward all mailer-daemon messages to me
rather than to the application. In other
words, I'd like to
Yeah, I know, but for reasons I can't get into here, that's not an option.
I need to handle this at the MTA.
- Drew
On Wed, Mar 19, 2014 at 10:24 AM, li...@rhsoft.net li...@rhsoft.net wrote:
Am 19.03.2014 15:19, schrieb Drew Mazurek:
I have an application that sends and receives email. I
Drew Mazurek:
I have an application that sends and receives email. I don't want to have
it process bounces, though, so I'd like its dedicated Postfix relay to
forward all mailer-daemon messages to me rather than to the application.
Bounces are sent to the envelope sender address. On the
Rewriting the envelope sender address at the first hop out of the
application seems to work best. Next question: is it possible to log what
the address was before it gets rewritten? Our mail.log now shows the new
bounce address, but for debugging purposes, it'd be nice to know what the
address
just don't switch to top-posting in the middle of a thread
Am 19.03.2014 19:57, schrieb Drew Mazurek:
Rewriting the envelope sender address at the first hop out of the application
seems to work best. Next question:
is it possible to log what the address was before it gets rewritten? Our
Drew Mazurek:
Mar 19 14:54:42 hostname postfix/cleanup[2873]: E7540258C6: message-id=[
message...@example.com]
Mar 19 14:54:42 hostname postfix/qmgr[1836]: E7540258C6: from=
exam...@example.com, size=4054, nrcpt=1 (queue active)
If you want to rewrite the sender of outbound mail, you could
I set up postfix + dovecot and know that I want to have mailing lists I
decided to install mailman.
Everything is working except that I cannot send emails to my mailing
list (and this is quite important, don't you think?).
When I'm sending a mail to my mailing list (t...@too.gy), I get a
Am 19.03.2014 20:08, schrieb Tout Guy:
I set up postfix + dovecot and know that I want to have mailing lists I
decided to install mailman.
Everything is working except that I cannot send emails to my mailing list
(and this is quite important, don't you
think?).
When I'm sending a
On Wed, Mar 19, 2014 at 3:03 PM, li...@rhsoft.net li...@rhsoft.net wrote:
just don't switch to top-posting in the middle of a thread
Am 19.03.2014 19:57, schrieb Drew Mazurek:
Rewriting the envelope sender address at the first hop out of the
application seems to work best. Next question:
I'm looking through the docs of sendmail, seeing how I can get it to
send to a specific port. But not seeing it.
Am I looking in the wrong place?
-tim
On 3/19/14, Lewin Bormann der.mess...@yahoo.com wrote:
It seems that the local delivery (pickup?) uses the content filter which
it shouldn't,
as lonf you are talking about pickup there is no port
involved at all and no smtp/smtpd setting is relevant
because it's just not SMTP
Am 19.03.2014 20:49, schrieb Tim Prepscius:
I'm looking through the docs of sendmail, seeing how I can get it to
send to a specific port. But not seeing it.
My aliases were generated using the genealiases tool given by mailman.
Plus, in my configuration, I have:
alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases
(my mailman aliases are located in /var/lib/mailman/data/aliases)
Here is a cat:
# This file is generated by
On 3/19/2014 2:36 PM, Wietse Venema wrote:
Drew Mazurek:
Mar 19 14:54:42 hostname postfix/cleanup[2873]: E7540258C6: message-id=[
message...@example.com]
Mar 19 14:54:42 hostname postfix/qmgr[1836]: E7540258C6: from=
exam...@example.com, size=4054, nrcpt=1 (queue active)
If you want to
so let's say I wanted to do what Lewin said,
have normal mail on 25, and then special non filtered mail (mail that
has already gone through the filter) on some other port, let's say
10025
At the end of the example filter script there is a sendmail command.
Is there anyway to have this work with
Am 19.03.2014 20:59, schrieb Tim Prepscius:
so let's say I wanted to do what Lewin said,
have normal mail on 25, and then special non filtered mail (mail that
has already gone through the filter) on some other port, let's say
10025
then you just configure that listener and avoid asking
Noel Jones:
On 3/19/2014 2:36 PM, Wietse Venema wrote:
Drew Mazurek:
Mar 19 14:54:42 hostname postfix/cleanup[2873]: E7540258C6: message-id=[
message...@example.com]
Mar 19 14:54:42 hostname postfix/qmgr[1836]: E7540258C6: from=
exam...@example.com, size=4054, nrcpt=1 (queue active)
Ok I will describe my goal:
There is a server.
On it runs postfix.
All mail is sent via localhost (or 127.0.0.1).
Meaning, I run a command and mail is sent, nobody is connecting from
outside and sending.
I need to save to a custom DB the mail after any headers are
changed/added by postfix.
So
SMTPD_POLICY_README says:
The sasl_* attributes (Postfix 2.2 and later) specify information about
how the client was authenticated via SASL. These attributes are empty in
case of no SASL authentication.
I read that as:
- I will know when SASL AUTH was successful
- I will know when SASL
On Wed, Mar 19, 2014 at 10:06:38PM +0100, Patrick Ben Koetter wrote:
Would it be technically feasible to transmit the following states too?
- SASL login attempted to use a non-permitted envelope-sender
This is only detected when one of reject_sender_login_mismatch
and friends fails,
Patrick Ben Koetter:
SMTPD_POLICY_README says:
The sasl_* attributes (Postfix 2.2 and later) specify information about
how the client was authenticated via SASL. These attributes are empty in
case of no SASL authentication.
I read that as:
- I will know when SASL AUTH was
* Wietse Venema postfix-users@postfix.org:
Patrick Ben Koetter:
SMTPD_POLICY_README says:
The sasl_* attributes (Postfix 2.2 and later) specify information about
how the client was authenticated via SASL. These attributes are empty in
case of no SASL authentication.
I read
On Wed, Mar 19, 2014 at 11:20:57PM +0100, Patrick Ben Koetter wrote:
My primary goal would be to detect SASL login attacks/abuse and block the
client/temporarily disable the account. Catching envelope-sender abuse is
less important to me.
All this should take place without tailing the log.
Wietse Venema:
Patrick Ben Koetter:
My primary goal would be to detect SASL login attacks/abuse and block the
client/temporarily disable the account. Catching envelope-sender abuse is
less important to me.
There is no way to find out about login failure, unless the client
sends HELO,
On 3/19/2014 3:26 PM, Tim Prepscius wrote:
Ok I will describe my goal:
There is a server.
On it runs postfix.
All mail is sent via localhost (or 127.0.0.1).
Meaning, I run a command and mail is sent, nobody is connecting from
outside and sending.
If the mail is injected locally via
So the other billperrotta account I tried to delete is where I posted the
issue I need help with.
--
View this message in context:
http://postfix.1071664.n5.nabble.com/My-other-email-is-blacklisted-for-some-reason-tp66188.html
Sent from the Postfix Users mailing list archive at Nabble.com.
I'm currently working on getting policyd rate limiting, and outbound spam
filtering put together, hopefully by the end of the week, but in the mean
time
I'm hoping there is a way to limit sending auth sessions to a time limit to
help stop the bleeding.
I was suggested to replace
local_recipient_maps = $virtual_mailbox_maps
to
local_recipient_maps = $virtual_mailbox_maps $alias_maps
I did but it' still not working...
Any suggestion?
31 matches
Mail list logo
