rd style of Unix usernames without the @domain, and
perform your mapping of "user@domain" to "user" in your IMAP
software. It would only take a bit of userdb/passdb magic in Dovecot.
Not terribly difficult. (Followup on Dovecot list if interested.)
Good luck.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
;master.cf" into an HTTP
link.
Haha, that will teach them not to post HTML to mailing lists! :)
(Well, no, it won't teach anybody anything, but we can all have a
laugh about it. :) )
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ist_threshold
http://dnswl.org/
My postscreen page, not yet updated for 2.11:
http://rob0.nodns4.us/postscreen.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t's bug database? Perhaps they fixed this for
RHEL5 also?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
; How do I turn off the D flag?
What is this "D flag"? Perhaps you need to go back to the one who
made the suggestion to you.
I would suggest that you start over with non-verbose logs (and
perhaps mail headers) which illustrate the problem, and current
"postconf -n" output.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
f the
Dovecot replies said, it looked like a probable Postfix issue. But
you need to comply with the list welcome message when posting. See:
http://www.postfix.org/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/
E.html#mail
WAG: 10020 is your httpd or webmail UID, and your webmail is wrongly
configured to use sendmail. Change your webmail client to use SMTP.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
igging on the stunnel configuration.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
p out as much spam as possible before that happens.)
If/when these botnets start trying to fly under the radar with
reasonable send rates, they are still detectable through content
filtering. URIBL lookups should catch these.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ding more domains.
This can probably be done better with SQL tricks rather than PCRE,
BTW. Not worth changing to SQL if you're not already using it, of
course.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Oct 24, 2013 at 10:00:00AM -0500, /dev/rob0 forgot to
terminate a PCRE expression:
> if /@example\.(com|net|org)$/
> /^(info|contact|etc)@ localuser@mydestination.domain
> endif
if /@example\.(com|net|org)$/
/^(info|contact|etc)@/ localuser@mydestination.dom
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
th the client, then. They
should have disconnected when rejected.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nguishing "outgoing"
emails from "incoming"? All mail comes in. All mail goes out.
> thanks for your tips
Scrap it all and start setting up amavisd-new.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
.0
(email marketers, trust level "none") as a +1 DNSBL. No, I would not,
but it's fun to think about. :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nting here in Postfix 2.x. Maybe a few examples added to
VIRTUAL_README?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Nov 12, 2013 at 11:45:51AM -0500, Wietse Venema wrote:
> /dev/rob0:
> > As Viktor said, while a domain aliasing feature might be
> > worth considering for an eventual Postfix 3.0, it's probably
> > not worth implementing here in Postfix 2.x. Maybe a few
> >
is global. This won't work as you might expect.
> -o smtp_helo_name=mx...
smtp_* settings are only applicable to the smtp(8) client.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
mavisd OR to "dfilt", not both.
> dfilt unix- n n - - pipe
> flags=Rq user=filter argv=/etc/postfix/disclaimer -f ${sender} --
> ${recipient}
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
think should have worked.
Regarding Nik's reply, no, chroot does not sound likely, and map
files do not need to be in a Postfix chroot; and no, verbose logs
won't help.
http://www.postfix.org/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consultin
9.7, 9.8, and 9.9 had new features which slightly
reduced the pain of DNSSEC. 9.10 won't be an exception.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t; this is OK, any proper MTA needs a PTR
>
> google for SMTP authentication
No, it does. It's an actual Yahoo outbound host, with FCrDNS and
whitelist entries in services like DNSWL.org.
I suspect the problem is as Wietse identified: chroot.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Sat, Dec 14, 2013 at 08:53:14PM +, Viktor Dukhovni wrote:
> On Sat, Dec 14, 2013 at 02:35:15PM -0600, /dev/rob0 wrote:
>
> > > The trick is to find tools that make operating a DNSSEC zone
> > > relatively painless. You get security, but it easier to mess
> &
l(1) has no concept of authentication, that is exclusively a
matter of SMTP.
> Or it could be done only using third-party tools?
Sure, a null client in place of sendmail, but why?
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Table Overview.
Note also that your mailstore/IMAP server potentially has more to do
with this question than Postfix does. See its documentation also.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
h gives trust away to some uncontrollable
> companies and governments also does not help a lot (probably even
> trying to prevent any wide adoption of DNS based certs, because
> they will kill their model to earn money).
Yep, I think DNSSEC and DANE will cheer you up quite well. :)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e DNSSEC-friendly. It sounds like you can run your
master nameserver and sign your zone, and they will provide slave
(secondary) name service for free (included with the domain
registration cost.)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ame
service. BIND, OTOH, is an all-in-one DNS implementation, with a
caveat: you really should not have authoritative and recursive
service in the same named instance, in general.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Feb 25, 2014 at 08:21:14AM -0500, Charles Marcus wrote:
> On 2/24/2014 3:52 PM, /dev/rob0 wrote:
> >On Mon, Feb 24, 2014 at 01:16:39AM +0100, Dirk Stöcker wrote:
> >>Oh yes - DNSSEC. When will it come? In hundred years?
> >
> >Dirk, do you mind explainin
SSEC was
something I had to do. I found that my Zoneedit nameservers didn't
support it, so I removed them and went for self-hosting. It never
occurred to me that "no DNSSEC" was an option. :)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
_maps set in main.cf and NOT including the "nis:" part.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tanding. EVERY restriction stage MUST resolve to
"dunno" or a permit action. If any stage results in "reject", the
mail is rejected.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ike a very bad idea.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
>
> I did but it' still not working...
>
> Any suggestion?
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
sts,
> tutorials and Mini-HowTos are just not working as advertised.
Of course not. Why would they? If you want to know how to configure
any given software package, consult its documentation.
http://www.postfix.org/VIRTUAL_README.html
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ookup. It is broken, bug-ridden garbage that will not be fixed.
Nobody in A.D. 2014 should be recommending it. The proper tool for
DNS troubleshooting is dig(1).
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Sat, Apr 05, 2014 at 06:23:05PM +0200, li...@rhsoft.net wrote:
> Am 05.04.2014 18:06, schrieb /dev/rob0:
> > One other comment to this thread: please, PLEASE, get rid of
> > nslookup. It is broken, bug-ridden garbage that will not be
> > fixed. Nobody in A.D. 2014 shou
I try to send email to
> the list., but as far as I know, I shouldn't need local aliases
> with this configuration
As explained above, no. Of course I am only guessing that your
mysql:/etc/postfix/mydestination.cf returns something when queried
for your list domains -- you did not share logs anywhere.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
They know
mail, and they have relationships with large receivers. If revenue
depends on your bulk mail, their fees will be money well spent.
(Perhaps they have reseller arrangements, if that is what's
appropriate in your case.)
Anyway, mynetworks (and the permit_mynetworks restriction) is the
answer to the question as posed, so I'll stop here.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
; : Sender address rejected: Access denied
> (Net::SMTPFatalError).
In your OP you also had this line:
-o
smtpd_sender_restrictions=permit_sasl_authenticated,permit_tls_clientcerts,reject
Which of those three restrictions are met?
1. permit_sasl_authenticated, no, the client did not AUTH
2.
nodns4.us.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s:
> /^X-SMTP-Client-Addr: (\S+)/ warn client address $1
>
> Instead of X-SMTP-Client-Addr use something that is unlikely
> to appear in other people's email.
Nice idea, but will these smtp_header_checks fire if rejection
occurs before DATA?
> This requires Postfix 2.5 or later.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
alties from time to time, but I
wouldn't blindly jump ship from software I know and trust unless
there was a very good reason.
> I've already made the postscreen changes on the systems, and
> already noticing fewer DNS queries.
>
> I've also removed swl.spamhaus.org entirely, thanks to a
> conversation with spamhaus and comments from Tom Hendrikx about
> it being discontinued.
Yep, I will be doing the same. Unfortunately I probably won't get
around to updating my web page very soon. Note also that I used
dnsbl.ahbl.org in postscreen; by the beginning of 2015 that will
become disastrous, as they are planning to put a wildcard in the
zone.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
mail is seen only if "/dev/rob0" is in the Subject:
il?
Postfix isn't sending this email, merely transporting it.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
l in BOTH mydestination and virtual_alias_domains
>
> Anyone know how to do this without errors/warnings?
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
> May 13 12:54:01 sparky postfix/cleanup[24668]: 7218221551:
> message-id=<20140513175401.7218221...@sparky.example.com>
> May 13 12:54:01 sparky postfix/qmgr[24600]: 7218221551:
> from=, size=782, nrcpt=1 (queue active)
> May 13 12:54:02 sparky postfix/smtp[24672]: 7218221551: to=,
> orig_to=, relay=rusty.example.net[192.168.3.5]:25, delay=0.92,
^^ Yes, Postfix rewrote this in virtual_alias_maps.
> delays=0.18/0.01/0.61/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
> 43ACE810A)
> http://www.fredshack.com/docs/postfix.html
Who's this? Just stick with the documentation you got with your own
Postfix, or use www.postfix.org.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
logs, but I know I have seen this scenario before:
listed on SORBS, Spamcop and DNSWL.
> > - move the offending DNSBL to the regular smtpd_*_access
> > checks, where whitelisting is possible.
>
> Sounds like my best option here.
Disagree. Better scoring solves the problem nicely. Your content
filtering will probably catch the ones your postscreen allows
through.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, May 13, 2014 at 05:27:26PM -0500, deoren wrote:
> On 2014-05-13 14:46, /dev/rob0 wrote:
> >On Tue, May 13, 2014 at 02:15:48PM -0500, deoren wrote:
> >>If I send an email to 'root' and $myorgin is set to $mydomain
> >>(which is also set properly), shou
eference was made above, or you can visit it online:
http://www.postfix.org/pipe.8.html
As for the decoding of Subject: headers, I don't know, but you
could start by consulting the source code of a recent and well-
maintained open source MUA.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
a
milter.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ion
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nk I have the answer now:
snip
> 3) Add "/^Subject: \[SPAM\]/ DISCARD" to the
> /etc/postfix/header_checks (check the
> /etc/mail/spamassassin/local.cf to see the exact string to match)
It's not particularly safe to discard mail flagged as spam, your own
GTUBE adventure here being a good example why not.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
, their scripts
populate and maintain the chroot. So blame Debian users for their
failure to read Debian's documentation.
But you are right; it's not a good idea.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
sites will choose to block them.
> On the other hand, if you decide to start a proper opt-in anonymous
> service contact me. That would be a great service and I have some
> ideas about that.
I think anonymity is important. Unfortunately I don't have time to
help right now.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
st the recipient's reply.
I don't know if any of the existing projects (such as cbpolicyd or
postfwd) can do this easily, but it shouldn't be hard to add.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Aug 21, 2014 at 03:51:05PM -0700, Ronald F. Guilmette wrote:
> In message <20140821215806.gx23...@harrier.slackbuilds.org>,
> /dev/rob0 wrote:
> >I don't know if any of the existing projects (such as cbpolicyd
> >or postfwd) can do this easily, but it shou
gt; For submission of list messages to a large number of recipients,
> I would generally use sendmail(1) rather than SMTP. Don't know
> whether mailman supports that.
Interesting. They do, but documentation specifically recommends
against it.
--
http://rob0.nodns4.us/
Offlist GMX
ntication, that script might end up in our BADGUY
list.
Legitimate submission and IMAP traffic, like SSH, is more likely to
come from a human sitting at a computer (smartphone.) So possibly
similar limits will work.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
amassassin is built-in, assuming that your perl can find the
appropriate SA modules. You'd simply have to configure your
amavisd-new to run your filter script.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Hat say
when you asked?
> > Of course even better, just upgrade to 3.0.4 or 3.1.0.
It's not difficult when using a SRPM + rpmbuild(1).
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
orged mail from worms or viruses.
(Especially read the rest of that, the "details" referred to from
reject_unlisted_sender.)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t is OT, if you share more information, we'll
perhaps be able to spot something wrong.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ot;postconf -nf ; postconf -Mf" are appropriate,
because there might indeed be a Postfix issue.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
mian, whom
I know from this mailing list and from IRC to be competent. He'll
probably reply too.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ndmail binary.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
any client, so settings which govern what it does in
conversation with clients are all moot.
If any one (or two) of those three are "yes", then postscreen will
talk to clients.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
>
> You can't do this with postfix alone.
> You would not need a full external filter, but you could use a
> policy service or a tcp table, either of which are fairly simple and
> lightweight.
>
> Or you could just use the Message-ID as your mostly-unique identifier.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
: just say yes. Legitimate
clients always say HELO/EHLO. You'll never lose any real mail by
requiring HELO/EHLO. And regarding postscreen_helo_required: note
that you've already decided you're not going to accept the mail when
postscreen is in a position to enforce it or not.
--
you happen to
have something on localhost sending mail.
Perhaps a better idea is: only apply these header_checks before (or
after?) the filter. See:
postconf.5.html#receive_override_options
postconf.5.html#cleanup_service_name
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Fri, Mar 18, 2016 at 10:57:03AM -0300, Lucas Castro wrote:
> please, post your postconf -n.
Without the relevant logging to demonstrate the issue observed by the
OP, this wouldn't help.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
onf.5.html#postscreen_access_list ).
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t;. If set as
"enforce" you'll get the full dialog with postscreen and multiple
lines logged. With "drop" it will be dropped in lieu of giving a
banner.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
to the real server safely (SASL AUTH + STARTTLS on submission.)
The SOHO_README will have some guidance for you if you do that.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
you can get a list of IP addresses (CIDR blocks), you can use a
cidr_table(5) lookup to block them more safely and surely (until they
buy/steal different hosting, of course.)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
actions in the same file, 'ns_access.pcre'.
Again refer to the access(5) manual, access.5.html -- yes, any valid
action can be the result of any lookup. To use a custom restriction
class name as a lookup result, that name must be:
1. listed in smtpd_restriction_classes, and
2. defined in main.cf
> Again this example was really helpful -- not just in solving this
> specific problem but giving an idea of how to add & layer
> restrictions, and how they 'flow'.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
standing is that inclusion of (for example) "relay_domains"
> in $parent_domain_matches_subdomains would treat "example.com" as
> ".example.com" for matching purposes, but would otherwise be a
> no-op if the subdomain is already dot-prefixed.
Nope. If you
On Tue, Mar 29, 2016 at 08:42:12AM -0700, Michael Fischer wrote:
> On Tue, Mar 29, 2016 at 8:36 AM, /dev/rob0 wrote:
>
> >> According to my reading of the documentation, if $relay_domains
> >> includes ".example.com", it should relay mail for
> >>
On Tue, Mar 29, 2016 at 08:53:48AM -0700, jaso...@mail-central.com wrote:
> On Tue, Mar 29, 2016, at 08:29 AM, /dev/rob0 wrote:
> > (However, in this thread you do seem to be focusing on spam from the
> > quasi-legitimate marketers who might be in compliance with the USA
> >
2.10.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nt
> zen.spamhaus.org, reject_rbl_client bl.spamcop.net
I wouldn't reject on Spamcop. It's an automated list, and the
Spamcop folks will tell you it's best when used in a scoring system.
Your mail, so it's up to you, of course.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
how both of them
together could be useful?
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
smtp_sasl_auth_enable = yes
> smtp_sasl_password_maps = hash:/etc/postfix/sasl-passwords
> smtp_tls_CAfile = /etc/postfix/ssl/postfix_default.pem
This is likely due to a TLS failure. Add
smtp_tls_loglevel = 1
to enable logging of TLS activity.
> smtp_tls_security_level = may
> smtpd_sasl_security
On Fri, Apr 01, 2016 at 08:13:14AM -0700, jaso...@mail-central.com wrote:
> I'm learning about whitelist scoring in postscreen_dnsbl_sites=
>
> /dev/rob0 mentioned using these
>
> postscreen_dnsbl_sites=
>... BLACKLISTS ...
>swl.spamhaus.o
t; I know those^ were already blocked, but some are sneaking
> through -- and I"m not yet entirely sure why or how.
I'm not either. Perhaps you should focus on the problem, and post
examples of it?
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
r" followed by zero or
more characters which are NOT a period. If this lookup follows the
reject_non_fqdn_helo_hostname restriction, it will never be used.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ink. I'll post another update
> in October, unless something dramatic happens before then.
Again, your efforts are appreciated.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
"aggressive", "moderate", "conservative", or "permissive", and I
manage which DNSBLs are used within each strategy definition.
Too often here we see postmasters who use DNSBL services without
knowing their policies (or even if the service is still being
ailed" as the transport. (You could also use "tcp"
> tables, but the "socketmap" protocol is somewhat better).
What about a check_recipient_mx_access lookup and a FILTER result? I
suppose that fails for multiple recipients where one or more of them
are not at that MX host.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
.
> Ok, so i'm wrong. Could you explain why?
Restriction classes are groups of smtpd(8) restrictions.
header_checks(5) is not a smtpd restriction. In fact it's not even
implemented in smtpd. See Wietse's reply in this thread.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ault question understood this, but
the one who asked it probably did not.
To proceed, we'll need the information as provided in the list
welcome message, which can be seen also here:
http://www.postfix.org/DEBUG_README.html#mail
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
elivering mail on
behalf of their user to one of your addresses.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
rg/SMTPD_ACCESS_README.html
and see also:
http://www.postfix.org/postconf.5.html#mynetworks
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
file, it still accepts the email?
>
> As documented since december 1998, if there is no match, then no
> decision is made.
>
> Wietse
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
l be:
> " permit_sasl_authenticated, reject, reject_unauth_destination"
Again, this can only happen with restriction classes.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
matter, however, is "UCE restriction" a proper
term to use here? I'd suggest that "UCE" is never proper. Are these
not more properly called just "restrictions"?
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
901 - 1000 of 1152 matches
Mail list logo
