Rewriting question

[Adrian P. van Bloois]

Hi All,
I'd like to catch ALL mail addressed to someth...@somedomain.blad and
rewrite that to something@certaindomain.
The point is .bla, I don't know what's in front of this. rH
how can I best do that?

Regards
Adrian


-- 
Adri P. van Bloois
Antonlaan 104   email:  adr...@pa0rda.nl
3701 VG Zeist   voice:  +31-(0)-30-6912741
The Netherlands fax:NONE

52 05'15.77"N 5 4'44.56"E
QTH-locater  JO 22 OC

The whole point of cooking is to get as much flavour out of the
ingredients as possible.
-- Delia Smith


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Local and Virtual Mail Delivery?

[Stan Hoeppner]

On 11/14/2011 1:10 PM, Edward Carraro wrote:

> I am using the Postfix 2.7.1 package that comes with Debian squeeze.

Note that 2.8.3 has been available for a while now in squeeze-backports.
 I installed it Oct 15 simply for access to the new permit_dnswl_client
parm.

-- 
Stan

Re: Rewriting question

[Stan Hoeppner]

On 11/15/2011 3:44 AM, Adrian P. van Bloois wrote:
> Hi All,
> I'd like to catch ALL mail addressed to someth...@somedomain.blad and
> rewrite that to something@certaindomain.
> The point is .bla, I don't know what's in front of this. rH
> how can I best do that?

The first step is to coherently explain to us exactly what you are
trying to accomplish.

-- 
Stan

Re: Rewriting question

[Claudio Kuenzler]

Hi Adrian

You can try to do this with smtp_generic_maps or if you only want to
rewrite the recipient address you can also use recipient_canonical_maps.
There's a lot of possibilities how to do that, depends on what you want to
achieve in detail.

http://www.postfix.org/postconf.5.html#smtp_generic_maps
http://www.postfix.org/postconf.5.html#recipient_canonical_maps

On Tue, Nov 15, 2011 at 12:34 PM, Stan Hoeppner wrote:

> On 11/15/2011 3:44 AM, Adrian P. van Bloois wrote:
> > Hi All,
> > I'd like to catch ALL mail addressed to someth...@somedomain.blad and
> > rewrite that to something@certaindomain.
> > The point is .bla, I don't know what's in front of this. rH
> > how can I best do that?
>
> The first step is to coherently explain to us exactly what you are
> trying to accomplish.
>
> --
> Stan
>

can't send mail between multiple postfix instances

[Amira Othman]

Hi all

I am using postfix 2.8 and I have configured two instances of postfix each
of them uses different ip and domain . The two instances are running but
when I try to send e-mail from one to another I get this error
status=deferred (connect to myserver2.com[192.168.1.11]:25: Connection
refused)

 

The configurationm as follows:

First Instance (postfix)

alias_database = hash:/etc/aliases

alias_maps = hash:/etc/aliases

broken_sasl_auth_clients = yes

command_directory = /usr/sbin

config_directory = /etc/postfix

daemon_directory = /usr/libexec/postfix

data_directory = /var/lib/postfix

disable_dns_lookups = yes

disable_vrfy_command = yes

home_mailbox = Maildir/

html_directory = no

inet_interfaces = 192.168.56.102,127.0.0.1

local_recipient_maps = proxy:unix:passwd.byname,
$alias_maps,$virtual_mailbox_maps

local_transport = local

mail_owner = postfix

mail_spool_directory = /var/spool/mail

mailbox_command = /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME

mailq_path = /usr/bin/mailq

manpage_directory = /usr/share/man

multi_instance_directories = /etc/postfix-out

multi_instance_enable = yes

multi_instance_wrapper = ${command_directory}/postmulti -p --

mydestination = localhost

mydomain = myserver.com

myhostname = mail.mysever.com

mynetworks = 192.168.56.0/24, 127.0.0.0/8

myorigin = $mydomain

newaliases_path = /usr/bin/newaliases

queue_directory = /var/spool/postfix

readme_directory = no

relay_domains =

sample_directory = /etc/postfix

sendmail_path = /usr/sbin/sendmail

setgid_group = postdrop

smtp_bind_address = 192.168.56.102

smtp_host_lookup = native

smtpd_banner = $myhostname ESMTP

smtpd_sasl_auth_enable = yes

smtpd_sasl_path = private/auth

smtpd_sasl_security_options = noanonymous

smtpd_sasl_type = dovecot

transport_maps = hash:/etc/postfix/transport

unknown_local_recipient_reject_code = 450

virtual_alias_maps = hash:/etc/postfix/virtual

virtual_gid_maps = static:501

virtual_mailbox_base = /home/vmail/

virtual_mailbox_domains = myserver.com,tech-vm.com

virtual_mailbox_maps = hash:/etc/postfix/vmailbox

virtual_minimum_uid = 500

virtual_transport = virtual

virtual_uid_maps = static:501

 

Second instance (postfix-out)

alias_database = hash:/etc/aliases

alias_maps = hash:/etc/aliases

authorized_submit_users =

broken_sasl_auth_clients = yes

command_directory = /usr/sbin

config_directory = /etc/postfix-out/

daemon_directory = /usr/libexec/postfix

data_directory = /var/lib/postfix-out

debug_peer_level = 2

disable_dns_lookups = yes

disable_vrfy_command = yes

home_mailbox = Maildir/

html_directory = no

inet_interfaces = 192.168.1.11

local_recipient_maps = proxy:unix:passwd.byname,
$alias_maps,$virtual_mailbox_maps

local_transport = local

mail_owner = postfix

mail_spool_directory = /var/spool/mail

mailbox_command = /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME

mailq_path = /usr/bin/mailq

manpage_directory = /usr/share/man

master_service_disable = inet

multi_instance_enable = yes

multi_instance_name = postfix-out

mydestination = localhost

mydomain = myserver2.com

myhostname = mail.mysever2.com

mynetworks = 192.168.1.0/24

myorigin = $mydomain

newaliases_path = /usr/bin/newaliases

queue_directory = /var/spool/postfix-out

readme_directory = no

relay_domains =

sample_directory = /etc/postfix

sendmail_path = /usr/sbin/sendmail

setgid_group = postdrop

smtp_bind_address = 192.168.1.11

smtp_host_lookup = native

smtpd_banner = $myhostname ESMTP

