Question

Help needed with virtual users / local relaying in postifx + dovecot

Asked by: Havin_it

Hello,

I've set up a simple mailserver on Gentoo Linux which uses the following components:

- fetchmail to receive from various POP3 accounts on the Internet
- dovecot-1.1_rc4 to deliver (using its own LDA and virtual users) and serve mail by IMAP
- postfix to route outgoing mail from the IMAP clients to my ISP's SMTP server (clients authenticate to postfix using dovecot-sasl; postfix uses cyrus-sasl to auth with the ISP server)

All is working well so far, but I want to make an addition. I want mail sent from one of the local accounts (whose "From:" address will be that of the external POP3 address) to one of the others (again, "to:" being the external address) to be routed directly back to LDA to the appropriate local mailbox instead of going out via the Internet and coming back.

My additional hope is that if I can make this work, I can also allow local daemons to send log/alert emails to one of these addresses.

I have had a stab at it, using the howto on dovecot's wiki, but with what I have currently, the emails I send are getting bounced with a "unknown user" message.

I've added the postfix and dovecot configs in the code-listing below. Hope it's clear enough; please let me know any other stuff you might need to see.

Hope somebody can help!

# section from /etc/postfix/main.cf
dovecot   unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${recipient}
 
--------------------------
# /etc/postfix/main.cf
queue_directory = /var/spool/postfix
command_directory = /usr/sbin
daemon_directory = /usr/lib/postfix
data_directory = /var/lib/postfix
mail_owner = postfix
myhostname = brazil
mydomain = localdomain
dovecot_destination_recipient_limit = 1
virtual_mailbox_domains = popaccount1.net, popaccount2.co.uk
virtual_transport = dovecot
virtual_mailbox_maps = hash:/etc/postfix/virtual
unknown_local_recipient_reject_code = 550
mynetworks = 192.168.2.0/28, 192.168.10.0/28, 127.0.0.0/8
relayhost = [post.demon.co.uk]
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_security_options =
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
smtpd_sasl_auth_enable = yes
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
debug_peer_level = 2
debugger_command =
         PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
         ddd $daemon_directory/$process_name $process_id & sleep 5
sendmail_path = /usr/sbin/sendmail
newaliases_path = /usr/bin/newaliases
mailq_path = /usr/bin/mailq
setgid_group = postdrop
html_directory = /usr/share/doc/postfix-2.5.1/html
manpage_directory = /usr/share/man
sample_directory = /etc/postfix
readme_directory = /usr/share/doc/postfix-2.5.1/readme
home_mailbox = .maildir/
 
# NB - pop3 domains changed for anonymity. 'brazil' is the machine's hostname but it has no FQDN.
 
--------------------------------------------
# /etc/dovecot/dovecot.conf
 
disable_plaintext_auth = no
log_path = /var/log/dovecot.log
info_log_path = /var/log/dovecot-info.log
ssl_disable = yes
ssl_cert_file = /etc/ssl/dovecot/server.pem
ssl_key_file = /etc/ssl/dovecot/server.key
mail_location = maildir:~/.maildir
dotlock_use_excl = yes
maildir_copy_with_hardlinks = yes
protocol imap {
}
protocol pop3 {
}
protocol managesieve {
  sieve=~/.dovecot.sieve
  sieve_storage=~/sieve
}
protocol lda {
  postmaster_address = postmaster@example.com
  mail_plugins = cmusieve
  mail_plugin_dir = /usr/lib/dovecot/lda
  sieve_global_path = /home/vmail/sieve
}
auth default {
  mechanisms = plain
  socket listen {
    master {
      path = /var/run/dovecot/auth-master
      mode = 0600
      user = vmail # User running deliver
    }
    client {
      path = /var/spool/postfix/private/auth
      mode = 0660
      user = postfix
      group = postfix
    }
  }
  passdb passwd-file {
    args = /etc/dovecot/passwd
  }
  userdb static {
    args = uid=vmail gid=vmail home=/home/vmail/%u
  }
  user = root
}
dict {
}
plugin {
}

                                  
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:

Select allOpen in new window

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2008-04-03 at 08:38:44ID23293166
Tags

postfix

,

2.5.1

Topics

Email Servers

,

Simple Mail Transfer Protocol (SMTP)

,

Linux

