Re: Trouble with ORCPT variable IN RCPT TO command
-Message d'origine- From: Wietse Venema Sent: Thursday, September 17, 2015 4:13 PM To: Postfix users Subject: Re: Trouble with ORCPT variable IN RCPT TO command Jean-Francois Couture: Last weekend one of our service provider for our application upgraded there email server (Apache JAMES). And now, there telling us that the ORCPT variable is not supported. SMTP servers that announce DSN support and reject ORCPT are BROKEN. You can configure Postfix to pretend that a server does not support DSN. See: http://www.postfix.org/postcon5.5/html#smtp_discard_ehlo_keyword_address_maps http://www.postfix.org/postcon5.5/html#smtp_discard_ehlo_keywords Wietse Thank you, that did the trick. Jeff C.
Trouble with ORCPT variable IN RCPT TO command
Hi, Last weekend one of our service provider for our application upgraded there email server (Apache JAMES). And now, there telling us that the ORCPT variable is not supported. or mail bounces with this error: Sep 15 00:35:40 devsys-prod-com-mta01 postfix/smtp[23429]: D01B34127C: to=u...@provider.com, relay=10.254.254.10[10.254.254.10]:25, conn_use=11, delay=43, delays=40/3.5/0.11/0.08, dsn=5.0.0, status=bounced (host 10.254.254.10[10.254.254.10] said: 504 Unrecognized or unsupported option: ORCPT (in reply to RCPT TO command)) (10.254.254.10 is there internal mail server and we use a VPN to send directly, there email server is not available on direct internet links) I telneted to there server and tried to send commands and sure enough, it rejected the RCPT TO where there was a ORCPT variable here is what I did: MAIL FROM:<u...@email.com> RET=HDRS ENVID=QQ314159 250 2.1.0 Sender <u...@email.com> OK RCPT TO:<u...@email.com> NOTIFY=SUCCESS,DELAY ORCPT=rfc822;u...@email.com <--- this doesn’t work 504 Unrecognized or unsupported option: ORCPT RCPT TO:<<u...@email.com>> NOTIFY=SUCCESS,DELAY <--- this worked without the ORCPT. 250 2.1.5 Recipient <<u...@email.com>> OK I also tried to send a test email with postfix’s ‘sendmail’ command and got the same error in the log file. My question is, Can i strip that variable before relaying the mail to the provider’s server ? Thank you for any help on this. Jeff C. Jean-Francois Couture Administrateur Système Devsys 6775, boul. Henri-Bourassa Québec (Québec) G1H 3C6 Téléphone : (418) 977-4882 Télécopieur: (418) 977-4883 jfcout...@devsys-inf2001.com
Multiple delays based on different domains.
Hi, I need to setup a mail server that will use delays based on domain names. For now, I have a default setup with a transport_map with the domains I need to send emails to. (Those domain are reached by our VPNs). I need to send emails to those domains with a 0s delay and all other emails not in these domain scopes to the outside world (internet) with a 15s delay. The way I see it, I have 2 possibilities: #1 use multiple instances and setup the first one with a 0s delay, use my transport map to send to the preselected domains and send the rest of the emails to a second instance that will insert a 15s delay. #2 Is (and correct me if I missunderstood how this work): In master.cf, setup a second transport name using the smtp transport (ex.): proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp nolimitunix -- n-- smtp - added one and link my already made transport map to the new one AND make a entry in main.cf : nolimit_destination_rate_delay = 0s and set the default like this: default_destination_rate_delay = 3s for the rest of emails. I’d like to setup #2 but i’m not sure if its even possible. So the bottom question is, Can I setup #2 or should I stay away from it and use option #1 ? thank. Jeff C.
Multiple delays based on different domains.
** Sorry if double posting, I think I had the wrong list ** Hi, I need to setup a mail server that will use delays based on domain names. For now, I have a default setup with a transport_map with the domains I need to send emails to. (Those domain are reached by our VPNs). I need to send emails to those domains with a 0s delay and all other emails not in these domain scopes to the outside world (internet) with a 15s delay. The way I see it, I have 2 possibilities: #1 use multiple instances and setup the first one with a 0s delay, use my transport map to send to the preselected domains and send the rest of the emails to a second instance that will insert a 15s delay. #2 Is (and correct me if I missunderstood how this work): In master.cf, setup a second transport name using the smtp transport (ex.): proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp nolimitunix -- n-- smtp - added one and link my already made transport map to the new one AND make a entry in main.cf : nolimit_destination_rate_delay = 0s and set the default like this: default_destination_rate_delay = 3s for the rest of emails. I’d like to setup #2 but i’m not sure if its even possible. So the bottom question is, Can I setup #2 or should I stay away from it and use option #1 ? thank. Jeff C.
Re: Multiple delays based on different domains.
Thank you. I will build my #2 choice then. J-F Couture -Message d'origine- From: Wietse Venema Sent: Thursday, June 07, 2012 2:20 PM To: Postfix users Subject: Re: Multiple delays based on different domains. Jean-Francois Couture: #2 Is (and correct me if I missunderstood how this work): In master.cf, setup a second transport name using the smtp transport (ex.): proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp nolimitunix -- n-- smtp - added one and link my already made transport map to the new one AND make a entry in main.cf : nolimit_destination_rate_delay = 0s and set the default like this: default_destination_rate_delay = 3s for the rest of emails. I?d like to setup #2 but i?m not sure if its even possible. You can have different delays for different mail delivery transports, and you can send different destinations over different transports. Therefore, the two combined will also work. I suggest using smtp_destination_rate_delay = 3s so you won't slow down local mailbox deliveries. Wietse