smtpd_sasl_auth_enable = yes

smtpd_sasl_authenticated_header = yes

smtpd_sasl_path = private/auth

smtpd_sasl_security_options = noanonymous

smtpd_sasl_type = dovecot

transport_maps = hash:/etc/postfix-out/transport

unknown_local_recipient_reject_code = 550

virtual_alias_maps = hash:/etc/postfix-out/virtual

virtual_gid_maps = static:501

virtual_mailbox_base = /home/vmail/

virtual_mailbox_domains = myserver2.com

virtual_mailbox_maps = hash:/etc/postfix-out/vmailbox

virtual_minimum_uid = 500

virtual_transport = virtual

virtual_uid_maps = static:501

 

 

regards

 

 

Re: can't send mail between multiple postfix instances

[Benny Pedersen]

On Tue, 15 Nov 2011 14:17:39 +0200, Amira Othman wrote:

error status=deferred (connect to myserver2.com[192.168.1.11]:25:
Connection refused)


netstat -natpu | grep -r ':25'

does it listen ?

Re: Rewriting question

[Noel Jones]

On 11/15/2011 3:44 AM, Adrian P. van Bloois wrote:
> Hi All,
> I'd like to catch ALL mail addressed to someth...@somedomain.blad and
> rewrite that to something@certaindomain.
> The point is .bla, I don't know what's in front of this. rH
> how can I best do that?
> 
>   Regards
>   Adrian
> 
> 


The general answer is to use a regexp or pcre table.  For a more
specific answer, we would need to know *exactly* what you're trying
to rewrite and why it needs rewriting.

http://www.postfix.org/ADDRESS_REWRITING_README.html
http://www.postfix.org/regexp_table.5.html
http://www.postfix.org/pcre_table.5.html



  -- Noel Jones

smtpd_reject_footer not showing original error message in Outlook

[Jeetu]

Hi,

I'm using postfix v2.8.6 with
smtpd_reject_footer = Please see http://goo.gl/xxx for explanation of 
the problem


Now the problem is i get the original error message like "User unknown 
in virtual alias table" with Thunderbird and Roundcube with the above link.


But if use MS outlook i don't get original error message
i get a bounce back as

The following recipient(s) cannot be reached:

's...@xx.com' on 11/8/2011 4:20 PM
554 5.5.1 Please see
http://goo.gl/xxx for explanation of the problem.

--
-Jeetu


--
Powered by BigRock

Re: smtpd_reject_footer not showing original error message in Outlook

[Wietse Venema]

Jeetu:
> Hi,
> 
> I'm using postfix v2.8.6 with
> smtpd_reject_footer = Please see http://goo.gl/xxx for explanation of 
..
> But if use MS outlook i don't get original error message
> i get a bounce back as
> 
> The following recipient(s) cannot be reached:
> 
> 's...@xx.com' on 11/8/2011 4:20 PM
> 554 5.5.1 Please see
> http://goo.gl/xxx for explanation of the problem.

You mean, The Postfix response is this:

554-5.1.1  Recipient address rejected: user unknown in etc.
554 5.1.1 Please see http://goo.gl/xxx for explanation of the problem. 

But MS Outlook reports only text from the last line (I still hope
they translated the 5.1.1 as "there is a problem with the email
address").

There are two solutions: (1) don't use software that thrashes
multi-line responses, and (2) don't send multi-line responses.

The options for the second solution are: (2a) don't send reply
footers, and (2b) combine error response and footer text into one
line.

Considering that multi-line responses were standardized in 1982,
and that other mail servers also send multi-line RCPT TO responses,
it is just a matter of time before we will reach state (1). If the
issue really bothers you, I suggest option (2a).

Wietse

Re: can't send mail between multiple postfix instances

[Viktor Dukhovni]

On Tue, Nov 15, 2011 at 02:17:39PM +0200, Amira Othman wrote:

> I am using postfix 2.8 and I have configured two instances of postfix each
> of them uses different ip and domain . The two instances are running but
> when I try to send e-mail from one to another I get this error
> status=deferred (connect to myserver2.com[192.168.1.11]:25: Connection
> refused)

The documentation for multiple instances clearly explains that the initial
settings for a new instance of Postfix include "master_service_disable =
inet". You need to remove this setting once the instance is fully configured
if it is to be used to receive traffic via SMTP.

> Second instance (postfix-out)
> 
> inet_interfaces = 192.168.1.11
> master_service_disable = inet
> multi_instance_enable = yes
> multi_instance_name = postfix-out

Do read the documentation carefully, there may be other issues
you've overlooked.

http://www.postfix.org/MULTI_INSTANCE_README.html

-- 
Viktor.

Two outgoing IP addresses on one postfix instance

[Marcin Hlybin]

Hello,

I am trying to add the second IP address to the same Postfix instance. I would 
like to separate mail traffic not creating many postfix instances.

In master.cf I have:

1.2.3.4:smtp inet n - - - - smtpd -o myhostname=mail1.domain.com 
1.2.3.5:smtp inet n - - - - smtpd -o myhostname=mail2.domain.com 

smtp unix - - - - - smtp -o smtp_bind_address=1.2.3.4
smtplist unix - - - - - smtp -o smtp_bind_address=1.2.3.5

Now, I can't set up a transport map because I don't want to specify origin 
domains.
My postfix works as a mail server for web applications.

Every mail that goes to 1.2.3.4 (mali1.domain.com) should go out with smtp 
transport and every mail that goes to 1.2.3.5 (mail2.domain.com) should go out 
with smtplist transport.

That is, every mail going to specific IP should go out with the same IP.
How can I do that?





-- 
Marcin Hlybin
http://twitter.com/marcinhlybin

Re: Two outgoing IP addresses on one postfix instance

[Jeroen Geilman]

On 2011-11-15 17:52, Marcin Hlybin wrote:

Hello,

I am trying to add the second IP address to the same Postfix instance. I would 
like to separate mail traffic not creating many postfix instances.

In master.cf I have:

1.2.3.4:smtp inet n - - - - smtpd -o myhostname=mail1.domain.com
1.2.3.5:smtp inet n - - - - smtpd -o myhostname=mail2.domain.com

smtp unix - - - - - smtp -o smtp_bind_address=1.2.3.4
smtplist unix - - - - - smtp -o smtp_bind_address=1.2.3.5

Now, I can't set up a transport map because I don't want to specify origin 
domains.
My postfix works as a mail server for web applications.

Every mail that goes to 1.2.3.4 (mali1.domain.com) should go out with smtp 
transport and every mail that goes to 1.2.3.5 (mail2.domain.com) should go out 
with smtplist transport.

That is, every mail going to specific IP should go out with the same IP.
How can I do that?



This is not possible in a single instance.

--
J.

Re: Two outgoing IP addresses on one postfix instance

[Wietse Venema]

Marcin Hlybin:
> Hello,
> 
> I am trying to add the second IP address to the same Postfix
> instance. I would like to separate mail traffic not creating many
> postfix instances.

The problem that you describe is exactly what multiple instances
are supposed to solve. 

You can kludge this up with "smtpd -o content_filter=smtplist:",
but that is just a kludge, and it requires Postfix 2.7 or later.

Wietse

> In master.cf I have:
> 
> 1.2.3.4:smtp inet n - - - - smtpd -o myhostname=mail1.domain.com 
> 1.2.3.5:smtp inet n - - - - smtpd -o myhostname=mail2.domain.com 
> 
> smtp unix - - - - - smtp -o smtp_bind_address=1.2.3.4
> smtplist unix - - - - - smtp -o smtp_bind_address=1.2.3.5
> 
> Now, I can't set up a transport map because I don't want to specify origin 
> domains.
> My postfix works as a mail server for web applications.
> 
> Every mail that goes to 1.2.3.4 (mali1.domain.com) should go out with smtp 
> transport and every mail that goes to 1.2.3.5 (mail2.domain.com) should go 
> out with smtplist transport.
> 
> That is, every mail going to specific IP should go out with the same IP.
> How can I do that?
> 
> 
> 
> 
> 
> -- 
> Marcin Hlybin
> http://twitter.com/marcinhlybin
> 
> 
> 

mime header checks

[K bharathan]

hi all
added a following regular expression for mime_header check

/^Subject:.*LOANS OFFER/ REJECT spam #1
 if i understand correctly cleanup service is doing the rejection;  how can
i stop notify the sender; is there any difference in mime_header check and
header_check
request for some clarity on the above
thanks

-bharathan

Re: mime header checks

[Jeroen Geilman]

On 2011-11-15 21:13, K bharathan wrote:

hi all
added a following regular expression for mime_header check

/^Subject:.*LOANS OFFER/ REJECT spam #1
 if i understand correctly cleanup service is doing the rejection;  
how can i stop notify the sender; is there any difference in 
mime_header check and header_check


header_checks and mime_header_checks do exactly what they say.
If your header checks reject mail, the sender will be notified.

If this is not what you want to do, specify a different action, such as 
DISCARD.



--
J.

Special character in email ID

[Justin]

New to postfix please bare with us. :)