Participating Experts
1
Points
0
Comments
14

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. SMTP error bounces sender's email to us - whose serve…
    (We are running GW 6.5.) There are about 20 people in a particular civic group in our town. One of our engineers (Susan Richard) is a member. When a specific person (lambservices.com) in this group emails the entire list, her message is bounced back to her by about 4 other...
  2. Exchange 2003 relaying ( Bounce Attacks??)
    Ok here is the breakdown. We have a exchange 2003 box that is only open on port 25 to our third party spam filtering company- Postini( on a specific range of ip's ) . All mail is routed through them to us .In order to allow outbound filtering we had to allow a reinjection hos...
  3. SMTP Relay via DMZ
    Good day experts -- I've got a Exchange BE to SMTP/IIS FE relay question that I couldn't find out there... Scenario: BE Exchange 2003 Server on private network relays outgoing email via DMZ. Mail gateway is IIS 6.0 running and SMTP VS. Mail is then forwarded out to the int...
  4. Bounced emails
    Hi I run SBS 2003 with an exchange server, to send mail I use AuthSmtp which I find to be pretty good however recently i have been getting this message from them and I dont really understand what I need to do, can anyone point me in the right direction? 'AuthSMTP account: x...
  5. SMTP Relay
    Ok, I know this has probably been answered 1000 time here, but humor me as I make sure I understand Exchange 2000 SMTP Relay. I have and exchange server sitting on my active directory domain, domain1.com and domain2.com. My domain is behind a firewall via NAT. Domain1.com...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: ahoffmannPosted on 2008-04-03 at 22:50:38ID: 21279310

AFAIK you need something like
   virtual_maps = hash:/etc/postfix/virtual
beside (what you already have):
   virtual_mailbox_maps = hash:/etc/postfix/virtual

 

by: Havin_itPosted on 2008-04-04 at 04:45:18ID: 21280591

Hi, thanks for the reply :)

