Re: bad From: field
* /dev/rob0 r...@gmx.co.uk: On Thursday 10 November 2011 15:21:17 Ralf Hildebrandt wrote: * privat ulrich.laut...@t-online.de: BTW, for composing and sending mail, I use mutt. in muttrc: my_hdr From: Ralf Hildebrandt ralf.hildebra...@charite.de I tried this, but now my mail says I am you! Please help!! Little story: When I first started with mutt I used Sven Guckes's (of vim fame) .muttrc and FORGOT to adapt my_hdr :| -- 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: postfix not running and not startable
Zitat von Dave Stevens g...@uniserve.com: I have a vps running ubuntu 10.04LTS on an openVZ platform. On top of that I installed Virtualmin GPL to help host web sites and simplify mail setup. I don't have much need for mail at the moment but I expect to in the next few months. Recently I ssh'd into the machine and did this: logwatch --mailto=m...@mydomain.com and after a few seconds I got a series of errors ending at line 870 in logwatch. The vps has 1.5 gigs guaranteed, 8GB burst, two cores, 40 gigs storage. Lots of resources as far as I can see. Investigation showed postfix not running. So... I issued this command to try to start postfix: sudo service postfix start and syslog shows this output: Nov 4 17:01:15 cl28810 postfix/master[11337]: fatal: bind: private/lmtp: No such file or directory Nov 4 17:01:36 cl28810 postfix/postfix-script[11515]: warning: not owned by postfix: /var/spool/postfix/private/anvil Nov 4 17:01:36 cl28810 postfix/postfix-script[11516]: warning: not owned by postfix: /var/spool/postfix/private/lmtp Nov 4 17:01:36 cl28810 postfix/postfix-script[11517]: warning: not owned by postfix: /var/spool/postfix/private/scache Nov 4 17:01:36 cl28810 postfix/postfix-script[11518]: warning: not owned by postfix: /var/spool/postfix/private/maildrop Nov 4 17:01:37 cl28810 postfix/postfix-script[11549]: starting the Postfix mail system Nov 4 17:01:37 cl28810 postfix/master[11550]: fatal: bind: private/lmtp: No such file or directory I don't understand the significance of these errors, although I can see they could cause problems. logwatch used to work on this machine so postfix was working then, a few months back. I had a look into /var/spool/postfix/private and got: # ls -l /var/spool/postfix/private/ ls: cannot access /var/spool/postfix/private/anvil: No such file or directory ls: cannot access /var/spool/postfix/private/lmtp: No such file or directory ls: cannot access /var/spool/postfix/private/scache: No such file or directory ls: cannot access /var/spool/postfix/private/maildrop: No such file or directory total 0 s? ? ? ? ?? anvil srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 bounce srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 bsmtp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 defer srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 discard srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 error srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 ifmail s? ? ? ? ?? lmtp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 local s? ? ? ? ?? maildrop srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 mailman srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 proxymap srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 proxywrite srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 relay srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 retry srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 rewrite s? ? ? ? ?? scache srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 scalemail-backend srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 smtp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 tlsmgr srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 trace srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 uucp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 verify srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 virtual and again don't understand what the significance of these errors is, or, more to the point, what to do to either diagnose or fix the problem. Your (virtual) filesystem is hosed. Nothing Postfix can do about and no way Postfix can operate with such errors. Reboot the Hardware Node with full filesystem check. What OpenVZ kernel you are running and what filesystem are the containers on? Regards Andreas smime.p7s Description: S/MIME Cryptographic Signature
Re: Problem In Zimbra Postfix
On 2011-11-11 06:33, Uma Shankar wrote: Hi Guys, Do you have any idea about how does the zimbra domain alias works. This is the postfix users mailing list. For support on Zimbra you'd have to contact their support. As currently I have done the following setup but I am getting an error Recipient address rejected: User unknown in virtual alias table; real domain: domain.com http://domain.com alias domain: aliasdomain.com http://aliasdomain.com user: t...@domain.com mailto:t...@domain.com No such configuration settings in postfix. creation of the alias domain: zmprov createAliasDomain aliasdomain.com http://aliasdomain.com domain.com http://domain.com zimbraMailCatchAllForwardingAddress @domain.com http://domain.com No such commands in postfix. Now if I send a mail from the outside to t...@aliasdomain.com mailto:t...@aliasdomain.com postfix says user unknown in virtual alias table. If I configure an alias for t...@domain.com mailto:t...@domain.com as t...@aliasdomain.com mailto:t...@aliasdomain.com all works correctly. That IS a postfix message, but alas impossible to troubleshoot unless you follow the instructions you received on joining the list: http://www.postfix.org/DEBUG_README.html#mail Is there a way to automagically do domain aliasing without create an alias for each filan user? (in plain postfix this is the default behaviour). In plain postfix this is absolutely not the default behaviour. -- J.
Re: Problem In Zimbra Postfix
--On Friday, November 11, 2011 11:03 AM +0530 Uma Shankar rajarya...@gmail.com wrote: Hi Guys, Do you have any idea about how does the zimbra domain alias works. As currently I have done the following setup but I am getting an error Recipient address rejected: User unknown in virtual alias table; The correct location to ask your question(s) would be at: http://www.zimbra.com/forums/ or, since you are a network edition user, to file a support ticket. You may also want to read http://wiki.zimbra.com/wiki/Managing_Domains --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. Zimbra :: the leader in open source messaging and collaboration
canonical.db: Inappropriate file type or format
Hello, Here is the system: freebsd2.higonnet.net 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 I have just built postfix from source Nov 11 20:12:41 freebsd2 postfix/master[64285]: reload -- version 2.8.7, configuration /usr/local/etc/postfix Nov 11 20:13:08 freebsd2 postfix/qmgr[64852]: warning: problem talking to service rewrite: Operation timed out Nov 11 20:13:14 freebsd2 postfix/cleanup[64928]: fatal: open database /usr/local/etc/postfix/canonical.db: Inappropriate file type or format The main.cf file has been copied without change so far from a working version 2.7.1 running under FreeBSD 8.1 The canonical.db file has been produced by using postmap hash: using the same canonical file as the aforementioned working older version. postconf -m says hash is possible. As unusal I must be doing something dumb and simple; I only wish I knew what it is... TIA Bernard Higonnet PS I believe all the other db files are also bad
Re: postfix not running and not startable
Quoting lst_ho...@kwsoft.de: Content-Type: text/plain; charset=ISO-8859-1; DelSp=Yes; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Zitat von Dave Stevens g...@uniserve.com: I have a vps running ubuntu 10.04LTS on an openVZ platform. On top of that I installed Virtualmin GPL to help host web sites and simplify mail setup. I don't have much need for mail at the moment but I expect to in the next few months. Recently I ssh'd into the machine and did this: logwatch --mailto=m...@mydomain.com and after a few seconds I got a series of errors ending at line 870 in logwatch. The vps has 1.5 gigs guaranteed, 8GB burst, two cores, 40 gigs storage. Lots of resources as far as I can see. Investigation showed postfix not running. So... I issued this command to try to start postfix: sudo service postfix start and syslog shows this output: Nov 4 17:01:15 cl28810 postfix/master[11337]: fatal: bind: private/lmtp: No such file or directory Nov 4 17:01:36 cl28810 postfix/postfix-script[11515]: warning: not owned by postfix: /var/spool/postfix/private/anvil Nov 4 17:01:36 cl28810 postfix/postfix-script[11516]: warning: not owned by postfix: /var/spool/postfix/private/lmtp Nov 4 17:01:36 cl28810 postfix/postfix-script[11517]: warning: not owned by postfix: /var/spool/postfix/private/scache Nov 4 17:01:36 cl28810 postfix/postfix-script[11518]: warning: not owned by postfix: /var/spool/postfix/private/maildrop Nov 4 17:01:37 cl28810 postfix/postfix-script[11549]: starting the Postfix mail system Nov 4 17:01:37 cl28810 postfix/master[11550]: fatal: bind: private/lmtp: No such file or directory I don't understand the significance of these errors, although I can see they could cause problems. logwatch used to work on this machine so postfix was working then, a few months back. I had a look into /var/spool/postfix/private and got: # ls -l /var/spool/postfix/private/ ls: cannot access /var/spool/postfix/private/anvil: No such file or directory ls: cannot access /var/spool/postfix/private/lmtp: No such file or directory ls: cannot access /var/spool/postfix/private/scache: No such file or directory ls: cannot access /var/spool/postfix/private/maildrop: No such file or directory total 0 s? ? ? ? ?? anvil srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 bounce srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 bsmtp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 defer srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 discard srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 error srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 ifmail s? ? ? ? ?? lmtp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 local s? ? ? ? ?? maildrop srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 mailman srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 proxymap srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 proxywrite srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 relay srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 retry srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 rewrite s? ? ? ? ?? scache srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 scalemail-backend srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 smtp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 tlsmgr srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 trace srw-rw-rw- 1 postfix postfix 0 2011-09-27 00:20 uucp srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 verify srw-rw-rw- 1 postfix postfix 0 2011-11-09 16:06 virtual and again don't understand what the significance of these errors is, or, more to the point, what to do to either diagnose or fix the problem. Your (virtual) filesystem is hosed. Nothing Postfix can do about and no way Postfix can operate with such errors. Reboot the Hardware Node with full filesystem check. What OpenVZ kernel you are running and what filesystem are the containers on? Regards Andreas # uname -a Linux cl28810 2.6.18-238.12.1.el5.028stab091.1PAE #1 SMP Wed Jun 1 13:59:03 MSD 2011 i686 GNU/Linux # cat mtab /dev/simfs / reiserfs rw,usrquota,grpquota 0 0 Like this, will get to the fsck later today. Thanks, Dave -- It is told that such are the aerodynamics and wing loading of the bumblebee that, in principle, it cannot fly...if all this be true...life among bumblebees must bear a remarkable resemblance to life in the United States. -- John Kenneth Galbraith, in American Capitalism: The Concept of Countervailing Power
Re: canonical.db: Inappropriate file type or format
On 11/11/2011 1:30 PM, Bernard T. Higonnet wrote: Hello, Here is the system: freebsd2.higonnet.net 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 I have just built postfix from source Nov 11 20:12:41 freebsd2 postfix/master[64285]: reload -- version 2.8.7, configuration /usr/local/etc/postfix Nov 11 20:13:08 freebsd2 postfix/qmgr[64852]: warning: problem talking to service rewrite: Operation timed out Nov 11 20:13:14 freebsd2 postfix/cleanup[64928]: fatal: open database /usr/local/etc/postfix/canonical.db: Inappropriate file type or format The main.cf file has been copied without change so far from a working version 2.7.1 running under FreeBSD 8.1 When you copy postfix setup files, you must then run # postfix upgrade-configuration and # postfix set-permissions When you copy indexed files between systems with different versions of the BDB library, you need to rebuild the files on the new system. Remove the existing unusable *.db files and postmap the input files to create new .db files. -- Noel Jones
Re: canonical.db: Inappropriate file type or format
On 11/11/2011 11:30 AM, Bernard T. Higonnet wrote: Hello, Here is the system: freebsd2.higonnet.net 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 I have just built postfix from source Nov 11 20:12:41 freebsd2 postfix/master[64285]: reload -- version 2.8.7, configuration /usr/local/etc/postfix Nov 11 20:13:08 freebsd2 postfix/qmgr[64852]: warning: problem talking to service rewrite: Operation timed out Nov 11 20:13:14 freebsd2 postfix/cleanup[64928]: fatal: open database /usr/local/etc/postfix/canonical.db: Inappropriate file type or format The main.cf file has been copied without change so far from a working version 2.7.1 running under FreeBSD 8.1 The canonical.db file has been produced by using postmap hash: using the same canonical file as the aforementioned working older version. postconf -m says hash is possible. As unusal I must be doing something dumb and simple; I only wish I knew what it is... TIA Bernard Higonnet PS I believe all the other db files are also bad It would be interesting to see the results of the following commands: file /usr/local/etc/postfix/canonical.db postconf canonical_maps postconf default_database_type Joe
Re: canonical.db: Inappropriate file type or format
On 11/11/2011 3:03 PM, Bernard T. Higonnet wrote: On 11/11/11 20:47, Noel Jones wrote: When you copy indexed files between systems with different versions of the BDB library, you need to rebuild the files on the new system. Remove the existing unusable *.db files and postmap the input files to create new .db files. I had already re-created all the db files postmap hash:file All the databases are still bad... The Inappropriate file type or format message is from opening a database with the wrong format, such as opening a btree: database as a hash:, or built from a different version of the BDB library, or the .db file is somehow corrupted. Please verify that you build your files with postmap hash:file and that your postconf -n output shows hash:file in all those map settings. It also may help to explicitly set default_database_type = hash in main.cf Is there any possibility of multiple postfix installations on your system, such as one hand-built and one from ports? One quick test is to see if you can query the map with postmap -q somekey hash:file or display the file with postmap -s hash:file. If those commands don't work, your postfix build is badly broken. -- Noel Jones
Re: Problem In Zimbra Postfix
Hi All, Thanks for your support. Regards, Uma Shankar On Fri, Nov 11, 2011 at 11:52 PM, Quanah Gibson-Mount qua...@zimbra.comwrote: --On Friday, November 11, 2011 11:03 AM +0530 Uma Shankar rajarya...@gmail.com wrote: Hi Guys, Do you have any idea about how does the zimbra domain alias works. As currently I have done the following setup but I am getting an error Recipient address rejected: User unknown in virtual alias table; The correct location to ask your question(s) would be at: http://www.zimbra.com/forums/ or, since you are a network edition user, to file a support ticket. You may also want to read http://wiki.zimbra.com/wiki/**Managing_Domainshttp://wiki.zimbra.com/wiki/Managing_Domains --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. Zimbra :: the leader in open source messaging and collaboration
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 simon.brere...@buongiorno.commailto:simon.brere...@buongiorno.com To: postfix users postfix-users@postfix.orgmailto: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.