We like to accept special 
characters in email id so surrounding the  email names with "", but 
still these emails are sent to fallback maildir.

Followed this man page --> http://www.postfix.org/aliases.5.html
The name is a local address (no domain part).  Use  double quotes  when the 
name contains any special characters such
as whitespace, `#', `:', or `@'. The  name  is  folded  to lowercase, in order 
to make database lookups case insensi- tive.


E.g., $firstem...@box.com, &tes...@mail.com, #t...@ju.com

Wrapped them as "$firstemail"@box.com, "&testem"@mail.com, "#test"@ju.com as 
well    "$firstem...@box.com"  - but no use.

Hmm...any thing else need to take care of ???


postfix
 version 2.4

postconf -n

alias_maps = pgsql:/etc/postfix.myd/dl.exp.pgsql, 
pgsql:/etc/postfix.myd/pdl.pgsql, regexp:/etc/postfix.myd/empty.dl.regexp
alternate_config_directories
 = /etc/postfix.myd /etc/postfix.dropbox /etc/postfix.out 
/etc/postfix.forward /etc/postfix.active /etc/postfix.fallback
bounce_queue_lifetime = 3d
bounce_template_file = /etc/postfix.myd/bounce.cf
command_directory = /usr/sbin
config_directory = /etc/postfix.myd
daemon_directory = /usr/libexec/postfix
default_destination_concurrency_limit = 50
default_destination_recipient_limit = 100
default_process_limit = 500
fast_flush_domains = hash:/etc/postfix.myd/nexthop.transport
header_address_token_limit = 16
header_size_limit = 1048576
home_mailbox = Maildir/
mail_owner = postfix
mailbox_size_limit = 0
mailbox_transport = virtual
manpage_directory = /usr/local/man
maximal_queue_lifetime = 30d
message_size_limit
 = 1048576000
mydestination =
mydomain = qa.myorg.com
myhostname = bobby.qa.myorg.com
mynetworks = xx.
myorigin = $myhostname
notify_classes = resource,software
proxy_interfaces = xx.
queue_directory = /var/spool/postfix.myd
readme_directory = /etc/postfix.myd
relay_domains =
relayhost = 127.0.0.1:10037
sample_directory = /etc/postfix.myd
sender_dependent_relayhost_maps = hash:/etc/postfix.myd/active_user.relay
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtp_connect_timeout = 10s
smtp_destination_recipient_limit = $default_destination_recipient_limit
smtp_tls_CAfile =
 /etc/postfix.myd/certs/ca-bundle.crt
smtp_tls_cert_file = /etc/postfix.myd/certs/server.crt
smtp_tls_key_file = /etc/postfix.myd/certs/server.key
smtp_tls_loglevel = 1
smtp_tls_per_site = hash:/etc/postfix/tls_per_site, static:MAY
smtp_tls_session_cache_timeout =
 3600s
smtpd_etrn_restrictions = permit_mynetworks, reject
syslog_name = postfix-myd
transport_maps
 = regexp:/etc/postfix.myd/myd.transport.regexp, 
hash:/etc/postfix.myd/vp.transport, 
hash:/etc/postfix.myd/active.transport, 
hash:/etc/postfix.myd/fallback.transport, 
hash:/etc/postfix.myd/external.transport
unknown_local_recipient_reject_code = 450
virtual_alias_maps
 = regexp:/etc/postfix.myd/my_domain_aliases.regexp, 
