the "domain" parameter in the ldap_table(5) manual.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
_recipient and notify_classes
if you want to get a postmaster's notice as well.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nd both of those are deprecated. smtp_use_tls is replaced by
smtp_tls_security_level, and smtpd_tls_security_level replaced
smtpd_use_tls.
http://www.postfix.org/TLS_README.html
As for the real question, the OP has not adequately described the
problem and goal, so we can't help with that.
--
http://r
o, after executing the above
> commands, run as root:
>/etc/init.d/postfix restart
This is a script which may (or may not) be provided by the
distributor. "postfix stop" and "postfix start" are the generic
upstream commands (this is the upstream list, not a Debian one.)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
to share the logs which show it.
> >Here is the main.cf file as it is currently configured:
snip
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
success
of DNSBLs against the previous generation of ratware.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ice and content filtering of submission.
> I am looking for a way to reduce the impact of this while
> we contact all these users.
I'd revoke their credentials ASAP, as soon as the compromised account
is identified.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist
pt and files it needs, it might work.
http://www.postfix.org/OVERVIEW.html
http://www.postfix.org/postconf.5.html#default_privs[1]
http://www.postfix.org/postconf.5.html#mail_owner
[1] Quote: "DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER."
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Postfix problems. It does not know what's wrong in
procmail.
> Could someone more expert than me point me in the right direction?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
er is rate limiting and
content filtering of authenticated senders.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
lude the fact that the OP or his organization is running those
forwarders, he might as well implement the rbldnsd there and be done.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
stration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
to it. :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Oct 23, 2012 at 10:42:44AM -0700, marintech wrote:
> Click the link to the forum, the text is there.
No. You will have better luck here by complying with the list's
guidelines.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only
You've likely created a routing loop between your server and the
spam filtering service. Don't forward already filtered mail back
to the filtering service.
Did you talk to the support desk at the filtering service?
--
http://rob0.nodns4.us/ -- system administration and cons
e how "looping" is
> occurring, I know I've not set that up. Yes I have asked the help
> desk of Spam Soap and they say it is my server.
>
> I'm sorry I'm not sure what you mean by this:
>
>
> /dev/rob0 wrote
> > We would look at the recip
togetincomingrelayworking.com.
Don't use unqualified names in maps unless you fully understand what
they are,
> my transport looks like this
> mx2.mail.com smtp :[mx1.mail.com]
---^
The space in there before the colon is wrong. And again, no listing
is shown for &qu
a check_sender_access lookup of
the null sender, and therein apply ips.backscatterers.org or other
backscatter DNSBL[s], but that entails a slight risk of loss of real
mail (sometimes a backscatter source might have a real bounce to
deliver), and it won't help with the load on the LDAP server.
If all the rejected recipient addresses follow some kind of pattern,
maybe a PCRE lookup can help. We don't know enough about it to
suggest anything more.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
kind of
> pattern, maybe a PCRE lookup can help. We don't know enough about
> it to suggest anything more.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ther adjustments may be necessary as well, depending
> on the particulars of your setup.
Unsetting mynetworks should be quite safe, acting just as if any
address checked is not within $mynetworks.
The good thing about mynetworks is that all other things that use
$mynetworks are consistent. The
o such file or directory
... apparently there is no ./demoCA/newcerts therein.
> Why is trying to use that config file? Should I alter it?
It's your system default openssl(1) config(5) file. Maybe you should
edit it. You certainly should look at it.
> [1] http://www.postfix.org/TLS_README.html#quick-start
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ober/068873.html
http://dovecot.org/list/dovecot/2012-October/069159.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
> mailman unix - n n - - pipe
> flags=FR user=mailman:mailman
> argv=/usr/lib/mailman/postfix-to-mailman.py ${nexthop} ${user}
> -----
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ey might not know any more
than you do about it. If you read and understand the documentation,
they definitely will not know more than you do.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ccomplish the same thing is to create a
Makefile and use make(1).
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
blem. I like Postfix more than Gmail
> ;-)
Perhaps, but you can't always expect Postfix to fix other bad
programming.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
one job well and can work together to do big jobs. It's
upgrade- and downgrade-resistant, also.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ttp://www.postfix.org/DATABASE_README.html
4. Search for MongoDB
It's not there, thus not implemented. There's also a "works in
progress" page (MongoDB is not there, either):
http://www.postfix.org/wip.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
#x27;t a good idea?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
PATTERNS", for the various
different lookups you might need to try. One of those is returning a
REJECT result.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
> am more confused where this block is happening.
Another suggestion: a recursive, case-ignored grep of /etc/postfix
for the domain in question.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
facility logs; these would only be
logs of the "info" priority level.
You should look for and rely upon whatever file you have which
receives "mail.*" logs (all syslog priorities of the "mail"
facility.)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ld be a
good option, indeed.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ly to RCPT TO command))
>
> In this example, no postfix/verify process occurs.
And we don't have enough information to say why not.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tful that you want or need a
MTA at all.
> http://pyropus.ca/software/getmail/
>
>
>
> config like i.e this
>
>
> [retriever]
> type = SimplePOP3Retriever
P.S.: Getmail also supports TLS/SSL. :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Mon, Nov 12, 2012 at 11:55:19AM -0500, John Hinton wrote:
> On 11/12/2012 9:52 AM, /dev/rob0 wrote:
> >On Mon, Nov 12, 2012 at 12:02:02PM +0100, Robert Schetterer wrote:
> >>Am 12.11.2012 11:21, schrieb Muhammad Yousuf Khan:
> >>>1. i have to download email from
t in an appropriate place.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
akes place before the logging of the connection. Postfix
wants to be able to tell you who it was, not just "unknown[IP]" if
possible.
[snip]
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
.com, account and
> acco...@localhost.example.com it won't be delivered locally.
It's probably time for you to show logs and postconf -n:
http://www.postfix.org/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
x.org/LOCAL_RECIPIENT_README.html
http://www.postfix.org/postconf.5.html#local_recipient_maps
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
being accepted
under permit_mynetworks, or via sendmail(1)?
> >For further information see the VIRTUAL_README [2].
> >
> >[1] http://www.postfix.org/postconf.5.html#virtual_alias_maps
> >[2] http://www.postfix.org/VIRTUAL_README.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
http://www.postfix.org/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
odns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ht just as well update a hash: file for mynetworks.
And another solution is to reconsider your SASL antipathy. It's
well-documented and not that hard to set up.
http://www.postfix.org/SOHO_README.html#client_sasl_enable
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
b and ${user}+c handled the same way, I created a
> link named .forward+b and .forward+c which pointed to .forward+a
> but as we know, it didn't worked.
Hard links work fine.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
n and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Mon, Dec 03, 2012 at 09:51:34PM +0100, Chris wrote:
> On Mon, 3 Dec 2012 13:26:25 -0600 /dev/rob0 wrote
> > On Mon, Dec 03, 2012 at 07:40:24PM +0100, Chris wrote:
> > > I've been asked to skip RBL checks for certain users on
> > > the domain. How can I d
as spam due to dynamic IP status, etc.
Spamassassin can be tailored for the job of submission scanning. The
URIBL checks are particularly good at detecting compromised accounts.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ission now, he will be soon. And possibly losing
his job in any case. Tomas is not in a good place right now.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Dec 04, 2012 at 07:46:10AM -0600, /dev/rob0 wrote:
> On Tue, Dec 04, 2012 at 11:59:01PM +1300, Peter wrote:
> > I would still also set up port 587 on the mail.example.com
> > IP as submission as well and try to encourage your users (at
> > least the ones you can) to
0, dsn=2.0.0, status=sent (delivered via dovecot
> service)
See, you accepted this for final delivery. You did not relay.
> Dec 6 23:30:51 machinename postfix/qmgr[4628]: 3653E371BAA1:
> removed
>
>
> And the mail is indeed delivered. In master.cf the
> submission-part looks like this:
So? Your telnet was to port 25.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s_loglevel = 1
> smtpd_tls_received_header = yes
> smtpd_tls_req_ccert = no
> smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
> smtpd_tls_session_cache_timeout = 3600s
> smtpd_use_tls = yes
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ternet domains in examples. There
are example.{com,net,org,...} for that.
Finally, see "EMAIL ADDRESS PATTERNS" in the access(5) manual.
http://www.postfix.org/access.5.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
u want forensic
evidence of the malware?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
; body are displayed together as two long lines.
In addition to postcat(1) as mentioned upthread, you can trace the
queue ID in your logs. That will probably also reveal the reasons
behind the bounces.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is se
. Why did you choose the snapshot
version? Note also that as snapshots go, that's very old. Perhaps you
should stick with official stable releases?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ncements/postfix-2.7.0.html
But then, you might as well just build and use 2.9.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
stem administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
r_login_maps to
return also "specialuser" for every valid address. Perhaps this is
easily done with your ldap_table(5) by means of "result_format"?
/path/to/postfix/ldapsender.cf :
...
result_format = %s,specialuser
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
BTW Reply-To: is set, and the offlist Cc: is not necessary.
On Wed, Dec 19, 2012 at 07:40:10PM -0500, Robert Moskowitz wrote:
> On 12/19/2012 06:31 PM, /dev/rob0 wrote:
> >On Wed, Dec 19, 2012 at 02:38:52PM -0500, Robert Moskowitz wrote:
> >>I am looking at a number of t
ery unlikely to do so,
unless, of course, it is possessed by malware.
Note that these limits would only slow down malware; they couldn't
stop it.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
plus any other
Tier 3, 1 point: reject with three of these sites
I'm not currently using psbl.surriel.com, but I'm sure it would be
fine in Tier 3. The whole point of Tier 3 is that it does NOT require
much confidence in those sites, but that when three of them agree,
there might
ly be useful for a few things, but in general, not
much.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
n, it should work.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
> support into the program. Once I became aware of the problem I
> simple recompiled the port and now all is well with the world
> again.
I would not say ALL is well. If you're using Dovecot IMAP, it makes
no sense at all not to use Dovecot SASL.
--
http://rob0.nodns4.us/ -- system a
tfix.org/aliases.5.html
> Excerpt from log:
> Command died with status 2:
> "/path/to/script 2>>/path/to/log". Command output:
> sh: 1: cannot create /path/to/log: Permission denied
--
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:
ess that they could set the sender address to anything they want.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
em administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
postfix-mx01/qmgr[18097]: 8B8362008B: removed
Perhaps you are confusing smtp(8) and smtpd(8)?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ql-virtual-maps.cf
> virtual_uid_maps = mysql:/etc/postfix/mysql/mysql-virtual-uid.cf
> virtual_gid_maps = mysql:/etc/postfix/mysql/mysql-virtual-gid.cf
> myhostname = mydomain.ru
> mydomain = mydomain.ru
> mydestination = localhost
> mynetworks = 192.168.9.0/24, 192.168.8.0/24, 192.168.7.0/24, 192.168.6.0/24,
> 127.0.0.0/8
> |
>
> What I should check in the first place?
Until you get the logs working there is little else we can say here.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
needed, then please let me
> know and I'll include it.
>
> Any pointers, examples or explanations will be appreciated. I've read
> in the documentation for virtual hosting and backup MX', but the answer
> seems to evades me.
FWIW, generally a backup MX is a bad idea. Why did you want it?
[snip]
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ttp://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
//en.wikiquote.org/wiki/Jamie_Zawinski#Attributed
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ing
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
rong;
this is not a localhost dns spoof attack. This is some other, more
mundane and ordinary, attack. You're going to have to cooperate if
you want help in solving it.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
g
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Wed, Feb 27, 2013 at 03:10:38PM -0600, Noel Jones wrote:
> On 2/27/2013 2:33 PM, /dev/rob0 wrote:
> > I only saw main.cf and some largely irrelevant logs.
>
> I was trying to be polite. That's all I saw too.
I tried to be polite also, but perhaps putting a little less
ob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
.5.html
http://www.postfix.org/local.8.html
http://www.postfix.org/postconf.5.html#recipient_delimiter
http://www.postfix.org/postconf.5.html#virtual_alias_maps
Other choices include pipe(8) and transport(5) maps, but this seems
simpler to me.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Feb 28, 2013 at 01:14:50PM +0500, Muhammad Yousuf Khan wrote:
> On Thu, Feb 28, 2013 at 3:17 AM, /dev/rob0 wrote:
> > On Wed, Feb 27, 2013 at 05:51:08PM +0500, Muhammad Yousuf Khan
> > wrote:
> >> i am using virtual users and domains, where i have 2 virtual
>
rintlink.net. IN A
>
> ;; AUTHORITY SECTION:
> cust.lkq.sprintlink.net. 7200 IN SOA ns1-auth.sprintlink.net.
> dns-admin.sprint.net. 2010080301 43200 3600 2419200 7200
>
> ;; Query time: 50 msec
> ;; SERVER: 206.228.179.10#53(206.228.179.10)
> ;; WHEN: Mon Mar 4 12:04:25 2013
> ;; MSG SIZE rcvd: 116
>
> --
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
m/archives/postfix/2010-04/0168.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
x 2.10)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
27;t allow
spew to continue.
> Hence our trying to reduce to amount of emails send to non-existent
> emails.
I think you'd also find that URIBL content filtering of submitted
mail very effective. This malware almost always tries to get victims
to look at spammy links.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t -lz -lm -lssl -lcrypto"
http://www.postfix.org/INSTALL.html
http://www.postfix.org/MYSQL_README.html
http://www.postfix.org/SASL_README.html#postfix_build
http://www.postfix.org/TLS_README.html#build_tls
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ini outbound relays as a CIDR expression or as single
# IP addresses without the /xx
ip.add.re.ss/xx permit_auth_destination
other.add.re.ss/xx permit_auth_destination
0.0.0.0/0 reject This host is not MX for example.com, go away.
--
http://rob0.nodns4.us/ -- system administrat
ed was 2-3 mumbles of smtpd_mumble_restrictions.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
en I left all my old spam restrictions alone. On rare
occasions I have seen where they are used.
All that said, I personally have not used Stan's PCRE list, but I've
seen it discussed here and elsewhere for a lot of years. I guess that
means I'm outdated also. ;)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Mar 28, 2013 at 11:09:58PM -0500, Stan Hoeppner wrote:
> On 3/28/2013 8:03 AM, /dev/rob0 wrote:
> > If postscreen DNSBLs are your only protection, what happens if
> > your DNS breaks? Spam flood! Here too, Stan's PCRE list can help,
> > again, at least as a HELO
06:09:33 firstname.lastn...@mathcom.com
> (host smtp.indra.com[209.169.0.20] said: 550 5.7.1 ...
> Access denied (in reply to RCPT TO command))
> lastn...@indra.com
>
> Any thoughts?
If this isn't enough to get you going, see here before posting again:
http://www.postfix.org/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
E.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tar.gz in the same directory)
You don't need md5sum, in fact, I'd think that the GPG signature
should give you greater assurance than md5sum.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
versed my polarity, I guess) I felt
that pain, but I suspect it would be difficult to implement, and
would cause many more lookups to be required.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nction. It will be nice to be positive again.
:)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
http://rob0.nodns4.us/postscreen.html
(I'm planning to maintain that page as an example configuration.)
Some questions remain: will the whitelist result give these hosts an
entry in the after-220 databases? Or would the pre-220 DNSBL test be
done every time?
--
http://rob0.nodns4.us/
701 - 800 of 1152 matches
Mail list logo
