On Jun 8, 2012, at 02:58, john wrote:
Are there any tools that would help in optimizing/tweaking the Postfix
configuration?
I have found that reading (and understanding) the Postfix documentation
is one of the best tools available, followed by trusting the defaults,
and reading the logs.
With regard to
http://www.mail-archive.com/postfix-users@postfix.org/msg44135.html
I am on the Exim end of this problem, or at least some of the servers I
use are, and I'm having trouble convincing the admins for these Exim
servers that it is a problem they need to fix.
In an attempt to do
Hi Wietse,
[ just subscribed to the list, I realized that our past conversation
was dropped since I was not subscribed, never mind ]
On Thu, Jun 07, 2012 at 08:16:53PM -0400, Wietse Venema wrote:
Willy Tarreau:
Regardless of command format details, if the proxy prepends a command
to the
Replying to myself,
Jun 8 07:10:03 ip-10-160-125-11 postfix/smtp[4735]:
example.com[72.34.48.xxx]:25: DATA
Jun 8 07:10:03 ip-10-160-125-11 postfix/smtp[4735]:
example.com[72.34.48.xxx]:25: 250 OK
I believe that this is the problem, the correct response from the
busted server should
Hello,
i use virtual user and virtual domains in postfix with mysql.
to existing users the mails will be delivered.
but when i create a alias (postfixadmin), the mail is bounced.
Jun 8 10:50:40 mail dovecot: auth-worker: sql(postmas...@zbfxxx.de):
Unknown user
Jun 8 10:50:40 mail
* Marko Weber we...@zackbummfertig.de:
Hello,
i use virtual user and virtual domains in postfix with mysql.
to existing users the mails will be delivered.
but when i create a alias (postfixadmin), the mail is bounced.
Jun 8 10:50:40 mail dovecot: auth-worker: sql(postmas...@zbfxxx.de):
share [fb] share [tw]
This is header of mail that i have received from mailchimp:
Return-Path:
bounce-mc.us2_6034522.1358370-achal.tomar58=gmail@mail76.us2.mcsv.net
Received: from mail76.us2.mcsv.net (mail76.us2.mcsv.net. [173.231.139.76])
by mx.google.com with ESMTP id
A bit of a strange request, but is there a simple way to have Postfix
continually defer mail to a specific recipient, say mail to
'defer.t...@domain.tld' ?
I know with header checks I can do magic like rejecting mail with 5xx
errors, but looking through http://www.postfix.org/header_checks.5.html
On Fri, 2012-06-08 at 11:26 +0100, Sam Jones wrote:
A bit of a strange request, but is there a simple way to have Postfix
continually defer mail to a specific recipient, say mail to
'defer.t...@domain.tld' ?
I know with header checks I can do magic like rejecting mail with 5xx
errors, but
achal tomar:
My query is how they add the received from header to the Return-Path
dyanamically,i also want to implement the same in my mail server,i have
Return-Path is defined in RFC 5321 and RFC 5322. This is the
envelope sender address (MAIL FROM in SMTP).
Wietse
Peter S?rensen:
Hi
I have a policy server restricting access to specific lists. If a
user is accepted the policy server return OK status
to postfix. The members on the list are found through virtual alias
and gets expanded.
I would like to put a content filter after this , that will grab
James:
Replying to myself,
Jun 8 07:10:03 ip-10-160-125-11 postfix/smtp[4735]:
example.com[72.34.48.xxx]:25: DATA
Jun 8 07:10:03 ip-10-160-125-11 postfix/smtp[4735]:
example.com[72.34.48.xxx]:25: 250 OK
I believe that this is the problem, the correct response from the
Willy Tarreau:
Either you need to update the protocol spec (require non-fragmented
proxy lines)
I have mixed opinions on this. On the one hand, we can't really impose
lower layers segmentation behaviour, so from a layering perspective, it
is not correct. On the other hand, the use cases
On 08/06/12 23:15, Wietse Venema wrote:
You're incorrect. With PIPELINING turned on, the first reply after the
client DATA command is the server's response for the client MAIL FROM
command. client: MAIL FROM:sender client: RCPT TO:recipient
client: DATA server: reply for MAIL FROM server:
Achal tomar:
Thanks for telling me about the RFC,but i want to know what configuration
changes i have to do in postfix to achieve my goal.
As per the RFC, Postfix prepends Return-Path: only
when it performs final delivery.
Wietse
James:
On 08/06/12 23:15, Wietse Venema wrote:
You're incorrect. With PIPELINING turned on, the first reply after the
client DATA command is the server's response for the client MAIL FROM
command. client: MAIL FROM:sender client: RCPT TO:recipient
client: DATA server: reply for MAIL
Wietse Venema wrote:
Achal tomar:
Thanks for telling me about the RFC,but i want to know what configuration
changes i have to do in postfix to achieve my goal.
As per the RFC, Postfix prepends Return-Path: only
when it performs final delivery.
Wietse
ok so how can i
On 08/06/12 23:41, Wietse Venema wrote:
This was discussed in my reply three weeks ago.
[...]
Maybe they installed a security firewall that mis-implements
SMTP PIPELINING.
Yes I see now that this is the same issue.
To add some data points, for future googlers if nothing else.
In this
On 6/8/2012 7:47 AM, Achal tomar wrote:
ok so how can i change he return path dynamically for each
user when he/she sends a mail,so that he return path includes his/her
user ID and also the to: header information,i want to do this in
postfix and i am using centOS 5 as an OS.
This is called
Achal tomar:
Thanks for telling me about the RFC,but i want to know what configuration
changes i have to do in postfix to achieve my goal.
Wietse Venema:
As per the RFC, Postfix prepends Return-Path: only
when it performs final delivery.
Achal tomar:
ok so how can i change he return path
Den 2012-06-07 12:56, Nicolae Ghimbovschi skrev:
Yeah, I see that. The file permissions are hardcoded.
That is why I tried to change Postfix's code.
where is the patch ?
mailq | grep mailaddr
postcat -q queueid | less
what more do you need ?
where is the patch ?
The patch used on postfix 2.0.19 is very simple:
mail_stream.c
- || fchmod(vstream_fileno(info-stream), 0700 | info-mode)
+ || fchmod(vstream_fileno(info-stream), 0770 | info-mode)
mailq | grep mailaddr
postcat -q queueid | less
The message processing is
Greetings,
In honor of IPv6 launch day I had figured I would get my mail server
IPv6-capable, but I've run into some trouble. I'm running Postfix 2.9.3
on a RHEL/CentOS 5-like Linux system but smtpd is only listening for
IPv4 connections. main.cf specifies listening everywhere:
Den 2012-06-08 02:58, john skrev:
Are there any tools that would help in optimizing/tweaking the
Postfix configuration?
start with a empty main.cf is my best :=)
since this inhirit optimized defaults, while it keeps dynamic change in
the host autoupdate
in other words, just add lines to
Am 08.06.2012 16:49, schrieb Benny Pedersen:
haveing mynetworks in main.cf is one of the worst if your network does not
contain more then one wan ip
depends
we are using it on all machines running postfix to specify exactly
that LAN ip-addresses from server machines which are allowed to
Michael Tharp:
Greetings,
In honor of IPv6 launch day I had figured I would get my mail server
IPv6-capable, but I've run into some trouble. I'm running Postfix 2.9.3
on a RHEL/CentOS 5-like Linux system but smtpd is only listening for
IPv4 connections. main.cf specifies listening
On 06/08/2012 11:03 AM, Wietse Venema wrote:
inet_interfaces = all
inet_protocols = all
Please show postconf -n output instead of main.cf.
Good idea, this is from postconf -n:
inet_interfaces = all
inet_protocols = ipv4
Curious. If I strace it it doesn't seem to make any socket()
On 06/08/2012 11:45 AM, Victoriano Giralt wrote:
El 08/06/12 17:40, Michael Tharp escribió:
Good idea, this is from postconf -n:
inet_interfaces = all
inet_protocols = ipv4
+^
Does this tell you anything?
Well, I had initially assumed that postfix was seeing my all
Thank you for answer my question
Hotmail email server is just for example. Maybe so many email server that
not in the china have these problems.
The question is, in China, the government have special firewall “ great
firewall of china”, It make me can not reach the mail server who do not put
the
Den 2012-06-08 17:50, Michael Tharp skrev:
Sorry for the noise.
make it like sendmail.m4 ?,here m4 using postconf -e configline, it
works for sendmail, why not for postfix ?, good weekend
I am new to Postfix and I am having trouble getting a feature that I
have working on our existing Sendmail delivery system to function on
the new Postfix delivery system.
Basically, I want all incoming email that does not have a + extension
such as localu...@example.com to deliver to
Michael Tharp:
inet_protocols = all
Wietse:
Please show postconf -n output instead of main.cf.
Michael Tharp:
inet_protocols = ipv4
This is what Postfix uses.
To edit main.cf, use
postconf -e 'inet_protocols = all'
Wietse
Hi!
I'm trying to configure an additional subdomain for the domain I use for
e-mails, but I'm having some trouble with it, 99.9% due to DNS.
Each time I try to send an e-mail outside my network I get the following
error:
myaddr...@gmail.com: host devels.es[78.138.97.64] said:
Nicolás schrieb:
myaddr...@gmail.com: host devels.es[78.138.97.64] said: 550-Verification
failed forn...@subdomain.devels.es 550-The mail server could not
deliver mail
ton...@subdomain.devels.es. The account or domain may not exist,
they may be
blacklisted, or missing the proper
Am 08.06.2012 20:19, schrieb Patrick Westenberg:
Nicolás schrieb:
myaddr...@gmail.com: host devels.es[78.138.97.64] said: 550-Verification
failed forn...@subdomain.devels.es 550-The mail server could not
deliver mail
ton...@subdomain.devels.es. The account or domain may not
El 08/06/2012 19:22, Reindl Harald escribió:
Am 08.06.2012 20:19, schrieb Patrick Westenberg:
Nicolás schrieb:
myaddr...@gmail.com: host devels.es[78.138.97.64] said: 550-Verification
failed forn...@subdomain.devels.es 550-The mail server could not
deliver mail
--On Friday, June 08, 2012 2:07 PM -0400 Wietse Venema
wie...@porcupine.org wrote:
Michael Tharp:
inet_protocols = all
Wietse:
Please show postconf -n output instead of main.cf.
Michael Tharp:
inet_protocols = ipv4
This is what Postfix uses.
To edit main.cf, use
postconf -e
Nicolás schrieb:
myaddr...@gmail.com: host devels.es[78.138.97.64] said: 550-Verification
...
subdomain.devels.es. IN MX 0 mail.devels.es
The response comes from devels.es with 78.138.97.64 but your MX-Records
points to mail.devels.es with 85.155.102.33.
Have you changed the records
El 08/06/2012 19:40, Patrick Westenberg escribió:
Nicolás schrieb:
myaddr...@gmail.com: host devels.es[78.138.97.64] said: 550-Verification
...
subdomain.devels.es. IN MX 0 mail.devels.es
The response comes from devels.es with 78.138.97.64 but your
MX-Records points to mail.devels.es with
This problem has nothing to do with Postfix. I apologize for taking
your time. Nonetheless I am posting the solution here in case someone
else runs into this.
As this is a new server host the appropriate access control list had not
been set on the direct delivery mailboxes for each user. For
On 06/08/2012 04:08 PM, Nicolae Ghimbovschi wrote:
where is the patch ?
The patch used on postfix 2.0.19 is very simple:
mail_stream.c
- || fchmod(vstream_fileno(info-stream), 0700 | info-mode)
+ || fchmod(vstream_fileno(info-stream), 0770 | info-mode)
mailq | grep mailaddr
On 06/06/2012 01:16 PM, Toni Mueller wrote:
Hi,
I recently upgraded a machine from Postfix 2.8 to 2.9. The machine uses,
amongst other things, a custom transport to facilitate masking outgoing
email addresses and sending with SMTP-AUTH.
In main.cf, this looks like follows:
42 matches
Mail list logo