hash:/etc/postfix.myd/virtual_users, 
hash:/etc/postfix.myd/virtual_dlists, hash:/etc/postfix.myd/dropboxes, 
regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
regexp:/etc/postfix.myd/unrewrite.regexp
virtual_gid_maps = static:10219
virtual_mailbox_base = /myd
virtual_mailbox_domains = mail.dir d.list pd.list
virtual_mailbox_limit = 1048576000
virtual_mailbox_maps = regexp:/etc/postfix/virtual_mailbox.regexp
virtual_minimum_uid = 1
virtual_transport = virtual
virtual_uid_maps =
 static:10219

Re: Special character in email ID

[Brian Evans - Postfix List]

On 11/15/2011 3:48 PM, Justin wrote:
> New to postfix please bare with us. :)
>
> We like to accept special characters in email id so surrounding the 
> email names with "", but still these emails are sent to fallback maildir.
>
> Followed this man page --> http://www.postfix.org/aliases.5.html
> The name is a local address (no domain part).  Use  double quotes 
> when the name contains any special characters such
You missed this valuable part of this line   "(no domain part)"

> as whitespace, `#', `:', or `@'. The  name  is  folded  to lowercase,
> in order to make database lookups case insensi- tive.
>
>
> E.g., $firstem...@box.com ,
> &tes...@mail.com , #t...@ju.com
> 
>
> Wrapped them as "$firstemail"@box.com, "&testem"@mail.com,
> "#test"@ju.com as well"$firstem...@box.com"  - but no use.
Aliases allows "$firstemail" or "&testem" or "#test". You MUST NOT
include the domain part.

As always, aliases(5) maps are only used for those users that are
delivered by the local(8) delivery agent.

Brian

Re: mime header checks

[K bharathan]

On Tue, Nov 15, 2011 at 10:47 PM, Jeroen Geilman  wrote:

> On 2011-11-15 21:13, K bharathan wrote:
>
>> hi all
>> added a following regular expression for mime_header check
>>
>> /^Subject:.*LOANS OFFER/ REJECT spam #1
>>  if i understand correctly cleanup service is doing the rejection;  how
>> can i stop notify the sender; is there any difference in mime_header check
>> and header_check
>>
>
> header_checks and mime_header_checks do exactly what they say.
> If your header checks reject mail, the sender will be notified.
>
> If this is not what you want to do, specify a different action, such as
> DISCARD.
>
>
> --
> J.
>
> thanks i'll try discard action

i've put two checks together as follows in the main.cf:

mime_header_checks = pcre:/etc/postfix/mime_header_checks
header_checks = regexp:/etc/postfix/header_checks

if i put the expression /^Subject:.*LOANS OFFER/ REJECT  in header_checks
it does not work but if i put the same  in mime_header_checks it works
even though  maps are different;  i think i miss soemthing obvious

RE: reject_non_fqdn_helo_hostname usefulness, safety

[Murray S. Kucherawy]

Just heard back from them:


"Murray, FYI, I was just notified by the correct person within eBay that this 
is being fixed now.  Thank you again for forwarding it along."



-MSK


From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] 
On Behalf Of Murray S. Kucherawy
Sent: Friday, November 11, 2011 11:47 PM
To: Steve Fatula; simon.brere...@buongiorno.com; postfix users
Subject: RE: reject_non_fqdn_helo_hostname usefulness, safety

I've forwarded this to some standards and practices compliance people inside 
eBay/PayPal.  I bet they'll be quite interested.   I know that they were 
planning to do some work on their DK/DKIM infrastructure at some point.  Maybe 
this was a side-effect.

Will advise when they reply.

-MSK

From: owner-postfix-us...@postfix.org 
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Steve Fatula
Sent: Thursday, November 10, 2011 9:04 PM
To: simon.brere...@buongiorno.com; 
postfix users
Subject: Re: reject_non_fqdn_helo_hostname usefulness, safety

From: Simon Brereton 
mailto:simon.brere...@buongiorno.com>>
To: postfix users mailto:postfix-users@postfix.org>>
Sent: Thursday, November 10, 2011 9:26 PM
Subject: Re: reject_non_fqdn_helo_hostname usefulness, safety



Write them a note with the RFC I say.  Standards are no good if you
let yours slip because it's Ebay.  or Google.  or InsetBrandnamehere.
I did exactly that. Have not heard back yet, if I ever will. I included some 
sample log messages so they could see some of the servers with the bad HELO 
name, not all of them have it, and of course the relevant RFC section. They had 
some Paypal/Ebay troubles today as well (some payments could not be made via 
Ebay checkout), and, I see they are making announced website changes starting 
tonight as well. Perhaps it was a lot of work and they just screwed up. 
Hopefully, some one who knows something will read the email and actually do 
something! I did whitelist them in the meantime to avoid the check.

Re: Special character in email ID

[Justin]

Brian, Thanks for the reply.

We have put quotes surrounded the mail name part only excluded the domain and 
made sure that main.cf has

resolve_dequoted_address as yes


We receive email from external sources and postfix forwards to our local mail 
store, here is the value of
"virtual_alias_maps" in main.cf


virtual_alias_maps = regexp:/etc/postfix.myd/my_domain_aliases.regexp, 
hash:/etc/postfix.myd/virtual_users, hash:/etc/postfix.myd/virtual_dlists, 
hash:/etc/postfix.myd/dropboxes, 
regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
regexp:/etc/postfix.myd/unrewrite.regexp

Sample virtual_users fragment
"#criticalema...@mydomain.com"   ms23/007/000/002/106/@mail.dir
"#criticalema...@mydomain.another.com"  ms23/007/000/002/106/@mail.dir

postmap creates virtual_users.db file using virtual_users and uses for lookup.

My perception is during the lookup it is not able to resolve the email to 
corresponding maildir, hence routing to fallback maildir rather than bouncing 
it back.(we don't want it to get bounce that part is fine).


Please let me know for more info.



From: Brian Evans - Postfix List 
To: postfix-users@postfix.org
Sent: Tuesday, November 15, 2011 2:58 PM
Subject: Re: Special character in email ID

On 11/15/2011 3:48 PM, Justin wrote:
> New to postfix please bare with us. :)
>
> We like to accept special characters in email id so surrounding the 
> email names with "", but still these emails are sent to fallback maildir.
>
> Followed this man page --> http://www.postfix.org/aliases.5.html
> The name is a local address (no domain part).  Use  double quotes 
> when the name contains any special characters such
You missed this valuable part of this line   "(no domain part)"

