Help with postfix

Jim Flanagan

15 Jan 2006 15 Jan '06

16:15

Hi, I'm trying to complete my migration from my suse 8.2 box to my clean install of Suse 10.0 retail. All default w KDE except I'm running Cyrus imap. That's all working. My internet domain is set us as example.com and mail.example.com. I'm on a dynamic ip, with my fqdn resolved to this ip. I can't seem to send/receive messages using thunderbird. I can send/receive using "mail". A telnet session does not seem to work correctly, see below, linux:/home/user # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.example.com ESMTP Postfix HELO 501 Syntax: HELO hostname HELO client.example.com 250 mail.example.com MAIL FROM: 250 Ok RCPT TO: 250 Ok Test mail from a telnet session. 502 Error: command not implemented . 502 Error: command not implemented QUIT 221 Bye Connection closed by foreign host. -and_ linux:/home/user # telnet 192.168.xxx.xxx 25 Trying 192.168.xxx.xxx... Connected to 192.168.xxx.xxx. Escape character is '^]'. 220 mail.example.com ESMTP Postfix HELO client.example.com 250 mail.example.com MAIL FROM: 250 Ok RCPT TO: 250 Ok DATA 354 End data with <CR><LF>.<CR><LF> Test mail from a telnet session. . 250 Ok: queued as 3E8A0D3D9 QUIT 221 Bye Connection closed by foreign host. I'm not sure postfix is reading my subnet correctly, postconf mynetworks mynetworks = 127.0.0.0/8 192.168.1.0/24 [::1]/128 [fe80::]/64 But my subnet is not in the 192.168.1.0/24 range. I tried setting it manually to my range, but got an error on postfix reload. Pehaps I'm not setting it correclty, or I need to do something with ifconfig. My ethernet card is set up by the yast default install. Connected to my nat router (small box). All local machines, including my new and old mail server get ip via dhcp from this router. At present postconf -n returns... postconf -n alias_maps = hash:/etc/aliases biff = no canonical_maps = hash:/etc/postfix/canonical command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/lib/postfix debug_peer_level = 2 defer_transports = disable_dns_lookups = no disable_mime_output_conversion = no html_directory = /usr/share/doc/packages/postfix/html inet_interfaces = all inet_protocols = all mail_owner = postfix mail_spool_directory = /var/mail mailbox_command = mailbox_size_limit = 51200000 mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man masquerade_classes = envelope_sender, header_sender, header_recipient masquerade_exceptions = root message_size_limit = 10240000 mydestination = $mydomain, $myhostname, localhost mydomain = example.com myhostname = mail.example.com myorigin = $mydomain newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/packages/postfix/README_FILES relayhost = localhost relocated_maps = hash:/etc/postfix/relocated sample_directory = /usr/share/doc/packages/postfix/samples sender_canonical_maps = hash:/etc/postfix/sender_canonical sendmail_path = /usr/sbin/sendmail setgid_group = maildrop smtp_sasl_auth_enable = no smtp_use_tls = no smtpd_client_restrictions = smtpd_helo_required = no smtpd_helo_restrictions = smtpd_recipient_restrictions = permit_mynetworks,reject_unauth_destination smtpd_sasl_auth_enable = no smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_use_tls = no strict_8bitmime = yes strict_rfc821_envelopes = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 The actual hostname of this box is not FQDN, but something like linux.local Any help appreciated. I need to move my email off my 8.2 box as security fixes aren't being supported any longer. Many thanks, Jim

Show replies by date

Sandy Drobic

15 Jan 15 Jan

16:37

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

Hi, I'm trying to complete my migration from my suse 8.2 box to my clean install of Suse 10.0 retail. All default w KDE except I'm running Cyrus imap. That's all working. My internet domain is set us as example.com and mail.example.com. I'm on a dynamic ip, with my fqdn resolved to this ip.

I can't seem to send/receive messages using thunderbird. I can send/receive using "mail". A telnet session does not seem to work correctly, see below,

