. Check the router
documentation and troubleshoot the networking.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
names.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
, and not that HOWTO.
;)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
/dev/rob0 or not-spam is in Subject: header
On Mon March 2 2009 13:07:18 Victor Duchovni wrote:
On Mon, Mar 02, 2009 at 12:56:33PM -0600, /dev/rob0 wrote:
Massive confusion, and looking back on the thread somewhat, I still
think we're lacking a good description of the problem.
On Mon March 2 2009 06:31:09 Leonardo Coelho wrote
charge money for a DNS service ...
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
used Timo's patch. :)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
recipients, but the @yahoo.co.jp senders originated from your own
server. Compromised HTTP+PHP service?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
That's the problem, there's nothing in the logs.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
them
whitelisted? Whitelisting is a slippery slope, seldom the right
answer to the real problem.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
bounce_queue_lifetime = 0
default_destination_rate_delay = 2s
default_destination_recipient_limit = 1
default_recipient_limit = 100
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
for a logfile. Look into your OS
documentation about how they have configured your syslogd(8).
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
? Is
there any wisdom anyone would be willing to share, pro's con's, etc.
to help proceed?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
it wrong, we are
corrected by the ones who really know.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
automate it.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
, and it could cost you some real
mail.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
as per DEBUG_README.html#mail.
I can guess, maybe you have a transport(5) setting. It may or may not
have any relation to the virtual_alias_maps setting. Probably not, is
my guess.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
= 1073741824
virtual_mailbox_maps = ldap:/etc/postfix/vaccounts.cf
virtual_uid_maps = static:1001
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
:/etc/postfix/virtual
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
)
distributor-provided packages of PostgreSQL. You might, however, need
to have *-devel packages installed. See your CentOS / RHEL
documentation.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
transport_maps as a
dual-use lookup as an address class definition, because that could
cause you to accept mail that's not yours.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Mon May 11 2009 12:08:02 Magnus Bäck wrote:
On Monday, May 11, 2009 at 18:59 CEST,
/dev/rob0 r...@gmx.co.uk wrote:
[...]
BTW, I always use complete paths for lookups. I think ldap:vldap
defaults to ldap:$config_directory/vldap, but it never hurts to
be specific, so you know what
(similar) way
The first one also shows how to accomplish subdomain matching in hash:
maps.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
...@wikikalendar.com.
See also the list welcome message and/or DEBUG_README.html#mail for
suggestions on how to get the most benefit from a post to this list.
See as well, VIRTUAL_README.html , which explains the issue at hand.
--
Offlist mail to this address is discarded unless
/dev/rob0
.
[1] In fact I wrote that factoid.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Thu May 28 2009 23:21:06 Steve wrote:
way of the 1980's 'is the law' that leads to entirely useless, rude
and incorrect answers.
Replied offlist. I think this thread should stop here. Thank you.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject
your system.
Sigh ... these disclaimers are offensive, even more so when posted on
public mailing lists.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
/DATABASE_README.html for map types overview.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
was the point in keeping home directories
clean?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
nameservers. Do the easy things to improve performance before you try
the difficult ones.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
. As in the
your.domain example, but with localhost for your.domain.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
and relevant snippets from
the map files.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
, and they will at some point fail to
follow the instructions they were given. You'll want to send them a
message telling them that their fax wasn't sent and why, and repeat the
instructions (or link them to a Web page explaining it.)
--
Offlist mail to this address is discarded unless
/dev/rob0
domain).
Is there a standard way ?
Use smtpd_sender_login_maps as already suggested, and ...
http://www.postfix.org/RESTRICTION_CLASS_README.html
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
the LDAP query?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
here.)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
://en.wikipedia.org/wiki/FCrDNS
[1] Strictly speaking, it's $smtp_helo_name which should resolve, but
the default value for smtp_helo_name is $myhostname, and I would
not generally recommend setting smtp_helo_name without good reason.
--
Offlist mail to this address is discarded unless
/dev
On Monday 27 July 2009 18:07:51 ghe wrote:
On 7/27/09 1:45 PM, /dev/rob0 wrote:
[1] Strictly speaking, it's $smtp_helo_name which should resolve, but
the default value for smtp_helo_name is $myhostname, and I would
not generally recommend setting smtp_helo_name without good reason
to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
reduce their number of
Spamhaus queries, or to address the issue of that lag.
permit
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Monday 27 July 2009 16:57:20 mouss wrote:
/dev/rob0 a écrit :
Unfortunately, I have found that many Web programmers don't bother to
read RFC's and find out what characters are allowed in email addresses.
Many sites will not accept a + in your username. I think the old
default qmail
services, and as Magnus noted, DSBL is defunct.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
IN A 174.120.31.226
It resolves fine, here.
As Brian said, find where it came in, if you still think it's
suspicious.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
been
targeted for abuse by 419 scammers in particular.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
was not. That is, you're right, but not
for the reason you thought you were. :) Doing recipient validation is
the socially responsible thing to do, before wasting the RBL's limited
resources.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
here is the result of my postconf -n
Snipped as irrelevant at this point, as you included no logs.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
is merely
regarding a perceived need for this in said README.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
://www.postfix.org/SMTPD_ACCESS_README.html
http://www.postfix.org/access.5.html
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
(paternalism, you might even say), not less.
Good luck.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
thought you wanted to
reject these headers?
See the [!!] for items you might need to provide.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
at it
again! (Don't ask how I know this!)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
mechanism to the search,
and you will probably find the second best answer.
The best answer: refuse to support broken mail clients!
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
a horribly bad headache this very evening, in fact. Just a
coincidence? I doubt it.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
is discarded unless
/dev/rob0 or not-spam is in Subject: header
is discarded unless
/dev/rob0 or not-spam is in Subject: header
://www.postfix.org/TLS_README.html
http://www.postfix.org/postconf.5.html#smtpd_tls_wrappermode
[1] - http://www.postfix.org/SASL_README.html
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
by the
Postfix SASL_README with reference to the Dovecot wiki where needed.
For an excellent SASL+Postfix resource, refer to Patrick Ben Koetter's
online pages and posts here on the mailing list.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
on Suse Linux 9.3
That's pretty old. Postfix 2.2 is no longer maintained. (I think it
will get any security-related attention it might need, but no routine
bugfixes.)
Any ideas?
Don't use procmail if you don't understand it.
--
Offlist mail to this address is discarded unless
/dev/rob0
://www.postfix.org/SASL_README.html#client_sasl
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
in all that?
I (subjectively) think Zen rejects about 75% of all connections that
come to my server. Somehow, real email still seems to get through.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
(5) and not password. The list
has body_checks(5) in place which returned my original reply:
BOUNCE postfix-users@postfix.org: Admin request of
type /^\s*passwd\b/i at line 8. Perhaps this one will suffice.
--
Offlist mail to this address is discarded unless
/dev/rob0
.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
, if using the DNSBL
properly?
The choice is clear, to me.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
unless
/dev/rob0 or not-spam is in Subject: header
and well-reasoned default settings. Leave them alone?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
could be had from simply defining a restriction as a
variable in main.cf.)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
record.)
In your DNS zone file :
relayhost.example.com. MX 10 host1.example.com.
relayhost.example.com. MX 20 host2.example.com.
Or, same priorities if that fits the need better.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject
always mentions version-specific behavior, but it's
probably better to avoid the problem. The documentation that came
with your version was up-to-date for your version.
Thanks for reading.
Good to see you again!
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam
of overriding global DNS for a host
can be had using dnsmasq(8).
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
/local/etc/transport
snip
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
...@domain in alias_maps. My guess would be that you misunderstood
something.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
.
smtpd_sender_restrictions = permit_sasl_authenticated,
permit_mynetworks
Does nothing.
See http://www.postfix.org/SMTPD_ACCESS_README.html for an overview
of access(5) features.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Sunday 06 September 2009 10:41:54 Paul Beard wrote:
On Sep 5, 2009, at 11:20 PM, /dev/rob0 wrote:
(A detailed description of the problem, why your host cannot accept
mail at all, which was snipped.)
Try giving us the complete, non-verbose logs for a mail that
illustrates the problem
and
DEBUG_README) by not posting the logging in question.
If, however, my guess was right, I highly recommend that you stop
Postfix and your httpd+PHP immediately, before any more damage is
done. You might already be blacklisted.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam
.)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
DNSBLs, your
users will find that although they can send mail, no one will get it.
One way or another, you cannot ignore this problem. The sooner you
stop outgoing spam, the more likely that you can repair the damage.
--
Offlist mail to this address is discarded unless
/dev/rob0
to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
, I should have included that this step was also done
and that transport.db exists.
Next step: postconf transport_maps. By default transport_maps is
not set.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Thursday 17 September 2009 13:40:56 Wietse Venema wrote:
/dev/rob0:
On Thursday 17 September 2009 13:02:20 Victor Duchovni wrote:
On Thu, Sep 17, 2009 at 01:59:25PM -0400, fursink wrote:
Would the fact that this is 2.3.3... prevent the transport
from working at all
a spec file if someone has been down
this road.
This comes up on the list regularly, most recently: yesterday! See
the thread with Subject: 2.6 RPM.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
is discarded unless
/dev/rob0 or not-spam is in Subject: header
is not accessible.
Verify is the keyword that you might have missed.
http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
:
bad.example.comREJECT did you mean good.example.com?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
to be certain we are
doing the right things.
Perhaps the person who told you that would work (had been working)
was wrong. See access.5.html , EMAIL ADDRESS PATTERNS, to see what
is looked up for check_sender_access.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam
is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Sunday 04 October 2009 15:57:30 mouss wrote:
/dev/rob0 a écrit :
On Sunday 04 October 2009 11:24:31 mic...@casa.co.cu wrote:
Another subject of consultation, I have implemented bogofilter in
my work, I have been trained according to the documentation at
this point that the messages
to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
who
consider accept-then-bounce a valid way to handle email are now a
small and thoroughly discredited minority.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Sunday 01 November 2009 12:24:54 mouss wrote:
Simon Morvan a écrit :
Le 30/10/2009 16:05, /dev/rob0 a écrit :
[snip]
Consider Zen here. It also incorporates the (not-quite-so) new PBL,
which has been very effective here.
The last time I tried it, Zen included too many legitimate
the OP has figured out something anyway.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Tue, Nov 03, 2009 at 09:26:33AM +, Simon Waters wrote:
On Monday 02 November 2009 20:30:00 /dev/rob0 wrote:
Please note that the question itself is a matter of GIGO. The munged
IP address cannot be in mynetworks according to the postconf shown,
because it was rejected
there is pipe.8.html to set up a transport to external
software.
Of course all the .html references should be on your own machine;
they can also be found at http://www.postfix.org/ .
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
mung a specific email address if desired, but
domain names and IP addresses might be very important.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
and IP addresses might be very important.
One step I neglected to mention in my previous post: postfix stop.
Your damage increases with every spam you send.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
1 - 100 of 1094 matches
Mail list logo