> as whitespace, `#', `:', or `@'. The  name  is  folded  to lowercase,
> in order to make database lookups case insensi- tive.
>
>
> E.g., $firstem...@box.com ,
> &tes...@mail.com , #t...@ju.com
> 
>
> Wrapped them as "$firstemail"@box.com, "&testem"@mail.com,
> "#test"@ju.com as well    "$firstem...@box.com"  - but no use.
Aliases allows "$firstemail" or "&testem" or "#test". You MUST NOT
include the domain part.

As always, aliases(5) maps are only used for those users that are
delivered by the local(8) delivery agent.

Brian

Re: Special character in email ID

[Jeroen Geilman]

On 2011-11-15 23:14, Justin wrote:

Brian, Thanks for the reply.

We have put quotes surrounded the mail name part only excluded the 
domain and made sure that main.cf has

resolve_dequoted_address as yes*
*

We receive email from external sources and postfix forwards to our 
local mail store, here is the value of

"virtual_alias_maps" in main.cf

virtual_alias_maps = regexp:/etc/postfix.myd/my_domain_aliases.regexp, 
hash:/etc/postfix.myd/virtual_users, 
hash:/etc/postfix.myd/virtual_dlists, hash:/etc/postfix.myd/dropboxes, 
regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
regexp:/etc/postfix.myd/unrewrite.regexp


Sample virtual_users fragment
"#criticalema...@mydomain.com"   ms23/007/000/002/106/@mail.dir
"#criticalema...@mydomain.another.com"  ms23/007/000/002/106/@mail.dir

postmap creates virtual_users.db file using virtual_users and uses for 
lookup.


There is no reference to virtual_users in the above virtual_alias_maps.

I think you are confusing virtual_alias_maps and virtual_mailbox_maps; 
this is not uncommon.


For a virtual address to be delivered to a virtual mailbox, the domain 
in question must be present in virtual_mailbox_domains AND the address 
must resolve to a mailbox in virtual_mailbox_maps.


Use

postmap -q "query" maptype:/map/location

to validate your maps.

--
J.

Re: reject_non_fqdn_helo_hostname usefulness, safety

[Steve Fatula]

From: Murray S. Kucherawy 
>To: Steve Fatula ; "simon.brere...@buongiorno.com" 
>; postfix users 
>Sent: Tuesday, November 15, 2011 3:19 PM
>Subject: RE: reject_non_fqdn_helo_hostname usefulness, safety
>
>
>Just heard back from them:
> 
>“Murray, FYI, I was just notified by the correct person within eBay that this 
>is being fixed now.  Thank you again for forwarding it along.”
> 
>-MSK
>   You must know the right guy! They ignored me. Feeling insignificant. ;-)

Re: Special character in email ID

[Justin]

Thanks a lot, mean while i will validate using postmap command,iassume the bold 
text is the reference ??


virtual_alias_maps = 
regexp:/etc/postfix.myd/my_domain_aliases.regexp,hash:/etc/postfix.myd/virtual_users,
 hash:/etc/postfix.myd/virtual_dlists, hash:/etc/postfix.myd/dropboxes, 
regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
regexp:/etc/postfix.myd/unrewrite.regexp



From: Jeroen Geilman 
To: postfix-users@postfix.org
Sent: Tuesday, November 15, 2011 4:18 PM
Subject: Re: Special character in email ID


On 2011-11-15 23:14, Justin wrote: 
Brian, Thanks for the reply.
>
>
>We have put quotes surrounded the mail name part only excluded the domain and 
>made sure that main.cf has
>
>resolve_dequoted_address as yes
>
>
>
>We receive email from external sources and postfix forwards to our local mail 
>store, here is the value of
>"virtual_alias_maps" in main.cf
>
>
>
>virtual_alias_maps = regexp:/etc/postfix.myd/my_domain_aliases.regexp, 
>hash:/etc/postfix.myd/virtual_users, hash:/etc/postfix.myd/virtual_dlists, 
>hash:/etc/postfix.myd/dropboxes, 
>regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
>regexp:/etc/postfix.myd/unrewrite.regexp
>
>
>Sample virtual_users fragment
>"#criticalema...@mydomain.com"   ms23/007/000/002/106/@mail.dir
>"#criticalema...@mydomain.another.com"  ms23/007/000/002/106/@mail.dir
>
>
>postmap creates virtual_users.db file using virtual_users and uses for lookup.
There is no reference to virtual_users in the above
virtual_alias_maps.

I think you are confusing virtual_alias_maps and
virtual_mailbox_maps; this is not uncommon.

For a virtual address to be delivered to a virtual mailbox, the
domain in question must be present in virtual_mailbox_domains AND
the address must resolve to a mailbox in virtual_mailbox_maps.

Use 

    postmap -q "query" maptype:/map/location

to validate your maps.


-- 
J.

Re: Special character in email ID

[Jeroen Geilman]

On 2011-11-15 23:36, Justin wrote:
Thanks a lot, mean while i will validate using postmap command,iassume 
the bold text is the reference ??


Yes, it is; it was buried beneath the irrelevance.

As I said before, virtual_alias_maps does not concern virtual *mailboxes*.



virtual_alias_maps = 
regexp:/etc/postfix.myd/my_domain_aliases.regexp,hash:/etc/postfix.myd/virtual_users, 
hash:/etc/postfix.myd/virtual_dlists, hash:/etc/postfix.myd/dropboxes, 
regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
regexp:/etc/postfix.myd/unrewrite.regexp



*From:* Jeroen Geilman 
*To:* postfix-users@postfix.org
*Sent:* Tuesday, November 15, 2011 4:18 PM
*Subject:* Re: Special character in email ID

On 2011-11-15 23:14, Justin wrote:

Brian, Thanks for the reply.

We have put quotes surrounded the mail name part only excluded the 
domain and made sure that main.cf  has

resolve_dequoted_address as yes*
*

We receive email from external sources and postfix forwards to our 
local mail store, here is the value of

"virtual_alias_maps" in main.cf

virtual_alias_maps = 
regexp:/etc/postfix.myd/my_domain_aliases.regexp, 
hash:/etc/postfix.myd/virtual_users, 
hash:/etc/postfix.myd/virtual_dlists, 
hash:/etc/postfix.myd/dropboxes, 
regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
regexp:/etc/postfix.myd/unrewrite.regexp