linux:/home/user # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.example.com ESMTP Postfix HELO 501 Syntax: HELO hostname HELO client.example.com 250 mail.example.com MAIL FROM: 250 Ok RCPT TO: 250 Ok Test mail from a telnet session. 502 Error: command not implemented . 502 Error: command not implemented QUIT 221 Bye Connection closed by foreign host.

smtp connection needs these steps: telnet mail.example.com 25 Trying xxx.xxx.xxx.xxx... Connected to mail.example.com. Escape character is '^]'. 220 mail.example.com ESMTP Postfix ehlo client.example.com 250-mail.example.com mail from: 250 Ok rcpt to: 250 Ok data ..... cr/lf . cr/lf

...

I'm not sure postfix is reading my subnet correctly,

postconf mynetworks mynetworks = 127.0.0.0/8 192.168.1.0/24 [::1]/128 [fe80::]/64

But my subnet is not in the 192.168.1.0/24 range. I tried setting it manually to my range, but got an error on postfix reload. Pehaps I'm not setting it correclty, or I need to do something with ifconfig. My ethernet card is set up by the yast default install. Connected to my nat router (small box). All local machines, including my new and old mail server get ip via dhcp from this router.

Always set a server up with a static ip.

...

At present postconf -n returns...

postconf -n alias_maps = hash:/etc/aliases biff = no canonical_maps = hash:/etc/postfix/canonical command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/lib/postfix debug_peer_level = 2 defer_transports = disable_dns_lookups = no disable_mime_output_conversion = no html_directory = /usr/share/doc/packages/postfix/html inet_interfaces = all inet_protocols = all mail_owner = postfix mail_spool_directory = /var/mail mailbox_command = mailbox_size_limit = 51200000 mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man masquerade_classes = envelope_sender, header_sender, header_recipient masquerade_exceptions = root message_size_limit = 10240000 mydestination = $mydomain, $myhostname, localhost mydomain = example.com myhostname = mail.example.com myorigin = $mydomain newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/packages/postfix/README_FILES relayhost = localhost

Uh, what is that supposed to do? This should be the mail server of your isp or you can leave it empty and try to send directly. Though that will lead to many rejected mails from big isp that refuse to accept mails from dynamic ips.

...

relocated_maps = hash:/etc/postfix/relocated sample_directory = /usr/share/doc/packages/postfix/samples sender_canonical_maps = hash:/etc/postfix/sender_canonical sendmail_path = /usr/sbin/sendmail setgid_group = maildrop smtp_sasl_auth_enable = no smtp_use_tls = no smtpd_client_restrictions = smtpd_helo_required = no smtpd_helo_restrictions = smtpd_recipient_restrictions = permit_mynetworks,reject_unauth_destination smtpd_sasl_auth_enable = no smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_use_tls = no strict_8bitmime = yes strict_rfc821_envelopes = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550

The actual hostname of this box is not FQDN, but something like linux.local

Any help appreciated. I need to move my email off my 8.2 box as security fixes aren't being supported any longer.

Log entries? I am flying blind here! Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

Anders Johansson

16:38

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

RCPT TO: 250 Ok Test mail from a telnet session. 502 Error: command not implemented

You never issued the DATA command

...

DATA 354 End data with <CR><LF>.<CR><LF> Test mail from a telnet session. . 250 Ok: queued as 3E8A0D3D9

Here you did, so it was accepted. What did you see in /var/log/mail when this happened?

...

But my subnet is not in the 192.168.1.0/24 range. I tried setting it