I was using $virtual_alias_maps previously (this is the Postfix 2.5.* descendant of virtual_maps) but the problem with that was that it rewrote the headers and then tried to send the mail via the ISP server (which obviously didn't work).

What I currently have is better in that it knows the mail should be passed to LDA, but I think the problem is LDA doesn't receive the right information to pass it to the appropriate virtual mailbox.

The listing below shows the output when I try to send a message from one user to the other (including the bounce, which also fails) with my current config, plus below that is the contents of the file /etc/postfix/virtual.

# /var/log/mail.log
Apr  4 12:35:56 brazil postfix/smtpd[22615]: connect from localhost[127.0.0.1]
Apr  4 12:35:56 brazil postfix/smtpd[22615]: E18A7157646: client=localhost[127.0.0.1]
Apr  4 12:35:56 brazil postfix/cleanup[22618]: E18A7157646: message-id=<20080404123556.1vippexass4444cs@brazil>
Apr  4 12:35:57 brazil postfix/qmgr[22549]: E18A7157646: from=<me@popaccount1.net>, size=829, nrcpt=1 (queue active)
Apr  4 12:35:57 brazil postfix/smtpd[22615]: disconnect from localhost[127.0.0.1]
Apr  4 12:35:57 brazil postfix/pipe[22619]: E18A7157646: to=<metoo@popaccount2.co.uk>, relay=dovecot, delay=0.53, delays=0.25/0.17/0/0.12, dsn=5.1.1, status=bounced (user unknown)
Apr  4 12:35:57 brazil postfix/cleanup[22618]: 68EE01578E5: message-id=<20080404113557.68EE01578E5@brazil>
Apr  4 12:35:57 brazil postfix/qmgr[22549]: 68EE01578E5: from=<>, size=2464, nrcpt=1 (queue active)
Apr  4 12:35:57 brazil postfix/bounce[22621]: E18A7157646: sender non-delivery notification: 68EE01578E5
Apr  4 12:35:57 brazil postfix/qmgr[22549]: E18A7157646: removed
Apr  4 12:35:57 brazil postfix/pipe[22619]: 68EE01578E5: to=<me@popaccount1.net>, relay=dovecot, delay=0.24, delays=0.12/0/0/0.12, dsn=5.1.1, status=bounced (user unknown)
Apr  4 12:35:57 brazil postfix/qmgr[22549]: 68EE01578E5: removed
 
-------------------------------------------------
# /etc/postfix/virtual
 
@popaccount1.net    localbox1
@popaccount2.co.uk  localbox2

                                              
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:

Select allOpen in new window

 

by: ahoffmannPosted on 2008-04-04 at 05:09:11ID: 21280769

> to send the mail via the ISP server
does your ISP allow to use his MTA as anonymous (spam) gateway? I doubt.

 

by: Havin_itPosted on 2008-04-04 at 09:19:52ID: 21283256

ahoffmann, I'm not sure what your basis is for this statement.

In case something's not clear, let me explain what is currently happening with outgoing mail.  There are multiple external mail accounts which my users fetch by POP3, and send outgoing mail that is "from" those accounts via postfix, which (as you should see from the configs posted above) authenticates with my ISP's SMTP server using the credentials they provided me. I am permitted to send mails with any "from" address I so choose, as long as I authenticate.  There is nothing anonymous about it.

 

by: ahoffmannPosted on 2008-04-05 at 01:58:53ID: 21287502

> I am permitted to send mails with any "from" address ..
that's what my question was about when refering to
 > send the mail via the ISP server (which obviously didn't work).

If your ISP allows to send mails with any from, then please post the error messages you get when you try to deliver mails to your ISP mail server.

 

by: Havin_itPosted on 2008-04-05 at 04:41:05ID: 21287808

Sorry, I may need to clarify that part also. Under that configuration (using $virtual_alias_maps) I had no problem sending mails to other recipients -- it was only the POP3 domains listed in the virtuals file that would fail, because their "To:" address was rewritten to e.g.

me@popaccount1.net --> localbox1@brazil.localdomain

...which obviously was meaningless to the ISP server. I'll post the full output if you think it'll help, but surely the current config (where at least postfix is trying to hand them to dovecot instead of the ISP server) is closer to being right.

 

by: ahoffmannPosted on 2008-04-05 at 05:49:12ID: 21287938

hmm, this sounds like you need to debug the process(es), we need hands on the system I guess
That's not possible with EE.

 

by: Havin_itPosted on 2008-04-05 at 06:30:28ID: 21288105

No need to be so defeatist ;) I can follow instructions well enough, so if someone can advise what else to spy on to get better debug info, I'll do it.

If you mean binary debugging, I don't think there is anything like that happening; nothing has segfaulted or puked in the tell-tale ways. I'm sure it is just misconfiguration -- I can even offer a couple of theories, though I hope I can express them well enough to be useful:

1) The "To" address that postfix is putting on the mail (or possibly leaving intact, as the output above might suggest) cannot be translated by dovecot LDA into the correct mailbox to deliver it to. I guess this would mean that either my /etc/postfix/virtuals is wrong, or the dovecot transport definition in master.cf (shown in the first post) needs changing.

...or...

2) Something is wrong with the SASL auth process. I don't think this is likely, as the mail  does at least get *into* postfix, and appears to attempt to deliver, which I don't think it would get that far if SASL wasn't working. And it definitely works OK for sending to non-virtual domains using the same client(s).

Hopefully these thoughts might help to steer the quest in the right direction. I will have a look at the program docs and see if I can find a way of getting more debug output.

 

by: ahoffmannPosted on 2008-04-05 at 07:46:41ID: 21288313

> If you mean binary debugging,
no, I mean you need to carefully watch the logfiles with debug inabled in main.cf when when you deliver your messages with the old and with the new configuration, so you can see where exactly the problem occours.

 

by: Havin_itPosted on 2008-04-05 at 09:42:35ID: 21288722

Okay, I added the following to main.cf

debug_peer_level = 9     #I've no idea how high I can set this, what is the max value?
debug_peer_list = 127.0.0.1

I'm still unsure if I can get more logging from dovecot -- I haven't posted any because the output doesn't say anything specific about the attempts that are failing. Any idea about this?

 

by: Havin_itPosted on 2008-04-06 at 04:46:39ID: 21291477

Okay, here's a log that (I think) covers both the initial send and the bounce. It doesn't mean much to me, but I do see that the sending address (metoo@popaccount2.co.uk) does get resolved to the mailbox (localbox2), so that bit does seem to work.  Okay, over to those who have some clue what all this means ;)