Sample virtual_users fragment
"#criticalema...@mydomain.com"  
ms23/007/000/002/106/@mail.dir 
"#criticalema...@mydomain.another.com" 
 
ms23/007/000/002/106/@mail.dir 


postmap creates virtual_users.db file using virtual_users and uses 
for lookup.


There is no reference to virtual_users in the above virtual_alias_maps.

I think you are confusing virtual_alias_maps and virtual_mailbox_maps; 
this is not uncommon.


For a virtual address to be delivered to a virtual mailbox, the domain 
in question must be present in virtual_mailbox_domains AND the address 
must resolve to a mailbox in virtual_mailbox_maps.


Use

postmap -q "query" maptype:/map/location

to validate your maps.

--
J.





--
J.

Re: Special character in email ID

[Justin]

postconf -n gave the following

virtual_mailbox_maps = regexp:/etc/postfix/v_m_box.regexp

Content is 

if /@mail\.dir$/
/^(.*)@mail\.dir$/ $1
endif

i guess this may confirm the mailbox a valid one.

Any other info do i need to look into?

TIA



From: Jeroen Geilman 
To: postfix-users@postfix.org
Sent: Tuesday, November 15, 2011 4:38 PM
Subject: Re: Special character in email ID


On 2011-11-15 23:36, Justin wrote: 
Thanks a lot, mean while i will validate using postmap command,iassume the bold 
text is the reference ??
>
Yes, it is; it was buried beneath the irrelevance.

As I said before, virtual_alias_maps does not concern virtual
*mailboxes*.



>
>virtual_alias_maps = 
>regexp:/etc/postfix.myd/my_domain_aliases.regexp,hash:/etc/postfix.myd/virtual_users,
> hash:/etc/postfix.myd/virtual_dlists, hash:/etc/postfix.myd/dropboxes, 
>regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
>regexp:/etc/postfix.myd/unrewrite.regexp
>
>
>
>
>From: Jeroen Geilman 
>To: postfix-users@postfix.org
>Sent: Tuesday, November 15, 2011 4:18 PM
>Subject: Re: Special character in email ID
>
>
>On 2011-11-15 23:14, Justin wrote: 
>Brian, Thanks for the reply.
>>
>>
>>We have put quotes surrounded the mail name part only excluded the domain and 
>>made sure that main.cf has
>>
>>resolve_dequoted_address as yes
>>
>>
>>
>>We receive email from external sources and postfix forwards to our local mail 
>>store, here is the value of
>>"virtual_alias_maps" in main.cf
>>
>>
>>
>>virtual_alias_maps = regexp:/etc/postfix.myd/my_domain_aliases.regexp, 
>>hash:/etc/postfix.myd/virtual_users, hash:/etc/postfix.myd/virtual_dlists, 
>>hash:/etc/postfix.myd/dropboxes, 
>>regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
>>regexp:/etc/postfix.myd/unrewrite.regexp
>>
>>
>>Sample virtual_users fragment
>>"#criticalema...@mydomain.com"   ms23/007/000/002/106/@mail.dir
>>"#criticalema...@mydomain.another.com"  ms23/007/000/002/106/@mail.dir
>>
>>
>>postmap creates virtual_users.db file using virtual_users and uses for lookup.
>There is no reference to virtual_users in the above
virtual_alias_maps.
>
>I think you are confusing virtual_alias_maps and
virtual_mailbox_maps; this is not uncommon.
>
>For a virtual address to be delivered to a virtual
mailbox, the domain in question must be present in
virtual_mailbox_domains AND the address must resolve to
a mailbox in virtual_mailbox_maps.
>
>Use 
>
>    postmap -q "query" maptype:/map/location
>
>to validate your maps.
>
>
>-- 
J.
>
>


-- 
J.

Re: Special character in email ID

[Jeroen Geilman]

On 2011-11-16 00:03, Justin wrote:

postconf -n gave the following

virtual_mailbox_maps = regexp:/etc/postfix/v_m_box.regexp

Content is
if /@mail\.dir$/
/^(.*)@mail\.dir$/ $1
endif

i guess this may confirm the mailbox a valid one.

Any other info do i need to look into?


I am not sure what the question is.

The observed behaviour corresponds with the configuration; if that is 
not what you intended, we will need more specific details on what you 
did intend.



--
J.

Re: Special character in email ID

[Justin]

Thank Jeroen.

I have executed the postmap command against the virtual_users, when i issue

postmap -q testu...@mydomain.com /etc/postfix/virtual_users it gives me the 
corresponding maildir value but when i say

postmap -q #criticalema...@mydomain.com/etc/postfix/virtual_users  --- syntax 
wrong


postmap -q "#criticalema...@mydomain.com"/etc/postfix/virtual_users  --- no 
result


postmap -q ""#criticalema...@mydomain.com""/etc/postfix/virtual_users  --- no 
result



Now the question boils down to how to give escape characters in this case to 
query the map??



Here is my sample virtual_users fragment
"#criticalema...@mydomain.com"   ms23/007/000/002/106/@mail.dir
"#criticalema...@mydomain.another.com"  ms23/007/000/002/106/@mail.dir
testu...@mydomain.com   ms11/007/000/002/108/@mail.dir




From: Jeroen Geilman 
To: postfix-users@postfix.org
Sent: Tuesday, November 15, 2011 4:38 PM
Subject: Re: Special character in email ID


On 2011-11-15 23:36, Justin wrote: 
Thanks a lot, mean while i will validate using postmap command,iassume the bold 
text is the reference ??
>
Yes, it is; it was buried beneath the irrelevance.

As I said before, virtual_alias_maps does not concern virtual
*mailboxes*.



