Zitat von Stan Hoeppner <[EMAIL PROTECTED]>:
Hello fellow smart hosters,
I've been running this way for 3 years now because I could never figure
out how to wildcard "everything else". Here's the top of my transport
file (a very small portion of it):
hardwarefreak.com smtp:[192.168.100.2
Wietse Venema wrote:
Rudy Gevaert:
Hi,
Previously we were running postfix 2.1.5 (Debian Sarge) and now have
upgraded to 2.3.8 (Etch).
We have several lmtp transports in master.cf:
mail1 unix - - n - - lmtp
mail2 unix - - n - -
postfix has defer & deferred queue directories
In what directory are the mails stored when they get deferred due to a
"unknown mail transport" error
I want to keep monitoring mymail server for such mails
Thanks
Ram
* ram <[EMAIL PROTECTED]>:
> postfix has defer & deferred queue directories
>
> In what directory are the mails stored when they get deferred due to a
> "unknown mail transport" error
> I want to keep monitoring mymail server for such mails
Use mailq and/or qshape
--
Ralf Hildebrandt ([EMAI
Dear users,
We have installed postfix 2.4.7 from source with openldap
and cyrus-sasl support. we have also installed openldap 2.3.39 and
cyrus-sasl-2.1.21.
cyrus-sasl is installed in /usr/local/cyrus-sasl directory.
How to tell Postfix to look for cyrus-SASL in this directory ?
Noel Jones wrote:
# main.cf
relayhost = [smtp.sbc.mail.yahoo4.akadns.net]
# transport
hardwarefreak.com smtp:[192.168.100.2]
All mail is sent to the relayhost, except for overrides listed in the
transport map.
Thank you Noel and to others who answered.
Apparently what was breaking thi
On Wed, Aug 06, 2008 at 04:59:48AM -0500, Stan Hoeppner wrote:
>
> And if you mention "man pages" I'll kick you in the teeth Henrik. No
> one would ever write a "how-two" if man pages were the holy grail of
> implementation. And I don't have the time to sift through man pages
> trying to fi
Henrik K wrote:
Sorry if I don't offer sympathies, but Postfix is notoriously well
documented and maintained. A quick look into the man page will show you how
it's spelled.
You missed my point entirely, it seems...
I agree that Postfix should warn in that case.
I don't understand why it do
Stan Hoeppner:
> Henrik K wrote:
> > Sorry if I don't offer sympathies, but Postfix is notoriously well
> > documented and maintained. A quick look into the man page will show you how
> > it's spelled.
>
> You missed my point entirely, it seems...
Take this discussion off-list or I will terminate
[EMAIL PROTECTED] wrote:
Dear users,
We have installed postfix 2.4.7 from source with openldap
and cyrus-sasl support. we have also installed openldap 2.3.39 and
cyrus-sasl-2.1.21.
cyrus-sasl is installed in /usr/local/cyrus-sasl directory.
How to tell Postfix to look for cyrus-SA
On Tue, Aug 5, 2008 at 12:56 PM, Wietse Venema <[EMAIL PROTECTED]> wrote:
> Seblu:
> [ Charset ISO-8859-1 unsupported, converting... ]
>> Hello,
>>
>> i use postfix postfix 2.5.1 on an OpenBSD 4.3 and i have a stange
>> behaviour (for me) with DNS lookup in logs.
>>
>> i've a local dns, which resol
Seblu:
> On Tue, Aug 5, 2008 at 12:56 PM, Wietse Venema <[EMAIL PROTECTED]> wrote:
> > Seblu:
> > [ Charset ISO-8859-1 unsupported, converting... ]
> >> Hello,
> >>
> >> i use postfix postfix 2.5.1 on an OpenBSD 4.3 and i have a stange
> >> behaviour (for me) with DNS lookup in logs.
> >>
> >> i've
Hello,
I am a newbie for advanced Postfix configure, I use Postfix at work
but the setting are given to me. I would like to add a filter but am
having trouble understanding what I need to do. Postfix is a great
tool and very extensive, that being said there are a lot of options/
configurations a
Jamie Bohr:
> Hello,
>
> I am a newbie for advanced Postfix configure, I use Postfix at work
> but the setting are given to me. I would like to add a filter but am
> having trouble understanding what I need to do. Postfix is a great
> tool and very extensive, that being said there are a lot of o
I was looking into doing some tarpit testing and i was wondering if the
implementation of tarpitting built into postfix acts the same way as
"spamd" handles it.
i read a summary for spamd and then read what the postfix configurations
did and it doesn't sound like they do the same thing but the
I already have a program that works externally from Postfix. It is
getting it to work from within Postfix that is the issue. Even the
script from http://www.postfix.org/FILTER_README.html#simple_filter
does not work. I think there is something I need to set something in
main.cf.
I added the fol
Hi all,
I have a machine that is both a postfix mailserver, and a NAT router for
a number of machines behind the box.
Because traffic from machines behind the box can cause the mailserver's
IP to be blacklisted, the mailserver machine has two IP addresses, one
for the mailserver, and one for
Hello.
I'm looking for a solution to desactivate antispam solution for a few
recipients.
By default, spamassassin is activated for all mails, with a rule like:
smtp inet n - n - - smtpd
-o content_filter=spamassassin
I would like to know if you have a solut
Graham Leggett wrote:
Because traffic from machines behind the box can cause the mailserver's
IP to be blacklisted, the mailserver machine has two IP addresses, one
for the mailserver, and one for NAT.
Just to be clear - the box has two public routeable IPs on the same
interface.
The first
On Wed, Aug 6, 2008 at 6:16 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have a machine that is both a postfix mailserver, and a NAT router for a
> number of machines behind the box.
>
> Because traffic from machines behind the box can cause the mailserver's IP
> to be blacklisted
Aaron Wolfe wrote:
What makes you think postfix is choosing the wrong interface?
The Received line added by the upstream mailserver receiving the test
messages from this box clearly shows that it received the email from the
second (NAT) public IP, instead of the primary public IP of the mail
On Wed, Aug 6, 2008 at 6:23 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Graham Leggett wrote:
>
> Because traffic from machines behind the box can cause the mailserver's IP
>> to be blacklisted, the mailserver machine has two IP addresses, one for the
>> mailserver, and one for NAT.
>>
>
> Ju
On Wed, Aug 6, 2008 at 6:48 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Aaron Wolfe wrote:
>
> What makes you think postfix is choosing the wrong interface?
>>
>
> The Received line added by the upstream mailserver receiving the test
> messages from this box clearly shows that it received the
Aaron Wolfe wrote:
If your network is doing things to get itself blacklisted, fix the
problem! Filter outbound SMTP, cleanup your network clients, whatever.
Been there, done that, way ahead of you.
You may not be aware of this, but while filtering outbound SMTP stops
outgoing spam, it does
On Wed, Aug 6, 2008 at 8:28 PM, Wietse Venema <[EMAIL PROTECTED]> wrote:
> Seblu:
>> On Tue, Aug 5, 2008 at 12:56 PM, Wietse Venema <[EMAIL PROTECTED]> wrote:
>> > Seblu:
>> > [ Charset ISO-8859-1 unsupported, converting... ]
>> >> Hello,
>> >>
>> >> i use postfix postfix 2.5.1 on an OpenBSD 4.3 an
Aaron Wolfe wrote:
This doesn't prove Postfiix is using the wrong interface. It simply
means the traffic is seen by the upstream server as coming from the
wrong interface. It is much more likely that your NAT config is wrong
and is SNATing the mail traffic to the same address that it SNATs
On Wed, Aug 6, 2008 at 7:12 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Aaron Wolfe wrote:
>
> If your network is doing things to get itself blacklisted, fix the
>> problem! Filter outbound SMTP, cleanup your network clients, whatever.
>>
>
> Been there, done that, way ahead of you.
>
> You
Graham Leggett:
[ Charset ISO-8859-1 unsupported, converting... ]
> Hi all,
>
> I have a machine that is both a postfix mailserver, and a NAT router for
> a number of machines behind the box.
>
> Because traffic from machines behind the box can cause the mailserver's
> IP to be blacklisted, the
Hi,
until now I worked around the SPF / mail forwarding / envelope-from
problem with using expand_owner_alias and having two local aliases for
every virtual user who wants his mail delivered to another account:
virtual: [EMAIL PROTECTED] john
aliases: john:
Seblu:
>
> and after a test my binary return a good resolution
>
> ./a.out
> server: got connection from 192.42.42.1
> host=toto.titi
>
> and the function gethostbyaddr return also a good answer !
Ok, now you should learn to find out what configuration files
your program uses.
$ krtrace ./a.ou
Aaron Wolfe wrote:
Blocking outbound SMTP traffic from sources other than your mail server
will prevent you from being blacklisted, plain and simple, unless of
course you are sending spam from your mail server.
It's not that simple.
Blocking outbound SMTP traffic keeps you off 99% of blackl
I wrote a tarpitting policy server.
It is patch for postgrey greylisting policy server.
It needs Postfix-2.3.x or more. (use SLEEP action)
taRgrey - S25R + tarpitting + greylisting
http://k2net.hakuba.jp/targrey/index.en.html
http://k2net.hakuba.jp/pub/targrey-0.30-postgrey-1.27.patch
t
On Wed, Aug 6, 2008 at 7:57 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Aaron Wolfe wrote:
>
> Blocking outbound SMTP traffic from sources other than your mail server
>> will prevent you from being blacklisted, plain and simple, unless of course
>> you are sending spam from your mail server.
Hi All, I'm having trouble locking down relaying and I can't see what
I'm doing wrong.
I'm trying to configure the server to only send mail iff:
1. Sender is on mynetworks, or
2. Sender is authenticated
Everything else should be rejected but it isn't, and I can't see whats
wrong with my config.
Aaron Wolfe wrote:
Why can your end users "access an outgoing port"? You are not
addressing this problem at it's source. Police your outbound traffic.
If its from an end user and it isn't bound for port 80 or 443, why are
you allowing the traffic to leave your network?
Because that is thr
Jason Drage <[EMAIL PROTECTED]> wrote:
> Hi All, I'm having trouble locking down relaying and I can't see what
> I'm doing wrong.
>
> I'm trying to configure the server to only send mail iff:
> 1. Sender is on mynetworks, or
> 2. Sender is authenticated
>
> Everything else should be rejected but
Sahil Tandon:
> Jason Drage <[EMAIL PROTECTED]> wrote:
>
> > Hi All, I'm having trouble locking down relaying and I can't see what
> > I'm doing wrong.
> >
> > I'm trying to configure the server to only send mail iff:
> > 1. Sender is on mynetworks, or
> > 2. Sender is authenticated
> >
> > Ever
* Graham Leggett <[EMAIL PROTECTED]>:
> Hi all,
>
> I have a machine that is both a postfix mailserver, and a NAT router for
> a number of machines behind the box.
>
> Because traffic from machines behind the box can cause the mailserver's
> IP to be blacklisted, the mailserver machine has two
38 matches
Mail list logo