Apr  6 12:22:22 brazil postfix/smtpd[10439]: connect from localhost[127.0.0.1]
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 192.168.2.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 192.168.2.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 192.168.10.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 192.168.10.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 127.0.0.0/8
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 127.0.0.0/8
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 220 brazil ESMTP Postfix
Apr  6 12:22:22 brazil postfix/smtpd[10439]: watchdog_pat: 0x80be508
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 11 flush 26
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 11 got 16
Apr  6 12:22:22 brazil postfix/smtpd[10439]: < localhost[127.0.0.1]: EHLO localhost
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-brazil
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-PIPELINING
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-SIZE 10240000
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-VRFY
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-ETRN
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_list_match: localhost: no match
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_list_match: 127.0.0.1: no match
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-AUTH PLAIN
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-ENHANCEDSTATUSCODES
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250-8BITMIME
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250 DSN
Apr  6 12:22:22 brazil postfix/smtpd[10439]: watchdog_pat: 0x80be508
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 11 flush 131
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 11 got 34
Apr  6 12:22:22 brazil postfix/smtpd[10439]: < localhost[127.0.0.1]: MAIL FROM:<me@popaccount1.net>
Apr  6 12:22:22 brazil postfix/smtpd[10439]: extract_addr: input: <me@popaccount1.net>
Apr  6 12:22:22 brazil postfix/smtpd[10439]: smtpd_check_addr: addr=me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: connect to subsystem private/rewrite
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_enable_read: fd 18
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_extend: fd 18
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_request_timer: set 0x80775d0 0x80c29f0 5
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_request_timer: set 0x8077600 0x80c29f0 1000
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr request = rewrite
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr rule = local
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr address = me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 18 flush 57
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 18 got 38
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 0
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: address
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: address
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: (list terminator)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rewrite_clnt: local: me@popaccount1.net -> me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_request_timer: reset 0x80775d0 0x80c29f0 5
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr request = resolve
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr sender =
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr address = me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 18 flush 54
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 18 got 92
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 0
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: transport
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: transport
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: dovecot
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: nexthop
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: nexthop
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: recipient
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: recipient
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 1024
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: (list terminator)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: resolve_clnt: `' -> `me@popaccount1.net' -> transp=`dovecot' host=`popaccount1.net' rcpt=`me@popaccount1.net' flags= class=virtual
Apr  6 12:22:22 brazil postfix/smtpd[10439]: ctable_locate: install entry key me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: extract_addr: in: <me@popaccount1.net>, result: me@popaccount1.net
Apr  6 12:22:22 brazil postfix/smtpd[10439]: fsspace: .: block size 4096, blocks free 71918
Apr  6 12:22:22 brazil postfix/smtpd[10439]: smtpd_check_queue: blocks 4096 avail 71918 min_free 0 msg_size_limit 10240000
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250 2.1.0 Ok
Apr  6 12:22:22 brazil postfix/smtpd[10439]: watchdog_pat: 0x80be508
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 11 flush 14
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 11 got 31
Apr  6 12:22:22 brazil postfix/smtpd[10439]: < localhost[127.0.0.1]: RCPT TO:<metoo@popaccount2.co.uk>
Apr  6 12:22:22 brazil postfix/smtpd[10439]: extract_addr: input: <metoo@popaccount2.co.uk>
Apr  6 12:22:22 brazil postfix/smtpd[10439]: smtpd_check_addr: addr=metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_request_timer: reset 0x80775d0 0x80c29f0 5
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr request = rewrite
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr rule = local
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr address = metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 18 flush 56
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 18 got 37
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 0
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: address
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: address
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: (list terminator)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rewrite_clnt: local: metoo@popaccount2.co.uk -> metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_request_timer: reset 0x80775d0 0x80c29f0 5
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr request = resolve
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr sender =
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr address = metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 18 flush 53
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 18 got 92
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 0
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: transport
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: transport
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: dovecot
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: nexthop
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: nexthop
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: recipient
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: recipient
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 1024
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: (list terminator)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: resolve_clnt: `' -> `metoo@popaccount2.co.uk' -> transp=`dovecot' host=`popaccount2.co.uk' rcpt=`metoo@popaccount2.co.uk' flags= class=virtual
Apr  6 12:22:22 brazil postfix/smtpd[10439]: ctable_locate: install entry key metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: extract_addr: in: <metoo@popaccount2.co.uk>, result: metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: event_request_timer: reset 0x80775d0 0x80c29f0 5
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr request = rewrite
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr rule = local
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr address = double-bounce
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 18 flush 50
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 18 got 50
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: flags
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 0
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: address
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: address
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: double-bounce@brazil.localdomain
Apr  6 12:22:22 brazil postfix/smtpd[10439]: private/rewrite socket: wanted attribute: (list terminator)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rewrite_clnt: local: double-bounce -> double-bounce@brazil.localdomain
Apr  6 12:22:22 brazil postfix/smtpd[10439]: >>> START Recipient address RESTRICTIONS <<<
Apr  6 12:22:22 brazil postfix/smtpd[10439]: generic_checks: name=permit_mynetworks
Apr  6 12:22:22 brazil postfix/smtpd[10439]: permit_mynetworks: localhost 127.0.0.1
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 192.168.2.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 192.168.2.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 192.168.10.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 192.168.10.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 127.0.0.0/8
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 127.0.0.0/8
Apr  6 12:22:22 brazil postfix/smtpd[10439]: generic_checks: name=permit_mynetworks status=1
Apr  6 12:22:22 brazil postfix/smtpd[10439]: >>> CHECKING RECIPIENT MAPS <<<
Apr  6 12:22:22 brazil postfix/smtpd[10439]: ctable_locate: leave existing entry key metoo@popaccount2.co.uk
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: recipient_canonical_maps: metoo@popaccount2.co.uk: not found
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? brazil
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost.localdomain
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_list_match: popaccount2.co.uk: no match
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: recipient_canonical_maps: @popaccount2.co.uk: not found
Apr  6 12:22:22 brazil postfix/smtpd[10439]: mail_addr_find: metoo@popaccount2.co.uk -> (not found)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: canonical_maps: metoo@popaccount2.co.uk: not found
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? brazil
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost.localdomain
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_list_match: popaccount2.co.uk: no match
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: canonical_maps: @popaccount2.co.uk: not found
Apr  6 12:22:22 brazil postfix/smtpd[10439]: mail_addr_find: metoo@popaccount2.co.uk -> (not found)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: virtual_alias_maps: metoo@popaccount2.co.uk: not found
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? brazil
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost.localdomain
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_list_match: popaccount2.co.uk: no match
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: virtual_alias_maps: @popaccount2.co.uk: not found
Apr  6 12:22:22 brazil postfix/smtpd[10439]: mail_addr_find: metoo@popaccount2.co.uk -> (not found)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: virtual_mailbox_maps: metoo@popaccount2.co.uk: not found
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? brazil
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost.localdomain
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_string: popaccount2.co.uk ~? localhost
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_list_match: popaccount2.co.uk: no match
Apr  6 12:22:22 brazil postfix/smtpd[10439]: maps_find: virtual_mailbox_maps: hash:/etc/postfix/virtual(0,lock|fold_fix): @popaccount2.co.uk = localbox2
Apr  6 12:22:22 brazil postfix/smtpd[10439]: mail_addr_find: metoo@popaccount2.co.uk -> localbox2
Apr  6 12:22:22 brazil postfix/smtpd[10439]: smtpd_check_rewrite: trying: permit_inet_interfaces
Apr  6 12:22:22 brazil postfix/smtpd[10439]: permit_inet_interfaces: localhost 127.0.0.1
Apr  6 12:22:22 brazil postfix/smtpd[10439]: before input_transp_cleanup: cleanup flags = enable_header_body_filter enable_automatic_bcc enable_address_mapping enable_milters
Apr  6 12:22:22 brazil postfix/smtpd[10439]: after input_transp_cleanup: cleanup flags = enable_header_body_filter enable_automatic_bcc enable_address_mapping
Apr  6 12:22:22 brazil postfix/smtpd[10439]: connect to subsystem public/cleanup
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 19 got 22
Apr  6 12:22:22 brazil postfix/smtpd[10439]: public/cleanup socket: wanted attribute: queue_id
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: queue_id
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: B0A131575BE
Apr  6 12:22:22 brazil postfix/smtpd[10439]: public/cleanup socket: wanted attribute: (list terminator)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: send attr flags = 178
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type T len 17 data 1207480942
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 21 data rewrite_co
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type S len 20 data me@popacco
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 25 data log_client
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 28 data log_client
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 21 data log_client
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 39 data log_messag
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 23 data log_helo_n
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 23 data log_protoc
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 21 data client_nam
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 29 data reverse_cl
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 24 data client_add
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 17 data client_por
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 19 data helo_name=
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 21 data client_add
Apr  6 12:22:22 brazil postfix/smtpd[10439]: B0A131575BE: client=localhost[127.0.0.1]
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type A len 40 data dsn_orig_r
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type R len 19 data metoo@popa
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 19 flush 452
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250 2.1.5 Ok
Apr  6 12:22:22 brazil postfix/smtpd[10439]: watchdog_pat: 0x80be508
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 11 flush 14
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 11 got 6
Apr  6 12:22:22 brazil postfix/smtpd[10439]: < localhost[127.0.0.1]: DATA
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type M len 0 data
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 48 data Received:
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 46 data ?by brazil
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 65 data ?for <metoo
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 354 End data with <CR><LF>.<CR><LF>
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 11 flush 37
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 11 got 673
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 73 data Received:
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 43 data ?with HTTP
Apr  6 12:22:22 brazil postfix/cleanup[10442]: B0A131575BE: message-id=<20080406122222.cmk8lczbzwcg8c8c@brazil>
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 52 data Message-ID
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 37 data Date: Sun,
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 43 data From: Robi
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 23 data To: metoo@
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 13 data Subject: T
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 17 data MIME-Versi
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 25 data Content-Ty
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 20 data ?charset=I
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 13 data ?DelSp="Ye
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 16 data ?format="f
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 27 data Content-Di
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 31 data Content-Tr
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 55 data User-Agent
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 0 data
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 10 data Testing :(
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 0 data
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 64 data ----------
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 64 data This messa
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 0 data
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type N len 0 data
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type X len 0 data
Apr  6 12:22:22 brazil postfix/smtpd[10439]: rec_put: type E len 0 data
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 19 flush 841
Apr  6 12:22:22 brazil postfix/qmgr[3195]: B0A131575BE: from=<me@popaccount1.net>, size=835, nrcpt=1 (queue active)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 19 got 18
Apr  6 12:22:22 brazil postfix/smtpd[10439]: public/cleanup socket: wanted attribute: status
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: status
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: 0
Apr  6 12:22:22 brazil postfix/smtpd[10439]: public/cleanup socket: wanted attribute: reason
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: reason
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute value: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: public/cleanup socket: wanted attribute: (list terminator)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: input attribute name: (end)
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 250 2.0.0 Ok: queued as B0A131575BE
Apr  6 12:22:22 brazil postfix/smtpd[10439]: watchdog_pat: 0x80be508
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 11 flush 37
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_buf_get_ready: fd 11 got 6
Apr  6 12:22:22 brazil postfix/smtpd[10439]: < localhost[127.0.0.1]: QUIT
Apr  6 12:22:22 brazil postfix/smtpd[10439]: > localhost[127.0.0.1]: 221 2.0.0 Bye
Apr  6 12:22:22 brazil postfix/smtpd[10439]: vstream_fflush_some: fd 11 flush 15
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 192.168.2.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 192.168.2.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 192.168.10.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 192.168.10.0/28
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostname: localhost ~? 127.0.0.0/8
Apr  6 12:22:22 brazil postfix/smtpd[10439]: match_hostaddr: 127.0.0.1 ~? 127.0.0.0/8
Apr  6 12:22:22 brazil postfix/smtpd[10439]: disconnect from localhost[127.0.0.1]
Apr  6 12:22:23 brazil postfix/pipe[10444]: B0A131575BE: to=<metoo@popaccount2.co.uk>, relay=dovecot, delay=0.67, delays=0.33/0.09/0/0.25, dsn=5.1.1, status=bounced (user unknown)
Apr  6 12:22:23 brazil postfix/cleanup[10442]: 423091578E4: message-id=<20080406112223.423091578E4@brazil>
Apr  6 12:22:23 brazil postfix/qmgr[3195]: 423091578E4: from=<>, size=2470, nrcpt=1 (queue active)
Apr  6 12:22:23 brazil postfix/qmgr[3195]: B0A131575BE: removed
Apr  6 12:22:23 brazil postfix/bounce[10446]: B0A131575BE: sender non-delivery notification: 423091578E4
Apr  6 12:22:23 brazil postfix/pipe[10444]: 423091578E4: to=<me@popaccount1.net>, relay=dovecot, delay=0.37, delays=0.09/0/0/0.28, dsn=5.1.1, status=bounced (user unknown)
Apr  6 12:22:23 brazil postfix/qmgr[3195]: 423091578E4: removed
                                              
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:
209:
210:
211:
212:
213:
214:
215:
216:
217:
218:
219:
220:
221:
222:
223:
224:
225:
226:
227:
228:
229:
230:
231:
232:
233:
234:
235:
236:
237:
238:
239:
240:
241:
242:
243:
244:
245:
246:
247:
248:
249:
250:
251:
252:
253:
254:
255:
256:
257:
258:
259:
260:
261:
262:
263:
264:
265:
266:
267:
268:
269:
270:
271:
272:
273:
274:
275:
276:
277:
278:
279:

Select allOpen in new window

 

by: Havin_itPosted on 2008-04-06 at 06:02:09ID: 21291635

While I wait for enlightenment on the above, I've done a simple test to try and narrow down the problem.  I edited master.cf and replaced the dovecot argument

-d ${recipient}

with

-d localbox2

And this time, the mail got through! So, progress. Now we know that it's this argument that is wrong, so we need to get postfix to make the right one.  It looks like it can already resolve the pop3 address to the mailbox name, but that isn't what we're getting in the ${recipient} variable.

The problem is, I don't know how to spy on what is in that variable (dovecot doesn't log the failed delivery attempts at all and there doesn't seem to be a way to make it), and I can't find a sausage about the variables in the master(5) or postconf(5) manpages.

 

by: Havin_itPosted on 2008-04-06 at 08:46:02ID: 21292148

Right. More facts I have established:

1) $virtual_mailbox_maps file lookups *ignore* what is on the right-hand side (which for me is the name of the corresponding mailbox: the info I need to get!). I think this means that the address isn't rewritten at all, which is no good to me.