>
>virtual_alias_maps = 
>regexp:/etc/postfix.myd/my_domain_aliases.regexp,hash:/etc/postfix.myd/virtual_users,
> hash:/etc/postfix.myd/virtual_dlists, hash:/etc/postfix.myd/dropboxes, 
>regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
>regexp:/etc/postfix.myd/unrewrite.regexp
>
>
>
>
>From: Jeroen Geilman 
>To: postfix-users@postfix.org
>Sent: Tuesday, November 15, 2011 4:18 PM
>Subject: Re: Special character in email ID
>
>
>On 2011-11-15 23:14, Justin wrote: 
>Brian, Thanks for the reply.
>>
>>
>>We have put quotes surrounded the mail name part only excluded the domain and 
>>made sure that main.cf has
>>
>>resolve_dequoted_address as yes
>>
>>
>>
>>We receive email from external sources and postfix forwards to our local mail 
>>store, here is the value of
>>"virtual_alias_maps" in main.cf
>>
>>
>>
>>virtual_alias_maps = regexp:/etc/postfix.myd/my_domain_aliases.regexp, 
>>hash:/etc/postfix.myd/virtual_users, hash:/etc/postfix.myd/virtual_dlists, 
>>hash:/etc/postfix.myd/dropboxes, 
>>regexp:/etc/postfix.myd/dropboxes.subdomains.regexp, 
>>regexp:/etc/postfix.myd/unrewrite.regexp
>>
>>
>>Sample virtual_users fragment
>>"#criticalema...@mydomain.com"   ms23/007/000/002/106/@mail.dir
>>"#criticalema...@mydomain.another.com"  ms23/007/000/002/106/@mail.dir
>>
>>
>>postmap creates virtual_users.db file using virtual_users and uses for lookup.
>There is no reference to virtual_users in the above
virtual_alias_maps.
>
>I think you are confusing virtual_alias_maps and
virtual_mailbox_maps; this is not uncommon.
>
>For a virtual address to be delivered to a virtual
mailbox, the domain in question must be present in
virtual_mailbox_domains AND the address must resolve to
a mailbox in virtual_mailbox_maps.
>
>Use 
>
>    postmap -q "query" maptype:/map/location
>
>to validate your maps.
>
>
>-- 
J.
>
>


-- 
J.

Re: Special character in email ID

[Jeroen Geilman]

On 2011-11-16 00:20, Justin wrote:

Thank Jeroen.

I have executed the postmap command against the virtual_users, when i 
issue


postmap -q testu...@mydomain.com /etc/postfix/virtual_users it gives 
me the corresponding maildir value


No, it does not - since this is a virtual ALIAS map, and not a mailbox map.


but when i say

postmap -q #criticalema...@mydomain.com 
/etc/postfix/virtual_users  --- 
syntax wrong


You'd need to quote the address localpart, as per the RFC.



postmap -q "#criticalema...@mydomain.com" 
/etc/postfix/virtual_users  --- 
no result


Meaning no match was found.



postmap -q ""#criticalema...@mydomain.com"" 
/etc/postfix/virtual_users  --- 
no result


Meaning no match was found.




Now the question boils down to how to give escape characters in this 
case to query the map??


The first example - double qoutes - will work fine.

I am still unclear what it is you want to achieve with all this; it is 
difficult to advise you to do anything until you explain this.



--
J.

Re: Special character in email ID

[Justin]

I apologize i have not included what are all combinations i have triednone 
worked, all i'm trying to do is
if the key has '#' in it how you query using postmap.



[root@myserv~]# postmap -q "#criticalemail1"@mydomain.com 
/etc/postfix/virtual_users

[root@myserv~]# postmap -q "##criticalemail1"@mydomain.com 
/etc/postfix/virtual_users

[root@myserv~]# postmap -q ""#criticalemail1""@mydomain.com 
/etc/postfix/virtual_users

[root@myserv~]# postmap -q #criticalema...@mydomain.com 
/etc/postfix/virtual_users
postmap: option requires an argument -- q
postmap: fatal: usage: postmap [-Nfinoprsvw] [-c config_dir] [-d key] [-q key] 
[map_type:]file...

[root@myserv~]# postmap -q "#"criticalema...@mydomain.com 
/etc/postfix/virtual_users
postmap: warning: database /etc/postfix/virtual_users.db is older than source 
file /etc/postfix/virtual_users

[root@myserv~]# postmap -q "#"criticalema...@mydomain.com 
/etc/postfix/virtual_users
postmap: warning: database /etc/postfix/virtual_users.db is older than source 
file /etc/postfix/virtual_users

[root@myserv~]# postmap /etc/postfix/virtual_users

[root@myserv~]# postmap -q "#"criticalema...@mydomain.com 
/etc/postfix/virtual_users

[root@myserv~]# postmap -q #criticalema...@mydomain.com 
/etc/postfix/virtual_users
postmap: option requires an argument -- q
postmap: fatal: usage: postmap [-Nfinoprsvw] [-c config_dir] [-d key] [-q key] 
[map_type:]file...

[root@myserv~]# postmap -q ""#criticalemail1""@mydomain.com 
/etc/postfix/virtual_users



Here is my sample virtual_users fragment
"#criticalemail1"@mydomain.com   ms23/007/000/002/106/@mail.dir
"#criticalemail1"@mydomain.another.com  
ms23/007/000/002/106/@mail.dirtestu...@mydomain.com   
ms11/007/000/002/108/@mail.dir






From: Jeroen Geilman 
To: postfix-users@postfix.org
Sent: Tuesday, November 15, 2011 5:29 PM
Subject: Re: Special character in email ID


On 2011-11-16 00:20, Justin wrote: 
Thank Jeroen.
>
>
>I have executed the postmap command against the virtual_users, when i issue
>
>
>postmap -q testu...@mydomain.com /etc/postfix/virtual_users it gives me the 
>corresponding maildir value 
No, it does not - since this is a virtual ALIAS map, and not a
mailbox map.


but when i say
>
>
>postmap -q #criticalema...@mydomain.com/etc/postfix/virtual_users  --- syntax 
>wrong
>
You'd need to quote the address localpart, as per the RFC.



>
>postmap -q "#criticalema...@mydomain.com"/etc/postfix/virtual_users  --- no 
>result
>
Meaning no match was found.



>
>postmap -q ""#criticalema...@mydomain.com""/etc/postfix/virtual_users  --- no 
>result
>
Meaning no match was found.



>
>
>
>Now the question boils down to how to give escape characters in this case to 
>query the map??
>
The first example - double qoutes - will work fine.

I am still unclear what it is you want to achieve with all this; it
is difficult to advise you to do anything until you explain this.



-- 
J.

./postconf: fatal: socket: Protocol not supported

[Sahil Tandon]

