On 1/1/11 9:36 PM, Stan Hoeppner wrote:
Wietse Venema put forth on 1/1/2011 9:50 AM:
Stan Hoeppner:
jason hirsh put forth on 12/31/2010 3:38 PM:
Dec 31 15:24:21 tuna postfix/smtpd[2514]:
asmtpout029.mac.com[17.148.16.104]: 554 5.5.1 Error: no valid recipients
Am I the only one that noticed
On Sat, 1 Jan 2011 21:36:58 -0800
Steve Jenkins st...@stevejenkins.com articulated:
[snip]
In getting our newsletter campaigns ready to send, we believe we've
done everything all the big ESPs ask: a relatively up-to-date version
of Postfix (2.3.3), a dedicated IP with a good reputation and no
Ralf Hildebrandt:
Immediately after I upgraded to postfix-2.8-20110102-nonprod, I got
these errors when connecting to the smtp port:
Jan 2 11:10:23 mail postfix/postfix-script[638]: stopping the Postfix mail
system
Jan 2 11:10:23 mail postfix/master[32086]: terminating on signal 15
Jan
On Sat, 2011-01-01 at 21:36 -0800, Steve Jenkins wrote:
This is a best practices question for other Postfix users who may be using
Postfix to send email to large opt-in mailing lists.
snip
So with all that explained, I have few questions:
1) What's the optimal way for us to process the
Wietse Venema:
I have built an event-driven TLS proxy for postscreen(8). This
addresses the problem that postscreen(8) could not be used when
SMTP clients require STARTTLS support.
This is now a regular snapshot postfix-2.8-20110102. There are no
code changes since the last non-production
Today I encountered this on the python.org mailserver:
Jan 2 14:49:54 albatross postfix/cleanup[5983]: 949B8EE99E: reject mime-error
improper use of 8-bit data in message header: To: Alice Bevan?McGregor
al...@com, web-...@python.org from localhost[127.0.0.1];
from=p...@com
* Ralf Hildebrandt ralf.hildebra...@charite.de:
On the other hand I'm wondering what that invalid 8-bit character
might be, since it LOOKS like a space in the bounce I got from pje.
It was a strange hyphen.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité -
/var/tmp/postfix-2.8-20110102/src/cleanup/cleanup_message.c
src/cleanup/cleanup_message.c
*** /var/tmp/postfix-2.8-20110102/src/cleanup/cleanup_message.c Tue Jul 27
16:34:20 2010
--- src/cleanup/cleanup_message.c Sun Jan 2 17:00:13 2011
***
*** 880,885
--- 880,886
/body_checks.
This is not needed. Postfix should already report one MIME error
to the SMTP client, as long as the message has no other reject
errors.
Wietse
diff -cr /var/tmp/postfix-2.8-20110102/src/cleanup/cleanup_message.c
src/cleanup/cleanup_message.c
*** /var/tmp/postfix-2.8-20110102
Hello,
Should I look in the source or is there a better location to change the
texts returned by Postfix after the error code for a connecting MTA? I'd
like to give custom messages back for (example) a failed rDNS check or helo
check. I don't want to change the returned number (421 or 550 if I'm
Mark Scholten:
Hello,
Should I look in the source or is there a better location to change the
texts returned by Postfix after the error code for a connecting MTA? I'd
like to give custom messages back for (example) a failed rDNS check or helo
check. I don't want to change the returned
On 1/2/2011 10:12 PM, Wietse Venema wrote:
Mark Scholten:
Hello,
Should I look in the source or is there a better location to change the
texts returned by Postfix after the error code for a connecting MTA? I'd
like to give custom messages back for (example) a failed rDNS check or helo
check. I
On 1/2/2011 10:36 PM, Jerrale G wrote:
On 1/2/2011 10:12 PM, Wietse Venema wrote:
Mark Scholten:
Hello,
Should I look in the source or is there a better location to change the
texts returned by Postfix after the error code for a connecting MTA?
I'd
like to give custom messages back for
On Monday 03 January 2011 04:12:46 Wietse Venema wrote:
Mark Scholten:
Hello,
Should I look in the source or is there a better location to change the
texts returned by Postfix after the error code for a connecting MTA? I'd
like to give custom messages back for (example) a failed rDNS
14 matches
Mail list logo