What is your range then? You replaced it with xxx.xxx in the paste from the telnet session, but that is fundamentally useless, as no one would be able to connect to your private IPs anyway, even if you published them all. You can hide public IPs if you want (but if it's a public mail server, you have to publish it at some point) but private IPs don't have to be protected

...

The actual hostname of this box is not FQDN, but something like linux.local

That shouldn't be used. Ever. .local isn't a valid domain, it's reserved for zeroconf stuff. But tell us what it says in /var/log/mail when you try to send a mail. Usually postfix is very good at specifying what the problem is

Jim Flanagan

17:30

New subject: [SLE] Help with postfix

Anders Johansson wrote:

...

Jim Flanagan wrote:

...
RCPT TO: 250 Ok Test mail from a telnet session. 502 Error: command not implemented

You never issued the DATA command

OK, I did telnet again to both "local host" and to "192.168.1.117" as follows: # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.example.com ESMTP Postfix HELO client.example.com 250 mail.jjfiii.com MAIL FROM: 250 Ok RCPT TO: 250 Ok DATA 354 End data with <CR><LF>.<CR><LF> Test mail from a telnet session. . 250 Ok: queued as CDBF3D440 QUIT 221 Bye Connection closed by foreign host. and # telnet 192.168.1.117 25 Trying 192.168.1.117... Connected to 192.168.1.117. Escape character is '^]'. 220 mail.example.com ESMTP Postfix HELO clinet.example.com 250 mail.example.com MAIL FROM: 250 Ok RCPT TO: 250 Ok DATA 354 End data with <CR><LF>.<CR><LF> Test mail from a telent session. . 250 Ok: queued as 954F5D458 QUIT /var/log/mail shows... Jan 15 11:12:07 cammee postfix/smtpd[23919]: connect from localhost[127.0.0.1] Jan 15 11:13:03 cammee postfix/smtpd[23919]: CDBF3D440: client=localhost[127.0.0.1] Jan 15 11:13:29 cammee postfix/cleanup[23922]: CDBF3D440: message-id=<20060115171234.CDBF3D440@mail.example.com> Jan 15 11:13:29 cammee postfix/qmgr[23866]: CDBF3D440: from=, size=365, nrcpt=1 (queue active) Jan 15 11:13:29 cammee postfix/smtp[23923]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024) Jan 15 11:13:29 cammee postfix/smtp[23923]: CDBF3D440: to=, relay=none, delay=55, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused) Jan 15 11:13:35 cammee postfix/smtpd[23919]: disconnect from localhost[127.0.0.1] Jan 15 11:13:59 cammee postfix/smtpd[23919]: connect from unknown[192.168.1.117] Jan 15 11:14:40 cammee postfix/smtpd[23919]: 954F5D458: client=unknown[192.168.1.117] Jan 15 11:14:56 cammee postfix/cleanup[23922]: 954F5D458: message-id=<20060115171426.954F5D458@mail.example.com> Jan 15 11:14:56 cammee postfix/qmgr[23866]: 954F5D458: from=, size=367, nrcpt=1 (queue active) Jan 15 11:14:56 cammee postfix/smtp[23923]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024) Jan 15 11:14:56 cammee postfix/smtp[23923]: 954F5D458: to=, relay=none, delay=30, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused) Jan 15 11:14:59 cammee postfix/smtpd[23919]: disconnect from unknown[192.168.1.117]

...

What is your range then? You replaced it with xxx.xxx in the paste from the telnet session, but that is fundamentally useless, as no one would be able to connect to your private IPs anyway, even if you published them all. You can hide public IPs if you want (but if it's a public mail server, you have to publish it at some point) but private IPs don't have to be protected

...
The actual hostname of this box is not FQDN, but something like linux.local

That shouldn't be used. Ever. .local isn't a valid domain, it's reserved for zeroconf stuff.

But tell us what it says in /var/log/mail when you try to send a mail. Usually postfix is very good at specifying what the problem is

OK, I have my nat router set to issue addresses to 192.168.1.110/120. The new server is 192.168.1.117. I'm not sure at this point what to name my server. The default install uses linux.local. On my old machine I have been usung successfully something like that, myserver.local, and had postfix using example.com as masquerade_domain. This server is my only server that will be used from email, http, smb, and other file sharing. Small home setup. Many thanks, Jim

Sandy Drobic

17:40

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

DATA 354 End data with <CR><LF>.<CR><LF> Test mail from a telnet session. . 250 Ok: queued as CDBF3D440 QUIT

Server accepts mails from localhost

...

/var/log/mail shows...

Jan 15 11:12:07 cammee postfix/smtpd[23919]: connect from localhost[127.0.0.1] Jan 15 11:13:03 cammee postfix/smtpd[23919]: CDBF3D440: client=localhost[127.0.0.1] Jan 15 11:13:29 cammee postfix/cleanup[23922]: CDBF3D440: message-id=<20060115171234.CDBF3D440@mail.example.com> Jan 15 11:13:29 cammee postfix/qmgr[23866]: CDBF3D440: from=, size=365, nrcpt=1 (queue active) Jan 15 11:13:29 cammee postfix/smtp[23923]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)

Maybe it would be a good idea to start amavisd-new? It seems your content-filter on port 10024 (standard port for amavisd-new is not working. rcamavisd status? rcamavisd start? log entries after starting? Send another testmail now. if it works: postsuper -R ALL

...

OK, I have my nat router set to issue addresses to 192.168.1.110/120. The new server is 192.168.1.117.

Just give the server a static ip, do not use a dynamic one, lest some day all your forwarded ports on your router point to a different pc and not your server.

...

I'm not sure at this point what to name my server. The default install uses linux.local. On my old machine I have been usung successfully something like that, myserver.local, and had postfix using example.com as masquerade_domain.

example.com is a domain name that is used exclusively for examples. Just set up a name and stick with it. You probably want to access your server from the internet side later, so set up a ddns name (dyndns.org, no-ip.org etc.). Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

Jim Flanagan

18:33

New subject: [SLE] Help with postfix

Sandy Drobic wrote:

...

Jim Flanagan wrote:

...
DATA 354 End data with <CR><LF>.<CR><LF> Test mail from a telnet session. . 250 Ok: queued as CDBF3D440 QUIT

Server accepts mails from localhost

...
/var/log/mail shows...

Jan 15 11:12:07 cammee postfix/smtpd[23919]: connect from localhost[127.0.0.1] Jan 15 11:13:03 cammee postfix/smtpd[23919]: CDBF3D440: client=localhost[127.0.0.1] Jan 15 11:13:29 cammee postfix/cleanup[23922]: CDBF3D440: message-id=<20060115171234.CDBF3D440@mail.example.com> Jan 15 11:13:29 cammee postfix/qmgr[23866]: CDBF3D440: from=, size=365, nrcpt=1 (queue active) Jan 15 11:13:29 cammee postfix/smtp[23923]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)

Maybe it would be a good idea to start amavisd-new? It seems your content-filter on port 10024 (standard port for amavisd-new is not working.

rcamavisd status? rcamavisd start?

log entries after starting?

Send another testmail now.

if it works: postsuper -R ALL

...
OK, I have my nat router set to issue addresses to 192.168.1.110/120. The new server is 192.168.1.117.

Just give the server a static ip, do not use a dynamic one, lest some day all your forwarded ports on your router point to a different pc and not your server.

...
I'm not sure at this point what to name my server. The default install uses linux.local. On my old machine I have been usung successfully something like that, myserver.local, and had postfix using example.com as masquerade_domain.

example.com is a domain name that is used exclusively for examples. Just set up a name and stick with it. You probably want to access your server from the internet side later, so set up a ddns name (dyndns.org, no-ip.org etc.).

Sandy Hi Sandy,

Running amavis start returns... /etc/init.d/amavis start returned 7 (program is not running): Starting virus-scanner (amavisd-new): The value of variable $myhostname is "cammee", but should have been a fully qualified domain name; perhaps uname(3) did not provide such. You must explicitly assign a FQDN of this host to variable $myhostname in amavisd.conf, or fix what uname(3) provides as a host's network name! ..failed So, it is getting fouled up wiht my hostname at present. I'm not clear as to what style to use as my host name. My postfix book says to use an fqdn, but I did not need to do that on my 8.2 box. I have jjfiii dot com set up as my fqdn, but my old 8.2 box has a hostname of something.local. As stated before, I used masquerade_domains = jjfiii dot com. That worked on that set up. Doen't seem to work on this one. Anyway, could I just use anyname as my server name, and re-set it in amavise, or do I really need to set my server name to my fqdn?? Tks, Jim

Sandy Drobic

18:59

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

Running amavis start returns... /etc/init.d/amavis start returned 7 (program is not running): Starting virus-scanner (amavisd-new): The value of variable $myhostname is "cammee", but should have been a fully qualified domain name; perhaps uname(3) did not provide such. You must explicitly assign a FQDN of this host to variable $myhostname in amavisd.conf, or fix what uname(3) provides as a host's network name! ..failed

I don't really understand your problem with the fqdn, but you are free to set the name to amavis.linux.site, if you wish. Just disable dns resolution for services that have to accept connections from amavis like the service on port 10025 in master.cf, otherwise you might suffer from dns time-outs.

...

So, it is getting fouled up wiht my hostname at present. I'm not clear as to what style to use as my host name. My postfix book says to use an fqdn, but I did not need to do that on my 8.2 box. I have jjfiii dot com set up as my fqdn, but my old 8.2 box has a hostname of something.local. As stated before, I used masquerade_domains = jjfiii dot com. That worked on that set up. Doen't seem to work on this one.

fqdn is at least a domain name or better a hostname with a domain name. If you have a local dns server set up a fantasy domain and provide correct dns forward and reverse resolution.

...

Anyway, could I just use anyname as my server name, and re-set it in amavise, or do I really need to set my server name to my fqdn??

Maybe it would help you if I explicitely tell you that the name itself will not be checked, only that it satisfies the definition of fully qualified domain name? What could hurt you is the missing reverse dns resolution. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

Jim Flanagan

19:10

New subject: [SLE] Help with postfix

...

Jim Flanagan wrote:

...
Running amavis start returns... /etc/init.d/amavis start returned 7 (program is not running): Starting virus-scanner (amavisd-new): The value of variable $myhostname is "cammee", but should have been a fully qualified domain name; perhaps uname(3) did not provide such. You must explicitly assign a FQDN of this host to variable $myhostname in amavisd.conf, or fix what uname(3) provides as a host's network name! ..failed

I don't really understand your problem with the fqdn, but you are free to set the name to amavis.linux.site, if you wish. Just disable dns resolution for services that have to accept connections from amavis like the service on port 10025 in master.cf, otherwise you might suffer from dns time-outs.

...
So, it is getting fouled up wiht my hostname at present. I'm not clear as to what style to use as my host name. My postfix book says to use an fqdn, but I did not need to do that on my 8.2 box. I have jjfiii dot com set up as my fqdn, but my old 8.2 box has a hostname of something.local. As stated before, I used masquerade_domains = jjfiii dot com. That worked on that set up. Doen't seem to work on this one.

fqdn is at least a domain name or better a hostname with a domain name. If you have a local dns server set up a fantasy domain and provide correct dns forward and reverse resolution.

...
Anyway, could I just use anyname as my server name, and re-set it in amavise, or do I really need to set my server name to my fqdn??

Maybe it would help you if I explicitely tell you that the name itself will not be checked, only that it satisfies the definition of fully qualified domain name? What could hurt you is the missing reverse dns resolution.

Sandy OK Sandy, this message received on my new mail server. I re-named my server from cammee.local to just cammee. Set $myshotname = 'mail.jjfiii.com' in amavisd.conf. I guess the problem was with amavis

Sandy Drobic wrote: the whole time. I did find thru uname that reverse dns did not resolve previoulsly. Does that still matter? You menitoned earlier about relay_host = localhost. I have that working now, but have found limitations in the past where I can't send email to certain isp's. How do I set that up to work with my isp's smtp server? I know the settings to address thier server, and my user name and password, but were do I enter these for postfix to use them? Many many thanks, Jim

Sandy Drobic

20:32

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

OK Sandy, this message received on my new mail server. I re-named my server from cammee.local to just cammee. Set $myshotname = 'mail.jjfiii.com' in amavisd.conf. I guess the problem was with amavis the whole time. I did find thru uname that reverse dns did not resolve previoulsly. Does that still matter?

You menitoned earlier about relay_host = localhost. I have that working now, but have found limitations in the past where I can't send email to certain isp's. How do I set that up to work with my isp's smtp server? I know the settings to address thier server, and my user name and password, but were do I enter these for postfix to use them?

I am using transport settings for those pesky domains. The necessary settings are the following: smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_type = cyrus /etc/postfix/sasl_passwd: [mail.myisp.net] username:password [mail.myisp.net]:submission username:password Some mailserver are satisfied if you have an ip from their network, others need smtp auth to verify the actual user. In the first case you only need to set the relay host, in the latter you have to set all the settings above. Make sure that you have the necessary sasl libraries installed. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

Jim Flanagan

16 Jan 16 Jan

01:07

New subject: [SLE] Help with postfix

Sandy Drobic wrote:

...

Jim Flanagan wrote:

...
OK Sandy, this message received on my new mail server. I re-named my server from cammee.local to just cammee. Set $myshotname = 'mail.jjfiii.com' in amavisd.conf. I guess the problem was with amavis the whole time. I did find thru uname that reverse dns did not resolve previoulsly. Does that still matter?

You menitoned earlier about relay_host = localhost. I have that working now, but have found limitations in the past where I can't send email to certain isp's. How do I set that up to work with my isp's smtp server? I know the settings to address thier server, and my user name and password, but were do I enter these for postfix to use them?

I am using transport settings for those pesky domains.

The necessary settings are the following:

smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_type = cyrus

/etc/postfix/sasl_passwd: [mail.myisp.net] username:password [mail.myisp.net]:submission username:password

Some mailserver are satisfied if you have an ip from their network, others need smtp auth to verify the actual user. In the first case you only need to set the relay host, in the latter you have to set all the settings above. Make sure that you have the necessary sasl libraries installed.

Hi Sandy, Now I'm getting a bit confused. I was going to set up smtp sasl auth enable for my email server, as well as tls, which would encrypt outside connections to that. Now my isp does not require encryption, but they do require smtpauth, unencrypted. I may be answering my own question there, but does the line smtp_sasl_auth_enable = yes refer to my relayhost, and the smtpd_sasl_auth_enable = yes refer to my mail server? If so then we are setting the relayhost to use smtp_sasl_auth and can separately set smtpd_sasl_auth to allow outside relay thru my mail server, to my isp's server to the destination? Sorry for the double questions. Jim

Sandy Drobic

06:47

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

Hi Sandy,

Now I'm getting a bit confused. I was going to set up smtp sasl auth enable for my email server, as well as tls, which would encrypt outside connections to that. Now my isp does not require encryption, but they do require smtpauth, unencrypted. I may be answering my own question there, but does the line smtp_sasl_auth_enable = yes refer to my relayhost, and the smtpd_sasl_auth_enable = yes refer to my mail server?

Correct, the smtp_* refer to the client part of Postfix and the smtpd_* parameter deal with your own server configuration.

...

If so then we are setting the relayhost to use smtp_sasl_auth and can separately set smtpd_sasl_auth to allow outside relay thru my mail server, to my isp's server to the destination?

That's right. They can be configured completely different from each other. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

Jim Flanagan

20:58

New subject: [SLE] Help with postfix

...

Jim Flanagan wrote:

...
Hi Sandy,

Now I'm getting a bit confused. I was going to set up smtp sasl auth enable for my email server, as well as tls, which would encrypt outside connections to that. Now my isp does not require encryption, but they do require smtpauth, unencrypted. I may be answering my own question there, but does the line smtp_sasl_auth_enable = yes refer to my relayhost, and the smtpd_sasl_auth_enable = yes refer to my mail server?

Correct, the smtp_* refer to the client part of Postfix and the smtpd_* parameter deal with your own server configuration.

...
If so then we are setting the relayhost to use smtp_sasl_auth and can separately set smtpd_sasl_auth to allow outside relay thru my mail server, to my isp's server to the destination?

That's right. They can be configured completely different from each other.

Sandy Many thanks Sandy for clarifying this. I never was sure about the distinction between to two till now. Its amazing how all this comes together at one time in ones understanding! I do have the relay working

Sandy Drobic wrote: thru my isp now, but I can say their servers are quite a bit busier than my own!! Much slower delivery times :) Jim

Jim Flanagan

15 Jan 15 Jan

19:20

New subject: [SLE] Help with postfix

...

Jim Flanagan wrote:

...
Running amavis start returns... /etc/init.d/amavis start returned 7 (program is not running): Starting virus-scanner (amavisd-new): The value of variable $myhostname is "cammee", but should have been a fully qualified domain name; perhaps uname(3) did not provide such. You must explicitly assign a FQDN of this host to variable $myhostname in amavisd.conf, or fix what uname(3) provides as a host's network name! ..failed

I don't really understand your problem with the fqdn, but you are free to set the name to amavis.linux.site, if you wish. Just disable dns resolution for services that have to accept connections from amavis like the service on port 10025 in master.cf, otherwise you might suffer from dns time-outs.

...
So, it is getting fouled up wiht my hostname at present. I'm not clear as to what style to use as my host name. My postfix book says to use an fqdn, but I did not need to do that on my 8.2 box. I have jjfiii dot com set up as my fqdn, but my old 8.2 box has a hostname of something.local. As stated before, I used masquerade_domains = jjfiii dot com. That worked on that set up. Doen't seem to work on this one.

fqdn is at least a domain name or better a hostname with a domain name. If you have a local dns server set up a fantasy domain and provide correct dns forward and reverse resolution.

...
Anyway, could I just use anyname as my server name, and re-set it in amavise, or do I really need to set my server name to my fqdn??

Maybe it would help you if I explicitely tell you that the name itself will not be checked, only that it satisfies the definition of fully qualified domain name? What could hurt you is the missing reverse dns resolution.

Sandy OK Sandy, this message received on my new mail server. I re-named my server from cammee.local to just cammee. Set $myshotname = 'mail.jjfiii.com' in amavisd.conf. I guess the problem was with amavis

Sandy Drobic wrote: the whole time. I did find thru uname that reverse dns did not resolve previoulsly. Does that still matter? You menitoned earlier about relay_host = localhost. I made it = <blank> and it sends, but have found limitations in the past where I can't send email to certain isp's. How do I set that up to work with my isp's smtp server? I know the settings to address thier server, and my user name and password, but were do I enter these for postfix to use them? Many many thanks, Jim

Patrick Shanahan

19:30

New subject: [SLE] Help with postfix

* Jim Flanagan [01-15-06 14:22]:

...

You menitoned earlier about relay_host = localhost. I made it = <blank> and it sends, but have found limitations in the past where I can't send email to certain isp's. How do I set that up to work with my isp's smtp server? I know the settings to address thier server, and my user name and password, but were do I enter these for postfix to use them?

in /etc/postfix/main.cf set relayhost = <your smtp.ip.provider.server> use Yast2 to do this. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Jim Flanagan

20:07

New subject: [SLE] Help with postfix

Patrick Shanahan wrote:

...

* Jim Flanagan [01-15-06 14:22]:

...
You menitoned earlier about relay_host = localhost. I made it = <blank> and it sends, but have found limitations in the past where I can't send email to certain isp's. How do I set that up to work with my isp's smtp server? I know the settings to address thier server, and my user name and password, but were do I enter these for postfix to use them?

in /etc/postfix/main.cf set relayhost = <your smtp.ip.provider.server>

use Yast2 to do this.

Hi Patrick, Thanks for the info, but I don't think yast will update my main.cf now as I ahve been editing it manually. I do see where to put the isp server name info in the main.cf, but not sure where to put the user name and password. Many thanks, Jim

Patrick Shanahan

20:18

New subject: [SLE] Help with postfix

* Jim Flanagan [01-15-06 15:08]:

...

Thanks for the info, but I don't think yast will update my main.cf now as I ahve been editing it manually. I do see where to put the isp server name info in the main.cf, but not sure where to put the user name and password.

first: delete /var/adm/SuSEconfig/md5/etc/postfix/mail.cf the edit with Yast2 -> Editor for /etc/sysconfig Files -> Network -> Mail -> Postfix -> POSTFIX_RELAYHOST add the address your isp gave you for smtp there will be no complaint from SuSEconfig for your previous alterations of /etc/postfix/main.cf as you deleted the md5 checkfile which will be regenerated the next time SuSEconfig runs. ps: I do not have user-name or password anywhere in main.cf and have no problems -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Anders Johansson

18:02

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

OK, I have my nat router set to issue addresses to 192.168.1.110/120. The new server is 192.168.1.117.

OK, this is actually in the 192.168.1.0/24 range, that range covers all addresses that start with 192.168.1

...

I'm not sure at this point what to name my server. The default install uses linux.local.

Not in 9.3 it didn't. .local will fail to work properly in 9.3. Older versions did, but more recent ones will default to using .site For the rest of the answer, see Sandy's mail

Anders Johansson

18:07

New subject: [SLE] Help with postfix

I blithered:

...

Not in 9.3 it didn't. .local will fail to work properly in 9.3.

I'm sorry, for some reason I got it into my head that you were running 9.3. But it's still true in 10.0, the default is linux.site. If you have .local in there, you either upgraded from an older installation and kept the old hostname, or you entered it manually

Jim Flanagan

18:21

New subject: [SLE] Help with postfix

Anders Johansson wrote:

...

I blithered:

...
Not in 9.3 it didn't. .local will fail to work properly in 9.3.

I'm sorry, for some reason I got it into my head that you were running 9.3. But it's still true in 10.0, the default is linux.site. If you have .local in there, you either upgraded from an older installation and kept the old hostname, or you entered it manually

What should I name my machine? I've never been clear on that. Or rather what style should I use? My postfix book says to use an fqdn, but I haven't done that in the past. Can I just make it something like bob, or george, or something like that. I could use my fqdn jjfiii dot com, but for some reason I'm a bit reluctant to do that, I guess for if/when I change the machine out in the future. Tks, Jim

Sandy Drobic

18:36

New subject: [SLE] Help with postfix

Jim Flanagan wrote:

...

Anders Johansson wrote:

...
I blithered:

...
Not in 9.3 it didn't. .local will fail to work properly in 9.3.

I'm sorry, for some reason I got it into my head that you were running 9.3. But it's still true in 10.0, the default is linux.site. If you have .local in there, you either upgraded from an older installation and kept the old hostname, or you entered it manually

What should I name my machine? I've never been clear on that. Or rather what style should I use? My postfix book says to use an fqdn, but I haven't done that in the past. Can I just make it something like bob, or george, or something like that. I could use my fqdn jjfiii dot com, but for some reason I'm a bit reluctant to do that, I guess for if/when I change the machine out in the future.

You can give it any name you like. I have a machine at work that is called spamkill, though I configured postfix to announce itself as gateway. You can see the real machine name in the header lines but otherwise it doesn't really matter. My local server here at home is katgar.washu.lab, it's a fantasy name, but my local dns server knows that domain, so all is fine. (^-^) Though I do recommend to set at least $myhostname in postfix main.cf to the name that should be visible for external clients, in your case jjfiii.com. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

6683

Age (days ago)

6684

Last active (days ago)

List overview

Download

19 comments

4 participants

participants (4)

Anders Johansson
Jim Flanagan
Patrick Shanahan
Sandy Drobic