This error was reported to me by a FreeBSD user, but I cannot reproduce
it on any of my development machines.  It occurs during build (sorry for
line wraps):

 rm -f ../../conf/main.cf.default
 cp postconf ../../bin
 (echo "# DO NOT EDIT THIS FILE. EDIT THE MAIN.CF FILE INSTEAD. THE";
 echo "# TEXT HERE JUST SHOWS DEFAULT SETTINGS BUILT INTO POSTFIX.";
 echo "#";  ./postconf -d) |egrep -v '^(myhostname|mydomain|mynetworks) '
 >../../conf/main.cf.default
 ./postconf: fatal: socket: Protocol not supported

... the full log is also available[1].  This is snapshot 20111012.
FWIW, this issue was recently discussed[2] on a FreeBSD mailing list.
There is something particular about the machine (to which I do not have
access) on which the build fails.  Has anyone seen similar socket errors
via postconf?  My next step is to solicit access to the problematic
machine and troubleshoot further.

[1] 
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.2003071512/postfix-current-2.9.20111012,4.log
[2] http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071419.html

-- 
Sahil Tandon

Re: ./postconf: fatal: socket: Protocol not supported

[Wietse Venema]

Sahil Tandon:
> This error was reported to me by a FreeBSD user, but I cannot reproduce
> it on any of my development machines.  It occurs during build (sorry for
> line wraps):
> 
>  rm -f ../../conf/main.cf.default
>  cp postconf ../../bin
>  (echo "# DO NOT EDIT THIS FILE. EDIT THE MAIN.CF FILE INSTEAD. THE";
>  echo "# TEXT HERE JUST SHOWS DEFAULT SETTINGS BUILT INTO POSTFIX.";
>  echo "#";  ./postconf -d) |egrep -v '^(myhostname|mydomain|mynetworks) '
>  >../../conf/main.cf.default
>  ./postconf: fatal: socket: Protocol not supported
> 
> ... the full log is also available[1].  This is snapshot 20111012.
> FWIW, this issue was recently discussed[2] on a FreeBSD mailing list.
> There is something particular about the machine (to which I do not have
> access) on which the build fails.  Has anyone seen similar socket errors
> via postconf?  My next step is to solicit access to the problematic
> machine and troubleshoot further.
> 
> [1] 
> http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.2003071512/postfix-current-2.9.20111012,4.log
> [2] http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071419.html

Postconf opens a socket to determine the mynetworks value (it
determines the local interfaces and their netmasks). 

I have heard about bizarre errors on FreeBSD (jail) systems where
the user-land library was out of sync with kernel-land, resulting
in data structure mis-matches and system calls returning nonsensical
results.

Wietse

Re: ./postconf: fatal: socket: Protocol not supported

[Sahil Tandon]

On Tue, 2011-11-15 at 20:41:08 -0500, Wietse Venema wrote:

> Sahil Tandon:
> > This error was reported to me by a FreeBSD user, but I cannot reproduce
> > it on any of my development machines.  It occurs during build (sorry for
> > line wraps):
> > 
> >  rm -f ../../conf/main.cf.default
> >  cp postconf ../../bin
> >  (echo "# DO NOT EDIT THIS FILE. EDIT THE MAIN.CF FILE INSTEAD. THE";
> >  echo "# TEXT HERE JUST SHOWS DEFAULT SETTINGS BUILT INTO POSTFIX.";
> >  echo "#";  ./postconf -d) |egrep -v '^(myhostname|mydomain|mynetworks) '
> >  >../../conf/main.cf.default
> >  ./postconf: fatal: socket: Protocol not supported

[ .. ]

> Postconf opens a socket to determine the mynetworks value (it
> determines the local interfaces and their netmasks). 
> 
> I have heard about bizarre errors on FreeBSD (jail) systems where the
> user-land library was out of sync with kernel-land, resulting in data
> structure mis-matches and system calls returning nonsensical results.

Thanks for the quick reply.

-- 
Sahil Tandon

450 4.7.1 Client host rejected

[Reindl Harald]

Hi

is there any good reason why this is rejected with 450 instead 5xx to
tell the sending server "do not try again with your config"?

Nov 16 03:53:37 mail postfix/smtpd[15778]: NOQUEUE: reject: RCPT from 
unknown[193.83.162.5]: 450 4.7.1 Client host
rejected: cannot find your reverse hostname, [193.83.162.5]



signature.asc
Description: OpenPGP digital signature

Re: 450 4.7.1 Client host rejected

[Amedeo Rinaldo]

Il 16/11/2011 03:58, Reindl Harald ha scritto:

Hi
is there any good reason why this is rejected with 450 instead 5xx to
tell the sending server "do not try again with your config"?

Nov 16 03:53:37 mail postfix/smtpd[15778]: NOQUEUE: reject: RCPT from 
unknown[193.83.162.5]: 450 4.7.1 Client host
rejected: cannot find your reverse hostname, [193.83.162.5]



Because PTR/DNS "no response / error" could be temporary..



Amedeo Rinaldo
--
Una volta eliminato l'impossibile, quello che resta, per improbabile che 
sia, deve essere la verità  (Sherlock Holmes)

Re: 450 4.7.1 Client host rejected

[/dev/rob0]

On Tuesday 15 November 2011 20:58:32 Reindl Harald wrote:
> is there any good reason why this is rejected with 450 instead 5xx
> to tell the sending server "do not try again with your config"?
> 
> Nov 16 03:53:37 mail postfix/smtpd[15778]: NOQUEUE: reject: RCPT
> from unknown[193.83.162.5]: 450 4.7.1 Client host rejected: cannot
> find your reverse hostname, [193.83.162.5]

postconf.5.html#unknown_client_reject_code
postconf.5.html#reject_unknown_client_hostname
-- 
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header

Re: 450 4.7.1 Client host rejected

[Sahil Tandon]

On Wed, 2011-11-16 at 03:58:32 +0100, Reindl Harald wrote:

> is there any good reason why this is rejected with 450 instead 5xx to
> tell the sending server "do not try again with your config"?

Yes, and that reason is documented in postconf(5).

> Nov 16 03:53:37 mail postfix/smtpd[15778]: NOQUEUE: reject: RCPT from
> unknown[193.83.162.5]: 450 4.7.1 Client host rejected: cannot find
> your reverse hostname, [193.83.162.5]

 http://www.postfix.org/postconf.5.html#reject_unknown_reverse_client_hostname
 http://www.postfix.org/postconf.5.html#unknown_client_reject_code

-- 
Sahil Tandon


pgpR0UVO8YFyj.pgp
Description: PGP signature