+ Rispondi al Thread
Visualizzazione dei risultati da 1 a 3 su 3

Discussione: [POSTFIX] Non invia correttamente le email

  1. #1
    Fabio_ non è in linea Scolaretto
    Post
    115

    [POSTFIX] Non invia correttamente le email

    Ciao a tutti, sono qui per chiedere un aiuto a voi esperti.
    Ho acquistato una vps con pannello plesk su cui devo farci girare 3 domini.
    l'hostname della vps è vps.dominio1.it
    plesk utilizza come servizio di posta postfix.
    Tutto funziona bene, le email vengono inviate e ricevute da tutti gli indirizzi e verso tutti gli indirizzi email tramite thunderbird o webmail.
    Il problema nasce quando invio una email tramite funzione mail() di php che gira su dominio2.com (in realtà il problema si presenta su tutti i domini presenti sulla vps).
    In poche parole ci sono indirizzi email che riescono a ricevere l'email inviata ed altri no (premetto che php non da errori)
    Vedendo i log di postfix ho notato che quando l'email non viene ricevuta è perchè viene respinta dal destinatario.

    codice:
    Oct 26 14:59:06 vps postfix/pickup[22157]: 15C512EEF: uid=10001 from=<fabio>
    Oct 26 14:59:06 vps postfix/cleanup[24075]: 15C512EEF: message-id=<fc4b5c8688ab138e06042cb14230cb4a@dominio2.com>
    Oct 26 14:59:06 vps postfix/qmgr[1683]: 15C512EEF: from=<fabio@vps.dominio1.it>, size=716, nrcpt=2 (queue active)
    Oct 26 14:59:06 vps postfix/smtp[24077]: certificate verification failed for dominiodestinatario.eu[***.***.***.***]:25: self-signed certificate
    Oct 26 14:59:07 vps postfix/smtp[24077]: 15C512EEF: to=<prova@dominiodestinatario.eu>, relay=dominiodestinatario.eu[***.***.***.***]:25, delay=1.1, delays=0.07/0.01/0.81/0.22, dsn=5.0.0, status=bounced (host dominiodestinatario.eu[***.***.***.***] said: 550-Verification failed for <fabio@vps.dominio1.it> 550-Previous (cached) callout verification failure 550 Sender verify failed (in reply to RCPT TO command))
    Oct 26 14:59:07 vps postfix/cleanup[24075]: 3857D2EF0: message-id=<20131026125907.3857D2EF0@vps.dominio1.it>
    Oct 26 14:59:07 vps postfix/qmgr[1683]: 3857D2EF0: from=<>, size=3475, nrcpt=1 (queue active)
    Oct 26 14:59:07 vps postfix/bounce[24080]: 15C512EEF: sender non-delivery notification: 3857D2EF0
    Oct 26 14:59:07 vps postfix/qmgr[1683]: 15C512EEF: removed
    Oct 26 14:59:07 vps postfix/error[24081]: 3857D2EF0: to=<fabio@vps.dominio1.it>, relay=none, delay=0.03, delays=0.01/0.01/0/0.01, dsn=5.0.0, status=bounced (User unknown in virtual alias table)
    Oct 26 14:59:07 vps postfix/qmgr[1683]: 3857D2EF0: removed
    La cosa strana è che lui fa partire l'email non dall'indirizzo di email da me impostato ma dal nome utente plesk + hostname.
    Ciò non è una costante, nel senso, se invio le email tramite thunderbird, il mittente è quello corretto e l'email arriva a destinazione, se la invio tramite php, mi si genera quel problema.
    Ho pensato allora fosse un problema di impostazione php ma è da escludersi perchè ho installato joomla e l'email inviate tramite esso vengono recapitate. In questo caso, però, il mittente viene settato con la casella di posta corretta e non con l'hostname.

    Vi allego i 2 header delle email ricevute, la prima con joomla, la seconda tramite funzione email (ovviamente ad un casella che riesce a ricevere questa email)

    codice:
    From - Fri Oct 25 13:47:46 2013
    X-Account-Key: account7
    X-UIDL: UID4120-1324073783
    X-Mozilla-Status: 0001
    X-Mozilla-Status2: 00000000
    X-Mozilla-Keys:                                                                                 
    Return-path: <info@dominio1.it>
    Envelope-to: info@dominiodestinatario.com
    Delivery-date: Fri, 25 Oct 2013 11:14:17 +0200
    Received: by vps.dominio1.it (Postfix, from userid 10001)
    	id 595B52EEB; Fri, 25 Oct 2013 11:14:14 +0200 (CEST)
    To: info@dominiodestinatario.com
    Subject: Account Details for prova at My CMS
    X-PHP-Originating-Script: 10001:phpmailer.php
    Date: Fri, 25 Oct 2013 11:14:14 +0200
    From: My CMS <info@dominio1.it>
    Message-ID: <0dde249234e658444642aac571cf08e0@dominio1.it>
    X-Priority: 3
    X-Mailer: PHPMailer 5.2.6 (https://github.com/PHPMailer/PHPMailer/)
    MIME-Version: 1.0
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: 8bit
    
    
    From - Sat Oct 26 18:08:05 2013
    X-Account-Key: account22
    X-UIDL: UID86-1382451572
    X-Mozilla-Status: 0001
    X-Mozilla-Status2: 00000000
    X-Mozilla-Keys: 
    Return-Path: <fabio@vps.dominio1.it>
    X-Original-To: info@dominiodestinatario.com
    Delivered-To: info@dominiodestinatario.com
    Received: by vps.dominio1.it (Postfix, from userid 10001)
    id CCAF92EED; Sat, 26 Oct 2013 18:07:28 +0200 (CEST)
    To: info@teamspeakeurope.com
    Subject: Prova 2 NUOVA
    X-PHP-Originating-Script: 10001:provaemail.php
    From: Info <info@dominio1.it>
    Reply-To: Info <info@dominio1.it>
    X-Mailer: PHP v5.3.3 
    MIME-Version: 1.0
    Content-type: text/html; charset=UTF-8
    Content-Transfer-Encoding: 8bit
    Message-Id: <20131026160728.CCAF92EED@vps.dominio1.it>
    Date: Sat, 26 Oct 2013 18:07:28 +0200 (CEST)
    Ho evidenziato in rosso ciò che mi sembra strano, nella prima email il mittente è il dominio (dominio1.it) nella seconda email il mittente è l'host (vps.dominio1.it)

    Sono giorni che sto impazzendo ma non riesco a venirne a capo, non ho ancora messo a fuoco il problema, dipende da postfix o da php? All'inizio pensavo dipendesse da php ma avendo avuto conferma che con joomla invia correttamente dovrebbe essere problema di postfix. Ma in quali termini dovrebbe essere un problema di postfix se il problema non si presenta sempre anche se le situazioni sono le medesime?

    Vi allego anche il semplicissimo script di test per l'invio della mail in php (l'ho provato anche su un altro dominio ed, ovviamente, funziona bene) in modo che abbiate tutti i dati per valutare.

    Codice PHP:
    <?php

    function InviaEmail($mail$oggetto$text)
    {    
    $header "From: Info <info@dominio1.it>\n";
    $header .= "Reply-To: Info <info@dominio1.it>\n";
    $header .= "Return-Path: Info <info@dominio1.it>\n";
    $header .= "X-Mailer: PHP v".phpversion()." \n";    
    $header .= "MIME-Version: 1.0\n";
    $header .= "Content-type: text/html; charset=UTF-8\n";
    $header .= "Content-Transfer-Encoding: 8bit\n";

    if (
    mail($mail$oggetto'<html><body>' $text '</body></html>'$header))
    {    
    return 
    true;    
    }
    else
    {    
    return 
    false;    
    }    
    }    

    if (
    InviaEmail('info@dominiodestinatario.com''Prova 1 NUOVA'"E' stata eseguita la pagina php alle:<br>ore " date("d/m/Y H:i:s"time()) . "<br>IP " $_SERVER['REMOTE_ADDR'] . "</b>"))
    {
    echo 
    'INVIATA email 1';
    }
    else
    {
    echo 
    'NON INVIATA email 1';    
    }

    ?>
    Vi allego anche la main di postfix

    codice:
    # Global Postfix configuration file. This file lists only a subset
    # of all parameters. For the syntax, and for a complete parameter
    # list, see the postconf(5) manual page (command: "man 5 postconf").
    #
    # For common configuration examples, see BASIC_CONFIGURATION_README
    # and STANDARD_CONFIGURATION_README. To find these documents, use
    # the command "postconf html_directory readme_directory", or go to
    # http://www.postfix.org/.
    #
    # For best results, change no more than 2-3 parameters at a time,
    # and test if Postfix still works after every change.
    
    # SOFT BOUNCE
    #
    # The soft_bounce parameter provides a limited safety net for
    # testing.  When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    #
    #soft_bounce = no
    
    # LOCAL PATHNAME INFORMATION
    #
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    #
    queue_directory = /var/spool/postfix
    
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    #
    command_directory = /usr/sbin
    
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    #
    daemon_directory = /usr/libexec/postfix
    
    
    # The data_directory parameter specifies the location of Postfix-writable
    # data files (caches, random numbers). This directory must be owned
    # by the mail_owner account (see below).
    #
    data_directory = /var/lib/postfix
    
    # QUEUE AND PROCESS OWNERSHIP
    #
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    #
    mail_owner = postfix
    
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #
    #default_privs = nobody
    
    # INTERNET HOST AND DOMAIN NAMES
    #
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #
    #mydomain = domain.tld
    
    
    # SENDING MAIL
    #
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # user@that.users.mailhost.
    #
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #
    #myorigin = $myhostname
    #myorigin = $mydomain
    
    # RECEIVING MAIL
    
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    #
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    #
    # Note: you need to stop/start Postfix when this parameter changes.
    #
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    inet_interfaces = all
    
    # Enable IPv4, and IPv6 if supported
    inet_protocols = all
    
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    #
    #
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    #
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    #
    # The default is $myhostname + localhost.$mydomain.  On a mail domain
    # gateway, you should also include $mydomain.
    #
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    #
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    #
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    #
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    #
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #
    mydestination = localhost.$mydomain, localhost, localhost.localdomain
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
    #       mail.$mydomain, www.$mydomain, ftp.$mydomain
    
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    #
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    #
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    #
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    #
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    #
    # - You define $mydestination domain recipients in files other than
    #   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    #   For example, you define $mydestination domain recipients in
    #   the $virtual_mailbox_maps files.
    #
    # - You redefine the local delivery agent in master.cf.
    #
    # - You redefine the "local_transport" setting in main.cf.
    #
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    #   feature of the Postfix local delivery agent (see local(8)).
    #
    # Details are described in the LOCAL_RECIPIENT_README file.
    #
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    #
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a user@domain.tld address.
    ##
    #local_recipient_maps = unix:passwd.byname $alias_maps
    #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    #
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    #
    unknown_local_recipient_reject_code = 550
    
    # TRUST AND RELAY CONTROL
    
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    #
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix.  See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    #
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    #
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    #
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network.  Instead, specify an explicit
    # mynetworks list by hand, as described below.
    #
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    #
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    #
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to.  See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    #
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    #   subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    #
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    #
    #
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace.  Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    #
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    #
    #relay_domains = $mydestination
    
    # INTERNET OR INTRANET
    
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    #
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    #
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    #
    # If you're connected via UUCP, see also the default_transport parameter.
    #
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    
    # REJECTING UNKNOWN RELAY USERS
    #
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    #
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    
    #
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a user@domain.tld address.
    #
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    
    # INPUT RATE CONTROL
    #
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    #
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    #
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #
    #in_flow_delay = 1s
    
    # ADDRESS REWRITING
    #
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    #
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    
    # "USER HAS MOVED" BOUNCE MESSAGES
    #
    # See the discussion in the ADDRESS_REWRITING_README document.
    
    # TRANSPORT MAP
    #
    
    #
    # See the discussion in the ADDRESS_REWRITING_README document.
    
    # ALIAS DATABASE
    #
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    #
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    #
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    #
    # It will take a minute or so before changes become visible.  Use
    # "postfix reload" to eliminate the delay.
    #
    #alias_maps = dbm:/etc/aliases
    alias_maps = hash:/etc/aliases, hash:/var/spool/postfix/plesk/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi".  This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    
    # ADDRESS EXTENSIONS (e.g., user+foo)
    #
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5) for the effects this has on
    # aliases, canonical, virtual, relocated and .forward file lookups.
    # Basically, the software tries user+foo and .forward+foo before
    # trying user and .forward.
    
    #
    #recipient_delimiter = +
    
    # DELIVERY TO MAILBOX
    #
    # The home_mailbox parameter specifies the optional pathname of a
    # mailbox file relative to a user's home directory. The default
    # mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
    # "Maildir/" for qmail-style delivery (the / is required).
    #
    #home_mailbox = Mailbox
    #home_mailbox = Maildir/
    
    # The mail_spool_directory parameter specifies the directory where
    # UNIX-style mailboxes are kept. The default setting depends on the
    # system type.
    #
    #mail_spool_directory = /var/mail
    #mail_spool_directory = /var/spool/mail
    
    # The mailbox_command parameter specifies the optional external
    # command to use instead of mailbox delivery. The command is run as
    # the recipient with proper HOME, SHELL and LOGNAME environment settings.
    # Exception:  delivery for root is done as $default_user.
    #
    # Other environment variables of interest: USER (recipient username),
    # EXTENSION (address extension), DOMAIN (domain part of address),
    # and LOCAL (the address localpart).
    #
    # Unlike other Postfix configuration parameters, the mailbox_command
    # parameter is not subjected to $parameter substitutions. This is to
    # make it easier to specify shell syntax (see example below).
    #
    # Avoid shell meta characters because they will force Postfix to run
    # an expensive shell process. Procmail alone is expensive enough.
    #
    # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
    # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
    #
    #mailbox_command = /some/where/procmail
    #mailbox_command = /some/where/procmail -a "$EXTENSION"
    
    # The mailbox_transport specifies the optional transport in master.cf
    # to use after processing aliases and .forward files. This parameter
    # has precedence over the mailbox_command, fallback_transport and
    # luser_relay parameters.
    #
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf.  The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    #
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #
    #mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
    
    # If using the cyrus-imapd IMAP server deliver local mail to the IMAP
    # server using LMTP (Local Mail Transport Protocol), this is prefered
    # over the older cyrus deliver program by setting the
    # mailbox_transport as below:
    #
    # mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
    #
    # The efficiency of LMTP delivery for cyrus-imapd can be enhanced via
    # these settings.
    #
    # local_destination_recipient_limit = 300
    # local_destination_concurrency_limit = 5
    #
    # Of course you should adjust these settings as appropriate for the
    # capacity of the hardware you are using. The recipient limit setting
    # can be used to take advantage of the single instance message store
    # capability of Cyrus. The concurrency limit can be used to control
    # how many simultaneous LMTP sessions will be permitted to the Cyrus
    # message store.
    #
    # To use the old cyrus deliver program you have to set:
    #mailbox_transport = cyrus
    
    
    # The fallback_transport specifies the optional transport in master.cf
    # to use for recipients that are not found in the UNIX passwd database.
    # This parameter has precedence over the luser_relay parameter.
    #
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf.  The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    #
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #
    #fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp
    #fallback_transport =
    
    # The luser_relay parameter specifies an optional destination address
    # for unknown recipients.  By default, mail for unknown@$mydestination,
    # unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
    # as undeliverable.
    #
    # The following expansions are done on luser_relay: $user (recipient
    # username), $shell (recipient shell), $home (recipient home directory),
    # $recipient (full recipient address), $extension (recipient address
    # extension), $domain (recipient domain), $local (entire recipient
    # localpart), $recipient_delimiter. Specify ${name?value} or
    # ${name:value} to expand value only when $name does (does not) exist.
    #
    # luser_relay works only for the default Postfix local delivery agent.
    #
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must specify "local_recipient_maps =" (i.e. empty) in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #
    #luser_relay = $user@other.host
    #luser_relay = $local@other.host
    #luser_relay = admin+$local
    
    # JUNK MAIL CONTROLS
    
    # The controls listed here are only a very small subset. The file
    # SMTPD_ACCESS_README provides an overview.
    
    # The header_checks parameter specifies an optional table with patterns
    # that each logical message header is matched against, including
    # headers that span multiple physical lines.
    #
    # By default, these patterns also apply to MIME headers and to the
    # headers of attached messages. With older Postfix versions, MIME and
    # attached message headers were treated as body text.
    #
    # For details, see "man header_checks".
    #
    #header_checks = regexp:/etc/postfix/header_checks
    
    # FAST ETRN SERVICE
    #
    # Postfix maintains per-destination logfiles with information about
    # deferred mail, so that mail can be flushed quickly with the SMTP
    # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
    # See the ETRN_README document for a detailed description.
    #
    # The fast_flush_domains parameter controls what destinations are
    # eligible for this service. By default, they are all domains that
    # this server is willing to relay mail to.
    #
    #fast_flush_domains = $relay_domains
    
    # SHOW SOFTWARE VERSION OR NOT
    #
    # The smtpd_banner parameter specifies the text that follows the 220
    # code in the SMTP server's greeting banner. Some people like to see
    # the mail version advertised. By default, Postfix shows no version.
    #
    # You MUST specify $myhostname at the start of the text. That is an
    # RFC requirement. Postfix itself does not care.
    #
    #smtpd_banner = $myhostname ESMTP $mail_name
    #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
    
    # PARALLEL DELIVERY TO THE SAME DESTINATION
    #
    # How many parallel deliveries to the same user or domain? With local
    # delivery, it does not make sense to do massively parallel delivery
    # to the same user, because mailbox updates must happen sequentially,
    # and expensive pipelines in .forward files can cause disasters when
    # too many are run at the same time. With SMTP deliveries, 10
    # simultaneous connections to the same domain could be sufficient to
    # raise eyebrows.
    #
    # Each message delivery transport has its XXX_destination_concurrency_limit
    # parameter.  The default is $default_destination_concurrency_limit for
    # most delivery transports. For the local delivery agent the default is 2.
    
    #local_destination_concurrency_limit = 2
    #default_destination_concurrency_limit = 20
    
    # DEBUGGING CONTROL
    #
    # The debug_peer_level parameter specifies the increment in verbose
    # logging level when an SMTP client or server host name or address
    # matches a pattern in the debug_peer_list parameter.
    #
    debug_peer_level = 2
    
    # The debug_peer_list parameter specifies an optional list of domain
    # or network patterns, /file/name patterns or type:name tables. When
    # an SMTP client or server host name or address matches a pattern,
    # increase the verbose logging level by the amount specified in the
    # debug_peer_level parameter.
    #
    #debug_peer_list = 127.0.0.1
    #debug_peer_list = some.domain
    
    # The debugger_command specifies the external command that is executed
    # when a Postfix daemon program is run with the -D option.
    #
    # Use "command .. & sleep 5" so that the debugger can attach before
    # the process marches on. If you use an X-based debugger, be sure to
    # set up your XAUTHORITY environment variable before starting Postfix.
    #
    
    debugger_command =
             PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
             ddd $daemon_directory/$process_name $process_id & sleep 5
    
    # If you can't use X, use this to capture the call stack when a
    # daemon crashes. The result is in a file in the configuration
    # directory, and is named after the process name and the process ID.
    #
    # debugger_command =
    #       PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
    #       echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
    #       >$config_directory/$process_name.$process_id.log & sleep 5
    #
    # Another possibility is to run gdb under a detached screen session.
    # To attach to the screen sesssion, su root and run "screen -r
    # <id_string>" where <id_string> uniquely matches one of the detached
    # sessions (from "screen -list").
    #
    # debugger_command =
    #       PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
    #       -dmS $process_name gdb $daemon_directory/$process_name
    #       $process_id & sleep 1
    
    # INSTALL-TIME CONFIGURATION INFORMATION
    #
    # The following parameters are used when installing a new Postfix version.
    #
    # sendmail_path: The full pathname of the Postfix sendmail command.
    # This is the Sendmail-compatible mail posting interface.
    #
    sendmail_path = /usr/sbin/sendmail.postfix
    
    # newaliases_path: The full pathname of the Postfix newaliases command.
    # This is the Sendmail-compatible command to build alias databases.
    #
    newaliases_path = /usr/bin/newaliases.postfix
    
    # mailq_path: The full pathname of the Postfix mailq command.  This
    # is the Sendmail-compatible mail queue listing command.
    #
    mailq_path = /usr/bin/mailq.postfix
    
    # setgid_group: The group for mail submission and queue management
    # commands.  This must be a group name with a numerical group ID that
    # is not shared with other accounts, not even with the Postfix account.
    #
    setgid_group = postdrop
    
    # html_directory: The location of the Postfix HTML documentation.
    #
    html_directory = no
    
    # manpage_directory: The location of the Postfix on-line manual pages.
    #
    manpage_directory = /usr/share/man
    
    # sample_directory: The location of the Postfix sample configuration files.
    # This parameter is obsolete as of Postfix 2.1.
    #
    sample_directory = /usr/share/doc/postfix-2.8.14/samples
    
    # readme_directory: The location of the Postfix README files.
    #
    readme_directory = /usr/share/doc/postfix-2.8.14/README_FILES
    virtual_mailbox_domains = $virtual_mailbox_maps, hash:/var/spool/postfix/plesk/virtual_domains
    virtual_alias_maps = $virtual_maps, hash:/var/spool/postfix/plesk/virtual
    virtual_mailbox_maps = , hash:/var/spool/postfix/plesk/vmailbox
    transport_maps = , hash:/var/spool/postfix/plesk/transport
    smtpd_tls_cert_file = /etc/postfix/postfix_default.pem
    smtpd_tls_key_file = $smtpd_tls_cert_file
    smtpd_tls_security_level = may
    smtpd_use_tls = yes
    smtp_tls_security_level = may
    smtp_use_tls = no
    smtpd_timeout = 3600s
    smtpd_proxy_timeout = 3600s
    disable_vrfy_command = yes
    mynetworks = 127.0.0.0/8 [::1]/128 ***.***.***.***/32 [***::***]/128
    smtpd_sender_restrictions = check_sender_access hash:/var/spool/postfix/plesk/blacklists, permit_sasl_authenticated, check_client_access pcre:/var/spool/postfix/plesk/non_auth.re
    smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated
    smtp_send_xforward_command = yes
    smtpd_authorized_xforward_hosts = 127.0.0.0/8 [::1]/128
    smtpd_sasl_auth_enable = yes
    smtpd_recipient_restrictions = permit_mynetworks, check_client_access pcre:/var/spool/postfix/plesk/no_relay.re, permit_sasl_authenticated, reject_unauth_destination
    virtual_mailbox_base = /var/qmail/mailnames
    virtual_uid_maps = static:30
    virtual_gid_maps = static:31
    smtpd_milters = , inet:127.0.0.1:12768
    non_smtpd_milters = , inet:127.0.0.1:12768
    sender_dependent_default_transport_maps = hash:/var/spool/postfix/plesk/sdd_transport_maps
    virtual_transport = plesk_virtual
    plesk_virtual_destination_recipient_limit = 1
    mailman_destination_recipient_limit = 1
    mailbox_size_limit = 0
    virtual_mailbox_limit = 0
    myhostname = vps.dominio1.it
    Spero vivamente voi possiate aiutarmi a trovare la soluzione.
    Grazie per l'aiuto che vorrete darmi.

    Ciao.

  2. #2
    Fabio_ non è in linea Scolaretto
    Post
    115
    Nessuna anima pia disponibile a darmi una mano?
    Sto provando e riprovando ma non riesco a venirne a capo. A volte credo sia un problema di postfix altre di php.
    Non riesco a mettere a fuoco il problema, l'unica cosa certa è che lo script dovrebbe inviare l'email con un indirizzo di dominio valido e non dall'utente legato all'hostname.
    Joomla invia le email tramite phpmailer e la funzione mail() (è così impostata dal pannello admin). Ho provato a caricare la classe ed inviare l'email con essa, ma stesso problema

    Codice PHP:
    <?php

    include './phpmailer/class.phpmailer.php';

    $mail = new PHPMailer;

    //$mail->isSMTP();                                      // Set mailer to use SMTP
    //$mail->Host = 'smtp1.example.com;smtp2.example.com';  // Specify main and backup server
    //$mail->SMTPAuth = true;                               // Enable SMTP authentication
    //$mail->Username = 'jswan';                            // SMTP username
    //$mail->Password = 'secret';                           // SMTP password
    //$mail->SMTPSecure = 'tls';                            // Enable encryption, 'ssl' also accepted

    $mail->From 'info@dominio2.it';
    $mail->FromName 'Mailer';
    //$mail->addAddress('josh@example.net', 'Josh Adams');  // Add a recipient
    //$mail->addAddress('ellen@example.com');               // Name is optional
    //$mail->addReplyTo('info@example.com', 'Information');
    //$mail->addCC('cc@example.com');
    //$mail->addBCC('bcc@example.com');

    //$mail->WordWrap = 50;                                 // Set word wrap to 50 characters
    //$mail->addAttachment('/var/tmp/file.tar.gz');         // Add attachments
    //$mail->addAttachment('/tmp/image.jpg', 'new.jpg');    // Optional name
    //$mail->isHTML(true);                                  // Set email format to HTML

    $mail->Subject 'Here is the subject';
    $mail->Body    "E' stata eseguita la pagina php alle:<br>ore " date("d/m/Y H:i:s"time()) . "<br>IP " $_SERVER['REMOTE_ADDR'] . "</b>";
    //$mail->AltBody = 'This is the body in plain text for non-HTML mail clients';


    $mail->addAddress('prova@dominiodestinatario.it'); 
    if(!
    $mail->send()) {
       echo 
    'Message could not be sent.';
       echo 
    'Mailer Error: ' $mail->ErrorInfo;
       exit;
    }
    echo 
    'Messaggio inviato' "<br>";

    ?>

    codice:
    From - Sun Oct 27 22:21:43 2013
    X-Account-Key: account25
    X-UIDL: UID5-1382625620
    X-Mozilla-Status: 0001
    X-Mozilla-Status2: 00000000
    X-Mozilla-Keys:                                                                                 
    Return-path: <info@dominio2.it>
    Envelope-to: prova@dominiodestinatario.it
    Delivery-date: Sun, 27 Oct 2013 22:21:30 +0100
    Received: from vps.dominio1.it ([***.***.***.***]:58833)
    	by web3.keliweb.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
    	(Exim 4.80.1)
    	(envelope-from <info@dominio2.it>)
    	id 1VaXm4-002M4i-Vn
    	for prova@dominiodestinatario.it; Sun, 27 Oct 2013 22:21:30 +0100
    Received: by vps.dominio1.it (Postfix, from userid 10001)
    	id 28DC741AF; Sun, 27 Oct 2013 22:21:34 +0100 (CET)
    To: prova@dominiodestinatario.it
    Subject: Account Details for qwerty at My CMS
    X-PHP-Originating-Script: 10001:phpmailer.php
    Date: Sun, 27 Oct 2013 22:21:34 +0100
    From: My CMS <info@dominio2.it>
    Message-ID: <bb92dcae4f676ab92e162a6ac4842477@teamspeakeurope.com>
    X-Priority: 3
    X-Mailer: PHPMailer 5.2.6 (https://github.com/PHPMailer/PHPMailer/)
    MIME-Version: 1.0
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: 8bit
    X-Spam-Status: No, score=0.8
    X-Spam-Score: 8
    X-Spam-Bar: /
    X-Ham-Report: Spam detection software, running on the system "web3.keliweb.com", has
     identified this incoming email as possible spam.  The original message
     has been attached to this so you can view it (if it isn't spam) or label
     similar future email.  If you have any questions, see
     root\@localhost for details.

    Ma come è possibile che joomla riesca ad inviare l'email correttamente ed io no?!?!?!?
    Ho evidenziato in rosso ciò che è corretto ma che con il mio script non fa, esce il nome utente + hostname.
    Inoltre, leggendo bene l'header, ho notato che, nonostante sia arrivata correttamente l'email, sia stata rilevata come possibile spam
    Voi siete la mia ultima spiaggia.


  3. #3
    L'avatar di Max.Riservo
    Max.Riservo non è in linea Scribacchino
    Post
    608
    Non uso PHP (quindi se il problema è lì non so cosa dirti) ma utilizzo PostFix (ed invio mail tramite Kmail e/o Roundcube).
    Intanto volevo evidenziarti questo messaggio di errore nel log di Postifix :
    Oct 26 14:59:07 vps postfix/error[24081]: 3857D2EF0: to=<fabio@vps.dominio1.it>, relay=none, delay=0.03, delays=0.01/0.01/0/0.01, dsn=5.0.0, status=bounced (User unknown in virtual alias table)
    L' errore sembrerebbe indicare che nella tabella dei virtual aliases non esista l' utente fabio@vps.dominio1.it : hai inserito l' utente nel file e poi lo hai compilato (postmap hash:nomefilealias oppure postalias nomefile oppure il comando previsto da tuo sistema) ?

    Io poi controllerei i parametri :
    - myhostname (nel mio caso è il nome del mio server)
    - mydomain (nel mio caso è commentato, nel tuo caso io proveri a scrivere mydomain = dominio1.it)
    - myorigin (nel mio caso è commentato, nel tuo caso proverei prima con myorigin = $myhostname e poi con = $mydomain)
    - relay_domains=$mydestination (anche se commentato dovrebbe essere il valore di default)
    - relay_host (nel mio caso è il nome del server SMTP a cui invio la posta affinchè venga spedita - in questo caso il mio dominio di posta gestito da Aruba)

    Sei sicuro che ti serva abilitare i virtual domains in PostFix?
    Altro non saprei dirti, ma credo che sia un problema di errata configurazione di PostFix e che PHP non abbia colpe!

+ Rispondi al Thread

Permessi di invio

  • Non puoi inserire discussioni
  • Non puoi inserire repliche
  • Non puoi inserire allegati
  • Non puoi modificare i tuoi messaggi