2) http://www.postfix.org/ADDRESS_CLASS_README.html#virtual_alias_class
"Purpose: hosted domains where each recipient address is aliased to a local UNIX system account or to a remote address."
This would, I guess, be why when I add $virtual_alias_domains and $virtual_alias_maps configuration directives, the messages get sent to the ISP server.

I think the current configuration may be a dead end. $virtual_mailbox_maps won't allow me (well, not that I can tell) to pass the correct mailbox name to LDA, so I need to see if I can come up with an alternative approach.

Is there a way I can use the transport table and $mydestination to get the desired result, perhaps?

 

by: Havin_itPosted on 2008-04-07 at 13:32:15ID: 21300311

Yay, I finally (after a sleepless night) solved it! This is arguably a bit hackish, but it does work so never mind ;)

First, I removed the virtual_* directives from /etc/postfix/main.cf. Then I added the directives below (see listing) and changed the dovecot transport definition in the master.cf file. Lastly I created the /etc/postfix/transport table, as shown.

Basically, the empty local_recipient_maps variable means that local usernames (which do not exist on my system in any sense that postfix can employ) are not checked, somails will not be rejected when sent to the domains I've listed in $mydestination. Instead, when those domains are looked-up in the transport table, they're instructed to use the dovecot transport. The part after the colon in the table is called the 'nexthop', and this is available as a variable to put as the -d argument in master.cf, so I use it to declare the name of the target mailbox.

I'm not even that clear on the intended definition of 'nexthop', so I don't know how semantically appropriate it is -- but as I said, it works so who cares?

NB -- using the blank local_recipient_maps declaration is something that should only *ever* be done on a server that isn't exposed to the Internet. Otherwise it will be a backscatter source.

# added variables in /etc/postfix/main.cf
mydestination = $myhostname, brazil.$mydomain, localhost.$mydomain, localhost,
        popaccount1.net, popaccount2.co.uk
 
transport_maps = hash:/etc/postfix/transport
local_recipient_maps =
 
---------------------------------------------
# dovecot transport definition in /etc/postfix/master.cf
dovecot   unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${nexthop}
 
-----------------------------------------------
# /etc/postfix/transport
popaccount1.net      dovecot:localbox1
popaccount2.co.uk    dovecot:localbox2
localhost            dovecot:localbox1
                                              
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:

Select allOpen in new window

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...