Limit amount of mails per sender a day?
Hello, is it possible to rate the amount of sent mails per user? Goal is: each mail user should not be possible to send more then 10.000 mails each day. And is it possible to set per user (mailaccount) ? thanks marko
Re: Limit amount of mails per sender a day?
Marko Weber: > > Hello, > is it possible to rate the amount of sent mails per user? > Goal is: each mail user should not be possible to send more then 10.000 > mails each day. > And is it possible to set per user (mailaccount) ? http://postfwd.org/ http://www.policyd.org/ Wietse
Re: Limit amount of mails per sender a day?
Original-Nachricht > Datum: Fri, 21 Oct 2011 14:47:41 +0200 > Von: Marko Weber > An: Postfix Users > Betreff: Limit amount of mails per sender a day? > > Hello, > is it possible to rate the amount of sent mails per user? > Goal is: each mail user should not be possible to send more then 10.000 > mails each day. > And is it possible to set per user (mailaccount) ? > Have a look at policyd -> http://policyd.sourceforge.net/readme.html It has a Sender Throttling > thanks > > marko > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Re: Limit amount of mails per sender a day?
Policyd ( http://www.policyd.org/ ) can probably do what you're after. Rich
high-availability mail cluster?
Hi Folks, I'm about to rebuild a server farm, and I'm thinking about alternate approaches to high-availability for our mail services. Right now, I just run a collection of services (including mail) on a virtual machine, on top of a disk farm, with auto-failover to a hot-spare backup on a 2nd machine. With the addition of a few more machines into the rack, I'm thinking about dis-aggregating several services, and wondering about service-specific high-availability strategies. Can anybody point me to examples, howtos, or what have you on building a high-availability mail cluster - I'm running Postfix, Amavisd, Spammassassin, ClamAV (plus Sympa for list management, and UW IMAP - but those aren't technically part of the mail processing). I'm specifically looking for approaches to redundant storage of mail ques, failover models, recovery from failure, and so forth. Thanks much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra
Re: high-availability mail cluster?
On Fri, 21 Oct 2011 09:27:03 -0400, Miles Fidelman wrote: > Hi Folks, > > I'm about to rebuild a server farm, and I'm thinking about alternate > approaches to high-availability for our mail services. > > Right now, I just run a collection of services (including mail) on a > virtual machine, on top of a disk farm, with auto-failover to a > hot-spare backup on a 2nd machine. With the addition of a few more > machines into the rack, I'm thinking about dis-aggregating several > services, and wondering about service-specific high-availability > strategies. > > Can anybody point me to examples, howtos, or what have you on building a > high-availability mail cluster - I'm running Postfix, Amavisd, > Spammassassin, ClamAV (plus Sympa for list management, and UW IMAP - but > those aren't technically part of the mail processing). I'm specifically > looking for approaches to redundant storage of mail ques, failover > models, recovery from failure, and so forth. > > Thanks much, > > Miles Fidelman Miles, I can outline our setup, which we have spent some time building. We have an external spam filtering solution, which in itself is load balanced and highly available which I will leave out. At the most basic layer we use VMware on commodity hardware, which gives us a lot of flexibility in deploying mail servers (i.e. cloning & templating). If you're not already virtualized I would highly recommend it. In our environment we have four separate mail servers that perform a single task each: - Inbound email (postfix) - POP/IMAP (dovecot) - Outbound email (postfix & dovecot for SASL) - Webmail (Roundcube) We do this to mitigate disaster risk, where if one service bugged out and caused the load to skyrocket, it would not break the other services. This setup has saved us from full blown outages many times, and instead we had a smaller outage that might have just impacted POP/IMAP or inbound mail separately. We also feel this solution is easier to manage as the configs are completely separated. We also have created two to four of each type of server, which are load balanced appropriately. We use NFS storage to tie all of the disk bound services together, as it is naturally a clustering solution for storage, and works great for this mail system. For super high availability we have implemented a NetApp Metro Cluster NAS, where we can instantly failover NFS services from our primary data center to our secondary data center 10 miles away. The virtual machines that host mail are located at both sites as well, and are clustered using a pair of hardware load balancers using VRRP for connectivity failover. This means close to zero downtime, which is really amazing. All of the authentication and aliasing is done from a Galera mysql database. Galera is a multi-master synchronous replication service for mysql, which allows us to host read/write capable cluster of mysql servers that exist at both data centers, providing the most crucial part of the HA solution in my mind. If you have any questions feel free to ask.
First Insallation, Bouncing Emails
Hi;
I've been working on getting postfix and dovecot up and running all week long.
I'm bouncing emails all over hell's half acre and clients are going bizzerck.
I've got the daemon running, but there are a lot of errors:
tail /var/log/maillog
Oct 20 10:13:59 example postfix/smtpd[28141]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30178 exit status 1
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30179 exit status 1
Oct 20 10:13:59 example postfix/smtpd[28458]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30180 exit status 1
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30181 exit status 1
Oct 20 10:13:59 example postfix/smtpd[28483]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/smtpd[28460]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30182 exit status 1
Oct 20 10:13:59 example postfix/smtpd[28455]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30183 exit status 1
Oct 20 10:13:59 example postfix/smtpd[28484]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30184 exit status 1
Oct 20 10:13:59 example postfix/smtpd[29917]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30185 exit status 1
Oct 20 10:13:59 example postfix/smtpd[29953]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30186 exit status 1
Oct 20 10:13:59 example postfix/smtpd[28485]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30187 exit status 1
Oct 20 10:14:15 example postfix/smtpd[30152]: connect from
unknown[66.248.165.32]
Oct 20 10:14:15 example postfix/smtpd[30152]: lost connection after EHLO from
unknown[66.248.165.32]
Oct 20 10:14:15 example postfix/smtpd[30152]: disconnect from
unknown[66.248.165.32]
I also get this in there:
Oct 20 10:13:15 example postfix/smtpd[30152]: warning: dict_nis_init: NIS
domain name not set - NIS lookups disabled
Oct 20 10:13:15 example postfix/smtpd[30152]: cannot load Certificate Authority
data: disabling TLS support
Oct 20 10:13:15 example postfix/smtpd[30152]: warning: TLS library problem:
30152:error:02001002:system library:fopen:No such file or
directory:bss_file.c:122:fopen('/etc/pki/tls/c
erts/cert.pem','r'):
Oct 20 10:13:15 example postfix/smtpd[30152]: warning: TLS library problem:
30152:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:125:
Oct 20 10:13:15 example postfix/smtpd[30152]: warning: TLS library problem:
30152:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system
lib:by_file.c:279:
Oct 20 10:13:15 example postfix/smtpd[30152]: connect from
unknown[66.248.165.32]
Oct 20 10:13:15 example postfix/smtpd[30152]: lost connection after EHLO from
unknown[66.248.165.32]
Oct 20 10:13:15 example postfix/smtpd[30152]: disconnect from
unknown[66.248.165.32]
Oct 20 10:13:57 example postfix/proxymap[28446]: warning: mysql query failed:
You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version f
or the right syntax to use near '??gifteatszone.com??? AND active = 1' at line 1
Oct 20 10:13:57 example postfix/trivial-rewrite[30154]: fatal:
proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf(0,lock|fold_fix): table
lookup problem
Oct 20 10:13:57 example postfix/trivial-rewrite[30155]: fatal:
proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf(0,lock|fold_fix): table
lookup problem
Oct 20 10:13:57 example postfix/proxymap[28444]: warning: mysql query failed:
You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version f
or the right syntax to use near '??awakelunch.info??? AND active = 1' at line 1
The TLS problem isn't mission-critical since it's just getting disabled, but
the mysql problem is critical. Maybe the sasl or pam_mysql is screwed up? How
check?
[root@example jack]# ps wax|grep postfix
4000 ? Ss 0:01 /usr/libexec/postfix/master
31839 pts/2 S+ 0:00 grep postfix
[root@example jack]# ps wax|grep postfixadmin
31842 pts/2 S+ 0:00 grep postfixadmin
[root@example jack]# ps wax|grep saslau
Re: First Insallation, Bouncing Emails
* Jack Fredrikson : > Oct 20 10:13:57 example postfix/proxymap[28446]: warning: mysql query failed: > You have an error in your SQL syntax; check the manual that corresponds to > your MySQL server version f > or the right syntax to use near '??gifteatszone.com??? AND active = 1' at > line 1 > Oct 20 10:13:57 example postfix/proxymap[28444]: warning: mysql query failed: > You have an error in your SQL syntax; check the manual that corresponds to > your MySQL server version f > or the right syntax to use near '??awakelunch.info??? AND active = 1' at line > 1 Check those -- 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: First Insallation, Bouncing Emails
Am 21.10.2011 16:32, schrieb Jack Fredrikson: > Hi; > I've been working on getting postfix and dovecot up and running all week > long. I'm bouncing emails all over hell's > half acre and clients are going bizzerck. I've got the daemon running, but > there are a lot of errors first: you are missing how to report problems "postconf -n" second: your are missing to build up a complex system step by step instead writing big configurations and then start debugging post your "master.cf" i bet this is a debian system and your postfix is chrooted "-" and "y" in this column is yes - change it to n and if i am right complain debian why these dumb maintainers do not stop their chroot-default which leads to trouble most of time -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature
Re: First Insallation, Bouncing Emails
From: Reindl Harald To: postfix-users@postfix.org Sent: Friday, October 21, 2011 10:39 AM Subject: Re: First Insallation, Bouncing Emails I'm on CentOS, not Debian [root@13gems postfix]# /usr/sbin/postconf -d | grep mail_version mail_version = 2.8.5 milter_macro_v = $mail_name $mail_version [root@13gems postfix]# /usr/sbin/postconf -n alias_maps = hash:/etc/aliases broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix content_filter = amavisfeed:[127.0.0.1]:10024 daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debug_peer_list = 127.0.0.1 disable_vrfy_command = yes home_mailbox = Mailbox html_directory = no inet_interfaces = localhost, $myhostname invalid_hostname_reject_code = 450 local_transport = virtual mail_owner = postfix mail_spool_directory = /var/spool/mail mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man maps_rbl_reject_code = 450 mydestination = localhost.$mydomain, localhost, $myhostname mydomain = 13gems.com myhostname = 13gems.com myorigin = $myhostname newaliases_path = /usr/bin/newaliases non_fqdn_reject_code = 450 queue_directory = /var/spool/postfix readme_directory = no sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop show_user_unknown_table_name = no smtpd_data_restrictions = reject_unauth_pipelining, reject_multi_recipient_bounce, permit smtpd_helo_required = yes smtpd_recipient_restrictions = permit_sasl_authenticated reject_unauth_destination reject_invalid_helo_hostname warn_if_reject reject_non_fqdn_helo_hostname warn_if_reject reject_unknown_helo_hostname warn_if_reject reject_unknown_client reject_non_fqdn_sender reject_non_fqdn_recipient reject_unknown_sender_domain reject_unknown_recipient_domain reject_rbl_client zen.spamhaus.org reject_rbl_client bl.spamcop.net reject_rbl_client dnsbl.sorbs.net=127.0.0.2 reject_rbl_client dnsbl.sorbs.net=127.0.0.3 reject_rbl_client dnsbl.sorbs.net=127.0.0.4 reject_rbl_client dnsbl.sorbs.net=127.0.0.5 reject_rbl_client dnsbl.sorbs.net=127.0.0.7 reject_rbl_client dnsbl.sorbs.net=127.0.0.9 reject_rbl_client dnsbl.sorbs.net=127.0.0.11 reject_rbl_client dnsbl.sorbs.net=127.0.0.12 warn_if_reject reject_rhsbl_sender dsn.rfc-ignorant.org warn_if_reject reject_rhsbl_sender abuse.rfc-ignorant.org warn_if_reject reject_rhsbl_sender whois.rfc-ignorant.org warn_if_reject reject_rhsbl_sender bogusmx.rfc-ignorant.org warn_if_reject reject_rhsbl_sender postmaster.rfc-ignorant.org permit smtpd_sasl_auth_enable = yes smtpd_sasl_path = /var/spool/postfix/private/auth smtpd_sasl_security_options = noanonymous, nodictionary smtpd_sasl_tls_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_auth_only = yes unknown_local_recipient_reject_code = 550 virtual_alias_maps = proxy:mysql:$config_directory/mysql_virtual_alias_maps.cf virtual_gid_maps = static:89 virtual_mailbox_base = /var/vmail virtual_mailbox_domains = proxy:mysql:$config_directory/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:$config_directory/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 89 virtual_transport = dovecot virtual_uid_maps = static:89 MASTER.CF smtp inet n - n - - smtpd -o content_filter=spamfilter:dummy 127.0.0.1:10025 inet n - n - - smtpd -o content_filter= -o smtpd_delay_reject=no -o smtpd_client_restrictions=permit_mynetworks,reject -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_data_restrictions=reject_unauth_pipelining -o smtpd_end_of_data_restrictions= -o smtpd_restriction_classes= -o mynetworks=127.0.0.0/8 -o smtpd_error_sleep_time=0 -o smtpd_soft_error_limit=1001 -o smtpd_hard_error_limit=1000 -o smtpd_client_connection_count_limit=0 -o smtpd_client_connection_rate_limit=0 -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_milters,no_address_mappings -o local_header_rewrite_clients= -o smtpd_milters= -o local_recipient_maps= -o relay_recipient_maps= amavisfeed unix - - n - 2 lmtp -o lmtp_data_done_timeout=1200 -o lmtp_send_xforward_command=yes -o disable_dns_lookups=yes -o max_use=20 587 inet n - n - - smtpd pickup fifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr tlsmgr unix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrit
Re: First Insallation, Bouncing Emails
Am 21.10.2011 16:52, schrieb Jack Fredrikson: That error appears to come from a file called /etc/postfix/mysql_virtual_alias_maps.cf that has this line: SELECT goto FROM alias WHERE address = ‘%s’ AND active = 1 Therefore, the address has question marks in it. Looks like a hacker, no? No, the quotation marks in that file are broken. Use '' (simple marks), and not some typographic variant of those (i.e., represented as three bytes in UTF-8, which gets logged as ???). -- --- Heiko.
Re: First Insallation, Bouncing Emails
On 21 October 2011 10:52, Jack Fredrikson wrote: > > From: Reindl Harald > To: postfix-users@postfix.org > Sent: Friday, October 21, 2011 10:39 AM > Subject: Re: First Insallation, Bouncing Emails > > > I'm on CentOS, not Debian > > Ralf Hildebrandt writes: > >>> Oct 20 10:13:57 example postfix/proxymap[28446]: warning: mysql query >>> failed: You have an error in your SQL syntax; check the manual that >>> corresponds to your MySQL server version f >>> or the right syntax to use near '??gifteatszone.com??? AND active = 1' at >>> line 1 >>> Oct 20 10:13:57 example postfix/proxymap[28444]: warning: mysql query >>> failed: You have an error in your SQL syntax; check the manual that >>> corresponds to your MySQL server version f >>> or the right syntax to use near '??awakelunch.info??? AND active = 1' at >>> line 1 > >> Check those > > That error appears to come from a file called > /etc/postfix/mysql_virtual_alias_maps.cf that has this line: > SELECT goto FROM alias WHERE address = ‘%s’ AND active = 1 > Therefore, the address has question marks in it. Looks like a hacker, no? What does /etc/postfix/mysql_virtual_alias_maps.cf look like? Simon
Re: First Insallation, Bouncing Emails
Something like: user = user_for_db password = password_for_db hosts = localhost dbname = database_name query = SELECT goto FROM alias WHERE address='%s' AND active = '1' What does /etc/postfix/mysql_virtual_alias_maps.cf look like? Simon Best regards. -- /*** *Leslie León Sinclair *Administrador de Redes *Facultad de Ingenieria Electrica, CUJAE. *Calle 114 #11901 e/ Ciclovía y Rotonda *Marianao 19390, Ciudad de la Habana, Cuba *Tel: (53 7) 266-3321 *Miembro de GUTL -> http://www.ecured.cu/index.php/Grupo_de_Usuarios_de_Tecnolog%C3%ADas_Libres_GUTL *Another happy Slackware& Debian GNU/Linux user *Proud GNU/Linux User #445535 -> http://counter.li.org/ *Katana yanai, otoko nanda. / Participe en Universidad 2012, del 13 al 17 de febrero de 2012. Habana, Cuba: http://www.congresouniversidad.cu Consulte la enciclopedia colaborativa cubana. http://www.ecured.cu Participe en el Segundo Congreso Medio Ambiente Construido y Desarrollo Sustentable (MACDES 2011) del 6 al 9 de diciembre de 2011, Hotel Nacional, Habana, Cuba: http://macdes.cujae.edu.cu
Re: high-availability mail cluster?
Am 21.10.2011 15:27, schrieb Miles Fidelman: > Hi Folks, > > I'm about to rebuild a server farm, and I'm thinking about alternate > approaches to high-availability for our mail services. > > Right now, I just run a collection of services (including mail) on a > virtual machine, on top of a disk farm, with auto-failover to a > hot-spare backup on a 2nd machine. With the addition of a few more > machines into the rack, I'm thinking about dis-aggregating several > services, and wondering about service-specific high-availability > strategies. > > Can anybody point me to examples, howtos, or what have you on building a > high-availability mail cluster - I'm running Postfix, Amavisd, > Spammassassin, ClamAV (plus Sympa for list management, and UW IMAP - but > those aren't technically part of the mail processing). I'm specifically > looking for approaches to redundant storage of mail ques, failover > models, recovery from failure, and so forth. > > Thanks much, > > Miles Fidelman > > i am using ha-loadbalancers, drbd-ocfs2 storage with dovecot clamav spamassassin postfix mysql on linux ubuntu lucid up to 5000 maildir mailboxes 2 lbs, 2 mail/imap/pop3servers, 1 central logging and backupserver nfs/syslog but thats only one choice, there are a lot of choices left which would work too -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: high-availability mail cluster?
Am 21.10.2011 18:10, schrieb Robert Schetterer: > Am 21.10.2011 15:27, schrieb Miles Fidelman: >> Hi Folks, >> >> I'm about to rebuild a server farm, and I'm thinking about alternate >> approaches to high-availability for our mail services. >> >> Right now, I just run a collection of services (including mail) on a >> virtual machine, on top of a disk farm, with auto-failover to a >> hot-spare backup on a 2nd machine. With the addition of a few more >> machines into the rack, I'm thinking about dis-aggregating several >> services, and wondering about service-specific high-availability >> strategies. >> >> Can anybody point me to examples, howtos, or what have you on building a >> high-availability mail cluster - I'm running Postfix, Amavisd, >> Spammassassin, ClamAV (plus Sympa for list management, and UW IMAP - but >> those aren't technically part of the mail processing). I'm specifically >> looking for approaches to redundant storage of mail ques, failover >> models, recovery from failure, and so forth. >> >> Thanks much, >> >> Miles Fidelman >> >> > > i am using ha-loadbalancers, drbd-ocfs2 storage > with dovecot clamav spamassassin postfix mysql > on linux ubuntu lucid up to 5000 maildir mailboxes > > 2 lbs, 2 mail/imap/pop3servers, 1 central logging and backupserver > nfs/syslog i just forgot, you may host this on vm machines too > > > but thats only one choice, there are a lot of choices left > which would work too i just forgot, you may host this on vm machines too -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: First Insallation, Bouncing Emails
2011/10/21 Leslie León Sinclair : > Something like: > > > user = user_for_db > password = password_for_db > hosts = localhost > dbname = database_name > query = SELECT goto FROM alias WHERE address='%s' AND active = '1' > Thanks. But I think we should see what the OP has in his. As someone already pointed out, if it's not using the correct quote it will be misinterpreted. Simon
Re: Limit amount of mails per sender a day?
Marko Weber: >> >> Hello, >> is it possible to rate the amount of sent mails per user? >> Goal is: each mail user should not be possible to send more then 10.000 >> mails each day. >> And is it possible to set per user (mailaccount) ? > > >Another good one is mailfromd, it can not only do the rate limiting, but, can >do many other things. All around good program, but fancier than some people >need. It has more features than the others mentioned. Steve
Re: First Insallation, Bouncing Emails
Hi; For some reason, having trouble with my yahoo account. Using friend's... From: Heiko Wundram To: postfix-users@postfix.org Sent: Friday, October 21, 2011 11:01 AM Subject: Re: First Insallation, Bouncing Emails > Am 21.10.2011 16:52, schrieb Jack Fredrikson: >> That error appears to come from a file called /etc/postfix/ mysql_virtual_alias_maps.cf that has this line: >> SELECT goto FROM alias WHERE address = ‘%s’ AND active = 1 >> Therefore, the address has question marks in it. Looks like a hacker, no? > > No, the quotation marks in that file are broken. Use '' (simple marks), and not some typographic variant of those (i.e., represented as three bytes in > UTF-8, which gets logged as ???). Arrggg! That was a subtle error! Thanks!!! Here's the latest printout from /var/log/maillog: Oct 21 08:20:44 example postfix/smtpd[23702]: connect from host.peakskillmediacenters.com[50.7.6.219] Oct 21 08:20:45 example postfix/smtpd[23702]: NOQUEUE: reject: RCPT from host.peakskillmediacenters.com[50.7.6.219]: 554 5.7.1 < ddejo...@dejonghgroup.com>: Relay access denied; from= to= proto=ESMTP helo= Oct 21 08:20:45 example postfix/smtpd[23702]: too many errors after RCPT from host.peakskillmediacenters.com[50.7.6.219] Oct 21 08:20:45 example postfix/smtpd[23702]: disconnect from host.peakskillmediacenters.com[50.7.6.219] Oct 21 08:20:45 example postfix/smtpd[23706]: connect from mta3.dealer.sel.sony.com[74.116.6.208] Oct 21 08:20:45 example postfix/smtpd[23706]: NOQUEUE: reject: RCPT from mta3.dealer.sel.sony.com[74.116.6.208]: 554 5.7.1 : Relay access denied; from= to=< ddejo...@dejonghgroup.com> proto=ESMTP helo= Oct 21 08:20:45 example postfix/smtpd[23706]: too many errors after RCPT from mta3.dealer.sel.sony.com[74.116.6.208] Oct 21 08:20:45 example postfix/smtpd[23706]: disconnect from mta3.dealer.sel.sony.com[74.116.6.208] Oct 21 08:20:58 example postfix/smtpd[23683]: warning: 115.167.111.169: hostname 115-167-111-169.wi-tribe.net.pk verification failed: Name or service not known Oct 21 08:20:58 example postfix/smtpd[23683]: connect from unknown[115.167.111.169] Oct 21 08:20:59 example postfix/smtpd[23683]: lost connection after MAIL from unknown[115.167.111.169] Oct 21 08:20:59 example postfix/smtpd[23683]: disconnect from unknown[115.167.111.169] Oct 21 08:20:59 example postfix/smtpd[23713]: connect from mta52.mt-cloud.net[216.213.172.165] Oct 21 08:20:59 example postfix/smtpd[23713]: lost connection after CONNECT from mta52.mt-cloud.net[216.213.172.165] Oct 21 08:20:59 example postfix/smtpd[23713]: disconnect from mta52.mt-cloud.net[216.213.172.165] Oct 21 08:20:59 example postfix/smtpd[23688]: connect from server107d.exghost.com[204.232.236.207] Oct 21 08:21:00 example postfix/smtpd[23688]: NOQUEUE: reject: RCPT from server107d.exghost.com[204.232.236.207]: 554 5.7.1 < rdejo...@dejonghgroup.com>: Relay access denied; from=< jwickl...@whartonsmith.com> to= proto=ESMTP helo= Oct 21 08:21:00 example postfix/smtpd[23688]: too many errors after RCPT from server107d.exghost.com[204.232.236.207] Oct 21 08:21:00 example postfix/smtpd[23688]: disconnect from server107d.exghost.com[204.232.236.207] Oct 21 08:21:02 example postfix/smtpd[23704]: connect from unknown[213.55.83.132] Oct 21 08:21:03 example postfix/smtpd[23704]: NOQUEUE: reject: RCPT from unknown[213.55.83.132]: 554 5.7.1 : Relay access denied; from= to= proto=SMTP helo= Oct 21 08:21:03 example postfix/smtpd[23704]: too many errors after RCPT from unknown[213.55.83.132] Oct 21 08:21:03 example postfix/smtpd[23704]: disconnect from unknown[213.55.83.132] Oct 21 08:21:08 example postfix/smtpd[23711]: connect from unknown[66.248.165.32] Oct 21 08:21:09 example postfix/smtpd[23702]: connect from mail.nghia.vn [116.109.128.19] Oct 21 08:21:10 example postfix/smtpd[23701]: connect from mta834.shop.josbank.com[63.236.77.173] Oct 21 08:21:10 example postfix/smtpd[23711]: lost connection after EHLO from unknown[66.248.165.32] Oct 21 08:21:10 example postfix/smtpd[23711]: disconnect from unknown[66.248.165.32] Oct 21 08:21:11 example postfix/smtpd[23701]: NOQUEUE: reject: RCPT from mta834.shop.josbank.com[63.236.77.173]: 554 5.7.1 : Relay access denied; from=< bo-bwtejugauwpkk5au7z7apbd7qr0...@b.shop.josbank.com> to=< ddejo...@dejonghgroup.com> proto=SMTP helo= Oct 21 08:21:11 example postfix/smtpd[23701]: too many errors after RCPT from mta834.shop.josbank.com[63.236.77.173] Oct 21 08:21:11 example postfix/smtpd[23701]: disconnect from mta834.shop.josbank.com[63.236.77.173] Oct 21 08:21:11 example postfix/smtpd[23707]: warning: 174.136.69.254: hostname Hypv2483.appliedi.net verification failed: Name or service not known Oct 21 08:21:11 example postfix/smtpd[23707]: connect from unknown[174.136.69.254] Oct 21 08:21:11 example postfix/smtpd[23707]: NOQUEUE: reject: RCPT from unknown[174.136.69.254]: 554 5.7.1 : Relay access denied; from= to= proto=ESMTP helo= Oct 21 08:21:11 example postfix/smtpd[23707]: too many errors after RCPT from unknown[174.136.69.254] Oc
