hey I know this isn't an OS question, but I'm lost!! New to configuring Postfix, with a few questions about how to configure Postfix. I'm running Fedora, with Postfix, from the basic yum install. The Sendmail process has been stopped. I can easily send a basic test mail from the cmdline. Ie: mail foo(a)gmail.com subject: blah test . Cc: works with no issue. However, the email on the gmail end, is in the Spam folder, which is to be expected. As I understand the different articles I've seen, Postfix can be configured to allow me to authenticate emails, to in effect, relay/send them using the authenticaion of a valid email user/passwd from a valid gmail account. (or from my own isp user/passwd). This would then allow the emails to be in the Inbox folder! I've seen a great deal of online articles, but I'm still confused as to exactly what's required to make this happen. I know that the main.cf, as well as the transports/sasl-passwd files have to be modified. I'm confused as to whether certs are actually required, or if TSL is/is not required.... So, I'm trying to figure out exactly what config files have to be modified, as well as what has to be inserted in the config files. If I could see the confi files from someone who's actually gone through this process, I could more quickly get my head around what I've screwed up!

On Thu, 2010-03-04 at 20:04 -0600, Mikkel wrote: > If you think of it that narrowly, then you are correct. But if you > take it as an example on how to set up using a smart host with sasl, > then you have a wider audience. > > For that matter, you get people like me, that 3 different smart > hosts, depending on the email address doing the sending. Then there > is the general relay host for the mail that does not match those > rules. Because this setup is on my home network, I can not send the > mail directly from here. For some reason the DSL IP addresses are on > the DUN list. ;) ---- I was just generally referring to the issue of smarthost = gmail which has nothing to do with SASL as far as I could imagine. For that matter, smarthost setup really has nothing to do with SASL.

I am definitely certain that few can match your ingenuity if you are doing 3 smarthost routing methods based upon sender e-mail address because you already know that while you are providing testimony to postfix's flexibility, it was not really designed to scratch that itch.

I can appreciate that it is probably not the easiest thing to get DSL IP addresses, especially dynamically assigned addresses out of Taiwan to be recognized as smtp sources these days... even if you get the e-mails delivered, I would suspect that the spam score would make it somewhat difficult.

On 10-03-04 23:10:45, Tim wrote: > On Thu, 2010-03-04 at 13:42 -0700, Craig White wrote: > > At this stage, I simply will not accept mail from any smtp server > > whose forward & reverse DNS don't match. So if you are sending me > > e-mails from server mail.example.com you better have a reverse DNS > > address that tells me that your ip address points to > mail.example.com. > > That's a rather bad idea, and simply not workable for an *awful* lot > of > people. You *will* be rejecting legit mail with that methodology. > > Although many of us have our own domains, many of them will be hosted > by > a service which hosts hundreds or thousands of other sites using > virtual > named based hosting. We don't each get an IP, and it's completely > impractical to expect that in an IPv4 world. The reverse IP will > point > to the host's domain name, not ours. > > You need to do *better* testing than simply forward and reverse > checking > of one domain name. Yes, Craig's method won't work with any form of virtual hosting or even when the server runs more than one service, as only one of them can be the official name. Servers I run specify which host they are, e.g., my own rapidxen.georgeanelson.com, which won't work with Craig's method. RFC 1912 FCrDNS simply checks that one of the results of a reverselookup maps back to that IP.[1] [1] <http://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>

On Thu, 2010-03-04 at 13:42 -0700, Craig White wrote: > At this stage, I simply will not accept mail from any smtp server > whose forward & reverse DNS don't match. So if you are sending me > e-mails from server mail.example.com you better have a reverse DNS > address that tells me that your ip address points to mail.example.com. That's a rather bad idea, and simply not workable for an *awful* lot of people. You *will* be rejecting legit mail with that methodology. Although many of us have our own domains, many of them will be hosted by a service which hosts hundreds or thousands of other sites using virtual named based hosting. We don't each get an IP, and it's completely impractical to expect that in an IPv4 world. The reverse IP will point to the host's domain name, not ours. You need to do *better* testing than simply forward and reverse checking of one domain name.

On 03/04/2010 06:27 PM, Craig White wrote: > I would submit that only a very tiny amount of people would actually do > what you are trying to do (use gmail as a smarthost). > > Yes, it would be worth it if you leave a trail behind in case anyone > else wants to do that. > If you think of it that narrowly, then you are correct. But if you take it as an example on how to set up using a smart host with sasl, then you have a wider audience. For that matter, you get people like me, that 3 different smart hosts, depending on the email address doing the sending. Then there is the general relay host for the mail that does not match those rules. Because this setup is on my home network, I can not send the mail directly from here. For some reason the DSL IP addresses are on the DUN list. ;)

hey... one more question. the tests i've done work, but the sender/from name on the email is the system name of the account that's doing the sending. is there a param in the main.cf file that can be set to force the sender/from name to a given name?

On Thu, 2010-03-04 at 16:00 -0800, bruce wrote: > craig... > > you misunderstand... > > if you were using postfix to relay through gmail's auth port (as i'm > looking to do) then the conf files would be extremely relevant! > > we'd be attempting to do the same thing... > > however, i finally got it to work!! > > and i thank you for your emails on this! > > i'll do a write up, and post to the list... > > thanks again! ---- I would submit that only a very tiny amount of people would actually do what you are trying to do (use gmail as a smarthost). Yes, it would be worth it if you leave a trail behind in case anyone else wants to do that. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- users mailing list users(a)lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

