Re: Why the name Postfix?
Wietse Venema previously_wrote on Mon-28-Mar 22 12:00AM > external name "Postfix". "post" was a different word for "mail", > and "fix" was for Sendmail, the inspiration for my efforts. It is a much cooler sounding name now that its decoded. But in retrospect the meaning is pretty obvious 臘
Re: not working smtpd_recipient_restrictions implementation - postFIXED!
Thank you to all who answered. I learnt from each of the three emails. My config file was seriously wonky (I have become a spam reader -- oh and aparrently spam sender) so it took some persuading but at least for now this particular dragon is slain. Wietse, you belong on Mount Olympus. Best wishes and thanks to all Eric Wietse Venema previously_wrote on Wed-02-Jun 21 7:34PM > Eric Smith: > > Dear fixers, > > > > My postfix ability has dissapated over many years without use :-( > > > > I tried and failing to REJECT an unwanted domain from accessing postfix > > through this in main.cf > > > > smtpd_recipient_restrictions = permit_mynetworks, > > Postfix won't reject mail from your network. > > > permit_sasl_authenticated, > > Postfix won't reject mail from an authenticated client. > > > check_sender_access > > hash:/etc/postfix/sender_access, > > This applies only if the client did not match permit_mynetworks > and did not match permit_sasl_authenticated. > > Wietse > > > reject_unauth_destination, > > reject_rbl_client zen.spamhaus.org, > > reject_rhsbl_reverse_client dbl.spamhaus.org, > > ... > > > > > > /etc/postfix/sender_access > > example2.org REJECT > > unwelcome.tld REJECT > > END > > > > % postmap /etc/postfix/sender_access > > > > % ls /etc/postfix/sender_access* > > sender_access sender_access.db > > > > % sudo postfix restart > > > > > > I wonder if there are any clues here to what I am doing wrong or where I > > might try to fix this. > > > > Thank you in advance and best wishes > > Eric > >
not working smtpd_recipient_restrictions implementation
Dear fixers, My postfix ability has dissapated over many years without use :-( I tried and failing to REJECT an unwanted domain from accessing postfix through this in main.cf smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_sender_access hash:/etc/postfix/sender_access, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, reject_rhsbl_reverse_client dbl.spamhaus.org, ... /etc/postfix/sender_access example2.org REJECT unwelcome.tld REJECT END % postmap /etc/postfix/sender_access % ls /etc/postfix/sender_access* sender_access sender_access.db % sudo postfix restart I wonder if there are any clues here to what I am doing wrong or where I might try to fix this. Thank you in advance and best wishes Eric
delay all email to a defined sender list
Hi List, It happened just one time too many today, in a rushed moment sending the wrong email to the wrong person. Is it possible to exclusively delay sending mail to specific recipients that appear on in a list? This way I suspected such an error of an email to one the special recipients, then I could still delete the email from the queue. Best Eric
configuration of mailman with postfix
Hi I have the following versions mailman 1:2.1.14-3 on postfix 2.9.1-5 and Ubuntu 12.04 LTS My installation is for lists on virtual domains NOT foobar.fruitcom.com but complete virtual domains, in this example foobar.com When I configure with the following instructions such as this one: http://free-electrons.com/blog/mailman-howto-ubuntu-10-04/ Postfix reports a warning: warning: /etc/postfix/main.cf: unused parameter: mailman_destination_recipient_limit=1 Mails sent to one of the list commit...@foobar.com give the following error: |/var/lib/mailman/mail/mailman post committee@fruitcom.com (expanded from commit...@foobar.com): unknown user: |/var/lib/mailman/mail/mailman post committee Is there a suggestion to address this particular issue which I think is the expansion to `committee@fruitcom.com' , alternatively, are there other complete configure instructions that might work? Thanks. -- Best regards, Eric Smith Mobile: 00 31 6 455 09313 - Tel Wageningen: +31 317 72
Re: configuration of mailman with postfix
Thanks Robert (Scott)
I have upgraded, checked and followed the Ubuntu docs.
transport in master.cf corrected (I had a typo that gave the
error with the user expansion), now it is like this;
[root@pepper ~] $ grep -A1 mailman /etc/postfix/master.cf
mailman unix - n n - - pipe
flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
${nexthop} ${user}
$ mutt fres...@fresher2.nl -stest/dev/null;sleep 2;\
sudo sh -c find /var/log/ -mmin -1; grep fresher /var/log/mail.log|tail -1
/var/log/syslog
/var/log/mail.log
/var/log/auth.log
Jul 25 20:45:53 localhost postfix/local[10429]: 70E4329020F: \
to=|/var/lib/mailman/mail/mailman post fres...@fruitcom.com, \
orig_to=fres...@fresher2.nl, relay=local, delay=0.17, \
delays=0.11/0/0/0.06, dsn=5.1.1, status=bounced (unknown user: \
|/var/lib/mailman/mail/mailman post fresher)
FWIW:
[eric@pepper ~] $ echo $HOSTNAME
pepper.fruitcom.com
(Tooth enamel wearing a bit thin)
Any ideas where I could look?
--
Eric Smith
Robert Schetterer wrote on Wed-25-Jul 12 2:36PM
Am 25.07.2012 14:30, schrieb Eric Smith:
Hi
I have the following versions mailman 1:2.1.14-3 on postfix 2.9.1-5 and
Ubuntu 12.04 LTS
My installation is for lists on virtual domains
NOT foobar.fruitcom.com
but complete virtual domains, in this example
foobar.com
When I configure with the following instructions such as this one:
http://free-electrons.com/blog/mailman-howto-ubuntu-10-04/
Postfix reports a warning:
warning: /etc/postfix/main.cf: unused parameter:
mailman_destination_recipient_limit=1
Mails sent to one of the list commit...@foobar.com give the following error:
|/var/lib/mailman/mail/mailman post committee@fruitcom.com
(expanded from
commit...@foobar.com): unknown user: |/var/lib/mailman/mail/mailman
post committee
Is there a suggestion to address this particular issue which I
think is the expansion to `committee@fruitcom.com' ,
alternatively, are there other complete configure instructions that might
work?
Thanks.
looks to me ,like you miss mailman in the transport table
look
https://help.ubuntu.com/community/Mailman
---snip
Associate the domain lists.example.com to the mailman transport with the
transport map. Edit the file /etc/postfix/transport:
lists.example.com mailman:
---snipend
then mailman_destination_recipient_limit=1 should work unless there
arent any more failures
http://www.postfix.org/postconf.5.html#transport_destination_recipient_limit
-snip
transport_destination_recipient_limit (default:
$default_destination_recipient_limit)
A transport-specific override for the
default_destination_recipient_limit parameter value, where transport is
the master.cf name of the message delivery transport.
Note: some transport_destination_recipient_limit parameters will not
show up in postconf command output before Postfix version 2.9. This
limitation applies to many parameters whose name is a combination of a
master.cf service name and a built-in suffix (in this case:
_destination_recipient_limit).
--snipend
--
Best Regards
MfG Robert Schetterer
receiving yahoo mails fails every so often
]: match_list_match: nm1-vm0.bullet.mail.ne1.yahoo.com: no match Jul 21 09:15:55 loki postfix/smtpd[23510]: match_list_match: 98.138.91.74: no match Jul 21 09:15:55 loki postfix/smtpd[23510]: send attr request = disconnect Jul 21 09:15:55 loki postfix/smtpd[23510]: send attr ident = smtp:98.138.91.74 Jul 21 09:15:55 loki postfix/smtpd[23510]: private/anvil: wanted attribute: status Jul 21 09:15:55 loki postfix/smtpd[23510]: input attribute name: status Jul 21 09:15:55 loki postfix/smtpd[23510]: input attribute value: 0 Jul 21 09:15:55 loki postfix/smtpd[23510]: private/anvil: wanted attribute: (list terminator) Jul 21 09:15:55 loki postfix/smtpd[23510]: input attribute name: (end) Jul 21 09:15:55 loki postfix/smtpd[23510]: lost connection after CONNECT from nm1-vm0.bullet.mail.ne1.yahoo.com[98.138.91.74] Jul 21 09:15:55 loki postfix/smtpd[23510]: disconnect from nm1-vm0.bullet.mail.ne1.yahoo.com[98.138.91.74] == Successful Connection: Jul 21 11:26:09 loki postfix/smtpd[25203]: connect from nm25.bullet.mail.ac4.yahoo.com[98.139.52.222] Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostname: nm25.bullet.mail.ac4.yahoo.com ~? 192.168.1.0/24 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostaddr: 98.139.52.222 ~? 192.168.1.0/24 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostname: nm25.bullet.mail.ac4.yahoo.com ~? 192.168.2.0/24 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostaddr: 98.139.52.222 ~? 192.168.2.0/24 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostname: nm25.bullet.mail.ac4.yahoo.com ~? 12.19.144.48/28 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostaddr: 98.139.52.222 ~? 12.19.144.48/28 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostname: nm25.bullet.mail.ac4.yahoo.com ~? 192.168.5.0/24 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_hostaddr: 98.139.52.222 ~? 192.168.5.0/24 Jul 21 11:26:09 loki postfix/smtpd[25203]: match_list_match: nm25.bullet.mail.ac4.yahoo.com: no match Jul 21 11:26:09 loki postfix/smtpd[25203]: match_list_match: 98.139.52.222: no match Jul 21 11:26:09 loki postfix/smtpd[25203]: send attr request = connect Jul 21 11:26:09 loki postfix/smtpd[25203]: send attr ident = smtp:98.139.52.222 Jul 21 11:26:09 loki postfix/smtpd[25203]: private/anvil: wanted attribute: status Jul 21 11:26:09 loki postfix/smtpd[25203]: input attribute name: status Jul 21 11:26:09 loki postfix/smtpd[25203]: input attribute value: 0 Jul 21 11:26:09 loki postfix/smtpd[25203]: private/anvil: wanted attribute: count Jul 21 11:26:09 loki postfix/smtpd[25203]: input attribute name: count Jul 21 11:26:09 loki postfix/smtpd[25203]: input attribute value: 1 Jul 21 11:26:09 loki postfix/smtpd[25203]: private/anvil: wanted attribute: rate Jul 21 11:26:09 loki postfix/smtpd[25203]: input attribute name: rate Jul 21 11:26:09 loki postfix/smtpd[25203]: input attribute value: 1 Jul 21 11:26:09 loki postfix/smtpd[25203]: private/anvil: wanted attribute: (list terminator) Jul 21 11:26:09 loki postfix/smtpd[25203]: input attribute name: (end) Jul 21 11:26:09 loki postfix/smtpd[25203]: nm25.bullet.mail.ac4.yahoo.com[98.139.52.222]: 220 mail.techsoft3d.com ESMTP Postfix Jul 21 11:26:09 loki postfix/smtpd[25203]: watchdog_pat: 0x7ffdf3b7c050 Jul 21 11:26:09 loki postfix/smtpd[25203]: nm25.bullet.mail.ac4.yahoo.com[98.139.52.222]: HELO nm25.bullet.mail.ac4.yahoo.com eric eric smith senior network administrator http://www.techsoft3d.com email: e...@techsoft3d.commailto:e...@techsoft3d.com skype: eric_ae_smith phone: 510-333-1729
Re: receiving yahoo mails fails every so often
The problem is this yahoo and yahoo alone fails to make connections, the problem is random,most emails come through just fine, the specific failures are not repeatable. But an parker of ours uses yahoo business serves for their email, they are getting timeout bounces on 1 in 10 emails sent to us. That is the best description that I have for this issue. As for the verboseness I added this debug_peer_list = yahoo.com to main.cf. It fails with this off as well. If its a local disk race condition why only yahoo and not any other domain. If its DNS issue, why yahoo and no other domain? I had thought that its a firewall mucking the TCP packets, no avail. So I am probably missing something in either my setup or in the log file hence why its included. Thanks, eric eric smith senior network administrator http://www.techsoft3d.com email: e...@techsoft3d.com skype: eric_ae_smith phone: 510-333-1729 On 7/21/11 11:46 AM, Victor Duchovni victor.ducho...@morganstanley.com wrote: On Thu, Jul 21, 2011 at 06:39:58PM +, Eric Smith wrote: Hi All, Here is a strange issue, incoming mail for yahoo fails roughly every 10th time. Also this is (reportedly) only happening to yahoo emails, all other email domains come through just fine. The setup is on ubuntu 10.4 LTS with the standard packages, postfix, clamav, amavis and spamassassin. I have tried many different solutions, TCP_window size is set to 64, 300 smtp process's is the limit, the system is not being overloaded. I also have worked with Sonicwall to make sure that the TCP packets are not getting munged. Any thoughts? You have failed to describe the problem. Failed connection: Jul 21 09:15:55 loki postfix/smtpd[23510]: connect from nm1-vm0.bullet.mail.ne1.yahoo.com[98.138.91.74] Jul 21 09:15:55 loki postfix/smtpd[23510]: match_hostname: nm1-vm0.bullet.mail.ne1.yahoo.com ~? 192.168.1.0/24 Why is verbose logging enabled, turn it off. Jul 21 09:15:55 loki postfix/smtpd[23510]: nm1-vm0.bullet.mail.ne1.yahoo.com[98.138.91.74]: 220 mail.techsoft3d.com ESMTP Postfix Jul 21 09:15:55 loki postfix/smtpd[23510]: smtp_get: EOF Yahoo dropped the connection, probably before you even accepted it. With verbose logging slowing down your server, it may take too long from TCP 3-way handshake until a Postfix smtpd is ready to process it. Jul 21 09:15:55 loki postfix/smtpd[23510]: lost connection after CONNECT from nm1-vm0.bullet.mail.ne1.yahoo.com[98.138.91.74] Jul 21 09:15:55 loki postfix/smtpd[23510]: disconnect from nm1-vm0.bullet.mail.ne1.yahoo.com[98.138.91.74] First turn off verbose logging. Then make sure your syslog is not doing synchronous writes to disk for every log message. Then see whether you still have a problem. Yahoo is timing out you server. Perhaps your DNS is also slow. -- Viktor.
Re: receiving yahoo mails fails every so often
Damn that was what I was afraid ofŠ.. Let see where that rabbit hole brings us, and thank you. Best eric eric smith senior network administrator http://www.techsoft3d.com email: e...@techsoft3d.com skype: eric_ae_smith phone: 510-333-1729 On 7/21/11 12:00 PM, Jeroen Geilman jer...@adaptr.nl wrote: On 2011-07-21 20:55, Eric Smith wrote: The problem is this yahoo and yahoo alone fails to make connections, the problem is random,most emails come through just fine, the specific failures are not repeatable. But an parker of ours uses yahoo business serves for their email, they are getting timeout bounces on 1 in 10 emails sent to us. That is the best description that I have for this issue. As for the verboseness I added this debug_peer_list = yahoo.com to main.cf. It fails with this off as well. If its a local disk race condition why only yahoo and not any other domain. If its DNS issue, why yahoo and no other domain? I had thought that its a firewall mucking the TCP packets, no avail. So I am probably missing something in either my setup or in the log file hence why its included. No, the remote SMTP server not connecting to your server is not caused by your configuration. Do a tcpdump *on the internet connection*, to see what's what. -- J.
Re: receiving yahoo mails fails every so often
This box does one thing only cleans email before forwarding onto an exchange forest. The system is over kill, quad core intel, 16GB memory, hdd is a velociraptor. This is for a network on which we get around 1 email every second. System load never gets 0.1. DNS are two servers both on gigabit on diff networks. All of the body checks are post queue, done by amavis. Will check synchronous syslog, but given the lack of load, not that hopeful. No its a problem up stream, one that tcpdump will help me get an answer. Thank you though. best eric eric smith senior network administrator http://www.techsoft3d.com email: e...@techsoft3d.com skype: eric_ae_smith On 7/21/11 12:13 PM, Victor Duchovni victor.ducho...@morganstanley.com wrote: On Thu, Jul 21, 2011 at 07:05:41PM +, Eric Smith wrote: Damn that was what I was afraid of?.. So I am probably missing something in either my setup or in the log file hence why its included. No, the remote SMTP server not connecting to your server is not caused by your configuration. Do a tcpdump *on the internet connection*, to see what's what. Actually, it can be your configuration if low throughput drives up concurrency to the configured limit, and then connection service latency climbs. Poor throughput can be caused by many factors: - Slow DNS resolution - Inadequate disk I/O capacity - Insufficient network bandwidth - Misconfigured synchronous syslog (default Linux) - Excessive cleanup header/body checks - Slow proxy filters - Slow milters - Slow policy services - Slow lookup tables (MySQL, ...) ... -- Viktor.
return mails received when receiving server implements delay
Whenever I send mail to a server implimenting delay, I receive from MAILER-DAEMON on my own server a mail with body: This is the mail system at host pepper.fruitcom.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system --@fruitcom.com (expanded from --): bad address syntax -n...@fruitcom.com (expanded from -N): bad address syntax -r...@fruitcom.com (expanded from -R): bad address syntax fail...@fruitcom.com (expanded from failure): unknown user: failure f...@fruitcom.com (expanded from full): unknown user: full de...@fruitcom.com (expanded from delay): unknown user: delay Here are the logs when mailing the postfix list server; Jun 23 13:30:20 pepper postfix/qmgr[1447]: 500C1290144: from=majordomo-ow...@cloud9.net, size=10278, nrcpt=1 (queue active) Jun 23 13:30:20 pepper postfix/local[4655]: 500C1290144: to=e...@fruitcom.com, orig_to=e...@fruitcom.com, relay=local, delay=0.26, delays=0.16/0/0/0.09, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail -a $EXTENSION) Jun 23 13:30:20 pepper postfix/qmgr[1447]: 500C1290144: removed Jun 23 13:30:55 pepper postfix/pickup[370]: EE5932901A3: uid=1000 from=eric Jun 23 13:30:55 pepper postfix/cleanup[4747]: EE5932901A3: message-id=mailbox-5944-1308828645-22977@pepper Jun 23 13:30:55 pepper postfix/qmgr[1447]: EE5932901A3: from=e...@fruitcom.com, size=674, nrcpt=8 (queue active) Jun 23 13:30:56 pepper postfix/error[4639]: EE5932901A3: to=--@fruitcom.com, orig_to=--, relay=none, delay=0.03, delays=0.02/0/0/0.01, dsn=5.1.3, status=bounced (bad address syntax) Jun 23 13:30:56 pepper postfix/error[4639]: EE5932901A3: to=-n...@fruitcom.com, orig_to=-N, relay=none, delay=0.05, delays=0.02/0/0/0.02, dsn=5.1.3, status=bounced (bad address syntax) Jun 23 13:30:56 pepper postfix/error[4639]: EE5932901A3: to=-r...@fruitcom.com, orig_to=-R, relay=none, delay=0.05, delays=0.02/0/0/0.03, dsn=5.1.3, status=bounced (bad address syntax) Jun 23 13:30:56 pepper postfix/local[5493]: EE5932901A3: to=fail...@fruitcom.com, orig_to=failure, relay=local, delay=0.06, delays=0.02/0.02/0/0.01, dsn=5.1.1, status=bounced (unknown user: failure) Jun 23 13:30:56 pepper postfix/local[4655]: EE5932901A3: to=f...@fruitcom.com, orig_to=full, relay=local, delay=0.06, delays=0.02/0.03/0/0.01, dsn=5.1.1, status=bounced (unknown user: full) Jun 23 13:30:56 pepper postfix/local[4640]: EE5932901A3: to=e...@fruitcom.com, orig_to=eric.sm...@trustfood.org, relay=local, delay=0.26, delays=0.02/0.01/0/0.22, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail -a $EXTENSION) Jun 23 13:30:56 pepper postfix/local[4455]: EE5932901A3: to=de...@fruitcom.com, orig_to=delay, relay=local, delay=0.99, delays=0.02/0.01/0/0.96, dsn=5.1.1, status=bounced (unknown user: delay) Jun 23 13:30:58 pepper postfix/smtp[4845]: EE5932901A3: to=majord...@cloud9.net, relay=mail.cloud9.net[168.100.1.3]:25, delay=2.9, delays=0.02/0.01/0.54/2.3, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as A5687104C3A) What should I do to fix this? Thanks Eric Smith
Re: return mails received when receiving server implements delay
_How_ are you sending these mails? Looking at the above output, this looks suspicously like a command line gone wrong, something like command -- -N -R failure,full,delay recipi...@example.net Thanks Stefan. Well done you out me on the right path. It is this command in my MUA, set sendmail = /usr/lib/sendmail -oem -oi-f eric.sm...@trustfood.org It never was a problem with servers implementing delay and now it has been for the last months, why could that be? ciao Eric
Re: return mails received when receiving server implements delay - solved
Ah, there was no space between the -oi and the -f. I broke it trying to impliment it some months ago, thanks again for solving this irritating mystery. great. -- - Eric Smith Eric Smith said: _How_ are you sending these mails? Looking at the above output, this looks suspicously like a command line gone wrong, something like command -- -N -R failure,full,delay recipi...@example.net Thanks Stefan. Well done you out me on the right path. It is this command in my MUA, set sendmail = /usr/lib/sendmail -oem -oi-f eric.sm...@trustfood.org It never was a problem with servers implementing delay and now it has been for the last months, why could that be? ciao Eric
yahoo sending to me is timing out
Hello postfix world, I seem to be receiving all of my emails excepting some from people who have emails with yahoo email acounts.They are either taking up to 20 hours in yahoo's queue or being returned. The postfix is a spam filter (amavis/clamscan/SA) for an exchange forest of 55 users, not many, so not much of a load. I am not getting any reports from other legitimate domains sending us emails having this issue. I have tried a bunch of things found on the internet, but the errors still exist. This was not a problem on my prior filter build on postfix 2.2.10. I had generally ignored such errors as my thinking was that these were caused by poorly designed bots, that may be a mistaken assumption with this more current postfix. I am thinking that there is more controls that I might be missing. So please find below an error from a client at yahoo, examples or the errors in postfix logs and my postfix -n output. Thank you for any help or insights that you may have! Eric Client errors are like this, Sorry, we were unable to deliver your message to the following address. Message expired for domain techsoft3d.com http://techsoft3d.com/ Getting these sorts of errors from yahoo on my postfix 2.8.1 server, Jun 3 17:32:02 loki postfix/smtpd[2579]: connect from nm16-vm0.bullet.mail.sp2.yahoo.com[98.139.91.210] Jun 3 17:32:02 loki postfix/smtpd[2579]: C012C640593: client=nm16-vm0.bullet.mail.sp2.yahoo.com[98.139.91.210] Jun 3 17:32:02 loki postfix/smtpd[2579]: lost connection after RCPT from nm16-vm0.bullet.mail.sp2.yahoo.com[98.139.91.210] Jun 3 17:32:02 loki postfix/smtpd[2579]: disconnect from nm16-vm0.bullet.mail.sp2.yahoo.com[98.139.91.210] And May 30 00:39:35 loki postfix/smtpd[24178]: connect from nm8-vm0.bullet.mail.ne1.yahoo.com[98.138.91.23] May 30 00:39:35 loki postfix/smtpd[24178]: lost connection after CONNECT from nm8-vm0.bullet.mail.ne1.yahoo.com[98.138.91.23] May 30 00:39:35 loki postfix/smtpd[24178]: disconnect from nm8-vm0.bullet.mail.ne1.yahoo.com[98.138.91.23] Here is my postconf -n: alias_maps = hash:/etc/aliases config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 inet_protocols = ipv4 local_recipient_maps = local_transport = error:local mail delivery is disabled message_size_limit = 2 mydestination = techsoft3d.com,ts3d.net,ts3d.lan mydomain = techsoft3d.com myhostname = mail.techsoft3d.com mynetworks = 192.168.1.0/24 192.168.2.0/24 12.19.144.48/28 myorigin = techsoft3d.com proxy_interfaces = 12.19.144.50 relay_domains = $mydomain, ts3d.lan, ts3d.net relay_recipient_maps = hash:/etc/postfix/relay_recipients relayhost = smtpd_client_restrictions = reject_rbl_client jksahdkjshakjfkjgsajdh.sbl-xbl.dq.spamhaus.net smtpd_data_restrictions = reject_unauth_pipelining smtpd_helo_required = yes smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination tcp_windowsize = 256 transport_maps = hash:/etc/postfix/transport eric eric smith senior network administrator http://www.techsoft3d.com email: e...@techsoft3d.com skype: eric_ae_smith phone: 510-333-1729
