Re: mailq full but nothing in active/deferred/incoming
Le 07/06/2011 01:13, Wietse Venema a écrit : St?phane MERLE: Postfix installs its own sendmail command, to avoid breaking PHP etc. This was a smarter move than having to re-educate people. yes, I must agree on that ! (that's just confusing because the /usr/sbin/sendmail is not a script but a binary ... so I though that was the mta) so to make sure : 1 - for the 10s pause between emails, it's due to the sendmail command ? # dpkg -S sendmail | grep bin postfix: /usr/sbin/sendmail Instead of asking if /usr/sbin/sendmail causes a delay, why don't jou just SEND EMAIL WITHOUT PHP and see if that causes a delay. If there is no such delay then /usr/sbin/sendmail is not the problem. yes, that's the simplest way, but ... I don't have the delay anymore (so I can't try), I think the hosting company problem is now solve, and hopefully I wont get the problem anymore. you think that the delay is coming from the mail php function ? (I really though that the postfix had a kind of security that hold the mail when the mailq is starting to be too full). As for the other questions, why would you throw away email that was intended to be delivered? Because of the delay, most of those email (80/85 %) where coupon to use for monday (yesterday, we began to sent them on saturday). So we decided on monday morning to cancel the rest to sent of the mailing but ... I was unable to do it (I could switch off the postfix, but then where were the mail ..., again, nothing in active/deferred/incoming). At the end the coupon which is still written to work on Monday will also be working today and tomorrow to be sure Again, don't think that I blame postfix for something, this software is just perfect and is working like a charm 99% of the time and here the problem is not even coming from him ... it's just that I never had this kind of thing (mail in the mailq but nothing in qshape on active or deferred). It's also probably a language matter, as I don't get all the subtility of the documentation [I found most of the explanations of sendmail afterward and get the ! information for the hold status in mailq afterward too in http://www.postfix.org/sendmail.1.html] I must add that I bought the book : postfix la référence of Kyle Dent and it help me a lot in the set up a year or 2 ago Thanks for your time, patience and work. Stéphane
Re: postscreen_dnsbl_sites vs. reject_rbl_client
* Rich Wales ri...@richw.org: If I enable postscreen and specify my choice of blocklists and whitelists in postscreen_dnsbl_sites, am I correct in assuming that I might as well remove any reject_rbl_client and permit_dnswl_client clauses from my smtpd_*_restrictions, since they will now be redundant? Since postscreen uses caching extensively, it might make sense to query the RBLs another time, since a host may be blacklisted in the meantime. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: postscreen_dnsbl_sites vs. reject_rbl_client
* Rich Wales ri...@richw.org: value from a given list. (I won't go into the details, they would be off-topic here, but it's nice to have this capability.) It will probably start a flamewar, but I personally am interested in your particular weights on the different RBLs -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: access(5) OTHER ACTIONS question
It sounds to me like you are saying that... lookup result := special action | (other action [,])* [special action] No, I wrote: One line NOT starting with REJECT or PREPEND etc., containing OTHER ACTIONS (note plural) than REJECT or PREPEND etc. Therefore: result = special | notspecial+ Learn to read what I write, not what you want to see. Wietse
Re: postscreen_dnsbl_sites vs. reject_rbl_client
Rich Wales: Note that postscreen caches the results of successful tests, so that it does not repeat every test for every connection. This is controlled by the postscreen_mumble_ttl parameters. Some caching may also be done by my DNS server too, right? This would, of course, be transparent to Postfix and would depend on the TTL info from the whitelist / blocklist. Note the following difference. postscreen caches that the client IS NOT listed in DNSBL. It doesn't cache clients that are listed. DNS servers cache that the client IS listed in DNSBL. They don't cache non-existent DNSBL records. So, the two really cache opposite things, if we focus on good SMTP clients. And that is where Postfix tries to minimize the performance hit. Wietse
Re: mailq full but nothing in active/deferred/incoming
St?phane MERLE: problem is not even coming from him ... it's just that I never had this kind of thing (mail in the mailq but nothing in qshape on active or deferred). Mailq reports mail in all Postfix queues: MAILDROP, INCOMING, ACTIVE DEFERRED, and HOLD. You were using qshape for ACTIVE and DEFERRED, and therefore missed all the mail in all the other queues. Wietse
Re: postfix + .forward and forcing the From address
Wietse Venema: Wietse Venema: Michael Way: it would be?: if !/[[::]]user1\.home@work\.com$/ /./ user1\.home@work\.com Don't use \ in the replacement text! endif Looks like you want to replace all senders in outbound email by your own email address. In that case it is sufficient to do this: /etc/postfix/main.cf: sender_canonical_maps = pcre:/etc/postfix/sender_canonical sender_canonical_classes = envelope_sender /etc/postfix/sender_canonical: /./ your-email-address-here-without-backslashes-garbage The problem with this is that it also replaces the sender on inbound email, that is, if affects mail that you receive, and mail that you send out. In case anyone is still following this thread, what the original poster wants to do (forward a copy of his mail to an outside address, while replacing the envelope sender with his inside address) is fundamentally unsafe. It is fundamentally unsafe because mail goes into a loop when forwarded mail is undeliverable. The undeliverable message is returned to the inside email address, there it is forwarded again, then it bounces again, and so on. This is precisely what happens when you use default procmail rules to forward mail. This is also why doing these things was not made easy in Postfix many years ago. So long ago, that I had to re-discover the problem. Wietse
Re: postfix + .forward and forcing the From address
It seems my smtpd exchange server is still unhappy even with this last solution. I'm getting: 550 5.7.1 Client does not have permissions to send as this sender (in reply to end of DATA command)) This follows your suggestion to put this in /etc/postfix/sender_canonical: /./ user1.h...@work.com Perhaps I should give procmail a try? I'm not sure it can rewrite the header or not as required by our smtpd exchange server, but I suppose I should try? --mike On Mon, Jun 6, 2011 at 8:14 PM, Wietse Venema wie...@porcupine.org wrote: Looks like you want to replace all senders in outbound email by your own email address. In that case it is sufficient to do this: /etc/postfix/main.cf: sender_canonical_maps = pcre:/etc/postfix/sender_canonical sender_canonical_classes = envelope_sender /etc/postfix/sender_canonical: /./ your-email-address-here-without-backslashes-garbage The problem with this is that it also replaces the sender on inbound email, that is, if affects mail that you receive, and mail that you send out. The alternative, smtp_generic_maps, chanes outbound mail only, but it has a worse problem: it updates From, To: and so on. There currently is no option to apply smtp_generic_maps to the sender only. Wietse
Re: postfix + .forward and forcing the From address
Sorry I didn't read your e-mail before hitting the send button. You are correct about it going into a loop, and the only way to stop it is to remove the rules in main.cf and then postfix reload. I'm wondering why you call it unsafe? Is this because it will fill up your log files if you don't realize it? I suppose I'm going to have to find another solution. Apparently Thunderbird has a way to wrap the header with the appropriate information, but I'm not a fan of doing things this way. thanks, mike On Tue, Jun 7, 2011 at 8:48 AM, Wietse Venema wie...@porcupine.org wrote: Wietse Venema: Wietse Venema: Michael Way: it would be?: if !/[[::]]user1\.home@work\.com$/ /./ user1\.home@work\.com Don't use \ in the replacement text! endif Looks like you want to replace all senders in outbound email by your own email address. In that case it is sufficient to do this: /etc/postfix/main.cf: sender_canonical_maps = pcre:/etc/postfix/sender_canonical sender_canonical_classes = envelope_sender /etc/postfix/sender_canonical: /./ your-email-address-here-without-backslashes-garbage The problem with this is that it also replaces the sender on inbound email, that is, if affects mail that you receive, and mail that you send out. In case anyone is still following this thread, what the original poster wants to do (forward a copy of his mail to an outside address, while replacing the envelope sender with his inside address) is fundamentally unsafe. It is fundamentally unsafe because mail goes into a loop when forwarded mail is undeliverable. The undeliverable message is returned to the inside email address, there it is forwarded again, then it bounces again, and so on. This is precisely what happens when you use default procmail rules to forward mail. This is also why doing these things was not made easy in Postfix many years ago. So long ago, that I had to re-discover the problem. Wietse
fqrdns.regexp
Hi list, Reading the archives I saw that there is a nice regexp with dynamic hostnames available here: www.hardwarefreak.com/fqrdns.regexp Unfortunately this file seems to be unavailable at the moment for some reason. Do you guys happen to know from where this file (latest) version can be downloaded. TIA, Mikael
Re: postfix + .forward and forcing the From address
On Mon, Jun 06, 2011 at 02:46:57PM -0400, Michael Way wrote: I have a setup where I use postfix to connect to my work smtpd exchange server via TLS encryption and normal login authentication. This smtpd server also requires that the From address in the email header is from the same user that authenticates, otherwise I get a: Client does not have permissions to send as this sender I can send emails via this system just fine using mutt or whatever command line mail I like, BUT I also use fetchmail to get email from our IMAP server. I then use a .forward file to keep a local copy AND send a copy to gmail as a backup. Ugly and complex, but, oh well. Unfortunately my work smptd exchange server rejects all of the forwards to gmail because it sees that the From address is NOT from the authenticated user (at least that is what I gather when I get these messages Client does not have permissions to send as this sender So why not just take MSexChange out of the picture? Set up direct authentication to gmail. SASL_README.html#client_sasl just as you did, setting it up to authenticate to MSexChange. Have your .forward invoke sendmail(1) with your gmail address as the sender. Then maybe a transport_maps entry to force your gmail address to use the gmail submission service. Did I miss something? Does that not achieve the original goal? -- Offlist mail to this address is discarded unless /dev/rob0 or not-spam is in Subject: header
Re: postfix + .forward and forcing the From address
I can send emails via this system just fine using mutt or whatever command line mail I like, BUT I also use fetchmail to get email from our IMAP server. I then use a .forward file to keep a local copy AND send a copy to gmail as a backup. Ugly and complex, but, oh well. Until they moved over to this new TLS/Auth system I'd been using this for years - so I guess I've gotten used to its ugliness and complexity :-) So why not just take MSexChange out of the picture? Set up direct authentication to gmail. SASL_README.html#client_sasl just as you did, setting it up to authenticate to MSexChange. Have your .forward invoke sendmail(1) with your gmail address as the sender. Then maybe a transport_maps entry to force your gmail address to use the gmail submission service. Did I miss something? Does that not achieve the original goal? Yes, I agree that this would be the obvious way to attack it except that our corporate firewall does not allow such outbound smtp packets on ports less than 1024: e.g. % telnet smtp.gmail.com 587 Trying 209.85.225.109... and never connecting... while for my corporate smtp server it does connect. You see, I'm trying to get around what *they* think is best for me and them... cheers mike
Re: mailq full but nothing in active/deferred/incoming
Hi, Le 07/06/2011 13:08, Wietse Venema a écrit : St?phane MERLE: problem is not even coming from him ... it's just that I never had this kind of thing (mail in the mailq but nothing in qshape on active or deferred). Mailq reports mail in all Postfix queues: MAILDROP, INCOMING, ACTIVE DEFERRED, and HOLD. You were using qshape for ACTIVE and DEFERRED, and therefore missed all the mail in all the other queues. is qshape able to show the HOLD and MAILDROP queue ? (it seem to alway show 0 for hold and I got a script error for maildrop : Use of uninitialized value $qt in subtraction (-) at /usr/sbin/qshape line 282. ) I'd like to monitor thoses queue and alert me if they grow up Stéphane
Re: postfix + .forward and forcing the From address
On Tue, Jun 07, 2011 at 10:38:44AM -0400, Michael Way wrote: So why not just take MSexChange out of the picture? Set up direct authentication to gmail. SASL_README.html#client_sasl just as you did, setting it up to authenticate to MSexChange. Have your .forward invoke sendmail(1) with your gmail address as the sender. Then maybe a transport_maps entry to force your gmail address to use the gmail submission service. Did I miss something? Does that not achieve the original goal? Yes, I agree that this would be the obvious way to attack it except that our corporate firewall does not allow such outbound smtp packets on ports less than 1024: e.g. % telnet smtp.gmail.com 587 Trying 209.85.225.109... and never connecting... while for my corporate smtp server it does connect. You see, I'm trying to get around what *they* think is best for me and them... Need Able System Administrators ;) I could suggest some sort of tunnelling to a host outside the Great Firewall, but that would likely be a violation of network use rules. The best next step that occurs to me would be to go to the IT gang and ask for support. If the answer is as I suspect, No, you may not and cannot do this, I guess you must either obey or resort to sneakernet solutions. Another possible approach is to see if there's any software to automate the gmail webmail interface. I know spammers have done it, because stuff like that is about the only spam that gets through to my mailboxes. Good luck. -- Offlist mail to this address is discarded unless /dev/rob0 or not-spam is in Subject: header
Re: postscreen_dnsbl_sites vs. reject_rbl_client
On Tue, Jun 07, 2011 at 07:03:34AM -0400, Wietse Venema wrote: Note the following difference. postscreen caches that the client IS NOT listed in DNSBL. It doesn't cache clients that are listed. DNS servers cache that the client IS listed in DNSBL. They don't cache non-existent DNSBL records. This depends on the negative TTL of the RBL zone. Generally, RBL zones have comparable positive and negative TTLs. For example Zen seems to have a 3 minute negative TTL: $ dig +noall +ans +auth -t a 127.2.0.192.zen.spamhaus.org zen.spamhaus.org. 150 IN SOA need.to.know.only. hostmaster.spamhaus.org. 1106071530 3600 600 432000 150 And a 15 minute positive TTL: $ dig +noall +ans -t a 126.145.66.190.zen.spamhaus.org 126.145.66.190.zen.spamhaus.org. 900 IN A 127.0.0.4 126.145.66.190.zen.spamhaus.org. 900 IN A 127.0.0.11 -- Viktor.
Re: Forwarding via virtual_mailbox_maps or virtual_maps not working
On Mon, Jun 06, 2011 at 10:40:18PM -0400, Islam, Towhid wrote:
virtual_alias_maps =
proxy:mysql:$config/mysql_virtual_alias_maps.cf,hash:/etc/postfix/vmailbox
Translated: look at the mysql first, then look at the vmailbox (db) table.
Except, this does not appear to work. In the old SuSE SLOX host, it works.
Sure, but what's in the vmailbox table? Is it actually a set of address
(to address) mappings? If these are virtual mailbox locations, they should
be in:
default_database_type = hash
indexed = ${default_database_type}:${config_directory}/
virtual_mailbox_maps = ${indexed}vmailbox
--
Viktor.
Re: fqrdns.regexp
On Tue, Jun 7, 2011 at 7:06 AM, Бак Микаел mikael@yandex.ru wrote: Hi list, Reading the archives I saw that there is a nice regexp with dynamic hostnames available here: www.hardwarefreak.com/fqrdns.regexp Unfortunately this file seems to be unavailable at the moment for some reason. Do you guys happen to know from where this file (latest) version can be downloaded. TIA, Mikael It's http://www.hardwarefreak.com/fqrdns.pcre
Messages held in queue with no warning/error
Hello, We have a postfix server which does forwarding messages to virtual domains. B459E38562! 118003 Tue Jun 7 10:21:49 profs-cpsc-l-boun...@mailman.ucalgary.ca us...@ucalgary.ca us...@ucalgary.ca us...@ucalgary.ca [root@forward ~]# grep B459E38562 /var/log/maillog Jun 7 10:21:49 forward postfix/smtpd[19795]: B459E38562: client=mailman.ucalgary.ca[136.159.86.149] Jun 7 10:21:49 forward postfix/cleanup[18782]: B459E38562: hold: header Received: from forward2.ucalgary.ca (forward2.ucalgary.ca [136.159.34.105])??by mhub3.UCALGARY.CA (Postfix) with ESMTP id 7A94774004??for profs-cps...@mailman.ucalgary.ca;??Tue, 7 Jun 2011 10:21:29 from mailman.ucalgary.ca[136.159.86.149]; from=profs-cpsc-l-boun...@mailman.ucalgary.ca to=alh...@cpsc.ucalgary.ca proto=ESMTP helo=mailman.ucalgary.ca Jun 7 10:21:49 forward postfix/cleanup[18782]: B459E38562: message-id=bbbe706e2a04594d9edcd361a81c90ffc855774...@exmb01.admin.ad.ucalgary.ca [root@forward ~]# postcat -q B459E38562 |less *** ENVELOPE RECORDS hold/B459E38562 *** message_size: 1180034220 40 0 message_arrival_time: Tue Jun 7 10:21:49 2011 create_time: Tue Jun 7 10:21:49 2011 named_attribute: rewrite_context=remote sender: profs-cpsc-l-boun...@mailman.ucalgary.ca named_attribute: log_client_name=mailman.ucalgary.ca named_attribute: log_client_address=136.159.86.149 named_attribute: log_message_origin=mailman.ucalgary.ca[136.159.86.149] named_attribute: log_helo_name=mailman.ucalgary.ca named_attribute: log_protocol_name=ESMTP named_attribute: client_name=mailman.ucalgary.ca named_attribute: reverse_client_name=mailman.ucalgary.ca named_attribute: client_address=136.159.86.149 named_attribute: helo_name=mailman.ucalgary.ca named_attribute: client_address_type=2 warning_message_time: Tue Jun 7 11:21:49 2011 named_attribute: dsn_orig_rcpt=rfc822;us...@cpsc.ucalgary.ca original_recipient: us...@cpsc.ucalgary.ca recipient: us...@ucalgary.ca named_attribute: dsn_orig_rcpt=rfc822;us...@cpsc.ucalgary.ca original_recipient: us...@cpsc.ucalgary.ca recipient: us...@ucalgary.ca named_attribute: dsn_orig_rcpt=rfc822;us...@cpsc.ucalgary.ca original_recipient: us...@cpsc.ucalgary.ca recipient: us...@ucalgary.ca .. *** MESSAGE CONTENTS hold/B459E38562 *** Kai Wang System Services Information Technologies, University of Calgary, 2500 University Drive, N.W., Calgary, Alberta, Canada T2N 1N4 Phone (403) 220-2423 Fax (403) 282-9361
Re: Messages held in queue with no warning/error
On 06/07/2011 10:42 PM, Kai Wang wrote: Hello, We have a postfix server which does forwarding messages to virtual domains. B459E38562! 118003 Tue Jun 7 10:21:49 profs-cpsc-l-boun...@mailman.ucalgary.ca us...@ucalgary.ca us...@ucalgary.ca us...@ucalgary.ca [root@forward ~]# grep B459E38562 /var/log/maillog Jun 7 10:21:49 forward postfix/smtpd[19795]: B459E38562: client=mailman.ucalgary.ca[136.159.86.149] Jun 7 10:21:49 forward postfix/cleanup[18782]: B459E38562: hold: header Received: from forward2.ucalgary.ca (forward2.ucalgary.ca [136.159.34.105])??by mhub3.UCALGARY.CA (Postfix) with ESMTP id 7A94774004??forprofs-cps...@mailman.ucalgary.ca;??Tue, 7 Jun 2011 10:21:29 from mailman.ucalgary.ca[136.159.86.149]; from=profs-cpsc-l-boun...@mailman.ucalgary.ca to=alh...@cpsc.ucalgary.ca proto=ESMTP helo=mailman.ucalgary.ca Jun 7 10:21:49 forward postfix/cleanup[18782]: B459E38562: message-id=bbbe706e2a04594d9edcd361a81c90ffc855774...@exmb01.admin.ad.ucalgary.ca You configured something that sends the message to the HOLD queue; this does not happen automatically. As requested when you joined this list, show postconf -n and it will be easily explained. -- J.
Re: Messages held in queue with no warning/error
* Kai Wang kw...@ucalgary.ca: Hello, We have a postfix server which does forwarding messages to virtual domains. B459E38562! 118003 Tue Jun 7 10:21:49 profs-cpsc-l-boun...@mailman.ucalgary.ca us...@ucalgary.ca us...@ucalgary.ca us...@ucalgary.ca [root@forward ~]# grep B459E38562 /var/log/maillog Jun 7 10:21:49 forward postfix/smtpd[19795]: B459E38562: client=mailman.ucalgary.ca[136.159.86.149] Jun 7 10:21:49 forward postfix/cleanup[18782]: B459E38562: hold: header Received: from forward2.ucalgary.ca (forward2.ucalgary.ca [136.159.34.105])??by mhub3.UCALGARY.CA (Postfix) with ESMTP id 7A94774004??for profs-cps...@mailman.ucalgary.ca;??Tue, 7 Jun 2011 10:21:29 from mailman.ucalgary.ca[136.159.86.149]; from=profs-cpsc-l-boun...@mailman.ucalgary.ca to=alh...@cpsc.ucalgary.ca proto=ESMTP helo=mailman.ucalgary.ca Jun 7 10:21:49 forward postfix/cleanup[18782]: B459E38562: message-id=bbbe706e2a04594d9edcd361a81c90ffc855774...@exmb01.admin.ad.ucalgary.ca [root@forward ~]# postcat -q B459E38562 |less *** ENVELOPE RECORDS hold/B459E38562 *** message_size: 1180034220 40 0 message_arrival_time: Tue Jun 7 10:21:49 2011 create_time: Tue Jun 7 10:21:49 2011 named_attribute: rewrite_context=remote sender: profs-cpsc-l-boun...@mailman.ucalgary.ca named_attribute: log_client_name=mailman.ucalgary.ca named_attribute: log_client_address=136.159.86.149 named_attribute: log_message_origin=mailman.ucalgary.ca[136.159.86.149] named_attribute: log_helo_name=mailman.ucalgary.ca named_attribute: log_protocol_name=ESMTP named_attribute: client_name=mailman.ucalgary.ca named_attribute: reverse_client_name=mailman.ucalgary.ca named_attribute: client_address=136.159.86.149 named_attribute: helo_name=mailman.ucalgary.ca named_attribute: client_address_type=2 warning_message_time: Tue Jun 7 11:21:49 2011 named_attribute: dsn_orig_rcpt=rfc822;us...@cpsc.ucalgary.ca original_recipient: us...@cpsc.ucalgary.ca recipient: us...@ucalgary.ca named_attribute: dsn_orig_rcpt=rfc822;us...@cpsc.ucalgary.ca original_recipient: us...@cpsc.ucalgary.ca recipient: us...@ucalgary.ca named_attribute: dsn_orig_rcpt=rfc822;us...@cpsc.ucalgary.ca original_recipient: us...@cpsc.ucalgary.ca recipient: us...@ucalgary.ca .. *** MESSAGE CONTENTS hold/B459E38562 *** So what is your question? A header_checks entry put the mail on hold. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: access(5) OTHER ACTIONS question
In message 3qpvhy2tqszh...@spike.porcupine.org, Wietse wrote: It sounds to me like you are saying that... lookup result := special action | (other action [,])* [special action] No, I wrote: One line NOT starting with REJECT or PREPEND etc., containing OTHER ACTIONS (note plural) than REJECT or PREPEND etc. Therefore: result = special | notspecial+ Learn to read what I write, not what you want to see. I can only be slightly puzzled by your response, since I had no specific desires with respect to the true syntax, other than to understand whatever it might be. In any case, the syntax that you and Viktor posted has been most helpful to my understanding, and I thank you both for that. Thanks also for your patience and understanding. I had a semi-serious head injury at about this time last year and it is entirely plausible that my neurons dedicated to English parsing have not yet fully or properly reconnected (and may perhaps never do so). Fortunately, my ability to properly understand BNF seems to have been unaffected. Regards, rfg
RE: Forwarding via virtual_mailbox_maps or virtual_maps not working
Things a beginning to become clearer to me, bit by bit. Please bear with as I
not an expert or well versed in postfix.
Yes, vmailbox contains a set of address (to address) mappings. They are
actually a combination of virtual mailbox locations as well as email addresses
of users where the email is located elsewhere in different entities and
different domains (e.g. tis...@dnps.com [to be forwarded] to
isl...@gmail.com]. I realize that the latter should not be listed in the
vmailbox(.db) table. If need to do both then, do I need to include a
virtual_alias_maps, AND a virtual_mailbox_maps?
Lastly, I really do not understand the parameters you have laid out as the
following:
default_database_type = hash
indexed = ${default_database_type}:${config_directory}/
virtual_mailbox_maps = ${indexed}vmailbox
I think the last statement/parameter simply says that I'm using virtual mailbox
maps and its location, correct? Not sure about the preceding two parameters.
Could you please explain it to me (break it down) or point to an example?
Thanks again.
Towhid Islam
___
From: owner-postfix-us...@postfix.org [owner-postfix-us...@postfix.org] On
Behalf Of Victor Duchovni [victor.ducho...@morganstanley.com]
Sent: Tuesday, June 07, 2011 11:50 AM
To: postfix-users@postfix.org
Subject: Re: Forwarding via virtual_mailbox_maps or virtual_maps not working
On Mon, Jun 06, 2011 at 10:40:18PM -0400, Islam, Towhid wrote:
virtual_alias_maps =
proxy:mysql:$config/mysql_virtual_alias_maps.cf,hash:/etc/postfix/vmailbox
Translated: look at the mysql first, then look at the vmailbox (db) table.
Except, this does not appear to work. In the old SuSE SLOX host, it works.
Sure, but what's in the vmailbox table? Is it actually a set of address
(to address) mappings? If these are virtual mailbox locations, they should
be in:
default_database_type = hash
indexed = ${default_database_type}:${config_directory}/
virtual_mailbox_maps = ${indexed}vmailbox
--
Viktor.
IPv6 address in regexp lookup tables
How would I specify all IPv6 addresses starting with 2001:638:700:1005 in a regexp table? Regards, wolfgang
Re: IPv6 address in regexp lookup tables
Wolfgang Zeikat: How would I specify all IPv6 addresses starting with 2001:638:700:1005 in a regexp table? /^2001:638:700:1005:/, assuming a /64 or smaller subnet. But I wonder why CIDR tables would not be a better solution. Wietse
Re: IPv6 address in regexp lookup tables
In an older episode, on 2011-06-08 01:21, Wietse Venema wrote: /^2001:638:700:1005:/, assuming a /64 or smaller subnet. Thank you, Wietse. I have realized that I actually need to match all IPv6 addresses starting with 2001:638:700:, but /^2001:638:700:/ works fine, too. Best regards, wolfgang
Anyone run Postfix in FreeBSD jails environement ?
Hello Does anyone is running postfix in FreeBSD jails environement with success on a production server ? I'm thinking of it and would be interrested by any successful experience. Thank you.
