mxtoolbox is a great tool to see almost all blacklists on your ips, as
Luciano mentioned, but yahoo doesn't report their own blacklists so
that tool can only tell you if the ips have been blacklisted in other
places. TSS09 is the same as yahoo's old TS03 which is a permanent
block as the message te
I wish the world would use ipv6 enough for this to be worth doing, but
it's not going to have much benefit to you as there's almost no one
using it for smtp, from the last time I checked which was a few months
ago, google uses it perfectly, verizon too (maybe a few more cable
domains), yahoo looked
I'm not sure if postfix has any add ons that do this, but in my
opinion, you can probably bypass the mta completely and just read the
mail directories, every email is simply a file inside a directory,
with full headers and the message encoded in mime, so you could read
the files, parse the headers
If you are listed on spamhaus there will be a page about it normally
on their site, they have a few blacklists and some are worse than
others, so either check the response codes from postfix to see if that
tells you the what was listed. Also, if you know for certain that you
are listed by them, you
each instance has it's own copy of main.cf and master.cf so you have
to duplicate values. If you think most will be the same, perfect the
first instance and then copy that file to the new ones, and change
accordingly.
If I am wrong, someone please correct me, but I've never heard of any
kind of in
Postfix doesn't have any type of automatic detection of any
malfunctioning blacklists, it may be configurable on how long to wait
for a response, I'm not sure on that, but no dynamic changing of what
is being used, if you think that one though, postfix shouldn't do
anything like that. Would tempt p
Not sure if this helps, this may be specific to my set up, but in the
/etc/dovecot directory I have a file named "users" which lists every
email address and their file locations. If not, there must be a config
file somewhere so I'd look around.
On Mon, Jul 28, 2014 at 1:02 PM, Matthias Andree wro
Maybe you need to set your restrictions to more strict settings,
here's my setting for smtpd restrictions, someone else may have a
better config so open to discussion:
smtpd_recipient_restrictions = permit_mynetworks,
permit_sasl_authenticated, reject_invalid_hostname,
reject_non_fqdn_hostname, re
s down the line. After a little time, a few messages go in to the
deferral queue and I start getting these time outs again. I repeated
the above about 5 times and each time same results.
On Wed, Jun 25, 2014 at 5:59 PM, Wietse Venema wrote:
> Paul C:
>> Hey all, has anyone seen
Hey all, has anyone seen this happen with postfix ...
delivery temporarily suspended: connect to
mailin-01.mx.aol.com[64.12.88.132]:25: Connection timed out
I realize it probably some lag going on somewhere, just taking too
long to finish the smtp convo with aol, but its only happening with
aol a
Just scanning this thread, are you seeing the mail is actually failing
or is the log just concerning you?
I had a similar issue not too long ago that sounds like it could be
the same issue, where there's no obvious problem but you get an smtp
error at different parts of the injection process, like
r-postfix-us...@postfix.org] On Behalf Of Wietse Venema
> Sent: Tuesday, June 03, 2014 10:46 PM
> To: Postfix users
> Subject: Re: Error I'm not familiar with
>
> Paul C:
>> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: warning: hostname
>> cleers.dustypex.com does not res
ally sending the mail out? From the logs it looks like they are
trying to relay but its not going out.
On Tue, Jun 3, 2014 at 3:45 PM, Wietse Venema wrote:
> Paul C:
>> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: warning: hostname
>> cleers.dustypex.com does not resolve to
Hey guys, I'm seeing in my logs 2 things causing me some concern, I
don't need to go in to all my settings, just looking to see if
anything stands out from the message and common causes:
Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: warning: hostname
cleers.dustypex.com does not resolve to addres
led on the postfix
> server without resolving the issue. The other item that seems strange to me
> is I have other machines in the same subnet which are able to send without
> issue.
>
> Thanks,
> Blake
>
>
>
>
>
> On 05/12/2014 11:05 AM, Paul C wrote:
>>
What's the error? 220 is a successful response to the greeting and 250
is success for the helo command. The only I see that could cause issue
is you are using an internal ip, 10.12.0.100, maybe causing some of
your dns stuff to fail on the lookup? All I can see at this point.
On Mon, May 12, 2014
If its a small number of ip addresses trying to connect you might also
want to just block them with iptables too:
iptables -I INPUT -s 209.85.216.175 -j DROP
iptables -I INPUT -s 209.85.216.176 -j DROP
That line for each ip, then restart iptables
On Wed, Dec 11, 2013 at 5:52 PM, don magnify w
>From what I see from the spam scoring, you have a -100 from the domain
being whitelisted, i.e. google.com in your example. This gave the total
spam score a value of less than 0, and based on the header it says a 6.31
score or higher would cause the message to be blocked. So the spammer is
spoofing
phpmailer, or any other mime class, is not giving you the actual response
code of the end delivery of the email, unless you are directly sending your
email from phpmailer (which is possible but not intelligent). It can be
confusing to people when they don't understand the transport of the message
t
mtp_connect
but smtp-source looks like a stand alone script, probably a better fit.
Thanks guys.
On Tue, Oct 15, 2013 at 8:29 PM, Wietse Venema wrote:
> Paul C:
> > Hey everyone, I'm about to write a script which would replace my existing
> > php mime class / injector in
Hey everyone, I'm about to write a script which would replace my existing
php mime class / injector in to one written in C. This is custom code so I
am not asking for direct help with it, but since its in C and will work
with postfix exclusively, there's one part of it that would be good to hear
op
21 matches
Mail list logo