destination_concurrency_limit to relayhost only
Hi, Our postfix server serves several internal domains and relays outgoing traffic through our ISP SMTP relay server. This external SMTP server is limited to 3 destination domains at the same time. I am wondering if it is possible to set a destination_concurrency_limit of 3 to the relayhost SMTP server *only* and use the default limit for others SMTP servers. I know I can set this limit per domain using a transport map but i have to apply the limit to only a specific host : the relayhost. I'm running postfix 2.9.1 on RHEL 6.3 Thanks for your replies, Victor
Re: Duplicate Emails Sent
Hi Ed, It seems that site3.com smtp server use header recipients instead of SMTP RCPT TO recipients and also send to the sender ... Can you post email headers to check the Received From fields ? Le 18/03/2013 21:51, Ed a écrit : Hi All. The scenario: From: a...@site1.com To: b...@site2.com CC: m...@site3.com After receiving the email CC at site 3, site 3 is sending out emails to everyone on the original, basically a duplicate email arrives to the sender and everyone in the headers. >>a sends mail to b with me in cc. >>me sends mail to everyone in the email headers I am asking how to stop this behavior.? I tried in an earlier attempt to post my postconf contents here but was rejected due to size. Thanks Ed
Re: Migration from Microsoft Exchange Server
Hi Ashok Exchange is a SMTP server and a mailbox system. Postfix is only a SMTP server. If you want to stop using Exchange you may be interested by Zimbra : http://en.wikipedia.org/wiki/Zimbra All Zimbra suites contains a free .exe MS Exchange migration tool to migrate accounts and emails. Postfix is included in Zimbra. Regards, Victor d'Agostino Le 20/03/2013 12:12, Ashok Kumar J a écrit : Hi All, I want to migrate from Microsoft Exchange Server to Postfix mail server. please give your valuable suggestion. -- with regards Ashok Kumar J
Dont add the $myorigin domain to the FROM header field
Hi all, I use postfix as relay server to several internal domains. xxx is the main one. postconfig | grep domain prints : append_dot_mydomain = no mydomain = xxx myorigin = $mydomain relay_domains = $mydomain yyy zzz If postfix receives an email with a FROM (headers and in the SMTP dialog) without @xxx : mars 22 17:17:05 host=127.0.0.1 tls=off auth=off from=Administrateurrecipients= a...@yyy.fr mailsize=72764 smtpstatus=250 smtpmsg='250 2.0.0 Ok: queued as 7C1A472' exitcode=EX_OK Return-Path: Received: [...] Date: 22 Mar 2013 17:17:03 +0100 From: Administrateur To: a...@yyy.fr Subject: aaa [...] it automaticly add @xxx to the FROM header when it transfers the email to the next SMTP server. mars 22 17:17:06 myfinalhost postfix/qmgr[29863]: C0593684F41: from=, size=74777, nrcpt=1 (queue active) I would like to know how to disable this behavior, append_dot_mydomain is already set to no. Regards, Victor
Re: Dont add the $myorigin domain to the FROM header field
2013/3/22 Noel Jones > On 3/22/2013 11:44 AM, Victor d'Agostino wrote: > > Hi all, > > > > I use postfix as relay server to several internal domains. xxx is > > the main one. > > > > postconfig | grep domain prints : > > > > append_dot_mydomain = no > > mydomain = xxx > > myorigin = $mydomain > > relay_domains = $mydomain yyy zzz > > > > If postfix receives an email with a FROM (headers and in the SMTP > > dialog) without @xxx : > > > > mars 22 17:17:05 host=127.0.0.1 tls=off auth=off from=Administrateur > > recipients=a...@yyy.fr <mailto:a...@yyy.fr> mailsize=72764 > > smtpstatus=250 smtpmsg='250 2.0.0 Ok: queued as 7C1A472' exitcode=EX_OK > > > > > > Return-Path: mailto:administrat...@yyy.fr>> > > Received: [...] > > Date: 22 Mar 2013 17:17:03 +0100 > > From: Administrateur > > To: a...@yyy.fr <mailto:a...@yyy.fr> > > Subject: aaa > > [...] > > > > > > it automaticly add @xxx to the FROM header when it transfers the > > email to the next SMTP server. > > > > mars 22 17:17:06 myfinalhost postfix/qmgr[29863]: C0593684F41: > > from=, size=74777, nrcpt=1 (queue active) > > > > > > I would like to know how to disable this behavior, > > append_dot_mydomain is already set to no. > > > > Regards, > > > > Victor > > > > > http://www.postfix.org/ADDRESS_REWRITING_README.html#william > http://www.postfix.org/postconf.5.html#remote_header_rewrite_domain > > When you're using a content_filter, it's often useful to set: > # main.cf > remote_header_rewrite_domain = domain.invalid > > > > -- Noel Jones > Thanks for your reply, I do use a homemade content filter application. So I will try setting : remote_header_rewrite_domain = Victor
Re: Distributed Postfix
2013/3/26 Gaby L > ** > > > > Hi > My teoretic question is how configure multiple (distributed) postfix > mail servers for one domain,which can load balance tasks? (e.g gmail),but > all servers same (unique) users list,alias,rules for one domain? > > Thanks > gaby > > Hi, First, you can easily share or have a clone of /etc/postfix/ (nfs, rsync, etc) and also centralise your /var/log/maillog log file with rsyslog. If you don't need fault tolerance, load balancing is very easy to set with * haproxy* which is a tool to load balance tcp connections. If you do need fault tolerance you can do something like that : We did this in my company but it was pretty useless (50.000 emails per day is not a big deal). I think fault tolerance is more important than load balancing. Regards, Victor d'Agostino
Re: Distributed Postfix
see attachment 2013/3/26 Victor d'Agostino > 2013/3/26 Gaby L > >> ** >> >> >> >> Hi >> My teoretic question is how configure multiple (distributed) postfix >> mail servers for one domain,which can load balance tasks? (e.g gmail),but >> all servers same (unique) users list,alias,rules for one domain? >> >> Thanks >> gaby >> >> > > Hi, > > First, you can easily share or have a clone of /etc/postfix/ (nfs, rsync, > etc) and also centralise your /var/log/maillog log file with rsyslog. > > If you don't need fault tolerance, load balancing is very easy to set with > *haproxy* which is a tool to load balance tcp connections. > > If you do need fault tolerance you can do something like that : > > > We did this in my company but it was pretty useless (50.000 emails per day > is not a big deal). I think fault tolerance is more important than load > balancing. > > Regards, > > Victor d'Agostino > <>
Understanding postfix log
Hello, Can someone explains to me (or give a link) in this log May 15 10:58:13 LXLYOPFD11 postfix/smtp[12232]: B7B1B4800DC: to=< x...@gmail.com>, relay=10.220.8.20[10.220.8.20]:25, conn_use=7, delay=1991, delays=0.06/1990/0/0.66, dsn=2.0.0, status=sent (250 2.0.0 OK 1368608293 fe7si6820218wib.77 - gsmtp) What does "conn_use", "delays=a/b/c/d" and "dsn"means Thanks in advance ! Victor
Re: Understanding postfix log
Thanks for the help Victor 2013/5/15 Wietse Venema > Martin Sch?tte: > > > What does "conn_use", "delays=a/b/c/d" and "dsn"means > > > > http://www.postfix.org/CONNECTION_CACHE_README.html#safety > > > > http://www.postfix.org/postconf.5.html#delay_logging_resolution_limit > > > > http://www.postfix.org/DSN_README.html > > See RFC 3463 for the meaning of the numbers in dsn= logging. > http://tools.ietf.org/html/rfc3463 > > (the "dsn" in dsn=x.y.z is misnamed, but sendmail compatible :-). > > Wietse >
Re: Is it time for 2.x.y -> x.y?
Gentlemen, Don't feed the troll ! Regards, Victor Le 01/06/2013 15:42, Ove Evensen a écrit : I would say keep it as normal. 2.9 and then 2.10. If you can not see the difference between 2.1 and 2.10 you should not use postfix. Period! Regards Ove Jk. Evensen Original message From: Linux Addict Date: 01/06/2013 14:02 (GMT+00:00) To: Len Conrad Cc: postfix-us...@cloud9.net Subject: Re: Is it time for 2.x.y -> x.y? After 2.9, it should have been 3, not 2.10 ;) Sent from my iPhone On Jun 1, 2013, at 8:33 AM, Len Conrad wrote: > At 07:18 AM 6/1/2013, you wrote: >> Am 31.05.2013 22:56, schrieb Wietse Venema: >>> After the confusion that Postfix 2.10 is not Postfix 2.1, maybe it >>> is time to change the release numbering scheme. > > don't dumb postfix down. keep the current numbering style. > > Len > > >
Re: Significantly different date observed in Received and Date fields
Hi, The Date field is client side and may be wrong. Generaly mails are not deffered one month so i guess it is a client misconfiguration... The Received header fields are server side (but can also be modified by filtering application ... as SMTP does not provide any certification of body and headers) so you should trust more Received header. If the system time is wrong, this field will be wrong as postfix use system date and time. Le 25/08/2013 18:15, Mike Seda a écrit : Hi All, I've recently received mail from at least two individuals that contained Received field(s) with dates that significantly differed from that of the Date field. The time difference was approximately 1 month in each case - 1 case was over a month and 1 case was less than a month. Receiving such emails makes it very hard to follow certain conversations. One such example looked like this... Received: Sat, 24 Aug 2013 18:16:40 -0700 (PDT) Date: Thu, 01 Aug 2013 17:52:46 +0200 What would cause such a thing? FYI, one of the aforementioned emails contained headers indicating that the outgoing mail server was Postfix - the other indicated that the outgoing mail server was Exim. I should also add that my domain (that I'm currently receiving mail on) is hosted on Google Apps. I am very curious to hear your thoughts. Mike
Content filtering timeout : How to requeue instead of bouncing ?
Hi all,
I am using an external content_filter script with postfix 2.9.1.
Here is my master.cf :
# filter to a bash file
filterunix - n n - 12 pipe
flags=Rq user=filter null_sender=MAILER-DAEMON
argv=/path/to/script.sh [${sasl_username}] ${client_address}
${sender} ${recipient}
# smtp main interface
25inet n - - -0 smtpd
-o smtpd_sasl_auth_enable=yes
-o smtpd_sasl_security_options=noanonymous
-o
smtpd_client_restrictions=check_client_access,hash:/etc/postfix/access,permit_sasl_authenticated,reject
-o content_filter=filter:dummy
If the filter script timeout (60 minutes by default) the message is
bounced to the sender with the message Command time limit exceeded:
"/path/to/script.sh"
Is it possible to requeue the message instead of bouncing it ?
Regards,
Victor
Ce message et les éventuels documents joints peuvent contenir des informations
confidentielles. Au cas où il ne vous serait pas destiné, nous vous remercions
de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute
utilisation de ce message non conforme à sa destination, toute diffusion ou
publication, totale ou partielle et quel qu'en soit le moyen est formellement
interdite. Les communications sur internet n'étant pas sécurisées, l'intégrité
de ce message n'est pas assurée et la société émettrice ne peut être tenue pour
responsable de son contenu.
Re: Content filtering timeout : How to requeue instead of bouncing ?
Hi again
Well it seems that only "soft_bounce = yes" requeue bounces, but not
only if it is due to a command time limit exceeded.
A solution is to manage the timeout in the filtering application.
In my case, it is a bash script which call it.
So I choose to use the timeout utility (from coreutils) and exit 75
(temporary failure) to requeue the message when a timeout occures :
#!/bin/bash
[...]
/usr/bin/timeout 60m FILTERINGAPP ARGS
if [ $? -eq 124 ]; then
exit 75
fi
[...]
Victor
Message original
*Sujet: *Content filtering timeout : How to requeue instead of bouncing ?
*De : *Victor d'Agostino
*Pour : *postfix-users@postfix.org
*Date : *20/04/2015 10:24
Hi all,
I am using an external content_filter script with postfix 2.9.1.
Here is my master.cf :
# filter to a bash file
filterunix - n n - 12 pipe
flags=Rq user=filter null_sender=MAILER-DAEMON
argv=/path/to/script.sh [${sasl_username}] ${client_address}
${sender} ${recipient}
# smtp main interface
25inet n - - -0 smtpd
-o smtpd_sasl_auth_enable=yes
-o smtpd_sasl_security_options=noanonymous
-o
smtpd_client_restrictions=check_client_access,hash:/etc/postfix/access,permit_sasl_authenticated,reject
-o content_filter=filter:dummy
If the filter script timeout (60 minutes by default) the message is
bounced to the sender with the message Command time limit exceeded:
"/path/to/script.sh"
Is it possible to requeue the message instead of bouncing it ?
Regards,
Victor
Ce message et les éventuels documents joints peuvent contenir des informations
confidentielles. Au cas où il ne vous serait pas destiné, nous vous remercions
de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute
utilisation de ce message non conforme à sa destination, toute diffusion ou
publication, totale ou partielle et quel qu'en soit le moyen est formellement
interdite. Les communications sur internet n'étant pas sécurisées, l'intégrité
de ce message n'est pas assurée et la société émettrice ne peut être tenue pour
responsable de son contenu.
