Sendmail SMTP Relay

lockdoc

Well-Known Member
Also simpel gesagt, ich wuerde gerne meinen webserver emails versenden lassen via der php mail function.

Um das in Angriff zu nehmen, habe ich SASL--AUTH aus den ports installiert und sendmail mit den folgenden make.conf Vars neugebaut
Code:
SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL -DSTARTTLS
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl2 -lssl -lcrypto

<HOSTNAME>.<MYDOMAIN>.mc
Code:
divert(0)
VERSIONID(`$FreeBSD: release/9.0.0/etc/sendmail/freebsd.mc 223068 2011-06-14 04:33:43Z gshapiro $')
OSTYPE(freebsd6)
DOMAIN(generic)

FEATURE(access_db, `hash -o -T<TMPF> /etc/mail/access')
FEATURE(blacklist_recipients)
FEATURE(local_lmtp)
FEATURE(mailertable, `hash -o /etc/mail/mailertable')
FEATURE(virtusertable, `hash -o /etc/mail/virtusertable')

define(`SMART_HOST', `smtp.gmail.com')
define(`RELAY_MAILER_ARGS', `TCP $h 587')
define(`ESMTP_MAILER_ARGS', `TCP $h 587')
define(`authinfo', `hash /etc/mail/auth/client-info')dnl

define(`confCW_FILE', `-o /etc/mail/local-host-names')

DAEMON_OPTIONS(`Family=inet, Port=25, Name=TLSMTA')dnl

define(`confAUTH_OPTIONS', `A p')dnl
define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 PLAIN LOGIN')dnl
TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl

define(`CERT_DIR', `/etc/mail/certs')dnl
define(`confCACERT_PATH', `CERT_DIR')dnl
define(`confCACERT', `CERT_DIR/mycert.pem')dnl
define(`confSERVER_CERT', `CERT_DIR/mycert.pem')dnl
define(`confSERVER_KEY', `CERT_DIR/mykey.pem')dnl
define(`confCRL', `CERT_DIR/mykey.pem')dnl

define(`confBIND_OPTS', `WorkAroundBrokenAAAA')
define(`confNO_RCPT_ACTION', `add-to-undisclosed')
define(`confPRIVACY_FLAGS', `authwarnings,noexpn,novrfy')
MAILER(local)
MAILER(smtp)

auth/client-info
Code:
AuthInfo:smtp.gmail.com "U:root" "I:<GMAIL_USERNAME>@gmail.com" "P:<GMAIL_PWD>"
bauen
Code:
root> cd /etc/mail/auth
root> makemap hash client-info < client-info
root> chmod 600 client-info*

local-host-names
Code:
MY_DOMAIN.DE
www.MY_DOMAIN.DE
mail.MY_DOMAIN.DE
hostname.MY_DOMAIN.DE
MYDYNDNS.dyndns.org
gmail.com

access
Code:
localhost                               RELAY
127.0.0.1                               RELAY

MYDYNDNS.dyndns.org    RELAY
MYDOMAIN.de                      RELAY
192.168.0.1                             RELAY
gmail.com                               RELAY

Beim neubauen mache ich folgenden
Code:
root> cd /etc/mail
root> make
root> cp <HOSTNAME>.<MYDOMAIN>.cf sendmail.cf


Wenn ich jetzt versuche eine mail via console zu senden:
Code:
echo 'test'| mail -s 'test' username@meineUni.de

Dann kriege ich folgendes Debug in der /var/log/maillog
Code:
Jun  4 07:45:50 fileserver sm-mta[3520]: starting daemon (8.14.5): SMTP+queueing@00:30:00
Jun  4 07:45:58 fileserver sendmail[3525]: q545jwe8003525: from=lockdoc, size=60, class=0, nrcpts=1, msgid=<201206040545.q545jwe8003525@<HOSTNAME>.<MYDOMAIN>.de>, relay=root@localhost
Jun  4 07:45:58 fileserver sm-mta[3526]: STARTTLS=server, relay=localhost [127.0.0.1], version=TLSv1/SSLv3, verify=NO, cipher=DHE-DSS-AES256-GCM-SHA384, bits=256/256
Jun  4 07:45:58 fileserver sendmail[3525]: STARTTLS=client, relay=[127.0.0.1], version=TLSv1/SSLv3,[B][COLOR="Red"] verify=FAIL[/COLOR][/B], cipher=DHE-DSS-AES256-GCM-SHA384, bits=256/256
Jun  4 07:45:59 fileserver sm-mta[3526]: q545jw3p003526: from=<lockdoc@<HOSTNAME>.<MYDOMAIN>.de>>, size=418, class=0, nrcpts=1, msgid=<201206040545.q545jwe8003525@<HOSTNAME>.<MYDOMAIN>.de>>, proto=ESMTP, daemon=TLSMTA, relay=localhost [127.0.0.1]
Jun  4 07:45:59 fileserver sendmail[3525]: q545jwe8003525: to=<USERNAME>@<MEINEUNI>.de, ctladdr=lockdoc (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30060, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q545jw3p003526 Message accepted for delivery)
Jun  4 07:45:59 fileserver sm-mta[3528]: STARTTLS=client, relay=smtp.gmail.com, version=TLSv1/SSLv3, [COLOR="Red"]verify=FAIL[/COLOR], cipher=ECDHE-RSA-RC4-SHA, bits=128/128
Jun  4 07:45:59 fileserver sm-mta[3528]: q545jw3p003526: to=<<USERNAME>@<MEINEUNI>.de>, ctladdr=<lockdoc@<HOSTNAME>.<MYDOMAIN>.de>> (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30418, relay=smtp.gmail.com [173.194.69.108], dsn=5.0.0, [B][COLOR="Red"]stat=Service unavailable[/COLOR][/B]
Jun  4 07:45:59 fileserver sm-mta[3528]: q545jw3p003526: q545jx3o003528: DSN: Service unavailable
Jun  4 07:45:59 fileserver sm-mta[3528]: q545jx3o003528: to=<lockdoc@<HOSTNAME>.<MYDOMAIN>.de>>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31442, relay=local, dsn=2.0.0, stat=Sent



Also irgendwie kriege ich die mails nicht gesendet und bin jetzt ein wenig verwundert, was denn noch fehlt.

Edit: noch zur Info
+ habe eine dynamische IP und dyndns konfiguriert
+ Bin bei der Telekom

+ Falls es eine einfachere Methode gibt mit PHP mails zu versenden, als den sendmail zu confen, dann nehme ich natuerlich lieber das, weil ich nur die mails testen moechte, bis die ganze sache auf einen server wandert, der schon komplett konfiguriert ist
 
Zuletzt bearbeitet:
Seh ich das richtig, der Mailserver soll nur Mails verschicken? Sonst keine besonderen Anforderungen?
Wenn ich mich nicht allzusehr täusche musst du da gar nicht viel machen. Weder Relay noch großartige Auth-Verfahren brauchst du auch nicht (da du ja nicht von aussen einloggen willst).

Ich verwende lieber Postfix als sendmail. Bei Interesse, ich hab mal meine Konfiguration hier abgelegt:
http://www.denkrobat.de/wiki/index.php/Mailserver_einrichten (Diese sieht aber eben einen kompletten Mailserver vor (also mit IMAP und SMTP)).
 
Für ein einfaches Versenden der Mails aus einer Webanwendung reicht der sendmail aus der FreeBSD Basis vollkommen aus.

Da immer mehr Mailserver nur noch RFC konforme Emails annehmen, macht es Sinn den Hostnamen entsprechend der Adresse der Webanwendung zu benennen.

Dann einfach ins Verzeichnis "/etc/mail" wechseln und mit "make all install" die Konfigurationsdateien passend zum Host erstellen lassen. In die "/etc/rc.conf" fügst du folgendes ein:

Code:
sendmail_outbound_enable="YES"
sendmail_msp_queue_enable="YES"
sendmail_submit_enable="YES"

Danach im Verzeichnis "/etc/mail/" ein knappes "make start" und der Versand sollte klappen.

Den sendmail-sasl-auth Port kannst du wieder deinstallieren, das Basis-sendmail bleibt erhalten.

Die Anpassungen in der localhostnames und in der access brauchst du nicht.

Gruß b.
 
also ich hab dann mal wieder die standard sendmail.mc in die myhostname.mydomain.mc kopiert und die rc.conf vars gesetzt.

Wenn ich via shell
Code:
echo 'test'| mail -s 'test' <ME>@<UNI>.de
mache, dann kommen folgende Fehler

Code:
Jun  4 13:17:25 fileserver sendmail[9628]: q54BHPJh009628: from=lockdoc, size=60, class=0, nrcpts=1, msgid=<201206041117.q54BHPJh009628@fileserver.<MYDOMAIN>.de>, relay=root@localhost
Jun  4 13:17:26 fileserver sm-mta[9629]: q54BHPgC009629: from=<lockdoc@fileserver.<MYDOMAIN>.de>, size=418, class=0, nrcpts=1, msgid=<201206041117.q54BHPJh009628@fileserver.<MYDOMAIN>.de>, proto=ESMTP, daemon=IPv4, relay=localhost [127.0.0.1]
Jun  4 13:17:26 fileserver sendmail[9628]: q54BHPJh009628: to=<ME>@<UNIMAILHOST>.de, ctladdr=lockdoc (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30060, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q54BHPgC009629 Message accepted for delivery)
Jun  4 13:17:27 fileserver sm-mta[9631]: STARTTLS=client, relay=<UNIMAILHOST>.de., version=TLSv1/SSLv3, verify=FAIL, cipher=AES256-SHA, bits=256/256
Jun  4 13:17:27 fileserver sm-mta[9631]: q54BHPgC009629: to=<<ME>@<UNIMAILHOST>.de>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30418, relay=<UNIMAILHOST>.de. [<UNI_IP>], dsn=5.0.0, stat=Service unavailable
Jun  4 13:17:27 fileserver sm-mta[9631]: q54BHPgC009629: q54BHRgC009631: DSN: Service unavailable
Jun  4 13:17:30 fileserver sm-mta[9631]: q54BHRgC009631: SYSERR(root): <MEIN>.dyndns.org. config error: mail loops back to me (MX problem?)
Jun  4 13:17:30 fileserver sm-mta[9632]: q54BHUm3009632: p4FC21C9A.dip.t-dialin.net [<MY_IP>] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4
Jun  4 13:17:30 fileserver sm-mta[9631]: q54BHRgC009631: to=<lockdoc@fileserver.<MYDOMAIN>.de>, delay=00:00:03, xdelay=00:00:03, mailer=esmtp, pri=31442, relay=<MEIN>.dyndns.org. [<MY_IP>], dsn=5.3.5, stat=Local configuration error
Jun  4 13:17:30 fileserver sm-mta[9631]: q54BHRgC009631: q54BHRgD009631: return to sender: Local configuration error
Jun  4 13:17:30 fileserver sm-mta[9631]: q54BHRgD009631: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32466, relay=local, dsn=2.0.0, stat=Sent

Edit:, die Standard conf sieht jetzt wieder so aus:
Code:
divert(0)
VERSIONID(`$FreeBSD: release/9.0.0/etc/sendmail/freebsd.mc 223068 2011-06-14 04:33:43Z gshapiro $')
OSTYPE(freebsd6)
DOMAIN(generic)

FEATURE(access_db, `hash -o -T<TMPF> /etc/mail/access')
FEATURE(blacklist_recipients)
FEATURE(local_lmtp)
FEATURE(mailertable, `hash -o /etc/mail/mailertable')
FEATURE(virtusertable, `hash -o /etc/mail/virtusertable')
define(`confCW_FILE', `-o /etc/mail/local-host-names')

DAEMON_OPTIONS(`Name=IPv4, Family=inet')

define(`confBIND_OPTS', `WorkAroundBrokenAAAA')
define(`confNO_RCPT_ACTION', `add-to-undisclosed')
define(`confPRIVACY_FLAGS', `authwarnings,noexpn,novrfy')
MAILER(local)
MAILER(smtp)
 
das Kopieren der mc-Files kannst du dir ersparen, das übernimmt "make" in "/etc/mail"

beim "make all" werden aus den freebsd.* die HOSTNAME.* Konfig-Dateien

beim "make install" werden dann daraus die sendmail.* Dateien und "make start/restart" liest diese dann ein...

in den Dateien selbst musst du imho für einen simplen PHP-Mailversand nichts weiter konfigurieren, wenn der Versand einmal klappt, würde ich aber im maillog nachschauen ob es Probleme beim Zustellen der Emails bei den großen Providern gibt - evtl muss in der HOSTNAME.mc die Adresse deiner Anwendung eingetragen werden... später mehr

Deine Testemail wird an <UNIMAILHOST>.de übergeben, aber mit dem Fehler "Local configuration error" zurückgegeben und dann deinem Nutzer ins lokale Postfach zugestellt.

Kann es sein das du die Mails auf dem Server auch annimmst? In der local-host-names würden dann die Email-Domänen stehen, für welche du verantwortlich wärst.

Kannst du einmal die default Dateien in "/etc/mail" wiederherstellen und per "make all install" die Konfigs erzeugen lassen?

Was steht denn bezüglich sendmail alles in der rc.conf?
 
Kann es sein das du die Mails auf dem Server auch annimmst? In der local-host-names würden dann die Email-Domänen stehen, für welche du verantwortlich wärst.
hmm, also die local-host-names habe ich wieder geleert.

Kannst du einmal die default Dateien in "/etc/mail" wiederherstellen und per "make all install" die Konfigs erzeugen lassen?
Wie mache ich das?


In der rc.conf steht folgendes?
Code:
sendmail_enable="YES"
sendmail_outbound_enable="YES"
sendmail_msp_queue_enable="YES"
sendmail_submit_enable="YES"
 
Wie mache ich das?

Gute Frage, mit etwas Glück hast du unter "/usr/src/etc/mail" noch die Quelldateien, die könntest du in "/etc/mail" kopieren, dann wie gehabt weiter...

Leider weiß ich nicht, wie man default-Konfigs wiederherstellen kann - außer die Welt einmal zu bauen und die Dateien zu kopieren.
 
So, ich habe einfach die ganzen Konfig files aus einer JAIL genommen und reinkopiert und neu gemacht.

Die Fehlermeldung bleibt allerdings wie oben
<MEIN>.dyndns.org. config error: mail loops back to me (MX problem?)
 
Code:
Jun  4 13:17:27 fileserver sm-mta[9631]: q54BHPgC009629: to=<<ME>@<UNIMAILHOST>.de>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30418, relay=<UNIMAILHOST>.de. [<UNI_IP>], dsn=5.0.0, stat=Service unavailable

"Service unavailable" kommt als Antwort vom UNIMAILHOST und "dsn=5.0.0" steht laut RFC für permanenter, unbekannter Fehler...

Kannst du die Testmail woanders hinschicken? Als erstes vllt nem lokalen User unterjubeln und schauen ob sie ankommt.

Danach den UNIMAILHOST versuchen per telnet auf Port 25 zu erreichen und eine Email direkt per SMTP-Kommandos zu senden...

Welche Files hast du jetzt in "/etc/mail"?
 
Code:
telnet <UNIHOST> 25
Trying <IP>...
Connected to <UNIHOST>.
Escape character is '^]'.
220 <UNIHOST> - ESMTP (exim-4.75/mailfrontend-3) ready at Mon, 04 Jun 2012 23:10:29 +0200


Mail an mich selbst
Code:
echo 'test'| mail -s 'test' lockdoc@localhost
Und der maillog dazu:
Code:
Jun  4 23:13:53 fileserver sendmail[20574]: q54LDruV020574: from=lockdoc, size=42, class=0, nrcpts=1, msgid=<201206042113.q54LDruV020574@<MYDOMAIN>.de>, relay=root@localhost
Jun  4 23:13:56 fileserver sm-mta[20575]: q54LDr5n020575: from=<lockdoc@fileserver.<MYDOMAIN>.de>, size=398, class=0, nrcpts=1, msgid=<201206042113.q54LDruV020574@fileserver.<MYDOMAIN>.de>, proto=ESMTP, daemon=IPv4, relay=localhost [127.0.0.1]
Jun  4 23:13:56 fileserver sendmail[20574]: q54LDruV020574: to=lockdoc@localhost, ctladdr=lockdoc (1001/1001), delay=00:00:03, xdelay=00:00:03, mailer=relay, pri=30042, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q54LDr5n020575 Message accepted for delivery)
Jun  4 23:13:58 fileserver sm-mta[20577]: q54LDr5n020575: SYSERR(root): <MYDYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
Jun  4 23:13:58 fileserver sm-mta[20578]: q54LDwrw020578: p4FC21C9A.dip.t-dialin.net [<MYEXTERNAL_IP>] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4
Jun  4 23:13:58 fileserver sm-mta[20577]: q54LDr5n020575: to=<lockdoc@fileserver.<MYDOMAIN>.de>, delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=30398, relay=<MYDYNDNS>.dyndns.org. [<MY_EXTERMAL_IP>], dsn=5.3.5, stat=Local configuration error
Jun  4 23:13:58 fileserver sm-mta[20577]: q54LDr5n020575: q54LDw5n020577: DSN: Local configuration error
Jun  4 23:13:58 fileserver sm-mta[20577]: q54LDw5n020577: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=61422, relay=local, dsn=2.0.0, stat=Sent
Jun  4 23:13:58 fileserver sm-mta[20577]: q54LDw5n020577: to=<lockdoc@fileserver.<MYDOMAIN>.de>, delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=61422, relay=<MYDYNDNS>.dyndns.org., dsn=5.3.5, stat=Local configuration error
Jun  4 23:13:58 fileserver sm-mta[20577]: q54LDw5n020577: q54LDw5o020577: return to sender: Local configuration error
Jun  4 23:13:58 fileserver sm-mta[20577]: q54LDw5o020577: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32446, relay=local, dsn=2.0.0, stat=Sent


Also ich muss dazu sagen:
Der dyndns ist aktiviert und mein hostname ist fileserver.<MYDOMAIN>.de. Diese domain gibt es wirklich und zeigt mit dem CNAME auf <MYDYNDNS>.dyndns.org.
So ist meine Kiste auch ueber meine eigene domain erreichbar... evtl. verschluckt er sich aber dabei.


Hier noch der output von /etc/mail/:
Code:
total 484
-rw-r--r--  1 root  wheel    6814 Jun  4 19:31 Makefile
-rw-r--r--  1 root  wheel    2901 Jun  4 19:31 README
-rw-r--r--  1 root  wheel     630 Jun  4 19:31 access.sample
-rw-r--r--  1 root  wheel    1674 Jun  4 19:31 aliases
-rw-r-----  1 root  wheel  131072 Jun  4 19:31 aliases.db
-rw-r--r--  1 root  wheel   58232 Jun  4 19:31 fileserver.<MY_DOMAIN>.de.cf
-rw-r--r--  1 root  wheel    3958 Jun  4 19:31 fileserver.<MY_DOMAIN>.de.mc
-rw-r--r--  1 root  wheel   40706 Jun  4 19:31 fileserver.<MY_DOMAIN>.de.submit.cf
-r--r--r--  1 root  wheel     896 Jun  4 19:31 fileserver.<MY_DOMAIN>.de.submit.mc
-rw-r--r--  1 root  wheel   58265 Jun  4 19:31 freebsd.cf
-rw-r--r--  1 root  wheel    3958 Jun  4 19:31 freebsd.mc
-r--r--r--  1 root  wheel   40739 Jun  4 19:31 freebsd.submit.cf
-r--r--r--  1 root  wheel     896 Jun  4 19:31 freebsd.submit.mc
-r--r--r--  1 root  wheel    5657 Jun  4 19:31 helpfile
-rw-r--r--  1 root  wheel     405 Jun  4 19:31 mailer.conf
-rw-r--r--  1 root  wheel     249 Jun  4 19:31 mailertable.sample
-r--r--r--  1 root  wheel   58232 Jun  4 19:31 sendmail.cf
-r--r--r--  1 root  wheel   40706 Jun  4 19:31 submit.cf
-rw-r--r--  1 root  wheel     578 Jun  4 19:31 virtusertable.sample
 
Der Fehler 5.3.5. deutet auf falschen Nutzernamen/Passwort bei der SMTP Authentifizierung hin, hattest du den Sendmail-Sasl-Auth Port deinstalliert?

Wie es aussieht, wurden die Unzustellbarkeitsberichte root zugestellt. Kannst du mit "mail -f root" mal einen der Berichte anzeigen lassen? Mal schauen was da drin steht ...
 
Hier ist erstmal der Bericht
Code:
From MAILER-DAEMON Wed May 30 09:23:08 2012
Date: Wed, 30 May 2012 09:23:08 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON@<MY_DOMAIN>.de>
To: postmaster@fileserver.<MY_DOMAIN>.de
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)

This is a MIME-encapsulated message

--q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de

The original message was received at Wed, 30 May 2012 09:23:08 +0200 (CEST)
from localhost
with id q4U7N8C4073527

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>.de>
    (reason: 553 5.3.5 system config error)

   ----- Transcript of session follows -----
553 5.3.5 <MY_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error

--q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Wed, 30 May 2012 09:23:08 +0200 (CEST)

Message 539:
From MAILER-DAEMON Wed May 30 09:23:08 2012
Date: Wed, 30 May 2012 09:23:08 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON@<MY_DOMAIN>.de>
To: postmaster@fileserver.<MY_DOMAIN>.de
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)

This is a MIME-encapsulated message

--q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de

The original message was received at Wed, 30 May 2012 09:23:08 +0200 (CEST)
from localhost
with id q4U7N8C4073527

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>.de>
    (reason: 553 5.3.5 system config error)

   ----- Transcript of session follows -----
553 5.3.5 <MY_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error

--q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Wed, 30 May 2012 09:23:08 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MY_DYNDNS>.dyndns.org
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Wed, 30 May 2012 09:23:08 +0200 (CEST)

--q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de
Content-Type: message/rfc822

Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5) id q4U7N8C4073527;
        Wed, 30 May 2012 09:23:08 +0200 (CEST)
        (envelope-from MAILER-DAEMON)
Date: Wed, 30 May 2012 09:23:08 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201205300723.q4U7N8C4073527@fileserver.<MY_DOMAIN>.de>
To: <lockdoc@<MY_DYNDNS>.dyndns.org>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q4U7N8C4073527.1338362588/fileserver.<MY_DOMAIN>.de"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--q4U7N8C4073527.1338362588/fileserver.<MY_DOMAIN>.de

The original message was received at Wed, 30 May 2012 09:23:07 +0200 (CEST)
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<<MY_TO_EMAIL>@<MY_UNI_HOST>>
    (reason: 550-5.7.1 Your message was rejected due to spam filtering. Please see)

   ----- Transcript of session follows -----
... while talking to <MY_UNI_HOST>.:
>>> MAIL From:<lockdoc@<MY_DYNDNS>.dyndns.org> SIZE=439
<<< 550-5.7.1 Your message was rejected due to spam filtering. Please see
<<< 550 5.7.1 http://www.sophos.com/security/ip-lookup?ip=84.189.249.37
554 5.0.0 Service unavailable

--q4U7N8C4073527.1338362588/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Wed, 30 May 2012 09:23:07 +0200 (CEST)

Final-Recipient: RFC822; <MY_TO_EMAIL>@<MY_UNI_HOST>
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 550-5.7.1 Your message was rejected due to spam filtering. Please see
Last-Attempt-Date: Wed, 30 May 2012 09:23:07 +0200 (CEST)

--q4U7N8C4073527.1338362588/fileserver.<MY_DOMAIN>.de
Content-Type: message/rfc822

Return-Path: <lockdoc@<MY_DYNDNS>.dyndns.org>
Received: from fileserver.<MY_DOMAIN>.de (localhost [127.0.0.1])
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5) with ESMTP id q4U7N2C8073521
        for <<MY_TO_EMAIL>@<MY_UNI_HOST>>; Wed, 30 May 2012 09:23:07 +0200 (CEST)
        (envelope-from lockdoc@<MY_DYNDNS>.dyndns.org)
Received: (from lockdoc@localhost)
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5/Submit) id q4U72DUO058055
        for <MY_TO_EMAIL>@<MY_UNI_HOST>; Wed, 30 May 2012 09:02:13 +0200 (CEST)
        (envelope-from lockdoc)
Date: Wed, 30 May 2012 09:02:13 +0200 (CEST)
From: lockdoc <lockdoc@<MY_DYNDNS>.dyndns.org>
Message-Id: <201205300702.q4U72DUO058055@fileserver.<MY_DOMAIN>.de>
To: <MY_TO_EMAIL>@<MY_UNI_HOST>
Subject: subject

This is the body.

--q4U7N8C4073527.1338362588/fileserver.<MY_DOMAIN>.de--


--q4U7N8C5073527.1338362588/fileserver.<MY_DOMAIN>.de--

Und ja ich hab SASL wieder deinstalliert und sendmail neugebaut
 
Ich habe jetzt auch mal web.de, gmail und noch ne adresse probiert
Code:
Jun  4 23:43:42 fileserver sendmail[22367]: q54LhgfF022367: from=lockdoc, size=45, class=0, nrcpts=1, msgid=<201206042143.q54LhgfF022367@fileserver.<MY_DOMAIN>.>, relay=root@localhost
Jun  4 23:43:43 fileserver sm-mta[22368]: q54LhgcQ022368: from=<lockdoc@fileserver.<MY_DOMAIN>.>, size=391, class=0, nrcpts=1, msgid=<201206042143.q54LhgfF022367@fileserver.<MY_DOMAIN>.>, proto=ESMTP, daemon=IPv4, relay=localhost [127.0.0.1]
Jun  4 23:43:43 fileserver sendmail[22367]: q54LhgfF022367: to=ME@web.de, ctladdr=lockdoc (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30045, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q54LhgcQ022368 Message accepted for delivery)
Jun  4 23:43:44 fileserver sm-mta[22370]: q54LhgcQ022368: to=<ME@web.de>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30391, relay=mx-ha03.web.de. [213.165.67.104], dsn=5.0.0, stat=Service unavailable
Jun  4 23:43:45 fileserver sm-mta[22370]: q54LhgcQ022368: q54LhjcQ022370: DSN: Service unavailable
Jun  4 23:43:47 fileserver sm-mta[22370]: q54LhjcQ022370: SYSERR(root): <MY_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
Jun  4 23:43:47 fileserver sm-mta[22371]: q54Lhlca022371: p4FC21C9A.dip.t-dialin.net [<MY_EXT_IP>] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4
Jun  4 23:43:47 fileserver sm-mta[22370]: q54LhjcQ022370: to=<lockdoc@fileserver.<MY_DOMAIN>.>, delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=31415, relay=<MY_DYNDNS>.dyndns.org. [<MY_EXT_IP>], dsn=5.3.5, stat=Local configuration error
Jun  4 23:43:47 fileserver sm-mta[22370]: q54LhjcQ022370: q54LhjcR022370: return to sender: Local configuration error
Jun  4 23:43:47 fileserver sm-mta[22370]: q54LhjcR022370: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32439, relay=local, dsn=2.0.0, stat=Sent


Jun  4 23:43:50 fileserver sendmail[22375]: q54LhonD022375: from=lockdoc, size=44, class=0, nrcpts=1, msgid=<201206042143.q54LhonD022375@fileserver.<MY_DOMAIN>.>, relay=root@localhost
Jun  4 23:43:52 fileserver sm-mta[22376]: q54LhoT4022376: from=<lockdoc@fileserver.<MY_DOMAIN>.>, size=389, class=0, nrcpts=1, msgid=<201206042143.q54LhonD022375@fileserver.<MY_DOMAIN>.>, proto=ESMTP, daemon=IPv4, relay=localhost [127.0.0.1]
Jun  4 23:43:52 fileserver sendmail[22375]: q54LhonD022375: to=ME_AT_GMAIL@gmail.com, ctladdr=lockdoc (1001/1001), delay=00:00:02, xdelay=00:00:02, mailer=relay, pri=30044, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q54LhoT4022376 Message accepted for delivery)
Jun  4 23:43:52 fileserver sm-mta[22378]: STARTTLS=client, relay=gmail-smtp-in.l.google.com., version=TLSv1/SSLv3, verify=FAIL, cipher=RC4-SHA, bits=128/128
Jun  4 23:43:53 fileserver sm-mta[22378]: q54LhoT4022376: to=<ME_AT_GMAIL@gmail.com>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30389, relay=gmail-smtp-in.l.google.com. [173.194.69.26], dsn=2.0.0, stat=Sent (OK 1338846174 io2si8453439bkc.95)


Jun  4 23:43:57 fileserver sendmail[22382]: q54Lhv4I022382: from=lockdoc, size=51, class=0, nrcpts=1, msgid=<201206042143.q54Lhv4I022382@fileserver.<MY_DOMAIN>.>, relay=root@localhost
Jun  4 23:43:58 fileserver sm-mta[22383]: q54LhvQw022383: from=<lockdoc@fileserver.<MY_DOMAIN>.>, size=403, class=0, nrcpts=1, msgid=<201206042143.q54Lhv4I022382@fileserver.<MY_DOMAIN>.>, proto=ESMTP, daemon=IPv4, relay=localhost [127.0.0.1]
Jun  4 23:43:58 fileserver sendmail[22382]: q54Lhv4I022382: to=ME@<OTHER_DOMAIN>.de, ctladdr=lockdoc (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30051, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q54LhvQw022383 Message accepted for delivery)
Jun  4 23:43:58 fileserver sm-mta[22385]: q54LhvQw022383: to=<ME@<OTHER_DOMAIN>.de>, delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=30403, relay=mxlb.ispgateway.de. [80.67.18.126], dsn=5.0.0, stat=Service unavailable
Jun  4 23:43:58 fileserver sm-mta[22385]: q54LhvQw022383: q54LhwQw022385: DSN: Service unavailable
Jun  4 23:44:00 fileserver sm-mta[22385]: q54LhwQw022385: SYSERR(root): <MY_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
Jun  4 23:44:00 fileserver sm-mta[22422]: q54Li0GI022422: p4FC21C9A.dip.t-dialin.net [<MY_EXT_IP>] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4
Jun  4 23:44:00 fileserver sm-mta[22385]: q54LhwQw022385: to=<lockdoc@fileserver.<MY_DOMAIN>.>, delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=31427, relay=<MY_DYNDNS>.dyndns.org. [<MY_EXT_IP>], dsn=5.3.5, stat=Local configuration error
Jun  4 23:44:00 fileserver sm-mta[22385]: q54LhwQw022385: q54LhwQx022385: return to sender: Local configuration error
Jun  4 23:44:00 fileserver sm-mta[22385]: q54LhwQx022385: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32451, relay=local, dsn=2.0.0, stat=Sent

Alles will nicht laufen :(
 
Der ist aus der letzten Woche ;) hast du da ne Zeitmaschine kompiliert? In welchem Port steckt die???

Schau bitte was im logfile erscheint wenn du "echo 'test' | mail -s 'test' lockdoc' abschickst. Den Hostnamen brauchst du jetzt noch nicht mit angeben. Wenn die Mail nicht dem User lockdoc zugestellt wird, wäre der aktuelle Bericht interessant...

Ganz ehrlich, eigentlich ist der reine Mailversand mit sendmail kein großes Hexenwerk. Habe selbst FreeBSD Jails in welchen Webanwendungen per PHP Mails versenden. Mit sasl-auth hatte ich mal vor Urzeiten nen Mailserver aufgesetzt, welcher auch annehmen und per POP3 bereitstellen sollte.
 
Sorry, das mit der mail hab ich verplannt.
Also nochmal schritt fuer schritt:

Code:
root> echo 'test' | mail -s 'test' lockdoc

/var/log/maillog
Code:
Jun  4 23:55:58 fileserver sendmail[22712]: q54LtwnW022712: from=lockdoc, size=32, class=0, nrcpts=1, msgid=<201206042155.q54LtwnW022712@fileserver.<MY_DOMAIN>>, relay=lockdoc@localhost
Jun  4 23:56:00 fileserver sm-mta[22714]: q54Ltwrn022714: from=<lockdoc@fileserver.<MY_DOMAIN>>, size=391, class=0, nrcpts=1, msgid=<201206042155.q54LtwnW022712@fileserver.<MY_DOMAIN>>, proto=ESMTP, daemon=IPv4, relay=localhost [127.0.0.1]
Jun  4 23:56:00 fileserver sendmail[22712]: q54LtwnW022712: to=lockdoc, ctladdr=lockdoc (1001/1001), delay=00:00:02, xdelay=00:00:02, mailer=relay, pri=30032, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q54Ltwrn022714 Message accepted for delivery)
Jun  4 23:56:03 fileserver sm-mta[22716]: q54Ltwrn022714: SYSERR(root): <MY_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
Jun  4 23:56:03 fileserver sm-mta[22717]: q54Lu3Kv022717: p4FC21C9A.dip.t-dialin.net [MY_EXT_IP] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4
Jun  4 23:56:03 fileserver sm-mta[22716]: q54Ltwrn022714: to=<lockdoc@fileserver.<MY_DOMAIN>>, delay=00:00:03, xdelay=00:00:03, mailer=esmtp, pri=30391, relay=<MY_DYNDNS>.dyndns.org. [MY_EXT_IP], dsn=5.3.5, stat=Local configuration error
Jun  4 23:56:03 fileserver sm-mta[22716]: q54Ltwrn022714: q54Lu3rn022716: DSN: Local configuration error
Jun  4 23:56:03 fileserver sm-mta[22716]: q54Lu3rn022716: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=61415, relay=local, dsn=2.0.0, stat=Sent
Jun  4 23:56:03 fileserver sm-mta[22716]: q54Lu3rn022716: to=<lockdoc@fileserver.<MY_DOMAIN>>, delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=61415, relay=<MY_DYNDNS>.dyndns.org., dsn=5.3.5, stat=Local configuration error
Jun  4 23:56:03 fileserver sm-mta[22716]: q54Lu3rn022716: q54Lu3ro022716: return to sender: Local configuration error
Jun  4 23:56:03 fileserver sm-mta[22716]: q54Lu3ro022716: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32439, relay=local, dsn=2.0.0, stat=Sent

Und dann bekommt root 2 Nachrichten
Message1
Code:
Message 1:
From MAILER-DAEMON Mon Jun  4 23:57:52 2012
Date: Mon, 4 Jun 2012 23:57:52 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
To: <lockdoc@<MY_DYNDNS>.dyndns.org>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>

The original message was received at Mon, 4 Jun 2012 23:57:50 +0200 (CEST)
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>>
    (reason: 553 5.3.5 system config error)

   ----- Transcript of session follows -----
553 5.3.5 <MY_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>
Received-From-MTA: DNS; localhost
Arrival-Date: Mon, 4 Jun 2012 23:57:50 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MY_DYNDNS>.dyndns.org
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Mon, 4 Jun 2012 23:57:52 +0200 (CEST)

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>
Content-Type: message/rfc822

Return-Path: <lockdoc@<MY_DYNDNS>.dyndns.org>
Received: from fileserver.<MY_DOMAIN> (localhost [127.0.0.1])
        by fileserver.<MY_DOMAIN> (8.14.5/8.14.5) with ESMTP id q54LvlcO022767
        for <lockdoc@fileserver.<MY_DOMAIN>>; Mon, 4 Jun 2012 23:57:50 +0200 (CEST)
        (envelope-from lockdoc@<MY_DYNDNS>.dyndns.org)
Received: (from root@localhost)
        by fileserver.<MY_DOMAIN> (8.14.5/8.14.5/Submit) id q54LvlQ8022766
        for lockdoc; Mon, 4 Jun 2012 23:57:47 +0200 (CEST)
        (envelope-from lockdoc)
Date: Mon, 4 Jun 2012 23:57:47 +0200 (CEST)
From: lockdoc <lockdoc@<MY_DYNDNS>.dyndns.org>
Message-Id: <201206042157.q54LvlQ8022766@fileserver.<MY_DOMAIN>>
To: lockdoc@<MY_DYNDNS>.dyndns.org
Subject: test

test

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>--

Message2
Code:
From MAILER-DAEMON Mon Jun  4 23:57:52 2012
Date: Mon, 4 Jun 2012 23:57:52 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q54LvqcP022770.1338847072/fileserver.<MY_DOMAIN>"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)

This is a MIME-encapsulated message

--q54LvqcP022770.1338847072/fileserver.<MY_DOMAIN>

The original message was received at Mon, 4 Jun 2012 23:57:52 +0200 (CEST)
from localhost
with id q54LvqcO022770

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>>

   ----- Transcript of session follows -----
554 5.3.5 Local configuration error

--q54LvqcP022770.1338847072/fileserver.<MY_DOMAIN>
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>
Received-From-MTA: DNS; localhost
Arrival-Date: Mon, 4 Jun 2012 23:57:52 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MY_DYNDNS>.dyndns.org
Action: failed
Status: 5.5.0
Last-Attempt-Date: Mon, 4 Jun 2012 23:57:52 +0200 (CEST)

--q54LvqcP022770.1338847072/fileserver.<MY_DOMAIN>
Content-Type: message/rfc822

Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
        by fileserver.<MY_DOMAIN> (8.14.5/8.14.5) id q54LvqcO022770;
        Mon, 4 Jun 2012 23:57:52 +0200 (CEST)
        (envelope-from MAILER-DAEMON)
Date: Mon, 4 Jun 2012 23:57:52 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201206042157.q54LvqcO022770@fileserver.<MY_DOMAIN>>
To: <lockdoc@<MY_DYNDNS>.dyndns.org>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>

The original message was received at Mon, 4 Jun 2012 23:57:50 +0200 (CEST)
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>>
    (reason: 553 5.3.5 system config error)

   ----- Transcript of session follows -----
553 5.3.5 <MY_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>
Received-From-MTA: DNS; localhost
Arrival-Date: Mon, 4 Jun 2012 23:57:50 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MY_DYNDNS>.dyndns.org
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Mon, 4 Jun 2012 23:57:52 +0200 (CEST)

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>
Content-Type: message/rfc822

Return-Path: <lockdoc@<MY_DYNDNS>.dyndns.org>
Received: from fileserver.<MY_DOMAIN> (localhost [127.0.0.1])
        by fileserver.<MY_DOMAIN> (8.14.5/8.14.5) with ESMTP id q54LvlcO022767
        for <lockdoc@fileserver.<MY_DOMAIN>>; Mon, 4 Jun 2012 23:57:50 +0200 (CEST)
        (envelope-from lockdoc@<MY_DYNDNS>.dyndns.org)
Received: (from root@localhost)
        by fileserver.<MY_DOMAIN> (8.14.5/8.14.5/Submit) id q54LvlQ8022766
        for lockdoc; Mon, 4 Jun 2012 23:57:47 +0200 (CEST)
        (envelope-from lockdoc)
Date: Mon, 4 Jun 2012 23:57:47 +0200 (CEST)
From: lockdoc <lockdoc@<MY_DYNDNS>.dyndns.org>
Message-Id: <201206042157.q54LvlQ8022766@fileserver.<MY_DOMAIN>>
To: lockdoc@<MY_DYNDNS>.dyndns.org
Subject: test

test

--q54LvqcO022770.1338847072/fileserver.<MY_DOMAIN>--
 
und zum Testen:

vom Server eine telnet Verbindung auf einen der Mailserver, Port 25

erstes Kommando: "EHLO" - ohne irgendetwas... sollte zumindest bei googlemail klappen

dann "mail from: <beliebige gültige Emailadresse>" - Antwort etwas mit "Sender ok" o.ä.

anschließend "rcpt to: <mailbox (Emailadresse) auf dem Server>" - Antwort "accepted" oder so...

der Betreff, glaube mit "subject: test" - nach dem Enter bleibt die Zeile leer und der Cursor am Anfang - du kannst jetzt etwas Fließtext schreiben, dann Enter und einen Punkt (.) als EOM mit Enter übergeben

dann sollte die Mail verschickt werden... den Dialog per Quit schließen
 
okay... der aktuelle Bericht lässt immer noch auf ein sendmail Problem schließen...

ich schau morgen noch mal in meine Sendmailer...
 
Der Uni Mailserver war der einzigste der auf telnet 25 reagierte
Code:
>telnet <UNI_HOST> 25
Trying <UNI_IP>...
Connected to <UNI_HOST>.
Escape character is '^]'.
220 <UNI_HOST> - ESMTP (exim-4.75/mailfrontend-3) ready at Tue, 05 Jun 2012 09:16:36 +0200
EHLO
501 Syntactically invalid EHLO argument(s)
mail from: <ME>@<UNI_HOST>
550-5.7.1 Your message was rejected due to spam filtering. Please see
550 5.7.1 http://www.sophos.com/security/ip-lookup?ip=<MY_EXT_IP>
Connection closed by foreign host.

Unter dem sophos.com link wird meine IP als "dynamic IP address." klassifiziert
 
Der Uni Mailserver ist vorbildlich konfiguriert und gleicht deine IP mit ner Spam-Liste ab. Da deine öffentliche IP dynamisch ist, weist er deine Emails ab.

Die anderen Mailserver antworten sicherlich auch, zumindest tun sie es bei mir:

MX für googlemail.com: "telnet gmail-smtp-in.l.google.com 25"

Ich denke das bei dir schon alles absolut korrekt läuft. Versuch bitte eine Testmail an googlemail per "mail" Kommando zu senden. Poste anschließend bitte einmal die passenden Zeilen aus "/var/log/maillog".
 
Also auf ein neues:
command:
Code:
echo 'test' | mail -s 'test' <my_gmail>@gmail.com

dmesg:
Code:
Jun  5 10:52:53 fileserver sm-mta[46913]: q558qoKT046913: SYSERR(root): <My_DYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)

mail
Code:
Mail version 8.1 6/6/93.  Type ? for help.
"/var/mail/root": 1 message 1 new
>N  1 MAILER-DAEMON         Tue Jun  5 11:19 125/4592  "Postmaster notify: see transcript for details"
& 1
Message 1:
From MAILER-DAEMON Tue Jun  5 11:19:46 2012
Date: Tue, 5 Jun 2012 11:19:46 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q559Jj05047752.1338887986/fileserver.<MY_DOMAIN>.de"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)

This is a MIME-encapsulated message

--q559Jj05047752.1338887986/fileserver.<MY_DOMAIN>.de

The original message was received at Tue, 5 Jun 2012 11:19:45 +0200 (CEST)
from localhost
with id q559Jj04047752

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>.de>
    (reason: 553 5.3.5 system config error)

   ----- Transcript of session follows -----
553 5.3.5 <MYDYNDNS>.dyndns.org. config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error

--q559Jj05047752.1338887986/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 5 Jun 2012 11:19:45 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MYDYNDNS>.dyndns.org
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Tue, 5 Jun 2012 11:19:46 +0200 (CEST)

--q559Jj05047752.1338887986/fileserver.<MY_DOMAIN>.de
Content-Type: message/rfc822

Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5) id q559Jj04047752;
        Tue, 5 Jun 2012 11:19:45 +0200 (CEST)
        (envelope-from MAILER-DAEMON)
Date: Tue, 5 Jun 2012 11:19:45 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201206050919.q559Jj04047752@fileserver.<MY_DOMAIN>.de>
To: <lockdoc@<MYDYNDNS>.dyndns.org>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q559Jj04047752.1338887985/fileserver.<MY_DOMAIN>.de"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--q559Jj04047752.1338887985/fileserver.<MY_DOMAIN>.de

The original message was received at Tue, 5 Jun 2012 11:19:40 +0200 (CEST)
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<<my_gmail>@gmail.com>
    (reason: 550-5.1.1 The email account that you tried to reach does not exist. Please try)

   ----- Transcript of session follows -----
... while talking to gmail-smtp-in.l.google.com.:
>>> RCPT To:<<my_gmail>@gmail.com>
<<< 550-5.1.1 The email account that you tried to reach does not exist. Please try
<<< 550-5.1.1 double-checking the recipient's email address for typos or
<<< 550-5.1.1 unnecessary spaces. Learn more at
<<< 550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 fk5si629254bkc.146
550 5.1.1 <<my_gmail>@gmail.com>... User unknown
>>> DATA
<<< 503 5.5.1 RCPT first. fk5si629254bkc.146

--q559Jj04047752.1338887985/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 5 Jun 2012 11:19:40 +0200 (CEST)

Final-Recipient: RFC822; <my_gmail>@gmail.com
Action: failed
Status: 5.1.1
Remote-MTA: DNS; gmail-smtp-in.l.google.com
Diagnostic-Code: SMTP; 550-5.1.1 The email account that you tried to reach does not exist. Please try
Last-Attempt-Date: Tue, 5 Jun 2012 11:19:43 +0200 (CEST)

--q559Jj04047752.1338887985/fileserver.<MY_DOMAIN>.de
Content-Type: message/rfc822

Return-Path: <lockdoc@<MYDYNDNS>.dyndns.org>
Received: from fileserver.<MY_DOMAIN>.de (localhost [127.0.0.1])
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5) with ESMTP id q559Jd04047750
        for <<my_gmail>@gmail.com>; Tue, 5 Jun 2012 11:19:40 +0200 (CEST)
        (envelope-from lockdoc@<MYDYNDNS>.dyndns.org)
Received: (from lockdoc@localhost)
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5/Submit) id q559JdhH047749
        for <my_gmail>@gmail.com; Tue, 5 Jun 2012 11:19:39 +0200 (CEST)
        (envelope-from lockdoc)
Date: Tue, 5 Jun 2012 11:19:39 +0200 (CEST)
From: lockdoc <lockdoc@<MYDYNDNS>.dyndns.org>
Message-Id: <201206050919.q559JdhH047749@fileserver.<MY_DOMAIN>.de>
To: <my_gmail>@gmail.com
Subject: test

test

--q559Jj04047752.1338887985/fileserver.<MY_DOMAIN>.de--


--q559Jj05047752.1338887986/fileserver.<MY_DOMAIN>.de--

Dummerweise hab ich grade mal mein maillog geloescht und neu angelegt (damit es mal wieder etwas kleiner ist), chmod 640 oder chmod 600 probiert, aber sendmail scheint nach dem neustart nicht mehr in das log zu schreiben
 
dein Empfänger scheint nicht zu stimmen:
... while talking to gmail-smtp-in.l.google.com.:
>>> RCPT To:<<my_gmail>@gmail.com>
<<< 550-5.1.1 The email account that you tried to reach does not exist. Please try
<<< 550-5.1.1 double-checking the recipient's email address for typos or
<<< 550-5.1.1 unnecessary spaces. Learn more at
<<< 550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 fk5si629254bkc.146
550 5.1.1 <<my_gmail>@gmail.com>... User unknown

Ich habe selbst eine Google Adresse, ist der Domainname bei dir nicht @googlemail.com?

Die Berechtigungen für "/var/log/maillog" sind bei mir 640 root:wheel und meines Wissens nach rotiert FreeBSD die Files regelmäßig um 00:00 Uhr...

Mit "true > /var/log/maillog" hättest du die Datei leeren können.
 
Hmm, also ich habe eine xxx@gmail.com Adresse.
Aber wenn ich nochmal einen Schritt zurueckgehe und als root user eine mail an lockdoc sende
Code:
root> echo 'test' | mail -s 'test' lockdoc

Dann bekomme ich schon folgende Fehler.

Message 1
Code:
Message 1:
From MAILER-DAEMON Tue Jun  5 14:55:12 2012
Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
To: <lockdoc@<MY_DYNDNS>.dyndns.org>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de

The original message was received at Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>.de>
    (reason: 553 5.3.5 system config error)

   ----- Transcript of session follows -----
553 5.3.5 <MY_DYN_DNS>.dyndns.org. config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MY_DYN_DNS>.dyndns.org
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de
Content-Type: message/rfc822

Return-Path: <lockdoc@<MY_DYN_DNS>.dyndns.org>
Received: from fileserver.<MY_DOMAIN>.de (localhost [127.0.0.1])
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5) with ESMTP id q55CtAc7053187
        for <lockdoc@fileserver.<MY_DOMAIN>.de>; Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
        (envelope-from lockdoc@<MY_DYN_DNS>.dyndns.org)
Received: (from root@localhost)
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5/Submit) id q55CtArQ053185
        for lockdoc; Tue, 5 Jun 2012 14:55:10 +0200 (CEST)
        (envelope-from lockdoc)
Date: Tue, 5 Jun 2012 14:55:10 +0200 (CEST)
From: lockdoc <lockdoc@<MY_DYN_DNS>.dyndns.org>
Message-Id: <201206051255.q55CtArQ053185@fileserver.<MY_DOMAIN>.de>
To: lockdoc@<MY_DYN_DNS>.dyndns.org
Subject: test

test

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de--
Message 2
Code:
Message 2:
From MAILER-DAEMON Tue Jun  5 14:55:12 2012
Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q55CtCc8053192.1338900912/fileserver.<MY_DOMAIN>.de"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)

This is a MIME-encapsulated message

--q55CtCc8053192.1338900912/fileserver.<MY_DOMAIN>.de

The original message was received at Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
from localhost
with id q55CtCc7053192

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>.de>

   ----- Transcript of session follows -----
554 5.3.5 Local configuration error

--q55CtCc8053192.1338900912/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MY_DYN_DNS>.dyndns.org
Action: failed
Status: 5.5.0
Last-Attempt-Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)

--q55CtCc8053192.1338900912/fileserver.<MY_DOMAIN>.de
Content-Type: message/rfc822

Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5) id q55CtCc7053192;
        Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
        (envelope-from MAILER-DAEMON)
Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201206051255.q55CtCc7053192@fileserver.<MY_DOMAIN>.de>
To: <lockdoc@<MY_DYN_DNS>.dyndns.org>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de

The original message was received at Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<lockdoc@fileserver.<MY_DOMAIN>.de>
    (reason: 553 5.3.5 system config error)

   ----- Transcript of session follows -----
553 5.3.5 <MY_DYN_DNS>.dyndns.org. config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de
Content-Type: message/delivery-status

Reporting-MTA: dns; fileserver.<MY_DOMAIN>.de
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)

Final-Recipient: RFC822; lockdoc@<MY_DYN_DNS>.dyndns.org
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Tue, 5 Jun 2012 14:55:12 +0200 (CEST)

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de
Content-Type: message/rfc822

Return-Path: <lockdoc@<MY_DYN_DNS>.dyndns.org>
Received: from fileserver.<MY_DOMAIN>.de (localhost [127.0.0.1])
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5) with ESMTP id q55CtAc7053187
        for <lockdoc@fileserver.<MY_DOMAIN>.de>; Tue, 5 Jun 2012 14:55:12 +0200 (CEST)
        (envelope-from lockdoc@<MY_DYN_DNS>.dyndns.org)
Received: (from root@localhost)
        by fileserver.<MY_DOMAIN>.de (8.14.5/8.14.5/Submit) id q55CtArQ053185
        for lockdoc; Tue, 5 Jun 2012 14:55:10 +0200 (CEST)
        (envelope-from lockdoc)
Date: Tue, 5 Jun 2012 14:55:10 +0200 (CEST)
From: lockdoc <lockdoc@<MY_DYN_DNS>.dyndns.org>
Message-Id: <201206051255.q55CtArQ053185@fileserver.<MY_DOMAIN>.de>
To: lockdoc@<MY_DYN_DNS>.dyndns.org
Subject: test

test

--q55CtCc7053192.1338900912/fileserver.<MY_DOMAIN>.de--


--q55CtCc8053192.1338900912/fileserver.<MY_DOMAIN>.de--


Also irgendwas scheint da mit den MX Eintraegen und meiner Domain in Kombination mit dem dyndns nicht ganz hinzuhauen. Ich kann ja nichtmal im System emails versenden
 
es laeuft endlich!

Ich habe es jetzt hinbekommen.
Sendmail laeuft nun mit SASL_AUTH und kann mails auf meine TLD senden und empfangen. Dovecot habe ich auch installiert, damit ich das bequem handeln kann.
Zu alledem habe ich ihn jetzt in eine seperate JAIL gepackt.


Nun zur naechsten Frage:

Ich habe eine seperate www JAIL, die ja jetzt erstmal keine Mails versenden kann.
Nun waere mein Ziel, dass alle Mails die von der www JAIL gesendet werden ueber die MAIL-JAIL relayed werden und zwar immer als user lockdoc.

Ist das moeglich?
 
Zurück
Oben