On Thu, 2010-03-04 at 15:38 -0800, bruce wrote: > hey craig... > > not so fast!! > > i've seen some of those links.. and tried what they've stated. don't work!!! > > i've seen a few sites that imply that you need to set the cert(s) in > order to get the process to work correctly.. > > which is why i wanted to see the conf files of an actual centos user, > who''s running postfilx, so i can do a more complete apples to apples > comparison.. ---- but my configs (or anyone else's configs) would have nothing to do whatsoever with using gmail as a relay host for outbound mail. They are entirely irrelevant to what you are trying to do. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- users mailing list users(a)lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

On Thu, 2010-03-04 at 14:05 -0800, bruce wrote: > Hi Craig... > > I'm getting an err in my maillog file > Mar  4 13:42:17 lserver6 postfix/master[12985]: daemon started -- > version 2.3.3, configuration /etc/postfix > Mar  4 13:42:17 lserver6 postfix/qmgr[12988]: C01AF2DEEEE: > from=&lt;root(a)lserver6.tmesa.com&gt;, size=550, nrcpt=1 (queue active) > Mar  4 13:42:18 lserver6 postfix/smtp[12990]: C01AF2DEEEE: > to=&lt;badouglas(a)gmail.com&gt;, relay=smtp.gmail.com[74.125.43.109]:587, > delay=125, delays=124/0.04/0.71/0.17, dsn=5.7.0, status=bounced (host > smtp.gmail.com[74.125.43.109] said: 530 5.7.0 Must issue a STARTTLS > command first. 13sm724730bwz.15 (in reply to MAIL FROM command)) > Mar  4 13:42:47 lserver6 sendmail[12995]: o24Lgl76012995: from=root, > size=57, class=0, nrcpts=1, > msgid=&lt;201003042142.o24Lgl76012995(a)lserver6.tmesa.com&gt;, > relay=root@localhost > Mar  4 13:42:47 lserver6 postfix/smtpd[12996]: connect from > localhost.localdomain[127.0.0.1] > Mar  4 13:42:47 lserver6 postfix/smtpd[12996]: 534892DEF05: > client=localhost.localdomain[127.0.0.1] > Mar  4 13:42:47 lserver6 postfix/cleanup[12998]: 534892DEF05: > message-id=&lt;201003042142.o24Lgl76012995(a)lserver6.tmesa.com&gt; > Mar  4 13:42:47 lserver6 postfix/qmgr[12988]: 534892DEF05: > from=&lt;root(a)lserver6.tmesa.com&gt;, size=555, nrcpt=1 (queue active) > Mar  4 13:42:47 lserver6 sendmail[12995]: o24Lgl76012995: > to=badouglas(a)gmail.com, ctladdr=root (0/0), delay=00:00:00, > xdelay=00:00:00, mailer=relay, pri=30057, relay=[127.0.0.1] > [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as 534892DEF05) > Mar  4 13:42:47 lserver6 postfix/smtpd[12996]: disconnect from > localhost.localdomain[127.0.0.1] > > !!!!!! ERROR !!!!!!!!! > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Mar  4 13:42:48 lserver6 postfix/smtp[12999]: 534892DEF05: > to=&lt;badouglas(a)gmail.com&gt;, relay=smtp.gmail.com[72.14.221.111]:587, > delay=0.94, delays=0.07/0.03/0.67/0.17, dsn=5.7.0, status=bounced > (host smtp.gmail.com[72.14.221.111] said: 530 5.7.0 Must issue a > STARTTLS command first. e20sm1840001fga.10 (in reply to MAIL FROM > command)) > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > !!!!!! ERROR !!!!!!!!! > > > I've got the following in my conf files: > > main.cf > smtp_sasl_auth_enable = yes > smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd > smtp_sasl_security_options = > relayhost = smtp.gmail.com:587 > > > > > sasl_passwd > smtp.gmail.com                foo@gmail.com:foopasswd > > transports > gmail.com     smtp:[smtp.gmail.com]:587 > > > i did a > /usr/sbin/postmap    sasl-passwd > /usr/sbin/postmap    transports > > /sbin/service postfix restart > > > > any thoughts/comments? > ---- yes, you are trying to send mail through Gmail's servers (smarthost?) and you would necessarily have to configure that using Gmail's configuration requirements which have absolutely nothing to do postfix authentication with client SASL or client TLS. I just did a google search for 'postfix smarthost gmail' http://www.google.com/search?q=postfix+smarthost +gmail&btnG=Search&hl=en&sa=2 and I am sure one of the first 10 items (if not all of them) would help. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- users mailing list users(a)lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

hey craig. Thanks for the reply. I've been knee deep in docs since last night.. as well as testing some of what I've read. I've been looking at various sites, as well as the postfix.org site. At this point, I was looking to see where I'm screwing up, by taking a look at the conf files of someone who's actually gotten something like this implemented... Right now, I'm more or less spinnning my wheels!! Thanks! ps. I know something like this is doable, as I've created basic php apps in the past that did this kind of thing (the auth user/passwd) in php...

Craig White: > I actually have a long set of postfix rules which determine which mail > gets through - far more than 'simply forward and reverse checking' and > I'm surprised that you would think I would do less. Might have something to do with you saying this: "At this stage, I simply will not accept mail from any smtp server whose forward & reverse DNS don't match. So if you are sending me e-mails from server mail.example.com you better have a reverse DNS address that tells me that your ip address points to mail.example.com." If you didn't mean what you said, you should have said something different. Because, quite frankly, what you *said* isn't going to work. While I set all possible domain names (web server, mail server, MX records, etc.), to use my domain name instead of the hosting services, I cannot set the PTR for my host's mail server to point to my domain. And neither can thousands of other people.

This, is laughable, too: > I do this for many companies that are my clients and I get absolutely > no complaints (and very little spam). They're not going to know if they've not received real mail that was falsely identified as spam. Nor will you know about it if you make it impossible to email you about it.