I've been running Postfix+SpamAssassin+ClamAV for some time quite
successfully as the email gateway for our internal MS-Exchange server.
However, recently, my organization has been looking at setting up a
POP3/IMAP server for one of our domains. We don't need any of
Exchange's features, and frank
Andy Theuninck:
> I'm trying to write a python script that accepts input from pipe. I'm
> encountering permission issues that I don't understand.
>
> According to postfix's configuration, pipe commands are run as
> nobody:nobody. Logging from my script to /tmp agrees confirms this is
> the case.
On 10/15/2010 06:22 PM, Andy Theuninck wrote:
I'm trying to write a python script that accepts input from pipe. I'm
encountering permission issues that I don't understand.
According to postfix's configuration, pipe commands are run as
nobody:nobody.
The documentation doesn't say this /anywhere
On 10/15/2010 06:07 PM, Rafael Andrade wrote:
uid=1001 from=
That looks like somebody is either impersonating on your server, or they
hacked it.
smart:/var/spool/postfix/maildrop# mailq | head
-Queue ID- --Size-- Arrival Time -Sender/Recipient---
3AE78148180 8096 Wed Oct 1
Steve Jenkins:
> Hi, Wietse. Thanks for the speedy reply. I'm a big fan of Postfix, so first
> of all, thank you for developing such a great product. I cringe thinking
> about the days when I used to have to run Sendmail (shudder).
>
> Ok... so let me see if I understand what is happening on my se
On Fri, Oct 15, 2010 at 12:47:31PM -0700, Steve Jenkins wrote:
> 2) My server (familyname.com) accepts the message because mya...@familyname
> is a valid recipient that appears in my virtual aliases file, then forwards
> the message (based on the info in that virtual aliases file) to my aunt's
> a
On Fri, Oct 15, 2010 at 12:42:17PM -0700, Scott Brown wrote:
> Thanks Viktor! For anyone who runs into the same/similar problem: it seems
> no
> more up-to-date yum package is available for CentOS. I found some
> pre-compiled
> packages for CentOS 5 at http://www.linuxmail.info/postfix-rpm-p
Hi, Wietse. Thanks for the speedy reply. I'm a big fan of Postfix, so first
of all, thank you for developing such a great product. I cringe thinking
about the days when I used to have to run Sendmail (shudder).
Ok... so let me see if I understand what is happening on my server.
1) SpamCo forges a
Thanks Viktor! For anyone who runs into the same/similar problem: it seems no
more up-to-date yum package is available for CentOS. I found some pre-compiled
packages for CentOS 5 at http://www.linuxmail.info/postfix-rpm-packages/. I
was
able to do an rpm install of the 2.5.1 postfix package,
Steve Jenkins:
> There are a few entries in there that seem to match the "<>" bill, but I'm
> not sure I'm understanding what they're saying, or even what I should be
> looking for to troubleshoot.
>
> For some background, this is my personal server that I run my family's mail
> on. There are a fe
There are a few entries in there that seem to match the "<>" bill, but I'm
not sure I'm understanding what they're saying, or even what I should be
looking for to troubleshoot.
For some background, this is my personal server that I run my family's mail
on. There are a few local IMAP/POP accounts f
Hi,
today I added full IPv6 support and the amavisd-new bindings. Now it's possible
to have dnswl.py used as policy-service in postfix and if it find a MTA on a
whitelist, it automatically gets soft-whitelisted in amavis (using SQL).
I will put the new version on my side later on.
Have fun
Chr
On Fri, Oct 15, 2010 at 11:22:34AM -0500, Andy Theuninck wrote:
> 4. Cannot write to locations that are group-writable and set to some
> other group - even if the user nobody is part of the relevant group.
Postfix does not initialize secondary groups when running commands as
the $default_privs us
I'm trying to write a python script that accepts input from pipe. I'm
encountering permission issues that I don't understand.
According to postfix's configuration, pipe commands are run as
nobody:nobody. Logging from my script to /tmp agrees confirms this is
the case.
When my script is called by
Hello list,
Im having problems with messages stuck in mailq.
Checking the queue directory in /var/spool/postfix i see all msgs stucks
in maildrop directory:
smart:/var/spool/postfix# du -csh maildrop
158Mmaildrop
t 10 13:14:15 smart postfix/pickup[6447]: warning: C1F0A138163: message
ha
On Fri, Oct 15, 2010 at 08:57:48AM -0700, Scott Brown wrote:
> Anyway, what would be the best way to upgrade?
Read the Postfix release notes. These will highlight any potential
compatibility issues and major changes.
When upgrading from a release this old, yes you do need to stop Postfix
first.
Wietse,
Thanks again for your help. Also thanks to Viktor for his thoughts about the
version.
I checked and I see I do in fact have an old version of postfix installed,
which
is 2.3.3. This is surprising because I installed it using "yum install
postfix", which I had assumed would install the
Steve Jenkins:
> I've read through the readme at:
>
> http://www.postfix.org/BACKSCATTER_README.html
>
> and thought I was doing everything right. but my personal mail server is
> still getting listed at Backscatterer.org. :(
Have you looked in your logfile for mail from <>, that is sent by
your
My New York City client near Penn Station is a leading travel deals and
destination advice publishing firm (online and print). They are seeking a
full-time, on-site, salaried Email Systems Administrator to join their
technology team in the $80,000 to $100,000 range + benefits.
They follow best-
Scott Brown:
> Wietse,
> Awesome response - thank you very much!
>
> You have really demystified a lot of what's going on for me.
>
> I see what you're saying about there being better ways to update the Berkeley
> .db files. It does seem like an upgrade to a less disruptive approach would
> be
ok, i understand you..
Thanks!
2010/10/15 Victor Duchovni
> On Fri, Oct 15, 2010 at 12:46:29PM -0200, maximatt wrote:
>
> > i use postfix v2.4.3 and i have the following error message using
> > "sender_bcc_maps" parameter:
> >
> > Oct 15 12:26:12 maximatt postfix/error[16207]: 8639F66C924: to=<
I've read through the readme at:
http://www.postfix.org/BACKSCATTER_README.html
and thought I was doing everything right. but my personal mail server is
still getting listed at Backscatterer.org. :(
I'm running 2.6.5 and here's my postconf -n:
alias_database = hash:/etc/aliases
alias_maps = has
Wietse,
Awesome response - thank you very much!
You have really demystified a lot of what's going on for me.
I see what you're saying about there being better ways to update the Berkeley
.db files. It does seem like an upgrade to a less disruptive approach would be
in order.
But at the same t
On Fri, Oct 15, 2010 at 12:46:29PM -0200, maximatt wrote:
> i use postfix v2.4.3 and i have the following error message using
> "sender_bcc_maps" parameter:
>
> Oct 15 12:26:12 maximatt postfix/error[16207]: 8639F66C924: to=<
> s...@maximatt.com, sec2>, orig_to=,
> relay=none, delay=0.23,delays=0
On Fri, Oct 15, 2010 at 03:05:33PM +0200, Stefan wrote:
> in the appendix you will find a patch against Postfix 2.7.1 which adds write
> support to Postfix' MySQL client.
>
> If someone like to test it, then he will find Postfix RPMs with MySQL write
> support for recent versions of *SUSE linux
hi...
i use postfix v2.4.3 and i have the following error message using
"sender_bcc_maps" parameter:
Oct 15 12:26:12 maximatt postfix/smtpd[16188]: connect from
maximatt[x.x.x.x]
Oct 15 12:26:12 maximatt postfix/smtpd[16188]: setting up TLS connection
from maximatt.com[x.x.x.x]
Oct 15 12:26:12 ma
On Fri, Oct 15, 2010 at 09:55:07AM -0400, pf at alt-ctrl-del.org wrote:
> Are inline comments in map files ok to use? Will they break anything?
There is no such thing as an in-line comment in a Postfix configuration
file. None are documented, and none exist.
> check_reverse_client_hostname_acces
On Fri, Oct 15, 2010 at 06:43:56AM -0700, Scott Brown wrote:
> The lists of email addresses are in these virtual files,
> defined with this line in main.cf:
> virtual_alias_maps =
> hash:$config_directory/usermanaged/virtual.domain1.com,
> hash:$config_directory/usermanaged/virtual.do
Scott Brown:
> Usually, when the update-postfix.pl script runs, it tells Postfix to shut
> down
> and we get a logged message that says "postfix/postfix-script: stopping the
> Postfix mail system". Right after that, postfix responds with something like
> "postfix/master[11211]: terminating on
Are inline comments in map files ok to use? Will they break anything?
check_reverse_client_hostname_access...
/sip\..*\.bellsouth.net$/ DUNNO #static.bellsouth address
I don't see any errors in the log, but I don't want to create a nightmare later.
Hello,
I'm stuck with a problem where postfix is hanging sometimes when issuing a
"postfix stop" command. In my configuration, I have two domains I'm relaying
mail for with postfix. The lists of email addresses are in these virtual
files,
defined with this line in main.cf:
virtual_alias_maps
Hi list,
in the appendix you will find a patch against Postfix 2.7.1 which adds write
support to Postfix' MySQL client.
If someone like to test it, then he will find Postfix RPMs with MySQL write
support for recent versions of *SUSE linux here:
http://download.opensuse.org/repositories/home:/ru
Thank you Wiese.
On 10/15/2010 12:43 PM, Wietse Venema wrote:
Frank Bonnet:
Hello
Is it possible to check the relay_recipient_maps BEFORE greylisting ?
By default, Postfix rejects unknown recipients at the end of
smtpd_recipient_restrictions, but you can reject them earlier.
See:
http:
Uqlev advised me to use 2048 bit certs... after doing that... just the mail
client has limited to 128 bit session keys with thunderbird for example no
problem to get 256 bit session keys.
Thanks bye!!
El 15/10/2010, a las 11:16, Egoitz Aurrekoetxea Aurre escribió:
> Hi all,
>
> How could
Frank Bonnet:
> Hello
>
> Is it possible to check the relay_recipient_maps BEFORE greylisting ?
By default, Postfix rejects unknown recipients at the end of
smtpd_recipient_restrictions, but you can reject them earlier.
See:
http://www.postfix.org/postconf.5.html#reject_unlisted_recipient
http
Hello
Is it possible to check the relay_recipient_maps BEFORE greylisting ?
Thank you
relay_recipient_maps = hash:/usr/local/etc/postfix/relay_recipients
smtpd_recipient_restrictions =
reject_unknown_recipient_domain,
reject_unauth_pipelining,
permit_mynetworks,
reject_unauth_des
Hi all,
How could I force in postfix to cypher with 256 bits instead of just the 128
minimum default??
Thanks a lot!!
37 matches
Mail list logo
