On 16-3-2012 14:18, Viktor Dukhovni wrote:
/^X-Mailing-List:/REDIRECT some@address
DO NOT do this. If a particular recipient wants his list traffic left
a local mailbox, and the rest forwarded, that's up the to user's
LDA, say procmail(1), or similar. This must not be done at the
message lev
I am routing all mail for a domain to another SMTP server using the
transport map rule
adomain.comrelay:other.server
But I would like to exclude mailing lists, and have them processed locally,
using header_checks entries like this:
/^X-Mailing-List:/FILTER local:
Here, "local" is the
I found the problem by investigating the address verification traffic
between
Postfix and Exchange. I noticed Postfix was not verifying recent
addresses at all
so I figured Postfix must be caching verification results somewhere.
Indeed, there is a /var/lib/verify_cache.db and it contained the
On 12/12/2011 8:32 PM, Wietse Venema wrote:
What is the output of:
postconf smtpd_reject_unlisted_recipient
Reason I ask is that the "unlisted recipient" check also
does the relocated check.
Wietse
It might also be relevant that I'm using recipient address verification
against the Exc
What is the output of:
postconf smtpd_reject_unlisted_recipient
Reason I ask is that the "unlisted recipient" check also
does the relocated check.
smtpd_reject_unlisted_recipient = no
I have to accept unlisted recipients as there are no local users.
Everything is being relaid to an Exchange
On 12/12/2011 7:47 PM, Wietse Venema wrote:
Pim Zandbergen:
I can now reproduce the bouncing. Out of 22 tested recipients in
the relocated file, 7 consistently bounce, and 15 others consistently
reject.
What do you mean by that: you talked to the Postfix SMTP daemon
from one IP address, sent
On 12/12/2011 4:48 PM, Wietse Venema wrote:
The network-facing SMTP server is configured not to validate that
recipient, for example, due to explicit whitelisting in an access
map.
The access map contains whitelisted IP addresses only.
I can now reproduce the bouncing. Out of 22 tested recipie
I can't yet reproduce a bounce; i'm still figuring out under what
circumstances
a bounce will happen. Just being a local user, like I suggested in my
previous post
is not enough.
But here is an actual bounce sitting in my queue right now:
-Queue ID- --
I'm using postfix 2.7.5.
Some relocated messages are bounced, some are rejected.
It looks like this is the rule:
Messages to recipients that appear to be local users (through winbind in
my case) are bounced.
Messages to recipients that do not appear to be local are rejected.
This may be rele
I recently started using the relocated_maps feature and now am seeing some
bounce messages to forged addresses in the queue because of that.
It looks like this feature is bouncing rather than rejecting mail.
How can I avoid this?
Thanks,
Pim
For a couple of weeks I have been using "reject_unknown_helo_hostname" in
my "smtpd_helo_restrictions". This has helped to reject some 500 unsolicited
mail messages per day, on a total of around 1500.
Unfortunately, I've had to whitelist some 10 mail servers that are
misconfigured
but legitimate
Pim Zandbergen:
Wietse Venema wrote:
I know of no RFC that says only whitelisted clients can send email
over IPv6.
Well, it's their policy. I can respect that, if their assumption that
senders
should fall back to IPv4 is valid.
2 - Increase smtp_mx_session_limit (default: 2) so
Wietse Venema wrote:
This policy is mistaken for the following reasons.
Doesn't that make the whole ipv6whitelist.eu initiave "mistaken"?
Or could there be a correct way to use it?
As a side note: they do explain how to enable their whitelisting in Postfix:
http://www.ipv6whitelist.eu/implement
Wietse Venema wrote:
I know of no RFC that says only whitelisted clients can send email
over IPv6.
Well, it's their policy. I can respect that, if their assumption that
senders
should fall back to IPv4 is valid.
2 - Increase smtp_mx_session_limit (default: 2) so that Postfix
will knock
I cannot send mail to ISP nines.nl nor to their customers.
Nines.nl have three MX hosts:
two at weight 100, with IPv4 and IPv6 addresses
one at weight 500, IPv4 only
Their primary MX hosts defer all mail sent to their IPv6 address
with "451 Your IPv6 address is not whitelisted at ipv6whitelist.
15 matches
Mail list logo
