Re: outbound source ip adress

Hi! Sorry. am not good at much English. I use postmulti for Multi-Instance. However, an error is output. postmulti -I postfix-msz -G mta -e create postmulti: fatal: instance /postfix/postfix-msz, queue_directory=/ postfix/postfix-msz conflicts with instance /postfix/postfix-msz,

Re: /etc/mailname

Sébastien WENSKE wrote: What should contain this file, local or external fqdn ? Usually the external FQDN that you see when executing: host -t mx example.com (where example.com is your own domain) See 10.3.2 Mailname at http://www.debian.org/doc/manuals/reference/ch-gateway.en.html M.

Re: How to whilelist a host, for which name check fails?

Thank You for Your time and precious to me answer, Sahil: Next time, paste the output of 'postconf -n' instead. But the above Here it is: # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes

Re: Impossible to send mail using SSL for SMTP connection.

Nice to see You here, Mouss! Thank You for Your time and answer, again: Instead of this, use the 3d option: Use the STARTTLS command ... STARTTLS is the standard method for doing SSL/TLS in ESMTP. Ok. So I've done and here what I see: . Client's part: [14:59:19] SMTP 220 The eMail Service

Re: how to bypass milters, whitelist hosts

martin f krafft: also sprach Sahil Tandon sa...@tandon.net [2009.05.23.0037 +0200]: Why are *_checks and *_milters not end-of-data restrictions, or better yet, policy services? One example: 1.2.3.4 is rejected in an access(5) table referenced in smtpd_client_restrictions. Why wait

RE: /etc/mailname

Thanks all. Sebastien -Message d'origine- De : owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] De la part de . Envoyé : samedi 23 mai 2009 09:58 À : Sébastien WENSKE Cc : postfix-users@postfix.org Objet : Re: /etc/mailname Sébastien WENSKE wrote: What should

Re: Impossible to send mail using SSL for SMTP connection.

Sthu Pous: [14:59:19] ESMTP EHLO localhost [14:59:20] ESMTP 250-myhost.org [14:59:20] ESMTP 250-PIPELINING [14:59:20] ESMTP 250-SIZE 3072 [14:59:20] ESMTP 250-VRFY [14:59:20] ESMTP 250-ETRN [14:59:20] ESMTP 250-AUTH PLAIN LOGIN [14:59:20] ESMTP 250-AUTH=PLAIN LOGIN [14:59:20] ESMTP

Re: How to whilelist a host, for which name check fails?

On Sat, 23 May 2009, Sthu Pous wrote: are successfully traversed, the OK does not prevent messages from 1.2.3.4 going to amavisd-new, which is where it seems your problem Well. Is there a mechanism that allows me to whitelist a domain so that all farther actions are not taken? Depends on

delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused

hi today i get alot message like this delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused when the user try to send or get mail messages, this ist mi master.cf ( http://pastie.org/487545 ) and the main.cf ( http://pastie.org/487548 ) any idea what ist

Re: delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused

On Sat, 23 May 2009, Alfredo Andaluz Prado wrote: delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused when the user try to send or get mail messages, and the main.cf ( http://pastie.org/487548 ) Your main.cf contains: content_filter =

Re: how to bypass milters, whitelist hosts

Wietse Venema schrieb: martin f krafft: also sprach Sahil Tandon sa...@tandon.net [2009.05.23.0037 +0200]: Why are *_checks and *_milters not end-of-data restrictions, or better yet, policy services? One example: 1.2.3.4 is rejected in an access(5) table referenced in

Re: Impossible to send mail using SSL for SMTP connection.

Wietse Venema: Sthu Pous: [14:59:19] ESMTP EHLO localhost [14:59:20] ESMTP 250-myhost.org [14:59:20] ESMTP 250-PIPELINING [14:59:20] ESMTP 250-SIZE 3072 [14:59:20] ESMTP 250-VRFY [14:59:20] ESMTP 250-ETRN [14:59:20] ESMTP 250-AUTH PLAIN LOGIN [14:59:20] ESMTP 250-AUTH=PLAIN

Re: Postfix-2.6.0 RPM

sjm...@pobox.com (Simon J Mudd) writes: I'll see if I can make some time to build some 2.6 rpms, but am likely to respond more if there are people who show an interest in these rpms I build. For those interested I've updated the packages and you should be able to find:

Version 2.5.5

I have a test server about ready to become a live server, version 2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would be the latest I want to run? I see http://www.postfix.org/announcements/postfix-2.5.7.html shows what I would call minor issues for the 2.5.7 release set.

Re: Version 2.5.5

Scott Haneda: I have a test server about ready to become a live server, version 2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would be the latest I want to run? Unlike other products, you are not expected to stop using Postfix version X when Postfix version X+1 is

Re: Version 2.5.5

On May 23, 2009, at 5:10 PM, Wietse Venema wrote: Scott Haneda: I have a test server about ready to become a live server, version 2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would be the latest I want to run? Unlike other products, you are not expected to stop using

Re: Version 2.5.5

Scott Haneda wrote: Thank you Wietse. One point of clarification please. If 2.5.7 has defect back ports from 2.6, then that equates to new features brought into 2.5.7? Wietse said: Postfix 2.5.7 has 'defect fixes' back-ported from Postfix 2.6.0. [Emphasis added] Note that he says defect

Re: Version 2.5.5

Scott Haneda: On May 23, 2009, at 5:10 PM, Wietse Venema wrote: Scott Haneda: I have a test server about ready to become a live server, version 2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would be the latest I want to run? Unlike other products, you are not