Exim-Problem: unable to set gid uid
Gruesse! Ich habe seit einer Stunde ein Problem, alle meine Recherchen liefen ins Leere. Main exim4 wird hier von fetchmail gefüttert bzw. dient nur als lokaler MTA. Von jetzt auf gleich liefert exim keine Mails mehr aus und freezed jede Mail. Log einer lokalen Mail an meinen User: - 2006-03-10 15:45:58 1FHisQ-k5-Lf = [EMAIL PROTECTED] U=root P=local S=306 2006-03-10 15:45:58 1FHisQ-k5-Lf unable to set gid=1666 or uid=1666 (euid=102): local delivery to gerhard [EMAIL PROTECTED] transport=procmail_pipe 2006-03-10 15:45:58 1FHisQ-k5-Lf failed to read delivery status for [EMAIL PROTECTED] from delivery subprocess 2006-03-10 15:45:58 1FHisQ-k5-Lf pipe transport process returned non-zero status 0x0100: exit code 1 2006-03-10 15:45:58 1FHisQ-k5-Lf == [EMAIL PROTECTED] R=procmail T=procmail_pipe defer (-1) 2006-03-10 15:45:58 1FHisQ-k8-Tg = R=1FHisQ-k5-Lf U=Debian-exim P=local S=532 2006-03-10 15:45:58 1FHisQ-k5-Lf Frozen --- (Sorry für Umbrüche) Die Fehlermeldung an sich (und die Ursache) ist mir eigentlich schon klar: exim (Owner: debian-exim uid 102) kann nicht zu meiner uid/gid wechseln, um an procmail weiterzugeben. Aber warum auf einmal? Nichts wurde geändert/upgedatet, lediglich den apache2 habe ich neugestartet. Infos: --- - Debian sarge - alle Partitionen sind rw, konsistent und haben genug Platz. - beteiligt sind: fetchmail-exim-clamav-procmail-spamc Sowohl google und exim-FAQ beschreiben den Fehler bis zum Erbrechen, betrifft aber immer die Inbetriebnahme von exim. Also wenn exim ohne setuid bzw. ausreichend privelegierter User eingerichtet wurde. Ein Hinweis auf das Problem aus heiterem Himmel habe ich nicht gefunden. Was habe ich unternommem/überprüft: - - alle beteiligten Dienste neugestartet - Rechner neu gestartet ;-) - einen neuen User angelegt zum Testen (selbes Ergebniss) - im router/exim-procmail ist no_verify schon eingetragen. (FAQ) Symptome: - es betrifft jeden Transport, egal ob local delivery oder procmail - ein sendmail -qff (unfrozen) verarbeitet die Mails in der Queue dann ganz normal. Weiß jemand eine Lösung? Gruß Gerhard -- @[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] Don't panic! \* Greetings from Gerhard Brauer, \|/ \|/ \* 55411 Bingen am Rhein, Germany @~/ ,. \~@ \*.*** /_( \__/ )_\ |* IM: gerbra at jabber dot org \__U_/|* PGP: 96A08062 ___|*___ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Exim-Problem: unable to set gid uid [SOLVED]
Gruesse! * Gerhard Brauer [EMAIL PROTECTED] schrieb am [10.03.06 16:12]: Weiß jemand eine Lösung? Doch gefunden. /usr/sbin/exim4 war nicht mehr setuid gesetzt. Grrr. Ich frage mich nur: warum, woher? Wobei mir auch nicht bewußt war, daß es das vorher war. Ich war's definitiv nicht (Isch habe nüscht gemacht). Gefunden habe ich's, nachdem ich die Dateien mit dem Inhalt des debs verglichen habe. Es gibt ja irgendeinen daemon, der Änderungen an setuid/setgid überwacht. Kann ich das eigentlich auch im Nachhinein irgendwo noch feststellen? Ich greppe mal /var/log. Eingreifen von Fremdseite kann ich definitiv ausschließen. Gruß Gerhard -- @[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] Don't panic! \* Greetings from Gerhard Brauer, \|/ \|/ \* 55411 Bingen am Rhein, Germany @~/ ,. \~@ \*.*** /_( \__/ )_\ |* IM: gerbra at jabber dot org \__U_/|* PGP: 96A08062 ___|*___ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
mailman 2.0.11/exim problem
when I send a mail to the mailman-list nobody of the list gets the mail but the list owner gets the following information every 15 minutes. 2004-06-01 18:23:02 1BVALM-Bq-00 Neither the system_aliases director nor the address_pipe transport set a uid for local delivery of |/var/lib/mailman/mail/wrapper post mailman I installed mailman 2.0.11 with apt-get on a debian-woody / with exim. I did the configuration changes in exim.conf like it is described in http://www.exim.org/howto/mailman.html there is a user called exim and a group called exim on my server. who can help me? joachim -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: mailman 2.0.11/exim problem
Hallo Joachim, Joachim Schwendtner, 01.06.2004 (d.m.y): when I send a mail to the mailman-list nobody of the list gets the mail but the list owner gets the following information every 15 minutes. 2004-06-01 18:23:02 1BVALM-Bq-00 Neither the system_aliases director nor the address_pipe transport set a uid for local delivery of |/var/lib/mailman/mail/wrapper post mailman Offenbar weiss exim nicht, unter welcher UID er den rechts von dem Pipe-Symbol erwaehnten Befehl abarbeiten soll. Gruss, Christian -- Manche bilden sich ein, den Ton anzugeben, dabei machen sie nur Lärm. signature.asc Description: Digital signature
Re: Exim-problem
On Tue, May 25, 2004 at 03:03:35PM +0200, Mikael Bergman wrote: Exim verkar inte må bra, får följande: /etc/cron.daily/exim: failed to open DB file /var/spool/exim/db/retry: File exists failed to open DB file /var/spool/exim/db/wait-remote_smtp: File exists run-parts: /etc/cron.daily/exim exited with return code 1 Är det bara att ta bort filerna? Kör Debian unstable och Exim 3. Jepp, bara ta bort, de innehåller tips [1] om hur exim skall hantera medelanden, men om de saknas så är det värsta som kan hända att exim försöker leverera ett brev oftare än vad det var tänkt (inget problem med ett par hundra brev om dagen, ett problem vid ett par tusen brev i minuten :-). Annan fråga, ska jag uppgradera till Exim 4 eller rentav gå över till Postfix? Fördelar/nackdelar? Maskinen i fråga hanterar mail för mig och min familj, ett par hundra mail om dagen (lite listor och sånt). Jag säger nog exim 4, den har en massa trevliga finesser (som support från exim-users listan. [2]), plus att integreringen med exiscan gör spam/virus hanteringen snudd på trivial. Postfix har jag ingen egentlig erfarenhet av (mer en ett föredrag med Wietse Venema då den programmet fortfarande hette VMailer) så det flamkriget håller jag mig utanför (stånde på Exims sida:-) /jp [1] http://www.exim.org/exim-html-3.20/doc/html/spec_53.html#SEC880 [2] http://www.exim.org/pipermail/exim-users/Week-of-Mon-20040510/071324.html -- jens persson # A chunk was here doing something strange [EMAIL PROTECTED]# with psh etc. It is deleted, because it was Mäster Olofsväg 24 #evident non-sense. S-224 66 LUND;SWEDEN # --ANK # (in linux/net/ipv4/tcp.c)
exim problem
Dear: Debian Users I have a problem on exim smtp server. Some mail I send it give me an error below but when I test with qmail my 2nd smtp server it just working fine. 2004-04-20 12:08:38 1BFmYn-5Q-00 == [EMAIL PROTECTED] T=remote_smtp defer (-44): retry time not reached for any host The funny is I can send to hotmail via my exim smtp but accept to leader.com.my I have some problem. Best regards, Support -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Support [EMAIL PROTECTED] writes: 2004-04-20 12:08:38 1BFmYn-5Q-00 == [EMAIL PROTECTED] T=remote_smtp defer (-44): retry time not reached for any host The funny is I can send to hotmail via my exim smtp but accept to leader.com.my I have some problem. This is normal. Give it time, email is not instant. For whatever reason, it hasn't been able to deliver to leader.com.my yet. - -- Paul Johnson [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAhLI7UzgNqloQMwcRAkkEAJ9MP6UMeLPZN/hgZAoyBZV/T2IjNACgpFw+ ogvYXRAz30ov9B/AM3FSvgU= =tId4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem
* Clive Menzies [EMAIL PROTECTED] wrote: Have you made any recent changes? Perhaps it's queueing your mail before sending for some reason? I had this problem, although I recall the delay was nearer a minute. Are you using mutt? In your .muttrc file you need: set sendmail_wait=-1 Mine was previously set to 0. After the change everything was fine. Well, but telling the MUA not to wait for the MTA to deliver the Mails is not a good solution. You can work without waiting, but the mail still needs a minute more on it's way. [...and he is using Mozilla...] Clive Julius -- Julius Plenz, [EMAIL PROTECTED]Surf, Mail, Smile! www.cvmx.de/ http://plenz.com/ Please don't Cc me in your replies, thanks #129455376 3993 FD19 2AF0 E21E 5D74 E963 144C 5EE9 186D CA0D gpg --verbose --keyserver subkeys.pgp.net --recv-key 0x186DCA0D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem
Vineet Kumar wrote: * Ivan Wills ([EMAIL PROTECTED]) [040229 20:49]: Recently the server has started to take about 30s before sending a email message. (It never did this before) It does not matter what the size of the message is. It seems like the server is waiting for the 30s before listening to the client. I'd guess exim is trying to do an ident lookup with the client, but the client is silently dropping the ident requests. (Bad packet filter!) 30 seconds smells like a timeout; either ident or reverse DNS. This happens with every client? Is there a packet filter on the server side? Or a DNS misconfiguration? good times, Vineet The 30 seconds wait happens for all clients, and all the clients are behind a NAT firewall. So they are seen as one IP address ( which has an entry in the /etc/hosts file ) The firewalls name appears in the log files so it appears that exim is able to do a reverse look up. There is not packet filter running on the server either. Thank you for the suggestion though. Ivan -- ,###' *##/ Ivan Wills ,*##' Home Page : .*##)Email : [EMAIL PROTECTED] ,###' l##* ,. __ _. _ .*##' /%# ;*##*_*###*#' .*#\ ./###;. /##* /##' ,#*' '#*' '#* *%## *#* '*##* *##. .##' .*#/ |#*# # ##o#''#*#, ,##**##__*#* .#*, ,#*_*# *##' '*#|; *##'`*###*' '###*'##*' ,##'\#*. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem
I bounced your message back to the list, to continue the discussion in the public forum. This way, others may be able to provide input into the discussion, and still others may benefit from reading the discussion now and in the public list archives. * Ivan Wills ([EMAIL PROTECTED]) [040302 10:59]: Vineet Kumar wrote: * Ivan Wills ([EMAIL PROTECTED]) [040229 20:49]: Recently the server has started to take about 30s before sending a email message. (It never did this before) It does not matter what the size of the message is. It seems like the server is waiting for the 30s before listening to the client. I'd guess exim is trying to do an ident lookup with the client, but the client is silently dropping the ident requests. (Bad packet filter!) 30 seconds smells like a timeout; either ident or reverse DNS. This happens with every client? Is there a packet filter on the server side? Or a DNS misconfiguration? The 30 seconds wait happens for all clients, and all the clients are behind a NAT firewall. So they are seen as one IP address ( which has an entry in the /etc/hosts file ) Okay, well, that's not really a good test for all clients -- by asking that, I was trying to narrow down the problem to either the server or the client. If they're all going through the same connection, it doesn't help narrow it down. The firewalls name appears in the log files so it appears that exim is able to do a reverse look up. Right, it sounds like your DNS lookup is probably fine in this instance. I'd check that the NAT box isn't dropping inbound ident requests. It should instead be responding with TCP RST, as for all closed ports. I'd bet that's where your problem is. good times, Vineet P.S. Your sig is very large. This can be considered bad netiquette. Consider reducing its size; a good guideline is that it shouldn't exceed 4 lines (though I'm often guilty of exceeding this myself). In any case, aim for something that can be measured on the order of lines rather than a half-page. -- http://www.doorstop.net/ -- http://www.sprintpcs-sucks.org/ signature.asc Description: Digital signature
Re: exim problem
Vineet Kumar wrote: I bounced your message back to the list, to continue the discussion in the public forum. This way, others may be able to provide input into the discussion, and still others may benefit from reading the discussion now and in the public list archives. * Ivan Wills ([EMAIL PROTECTED]) [040302 10:59]: Vineet Kumar wrote: * Ivan Wills ([EMAIL PROTECTED]) [040229 20:49]: Recently the server has started to take about 30s before sending a email message. (It never did this before) It does not matter what the size of the message is. It seems like the server is waiting for the 30s before listening to the client. I'd guess exim is trying to do an ident lookup with the client, but the client is silently dropping the ident requests. (Bad packet filter!) 30 seconds smells like a timeout; either ident or reverse DNS. This happens with every client? Is there a packet filter on the server side? Or a DNS misconfiguration? The 30 seconds wait happens for all clients, and all the clients are behind a NAT firewall. So they are seen as one IP address ( which has an entry in the /etc/hosts file ) Okay, well, that's not really a good test for all clients -- by asking that, I was trying to narrow down the problem to either the server or the client. If they're all going through the same connection, it doesn't help narrow it down. The firewalls name appears in the log files so it appears that exim is able to do a reverse look up. Right, it sounds like your DNS lookup is probably fine in this instance. I'd check that the NAT box isn't dropping inbound ident requests. It should instead be responding with TCP RST, as for all closed ports. I'd bet that's where your problem is. good times, Vineet P.S. Your sig is very large. This can be considered bad netiquette. Consider reducing its size; a good guideline is that it shouldn't exceed 4 lines (though I'm often guilty of exceeding this myself). In any case, aim for something that can be measured on the order of lines rather than a half-page. Any suggestions on how to check if the firewall is sending a TCP RST? Ivan -- / [EMAIL PROTECTED] / _ _ / \ / | | | | /\/ \_| | | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 03, 2004 at 11:00:21AM +1100, Ivan Wills wrote: Any suggestions on how to check if the firewall is sending a TCP RST? telnet to the port. If you get Connection refused, then it is. If it times out, it's not. - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian. Because it *must* work. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFARY7HUzgNqloQMwcRAodQAKCkKKJTw1FzM31ZTNh/5WpO+xglaQCeNCO/ zSoWNv2g7jAOtHwL5Q3/MQE= =ABCs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
exim problem
Hi I am using Exim 3.35-1woodie2 under Debian Stable. Recently the server has started to take about 30s before sending a email message. (It never did this before) It does not matter what the size of the message is. It seems like the server is waiting for the 30s before listening to the client. Does any one have any suggestions as to why this might occur or suggestions on how to solve the problem? Thanks Ivan -- ,###' *##/ Ivan Wills ,*##' Home Page : .*##)Email : [EMAIL PROTECTED] ,###' l##* ,. __ _. _ .*##' /%# ;*##*_*###*#' .*#\ ./###;. /##* /##' ,#*' '#*' '#* *%## *#* '*##* *##. .##' .*#/ |#*# # ##o#''#*#, ,##**##__*#* .#*, ,#*_*# *##' '*#|; *##'`*###*' '###*'##*' ,##'\#*. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem
* Ivan Wills ([EMAIL PROTECTED]) [040229 20:49]: Recently the server has started to take about 30s before sending a email message. (It never did this before) It does not matter what the size of the message is. It seems like the server is waiting for the 30s before listening to the client. I'd guess exim is trying to do an ident lookup with the client, but the client is silently dropping the ident requests. (Bad packet filter!) 30 seconds smells like a timeout; either ident or reverse DNS. This happens with every client? Is there a packet filter on the server side? Or a DNS misconfiguration? good times, Vineet -- http://www.doorstop.net/ -- I am mortified to be told that, in the United States of America, the sale of a book can become a subject of inquiry, and of criminal inquiry too. -- President Thomas Jefferson signature.asc Description: Digital signature
Re: exim problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 01, 2004 at 03:36:05PM +1100, Ivan Wills wrote: Recently the server has started to take about 30s before sending a email message. (It never did this before) It does not matter what the size of the message is. It seems like the server is waiting for the 30s before listening to the client. Does any one have any suggestions as to why this might occur or suggestions on how to solve the problem? Have you made any recent changes? Perhaps it's queueing your mail before sending for some reason? - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian. Because it *must* work. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAQtRVUzgNqloQMwcRAkjjAKCWiv0w3jwtlc2e6GK6CkFv01VbDACgrIU8 VQz8zcJWwOnSYgzuU91siSo= =05tS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem
On (29/02/04 22:12), Paul Johnson wrote: On Mon, Mar 01, 2004 at 03:36:05PM +1100, Ivan Wills wrote: Recently the server has started to take about 30s before sending a email message. (It never did this before) It does not matter what the size of the message is. It seems like the server is waiting for the 30s before listening to the client. Does any one have any suggestions as to why this might occur or suggestions on how to solve the problem? Have you made any recent changes? Perhaps it's queueing your mail before sending for some reason? I had this problem, although I recall the delay was nearer a minute. Are you using mutt? In your .muttrc file you need: set sendmail_wait=-1 Mine was previously set to 0. After the change everything was fine. HTH Clive -- http://www.clivemenzies.co.uk strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[exim] Problem mit smtp-auth
HAllo, ich benutze exim3.35 und versende alle Mails über compusere - dachte ich wenigstens. Mittlerweile ist mir aufgefallen, das die mails nur verschickt werden, wenn ich mit CS eingewählt bin, ansonsten verschwinden meine mails ohne Warnung oder Meldung im Datennirvana. Zum testen habe ich mal arcor eingetragen, da erhalte ich wenigstens eine Mail: Mail delivery failed: returning message to sender ...Relaying denied - only use for SMTP_AUTH Es scheint, als würde exim nicht versuchen sich zu authentifizieren. Im folgenden ist ein Ausschnitt aus meiner exim.conf: #TRANSPORTS CONFIGURATION remote_smtp: driver = smtp authenticate_hosts = smtp.compuserve.de # authenticate_host = postman.arcor-online.net ... # ROUTERS CONFIGURATION smarthost: driver = domainlist transport = remote_smtp route_list = * smtp.compuserve.de bydns_a # route_list = * postman.arcor.de bydns_a end ... # AUTHENTICATION CONFIGURATION login: driver = plaintext #CS-Pro public_name = LOGIN client_send = : [EMAIL PROTECTED] : #arcor-smarthost: # public_name = PLAIN # client_send = : : Woran liegt es? MfG Steffen -- Wir sind nicht nur verantwortlich für das, was wir tun, sondern auch für das, was wir nicht tun. -- Jean-Baptiste Molière -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: [exim] Problem mit smtp-auth
Steffen Hey [EMAIL PROTECTED] wrote: ich benutze exim3.35 und versende alle Mails über compusere - dachte ich wenigstens. Mittlerweile ist mir aufgefallen, das die mails nur verschickt werden, wenn ich mit CS eingewählt bin, ansonsten verschwinden meine mails ohne Warnung oder Meldung im Datennirvana. Viele Provider öffnen ihr SMTP nur, wenn dua uch übr sie drin bist. Offene SMTP-Server würde ich mir als Provider auch nicht mehr erlauben. Zum testen habe ich mal arcor eingetragen, da erhalte ich wenigstens eine Mail: Mail delivery failed: returning message to sender ...Relaying denied - only use for SMTP_AUTH Arcor hat also SMTP-AUTH, Compuserver anscheinendn nicht. Es scheint, als würde exim nicht versuchen sich zu authentifizieren. Ich glaube, das ist auch nicht der default. Das hier wird Dir helfen: http://www.linuxer.onlinehome.de/apps/exim.htm natürlich die dort genannten gmx server durch Deien Server ersetzen. Heino -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: [exim] Problem mit smtp-auth
Hallo Steffen, Steffen Hey, 05.01.2004 (d.m.y): ich benutze exim3.35 und versende alle Mails über compuserve - dachte ich wenigstens. Mittlerweile ist mir aufgefallen, das die mails nur verschickt werden, wenn ich mit CS eingewählt bin, ansonsten verschwinden meine mails ohne Warnung oder Meldung im Datennirvana. Zum testen habe ich mal arcor eingetragen, da erhalte ich wenigstens eine Mail: Mail delivery failed: returning message to sender ...Relaying denied - only use for SMTP_AUTH Es scheint, als würde exim nicht versuchen sich zu authentifizieren. Im folgenden ist ein Ausschnitt aus meiner exim.conf: #TRANSPORTS CONFIGURATION remote_smtp: driver = smtp authenticate_hosts = smtp.compuserve.de An compuserve habe ich mich auch einmal in Sachen AMTP-Auth versucht. Ich habe es dann irgendwann aufgegeben, weil compuserve seine SMTP-Server wohl etwas anders konfiguriert hat. AFAIK scheiterte die Authentifizierung an einem fehlenden oder zu vielen Gleichheitszeichen in der SMTP-Kommunikation zu Beginn der Verbindung. Verbinde Dich mal via telnet auf Port 25 von smtp.compuserve.de, setze ein EHLO hostname ab und vergleiche den Output _akribisch_ mit dem von postman.arcor.de. # authenticate_host = postman.arcor-online.net Kann der denn auch SMTP-Auth? Ich habe dort postman.arcor.de eingetragen, mit dem es auch hinhaut. Gruss, Christian -- Die Situation wird nicht durch die Worte gehoben, sondern diese durch jene. -- Jean Paul pgp0.pgp Description: PGP signature
Re: exim problem - SMTP error from remote mailer after AUTH PLAIN
Solved. I had to change entries in /etc/email-addresses from
[EMAIL PROTECTED] to [EMAIL PROTECTED]
Mozilla mail can still send emails using
[EMAIL PROTECTED] Mozilla Thunderbird cannot and needs to use
[EMAIL PROTECTED] like exim. What is the difference between the way
mozilla mail does SMTP authentication and mozilla-thunderbird or exim?
On Sun, Jan 04, 2004 at 12:47:37AM -0500, Jerome R. Acks wrote:
For over a year now I've been using fetchmail, procmail, exim 3.36, and
mutt to send and receive email. After going away for three days, I
return to find that I can no longer send email via exim. I can still
send email using mozilla mail.
When I try to send a email via mutt and exim, I immediately get a
message log:
2004-01-03 23:18:45 [EMAIL PROTECTED] R=send_to_gateway
T=remote_smtp: retry time not reached for any host after a long failure
period
*** Frozen (delivery error message)
If I try to thaw message and deliver with exim -M, I get:
23:42:24 1Acziv-X5-00 Unfrozen by forced delivery
23:42:24 1Acziv-X5-00 SMTP error from remote mailer after AUTH
PLAIN: host outgoing.verizon.net [206.46.170.8]: 334 VXNlcm5hbWU6
23:42:24 1Acziv-X5-00 == [EMAIL PROTECTED] T=remote_smtp
defer (0): SMTP error from remote mailer after AUTH PLAIN: host
outgoing.verizon.net [206.46.170.8]: 334 VXNlcm5hbWU6
23:42:24 1Acziv-X5-00 ** [EMAIL PROTECTED]: retry timeout
exceeded
23:42:24 1Acziv-X5-00 [EMAIL PROTECTED]: error ignored
23:42:24 1Acziv-X5-00 Completed
What exactly does error 334 VXNlcm5hbWU6 mean? Does anyone have
suggestions on how to fix this?
I am using sarge. A few days ago an upgrade installed
exim_3.36-9.1_i386.deb, but that doesn't seem to be the problem, since
reinstalling exim_3.36-8_i386.deb results in the same error. I guess my
ISP, Verizon, who is not at all linux friendly, has changed something
again although whatever was done doesn't seem to have affected mozilla
mail from sending emails.
Nothing has changed in exim's configuration in over a year. Pertinent
pieces of /etc/exim/exim.conf:
##
# TRANSPORTS CONFIGURATION #
##
remote_smtp:
driver = smtp
authenticate_hosts = outgoing.verizon.net
##
# ROUTERS CONFIGURATION #
#Specifies how remote addresses are handled #
##
send_to_gateway:
driver = domainlist
transport = remote_smtp
route_list = * outgoing.verizon.net byname
##
# RETRY CONFIGURATION #
##
# Domain Error Retries
# -- - ---
* * F,2h,15m; G,16h,1h,1.5; F,4d,8h
##
# AUTHENTICATION CONFIGURATION #
##
# Setup for client side authentication to one host for multiple users,
# each with a separate password: To make the lookup function work
# set up a file, /etc/exim/smtp-passwd, of uid's, usernames and passwords.
# /etc/exim/smtp-passwd is owned by mail.mail so that passwords are not
# stored in a world readable file. The format of the file is:
#
# uid1:^username1^password1
# uid2:^username2^password2
# etc.
#
# where usernameX and passwordX are the login name and password on the
# host, and uidX is the user's uid on the local computer.
plain:
driver = plaintext
public_name = PLAIN
client_send =
${lookup{$originator_uid}lsearch{/etc/exim/smtp-passwd}{$value}}
--
Jerome
signature.asc
Description: Digital signature
Re: exim problem - SMTP error from remote mailer after AUTH PLAIN
| What exactly does error 334 VXNlcm5hbWU6 mean? The 334 is the response code from the server. The data after it is base64 encoded and decodes to Username:. On Sun, Jan 04, 2004 at 09:03:21PM -0500, Jerome R. Acks wrote: | Solved. I had to change entries in /etc/email-addresses from | [EMAIL PROTECTED] to [EMAIL PROTECTED] Aha. I guess when the server didn't like the username/passwd pair you sent it decided to switch from AUTH PLAIN to AUTH LOGIN. However, exim wasn't expecting an interactive prompt for the username and password, so it stopped processing right then. (BTW, AUTH LOGIN is not actually defined in any standard) | Mozilla mail can still send emails using | [EMAIL PROTECTED] Mozilla Thunderbird cannot and needs to use | [EMAIL PROTECTED] like exim. What is the difference between the way | mozilla mail does SMTP authentication and mozilla-thunderbird or exim? I don't know, use ethereal to see what is actually being sent across the wire. Different server, perhaps? -D -- He is no fool who gives up what he cannot keep to gain what he cannot lose. --Jim Elliot www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
mailman/exim problem
Exim's conf file attached as well as /etc/aliases due to possible relevance
already checked man mailman
[EMAIL PROTECTED]:~# man mailman
No manual entry for mailman
[EMAIL PROTECTED]:~#
[EMAIL PROTECTED]:~# apt-cache search mailman docs
[EMAIL PROTECTED]:~# apt-cache search mailman doc
[EMAIL PROTECTED]:~# apt-cache search mailman man
lg-issue91 - Issue 91 of the Linux Gazette.
mailman - Powerful, web-based mailing list manager
gforge-lists-mailman - Collaborative development tool - mailing-lists
(using Mailman)
[EMAIL PROTECTED]:~#
No other documentation available (good gods that's horrible in and of
itself)
So here goes it.
I have mailman 90% working. Automated, mailman originated messages (such
as subscribe request confirmations originating at the server (ala the
invite tool)), admin and user interface works. I can send and recieve
mail via local user accounts ('ve tested this thoroughly). My exim.conf
(attached) looks to be pretty tight, and aliases (attached) appears to
be set up correctly.
Replying to administrivia/relaying normal list traffic is still broke,
as is access to the public archive (which really doesn't exist due to
the fact messages aren't being sent). I've sent about 4 test messages
that have caused this:
Envelope-to: [EMAIL PROTECTED]
From: Cron Daemon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Cron [EMAIL PROTECTED] if [ -x /usr/lib/exim/exim3 -a
-f /etc/exim/exim.conf ]; then
+/usr/lib/exim/exim3 -q ; fi
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: HOME=/var/mail
X-Cron-Env: PATH=/usr/bin:/bin
X-Cron-Env: LOGNAME=mail
2004-01-03 13:08:01 1AcqVM-0007Rx-00 Neither the system_aliases director
nor the address_pipe transport set a uid
+for local delivery of |/var/lib/mailman/mail/mailman post listadmins
Now, in aliases, I tried putting root one space after the colon (in
between the pipe to |var/lib/blah/blah and listadmin*:) and wound up
with frozen messages. Reloading mailman (forcibly at times) has not
helped with either the frozen messages or the above situation. I can't
decide if it's Debian related or purely mailman related. Any help would
be greatly appreciated.
--
Joseph A. Nagy, Jr.
Student at Motlow State Community College
Political Activist Extrodinaire
The only fallacy is the inaction on our part to stave off the worst of
horrors, the stripping of personal freedom.
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system administrator.
# This file originally generated by eximconfig at Mon Dec 22 12:10:09 CST 2003
# See exim info section for details of the things that can be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word end. The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = joseph-a-nagy-jr.homelinux.org
# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not want
# to do any local deliveries, uncomment the following line, but do not supply
# any data for it. This sets local_domains to an empty string, which is not
# the same as not mentioning it at all. An empty string specifies that there
# are no local domains; not setting it at all causes the default value (the
# setting of qualify_recipient) to be used.
local_domains = localhost:joseph-a-nagy-jr.homelinux.org
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
#relay_domains =
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
Re: mailman/exim problem
On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote
Exim's conf file attached as well as /etc/aliases due to possible relevance
already checked man mailman
[EMAIL PROTECTED]:~# man mailman
No manual entry for mailman
[EMAIL PROTECTED]:~#
[EMAIL PROTECTED]:~# apt-cache search mailman docs
[EMAIL PROTECTED]:~# apt-cache search mailman doc
[EMAIL PROTECTED]:~# apt-cache search mailman man
lg-issue91 - Issue 91 of the Linux Gazette.
mailman - Powerful, web-based mailing list manager
gforge-lists-mailman - Collaborative development tool - mailing-lists
(using Mailman) [EMAIL PROTECTED]:~#
No other documentation available (good gods that's horrible in and
of itself)
Try below for more info:
www.list.org
So here goes it.
I have mailman 90% working. Automated, mailman originated messages
(such as subscribe request confirmations originating at the server
(ala the invite tool)), admin and user interface works. I can send
and recieve mail via local user accounts ('ve tested this thoroughly)
. My exim.conf
(attached) looks to be pretty tight, and aliases (attached) appears
to be set up correctly.
I've always had problems when I didn't put
user = list
in my exim.conf file.
This line is located near your system_aliases stanza.
hth,
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
On Sat, Jan 03, 2004 at 01:27:49PM -0600, Joseph A. Nagy, Jr. wrote: Exim's conf file attached as well as /etc/aliases due to possible relevance already checked man mailman [EMAIL PROTECTED]:~# man mailman No manual entry for mailman [EMAIL PROTECTED]:~# snip No other documentation available (good gods that's horrible in and of itself) Plenty of documentation and it should be right there on your machine: [EMAIL PROTECTED]:~$ ls -al /usr/share/doc/mailman/ total 152 drwxr-xr-x6 root root 4096 Nov 15 12:59 . drwxr-xr-x 286 root root 8192 Dec 17 15:12 .. -rw-r--r--1 root root 2166 May 20 2002 ACKNOWLEDGMENTS -rw-r--r--1 root root 686 Sep 22 2000 BUGS -rw-r--r--1 root root 9640 Apr 18 2002 FAQ -rw-r--r--1 root root20067 Nov 16 2000 INSTALL -rw-r--r--1 root root16652 May 20 2002 NEWS.gz -rw-r--r--1 root root 6155 Jan 3 2001 README -rw-r--r--1 root root 871 Jan 3 2001 README.BSD -rw-r--r--1 root root 3046 Sep 18 2002 README.Debian -rw-r--r--1 root root 9469 Sep 18 2002 README.EXIM -rw-r--r--1 root root 1059 Mar 12 2001 README.LINUX -rw-r--r--1 root root 1742 Jul 19 2000 README.NETSCAPE -rw-r--r--1 root root 2167 Oct 20 2000 README.QMAIL.gz -rw-r--r--1 root root 1528 Mar 21 2000 README.SENDMAIL -rw-r--r--1 root root 3991 Nov 10 2000 TODO.gz -rw-r--r--1 root root 3552 Mar 3 2001 UPGRADING.gz -rw-r--r--1 root root 6676 Sep 18 2002 changelog.Debian.gz -rw-r--r--1 root root 1248 Sep 18 2002 copyright drwxr-xr-x3 root root 4096 Nov 14 10:19 examples drwxr-xr-x3 root root 4096 Nov 14 10:19 html drwxr-xr-x2 root root 4096 Nov 14 10:19 images drwxr-xr-x2 root root 4096 Nov 14 10:19 src Also, this link is a great help: http://www.exim.org/howto/mailman.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
mike wrote:
On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote
Exim's conf file attached as well as /etc/aliases due to possible relevance
already checked man mailman
[EMAIL PROTECTED]:~# man mailman
No manual entry for mailman
[EMAIL PROTECTED]:~#
[EMAIL PROTECTED]:~# apt-cache search mailman docs
[EMAIL PROTECTED]:~# apt-cache search mailman doc
[EMAIL PROTECTED]:~# apt-cache search mailman man
lg-issue91 - Issue 91 of the Linux Gazette.
mailman - Powerful, web-based mailing list manager
gforge-lists-mailman - Collaborative development tool - mailing-lists
(using Mailman) [EMAIL PROTECTED]:~#
No other documentation available (good gods that's horrible in and
of itself)
Try below for more info:
www.list.org
I guess horribley inadequate documentation is better then none at all.
So here goes it.
I have mailman 90% working. Automated, mailman originated messages
(such as subscribe request confirmations originating at the server
(ala the invite tool)), admin and user interface works. I can send
and recieve mail via local user accounts ('ve tested this thoroughly)
. My exim.conf
(attached) looks to be pretty tight, and aliases (attached) appears
to be set up correctly.
I've always had problems when I didn't put
user = list
in my exim.conf file.
This line is located near your system_aliases stanza.
hth,
Mike
I think that did the trick. I restarted both exim and mailman and I'm
starting to get stuff from the test (soon to go live) list that I created.
--
Joseph A. Nagy, Jr.
Student at Motlow State Community College
Political Activist Extrodinaire
The only fallacy is the inaction on our part to stave off the worst of
horrors, the stripping of personal freedom.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
On Sat, Jan 03, 2004 at 05:43:29PM -0600, Joseph A. Nagy, Jr. wrote: mike wrote: On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote Exim's conf file attached as well as /etc/aliases due to possible relevance already checked man mailman [EMAIL PROTECTED]:~# man mailman No manual entry for mailman [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# apt-cache search mailman docs [EMAIL PROTECTED]:~# apt-cache search mailman doc [EMAIL PROTECTED]:~# apt-cache search mailman man lg-issue91 - Issue 91 of the Linux Gazette. mailman - Powerful, web-based mailing list manager gforge-lists-mailman - Collaborative development tool - mailing-lists (using Mailman) [EMAIL PROTECTED]:~# No other documentation available (good gods that's horrible in and of itself) Try below for more info: www.list.org I guess horribley inadequate documentation is better then none at all. What are you talking about? It is well documented! It does not get any better than this: http://www.exim.org/howto/mailman.html Also, did you see my other post? Look at /usr/share/doc/mailman It should be right there in front of you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
Andy Firman wrote: On Sat, Jan 03, 2004 at 05:43:29PM -0600, Joseph A. Nagy, Jr. wrote: mike wrote: On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote Exim's conf file attached as well as /etc/aliases due to possible relevance already checked man mailman [EMAIL PROTECTED]:~# man mailman No manual entry for mailman [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# apt-cache search mailman docs [EMAIL PROTECTED]:~# apt-cache search mailman doc [EMAIL PROTECTED]:~# apt-cache search mailman man lg-issue91 - Issue 91 of the Linux Gazette. mailman - Powerful, web-based mailing list manager gforge-lists-mailman - Collaborative development tool - mailing-lists (using Mailman) [EMAIL PROTECTED]:~# No other documentation available (good gods that's horrible in and of itself) Try below for more info: www.list.org I guess horribley inadequate documentation is better then none at all. What are you talking about? It is well documented! From a casual loo kat the website that is hard to tell. It does not get any better than this: http://www.exim.org/howto/mailman.html I saw that, it's geared towards source installs of mailman, not binary. The biggest difference is in setting of permissions and directories. Also, did you see my other post? Look at /usr/share/doc/mailman It should be right there in front of you! I saw, am gonna look at them this evening. I'm still having problems accessing the archives from the web. -- Joseph A. Nagy, Jr. Student at Motlow State Community College Political Activist Extrodinaire The only fallacy is the inaction on our part to stave off the worst of horrors, the stripping of personal freedom. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
exim problem - SMTP error from remote mailer after AUTH PLAIN
For over a year now I've been using fetchmail, procmail, exim 3.36, and
mutt to send and receive email. After going away for three days, I
return to find that I can no longer send email via exim. I can still
send email using mozilla mail.
When I try to send a email via mutt and exim, I immediately get a
message log:
2004-01-03 23:18:45 [EMAIL PROTECTED] R=send_to_gateway
T=remote_smtp: retry time not reached for any host after a long failure
period
*** Frozen (delivery error message)
If I try to thaw message and deliver with exim -M, I get:
23:42:24 1Acziv-X5-00 Unfrozen by forced delivery
23:42:24 1Acziv-X5-00 SMTP error from remote mailer after AUTH
PLAIN: host outgoing.verizon.net [206.46.170.8]: 334 VXNlcm5hbWU6
23:42:24 1Acziv-X5-00 == [EMAIL PROTECTED] T=remote_smtp
defer (0): SMTP error from remote mailer after AUTH PLAIN: host
outgoing.verizon.net [206.46.170.8]: 334 VXNlcm5hbWU6
23:42:24 1Acziv-X5-00 ** [EMAIL PROTECTED]: retry timeout
exceeded
23:42:24 1Acziv-X5-00 [EMAIL PROTECTED]: error ignored
23:42:24 1Acziv-X5-00 Completed
What exactly does error 334 VXNlcm5hbWU6 mean? Does anyone have
suggestions on how to fix this?
I am using sarge. A few days ago an upgrade installed
exim_3.36-9.1_i386.deb, but that doesn't seem to be the problem, since
reinstalling exim_3.36-8_i386.deb results in the same error. I guess my
ISP, Verizon, who is not at all linux friendly, has changed something
again although whatever was done doesn't seem to have affected mozilla
mail from sending emails.
Nothing has changed in exim's configuration in over a year. Pertinent
pieces of /etc/exim/exim.conf:
##
# TRANSPORTS CONFIGURATION #
##
remote_smtp:
driver = smtp
authenticate_hosts = outgoing.verizon.net
##
# ROUTERS CONFIGURATION #
#Specifies how remote addresses are handled #
##
send_to_gateway:
driver = domainlist
transport = remote_smtp
route_list = * outgoing.verizon.net byname
##
# RETRY CONFIGURATION #
##
# Domain Error Retries
# -- - ---
* * F,2h,15m; G,16h,1h,1.5; F,4d,8h
##
# AUTHENTICATION CONFIGURATION #
##
# Setup for client side authentication to one host for multiple users,
# each with a separate password: To make the lookup function work
# set up a file, /etc/exim/smtp-passwd, of uid's, usernames and passwords.
# /etc/exim/smtp-passwd is owned by mail.mail so that passwords are not
# stored in a world readable file. The format of the file is:
#
# uid1:^username1^password1
# uid2:^username2^password2
# etc.
#
# where usernameX and passwordX are the login name and password on the
# host, and uidX is the user's uid on the local computer.
plain:
driver = plaintext
public_name = PLAIN
client_send =
${lookup{$originator_uid}lsearch{/etc/exim/smtp-passwd}{$value}}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Einfaches Exim Problem
Hallo, kommentier mal den Eintrag qualify_domain = gmx.de aus, sonst fühlt sich Exim für diese Domäne zuständig. Daher auch die Mail an [EMAIL PROTECTED] Habe ich gemacht, wird aber leider nicht besser. Fehlermeldung: 2003-11-14 08:06:10 routing failed for [EMAIL PROTECTED]: unrouteable mail domain gmx.de *** Frozen (delivery error message) Gruß! Fabian -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Einfaches Exim Problem
Hallo Bertram,
plain:
driver = plaintext
public_name = PLAIN
client_send =
^${extract{3}{::}{${lookup{$sender_address}lsearch{/etc/exim/passwd.client}{$value}fail}}}^${extract{4}{::}{${lookup{$sender_address}lsearch{/etc/exim/passwd.client}{$value}fail}}}
Ich verwende die extract-key-Form; hierzu will ich nichts
sagen. Wozu brauchst Du zwei Doppelpunkte?
Keine Ahnung; hab' ich mit cut/paste von der angegbenen Seite
übertragen.
Was funktioniert nicht? Exim schreibt sehr ausfühliche
Logdateien. Schau doch mal in `/var/log/exim/mainlog'.
2003-11-14 08:06:10 routing failed for [EMAIL PROTECTED]:
unrouteable mail domain gmx.de
*** Frozen (delivery error message)
Wenn Du nicht zurechtkommst, kann ich Dir ja mal meine
Konfiguration schicken.
Wäre sehr nett!
Beste Grüße!
Fabian
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Einfaches Exim Problem
Hallo, Was funktioniert nicht? Exim schreibt sehr ausfühliche Logdateien. Schau doch mal in `/var/log/exim/mainlog'. 2003-11-14 08:06:10 routing failed for [EMAIL PROTECTED]: unrouteable mail domain gmx.de *** Frozen (delivery error message) - Das waren die Meldungen aus /var/spool/exim/msglog/... . Jetzt hab' ich endlich die Fehlermeldung aus /var/log/exim/mainlog: ... ... ... 2003-11-14 11:10:02 1AKO6R-0002Dc-00 Message is frozen 2003-11-14 11:10:02 1AKOG2-0002Tl-00 Message is frozen 2003-11-14 11:10:02 1AKOGP-0002UI-00 Message is frozen 2003-11-14 11:10:02 1AKXwB-Cz-00 Message is frozen 2003-11-14 11:10:02 End queue run: pid=1973 -qf 2003-11-14 11:10:06 1AKaty-UF-00 Rewrite of [EMAIL PROTECTED] yielded unqualified address root (Cron Daemon) 2003-11-14 11:10:06 1AKaty-UF-00 = [EMAIL PROTECTED] U=root P=local S=561 2003-11-14 11:10:06 1AKaty-UF-00 = fab [EMAIL PROTECTED] D=procmail T=procmail_pipe 2003-11-14 11:10:06 1AKaty-UF-00 Completed Und hier noch die letzte Meldung aus /var/log/exim/paniclog: ... 2003-11-14 11:10:06 1AKaty-UF-00 Rewrite of [EMAIL PROTECTED] yielded unqualified address root (Cron Daemon) Gruß! Fabian -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Einfaches Exim Problem
Hallo, Am Freitag, 14. Nov 2003, 11:17:03 +0100 schrieb Fabian Brännström: Jetzt hab' ich endlich die Fehlermeldung aus /var/log/exim/mainlog: ... 2003-11-14 11:10:06 1AKaty-UF-00 Rewrite of [EMAIL PROTECTED] yielded unqualified address root (Cron Daemon) Probier mal `exim -brw' (testet die Rewrite-Regeln), um mehr Information zu bekommen. Meine Konfiguration per PM. Gruß Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Einfaches Exim Problem
Hallo Leute, jetzt funktioniert es wunderbar! Zwar benutze ich noch evolution, aber demnächst (hoffentlich) wird mutt mit procmail eingesetzt. Meine Konfiguration per PM. Vielen Dank für deine Konfig; war sehr hilfreich. Besten Dank! Gruß Fabian -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Einfaches Exim Problem
* Bertram Scharpf [EMAIL PROTECTED] [13-11-2003 21:37]:
^${extract{3}{::}{${lookup...
Wozu brauchst Du zwei Doppelpunkte?
Man braucht nur einen. Habe vergessen es zu ändern.
Allerdings funktioniert es auch mit den beiden... :)
Gruss Uwe
pgp0.pgp
Description: PGP signature
Re: Einfaches Exim Problem
* Bertram Scharpf [EMAIL PROTECTED] [14-11-2003 12:18]: 2003-11-14 11:10:06 1AKaty-UF-00 Rewrite of [EMAIL PROTECTED] yielded unqualified address root (Cron Daemon) Probier mal `exim -brw' (testet die Rewrite-Regeln), um mehr Information zu bekommen. Hallo Bertram, ich weiß, dass die simple rewrite-rule [EMAIL PROTECTED] nicht optimal ist. Werde mal etwas mit [EMAIL PROTECTED] probieren. Meine Konfiguration per PM. Würde mich auch interessieren. :-) Bin gerade dabei meine Config für exim4 anzupassen. Zwei kleine Probleme habe ich noch dabei: Rewriting und Behandlung der Error-Messages. Habe schon einige Möglichkeiten probiert, aber eine Lösung habe ich noch nicht gefunden. Gruss Uwe pgp0.pgp Description: PGP signature
Re: Einfaches Exim Problem
Hallo, Am Freitag, 14. Nov 2003, 16:52:32 +0100 schrieb Uwe Kerstan: * Bertram Scharpf [EMAIL PROTECTED] [14-11-2003 12:18]: 2003-11-14 11:10:06 1AKaty-UF-00 Rewrite of [EMAIL PROTECTED] yielded unqualified address root (Cron Daemon) Probier mal `exim -brw' (testet die Rewrite-Regeln), um mehr Information zu bekommen. Hallo Bertram, ich weiß, dass die simple rewrite-rule [EMAIL PROTECTED] nicht optimal ist. Werde mal etwas mit [EMAIL PROTECTED] probieren. Meine Konfiguration per PM. Würde mich auch interessieren. :-) Langsam. Für Address Rewriting bin ich kein Experte. Ich sagte lediglich, daß es mir gelungen ist, nach dem Domainteil sortiert mehrere SMTP-Server zu bedienen samt Authentifizierung. Mit dem Rewriting kämpfe ich selber noch. Gruß Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Einfaches Exim Problem
Hallo Leute,
ich versuche seit Tagen eine einfache Exim.conf zu erstellen, die mir es
ermöglicht, als alleiniger User(fab) Mails über mail.gmx.de,
mailto.btx.dtag.de und mailto.tu-berlin.de zu verschicken; dabei muss
natürlich die Absendeadresse angepasst werden.
Ich bin nach folgender Anleitung vorgegangen:
http://www.openoffice.de/linux/buch/email.html
so dass ich mittlererweile über gmx versenden kann.
Große Probleme bereitet mir noch immer t-online und tu-berlin
einzubinden. Hierfür habe ich folgende Anleitung gefunden:
http://www.linuxer.onlinehome.de/apps/exim.htm
Kapitel:11. Mehrere Smarthosts mit Authentifizierung
Ich somit folgende Veränderungen zur einfachen gmx-Version gemacht:
##
# TRANSPORTS CONFIGURATION #
##
###remote_smtp:
### driver = smtp
### authenticate_hosts = mail.gmx.de
remote_smtp:
driver = smtp
authenticate_hosts = mail.gmx.net:mailto.tu-berlin.de
...
...
##
# ROUTERS CONFIGURATION #
#Specifies how remote addresses are handled #
##
###smarthost:
### driver = domainlist
### transport = remote_smtp
### route_list = * mail.gmx.de bydns_a
smarthost_mail_gmx_net:
condition = ${if eq {${lc:$sender_address_domain}}{gmx\.de}{true} fail}:
driver =
domainlist
transport =
remote_smtp
route_list = * mail.gmx.net
bydns_a
smarthost_auth_mail_onlinehome_de:
condition = ${if eq
{${lc:$sender_address_domain}}{tu-berlin\.de}{true} fail}:
driver =
domainlist
transport =
remote_smtp
route_list = * mailto.tu-berlin.de
bydns_a
end
...
...
##
# REWRITE CONFIGURATION #
##
[EMAIL PROTECTED]${lookup{$1}lsearch{/etc/email-addresses}\
### {$value}fail} frFs
[EMAIL PROTECTED] $header_from: Fs
end
##
# AUTHENTICATION CONFIGURATION #
##
### cram_md5:
### driver = cram_md5
### public_name = CRAM-MD5
### client_name = xxx
### client_secret = xxx
plain:
driver = plaintext
public_name = PLAIN
client_send =
^${extract{3}{::}{${lookup{$sender_address}lsearch{/etc/exim/passwd.client}{$value}fail}}}^${extract{4}{::}{${lookup{$sender_address}lsearch{/etc/exim/passwd.client}{$value}fail}}}
Meine passwd.client sieht dabei so aus:
[EMAIL PROTECTED]:fab:mail.gmx.de:xxxusernamexxx:xxxpasswortxxx
[EMAIL PROTECTED]:fab:mailto.tu-berlin.de:xxxusernamexxx:xxxpasswortxxx
Das ganze funktioniert aber nicht!?
Mich verwirrt ein wenig folgender Eintrag am Anfang der config:
qualify_domain = gmx.de
Dieser müsste sich doch auch dem verwendeten Provider anpassen?
Hat jemand vielleicht ein paar Hinweise, wie ich es besser machen kann?
Beste Grüße!
Fabian
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Einfaches Exim Problem
* Fabian Brännström [EMAIL PROTECTED] [13-11-2003 10:14]: Das ganze funktioniert aber nicht!? Fehlermeldung? pgp0.pgp Description: PGP signature
Re: Einfaches Exim Problem
On Thu, 2003-11-13 at 16:55, Uwe Kerstan wrote: * Fabian Brännström [EMAIL PROTECTED] [13-11-2003 10:14]: Das ganze funktioniert aber nicht!? Fehlermeldung? Hab' ich vergessen: 2003-11-13 21:30:07 routing failed for [EMAIL PROTECTED]: unrouteable mail domain gmx.de *** Frozen (delivery error message) Dabei fällt mir ja direkt das root auf; habe mir nun gedacht ich könnte das in der passwd.client ergänzen. -- neue Fehlermeldung: 2003-11-13 21:40:25 routing failed for [EMAIL PROTECTED]: unrouteable mail domain gmx.de *** Frozen (delivery error message) Hoffentlich hilft das weiter. Beste Grüße! Fabian -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Einfaches Exim Problem
2003-11-13 21:30:07 routing failed for [EMAIL PROTECTED]: unrouteable mail domain gmx.de *** Frozen (delivery error message) Dabei fällt mir ja direkt das root auf; habe mir nun gedacht ich könnte das in der passwd.client ergänzen. -- neue Fehlermeldung: 2003-11-13 21:40:25 routing failed for [EMAIL PROTECTED]: unrouteable mail domain gmx.de *** Frozen (delivery error message) Hallo, kommentier mal den Eintrag qualify_domain = gmx.de aus, sonst fühlt sich Exim für diese Domäne zuständig. Daher auch die Mail an [EMAIL PROTECTED] Hoffentlich hilft das weiter. Dito Gruß, Rolf -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
AMaViS + AntiVir + Exim Problem
Hallo,
ich hab auf meinem Mailserver exim3, amavis-perl-11 und
antivir-server-2.0.8 installiert. Die mails werden auch an amavis
weitergeleitet. Nur wenn ich mir eine Virusmail schicke, erkennt amavis
bzw. antivir dies nicht als solche. Wenn ich das virus-file von Hand
teste wird der Virus erkannt. Hat jemand eine Ahnung wiso das mit exim
nicht funktioniert?
## exim.conf ##
# TRANSPORTS CONFIGURATION
amavis:
driver = pipe
command = /usr/local/sbin/amavis -f ${sender_address} \
-d {pipe_addresses}
prefix =
suffix =
check_string =
escape_string =
return_output = false
return_path_add = false
user = amavis
group = amavis
path = /bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin
current_directory = /var/amavis
# DIRECTORS CONFIGURATION
amavis_director:
condition = ${if or { {eq {$received_protocol}{scanned-ok}} \
{eq {$received_protocol}{spam-scanned}} } {0}{1}}
driver = smartuser
transport = amavis
--
Best regards from Dresden
Viele Grüße aus Dresden
Christian Arnold
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
exim - problem
hello all ! Nie wiem co sie stalo , ale od trzech dni nie moge wysylac maila z konta na moim serwie, do mnie przychodza wszystkie . W logach mam caly czas np : [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached gdzie lezy problem ?? A przez ostatnie 4 dni nic nie zmienialem w konfiguracji Wczesniej upgradowlem (ok 2 tyg temu ) ssh i apache-ssl pozdr jazz
Re: exim - problem
On Wed, Apr 30, 2003 at 12:36:35PM +0200, jazz wrote: hello all ! Nie wiem co sie stalo , ale od trzech dni nie moge wysylac maila z konta na moim serwie, do mnie przychodza wszystkie . W logach mam caly czas np : [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached [EMAIL PROTECTED] routing defer (-42) : retry time not reached gdzie lezy problem ?? Wyżej. Poszukaj pierwszego komunikatu dotyczącego tego maila. Marcin -- Marcin Owsiany [EMAIL PROTECTED] http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216
Re: exim Problem?
Am 06.01.2003 09:07:56, Ulrich Wiederhold schrieb: immer mal wieder bleiben bei mir einige Mails im System hängen (exim), warum auch immer. Wenn ich diese Emails mit exim -Mt auftaue und per exim -q wieder abschicke, dann bekomme ich von meinem Provider folgende Fehlermeldung: [...] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mail.t-link.de [194.97.37.23]: 553 sorry, that domain isn't in my = list of allowed rcpthosts (#5.7.1) Hast Du mal versucht, die Mail ueber ein anderes SMTP-Relay loszuwerden? Mir scheint, da ist in Exim irgendwas fehlkonfiguriert. Was? Muss nicht sein. Man darf ruhig auch einmal in Betracht ziehen, dass Rechner auf der anderen Seite der Leitung falsch konfiguriert sind. Was hat das mit den rcpthosts aus sich? (Was ist das? Kann mich nicht erinnern, sowas konfiguriert zu haben). Das wuesste ich jetzt gerne, was Du da konfiguriert haben willst. rcpthosts=Recipient host=Empfaengerrechner. Der Provider verwendet smtp afet pop. Da ich aber alle 10 Minuten meine Emails abrufe und dann 30 Minuten lang Emails verschicken kann, sollte ich dadurch doch eigentlich keine Probleme bekommen... So ist dieses System gedacht. Bietet denn der Provider neben POP3 auch POP3S an? Der Dienst laeuft ueber Port 995 und bietet verschluesselte Mailuebertragung an, so dass Du auf die SMTP-AFTER-POP-Methode verzichten koenntest. Gruss Peter Blancke -- Nachtwaechter ist der Wahnsinn, weil er wacht... -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
exim Problem?
Hallo, immer mal wieder bleiben bei mir einige Mails im System hängen (exim), warum auch immer. Wenn ich diese Emails mit exim -Mt auftaue und per exim -q wieder abschicke, dann bekomme ich von meinem Provider folgende Fehlermeldung: From: Mail Delivery System [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Delivered-To: GMX delivery to [EMAIL PROTECTED] X-Failed-Recipients: [EMAIL PROTECTED] Date: Thu, 02 Jan 2003 18:40:06 +0100 X-Resent-By: Forwarder [EMAIL PROTECTED] X-Resent-For: [EMAIL PROTECTED] X-Resent-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=3D-99.0 required=3D6.0 tests=3DDATE_IN_PAST_48_96,MAILER_DAEMON,SPAM_PHRASE_03_05, USER_IN_WHITELIST version=3D2.43 X-Spam-Level:=20 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]= : host mail.t-link.de [194.97.37.23]: 553 sorry, that domain isn't in my = list of allowed rcpthosts (#5.7.1) -- This is a copy of the message, including all the headers. -- Return-path: [EMAIL PROTECTED] Received: from fzzgrr by home.sky.net with local (Exim 3.36 #1 (Debian)) id 18U9KA-00012j-00 for [EMAIL PROTECTED]; Thu, 02 Jan 2003 18:40:06 +0100 Date: Thu, 2 Jan 2003 18:40:06 +0100 From: Ulrich Wiederhold [EMAIL PROTECTED] To: xchat-discuss [EMAIL PROTECTED] Subject: fix ident? Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=3Diso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.4i X-Operating-System: Debian GNU/Linux testing/unstable (Kernel 2.4.20-rc4) Organization: Debian GNU/Linux-System Sender: [EMAIL PROTECTED] Mir scheint, da ist in Exim irgendwas fehlkonfiguriert. Was? Was hat das mit den rcpthosts aus sich? (Was ist das? Kann mich nicht erinnern, sowas konfiguriert zu haben). Uli Der Provider verwendet smtp afet pop. Da ich aber alle 10 Minuten meine Emails abrufe und dann 30 Minuten lang Emails verschicken kann, sollte ich dadurch doch eigentlich keine Probleme bekommen... -- 'The box said, 'Requires Windows 95 or better', so I installed Linux - TKK 5 -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Exim: problem mit mail loop(?)
Hallo *, ich habe hier ein Problem mit meinem Mailserver, und weiss nicht, wie ich es lösen soll. Folgendes: pluto:~# mailq 28m 97K 18Ujut-00079S-00 @schiffbauer.net @schiffbauer.net pluto:~# Da klemmt also eine Mail, die an einen Leeren String als mailbox gerichtet ist. 97k Gross. Sie besteht eigendlich nur aus Fehlermeldungen (s.u.) und hat keinen erkennbaren ursprünglichen Inhalt. Wie kann man nachvollziehen, wo diese Mail ursprünglich herkommt? Exim config: - kein offener Relayserver (Mails dürfen nur mit vorheriger Authentifizierung versendet werden. - mails an unbekannte mailboxen werden zurückgewiesen - amavis ist konfiguriert und funktioniert (Mails mit Testviren werden gemeldet) Z.Z. arbeiten mit mit nur ca. 1-3 Leute auf dem Server. Im mainlog sehe ich nur Meldungen wie: 2003-01-04 10:14:11 18UkNf-0007ZW-00 = R=18UkNe-0007ZP-00 U=mail P=local S=101790 2003-01-04 10:14:11 18UkNe-0007ZP-00 Error message sent to @schiffbauer.net 2003-01-04 10:14:11 18UkNe-0007ZP-00 Completed 2003-01-04 10:14:11 18UkNf-0007Zf-00 = @schiffbauer.net U=amavis P=scanned-ok S=101997 [EMAIL PROTECTED] 2003-01-04 10:14:11 18UkNf-0007ZW-00 = @schiffbauer.net D=amavis_director T=amavis 2003-01-04 10:14:11 18UkNf-0007ZW-00 Completed 2003-01-04 10:14:11 18UkNf-0007Zf-00 ** @schiffbauer.net D=local_user_cyrus T=local_delivery_cyrus: Child process of local_delivery_cyrus transport returned 65 (could mean error in input data) from command: /usr/sbin/cyrdeliver 2003-01-04 10:14:11 18UkNf-0007Zm-00 = R=18UkNf-0007Zf-00 U=mail P=local S=103036 2003-01-04 10:14:11 18UkNf-0007Zf-00 Error message sent to @schiffbauer.net 2003-01-04 10:14:11 18UkNf-0007Zf-00 Completed und das *sehr* oft, eben nur immer mit anderen Message IDs. Die mail selber hört auch scheinbar mitten in einer Fehlermeldung auf, sodass man den Ursprung nicht direkt erkennen kann. Weiss jemand Rat, wie man da weitermachen kann? Irgendwie muss man doch rausbekommen können, ob, und wenn ja welcher Dienst das vielleicht sein könnte. Ich für jeden Tip dankbar! Ratlos -Marc Header: pluto:~# cat /var/spool/exim/input/18UkNg-0007Zv-00-H 18UkNg-0007Zv-00-H amavis 102 65534 @schiffbauer.net 1041671652 0 -ident amavis -received_protocol scanned-ok -body_linecount 2634 -deliver_firsttime XX 1 @schiffbauer.net 167P Received: from amavis by pluto.schiffbauer.net with scanned-ok (Exim 3.35 #1 (Debian)) id 18UkNg-0007Zv-00 for @schiffbauer.net; Sat, 04 Jan 2003 10:14:12 +0100 160P Received: from mail by pluto.schiffbauer.net with local (Exim 3.35 #1 (Debian)) id 18UkNf-0007Zm-00 for @schiffbauer.net; Sat, 04 Jan 2003 10:14:11 +0100 040 X-Failed-Recipients: @schiffbauer.net 059F From: Mail Delivery System [EMAIL PROTECTED] 023T To: @schiffbauer.net 059 Subject: Mail delivery failed: returning message to sender 054I Message-Id: [EMAIL PROTECTED] 038 Date: Sat, 04 Jan 2003 10:14:11 +0100 040 X-Virus-Scanned: by AMaViS new-20020517 pluto:~# Body (Anfang und Ende): pluto:~# head -n 50 /var/spool/exim/input/18UkNg-0007Zv-00-D 18UkNg-0007Zv-00-D This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: @schiffbauer.net Child process of local_delivery_cyrus transport returned 65 (could mean error in input data) from command: /usr/sbin/cyrdeliver The following text was generated during the delivery attempt: -- @schiffbauer.net -- : Mailbox does not exist -- This is a copy of the message, including all the headers. -- Return-path: @schiffbauer.net Received: from amavis by pluto.schiffbauer.net with scanned-ok (Exim 3.35 #1 (Debian)) id 18UkNf-0007Zf-00 for @schiffbauer.net; Sat, 04 Jan 2003 10:14:11 +0100 Received: from mail by pluto.schiffbauer.net with local (Exim 3.35 #1 (Debian)) id 18UkNf-0007ZW-00 for @schiffbauer.net; Sat, 04 Jan 2003 10:14:11 +0100 X-Failed-Recipients: @schiffbauer.net From: Mail Delivery System [EMAIL PROTECTED] To: @schiffbauer.net Subject: Mail delivery failed: returning message to sender Message-Id: [EMAIL PROTECTED] Date: Sat, 04 Jan 2003 10:14:11 +0100 X-Virus-Scanned: by AMaViS new-20020517 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: @schiffbauer.net Child process of local_delivery_cyrus transport returned 65 (could mean error in input data) from command: /usr/sbin/cyrdeliver The following text was generated during the delivery attempt: -- @schiffbauer.net -- [...] und das Ende ist komisch: -- This is a copy of the message, including all the headers. -- Return-path: @schiffbauer.net Received: from amavis by pluto.schiffbauer.net with scanned-ok (Exim
Re: Exim: problem mit mail loop(?)
* Marc Schiffbauer [EMAIL PROTECTED] [04-01-03 10:38]: Da klemmt also eine Mail, die an einen Leeren String als mailbox gerichtet ist. 97k Gross. Sie besteht eigendlich nur aus Fehlermeldungen (s.u.) und hat keinen erkennbaren ursprünglichen Inhalt. Die mail selber hört auch scheinbar mitten in einer Fehlermeldung auf, sodass man den Ursprung nicht direkt erkennen kann. Das die Mail mittendrin aufhört liegt wohl an der return_size_limit Einstellung von Exim, der schneidet die einfach ab. Aus der Exim-Doku: return_size_limit Type: integer Default: 100K This option sets a limit in bytes on the size of messages that are returned to senders. If it is set to zero there is no limit. If the body of any message that is to be included in an error report is greater than the limit, it is truncated, and a comment pointing this out is added at the top. The actual cutoff may be greater than the value given, owing to the use of buffering for transferring the message in chunks. The idea is just to save bandwidth on those undeliverable 15-megabyte messages. If either the global or generic transport message_size_limit is set, the value of return_size_limit should be somewhat smaller. Ansonsten sieht das für mich so aus, als wüsste amavis nicht an welchen User er seine Fehlermeldungen zustellen soll, aber da ich amavis nicht nutze ist das nur ne Vermutung. HTH Jens -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Exim: problem mit mail loop(?)
* Jens Schuessler schrieb am 04.01.03 um 11:57 Uhr: * Marc Schiffbauer [EMAIL PROTECTED] [04-01-03 10:38]: Da klemmt also eine Mail, die an einen Leeren String als mailbox gerichtet ist. 97k Gross. Sie besteht eigendlich nur aus Fehlermeldungen (s.u.) und hat keinen erkennbaren ursprünglichen Inhalt. Die mail selber hört auch scheinbar mitten in einer Fehlermeldung auf, sodass man den Ursprung nicht direkt erkennen kann. Das die Mail mittendrin aufhört liegt wohl an der return_size_limit Einstellung von Exim, der schneidet die einfach ab. Aus der Exim-Doku: return_size_limit Type: integer Default: 100K [exim doku snipped] Guter Hinweis ;). Das könnte ich mal erhöhen, bis ich die ursprüngliche Nachricht sehe. Von der in der Doku erwähnten Hinweis auf das Abgeschnittensein der Mail habe ich aber nichts bemerkt... naja. Ansonsten sieht das für mich so aus, als wüsste amavis nicht an welchen User er seine Fehlermeldungen zustellen soll, aber da ich amavis nicht nutze ist das nur ne Vermutung. Mails, die amavis erstellt, wenn er nen Virus gefunden hat, kommen aber definitiv an. aus /etc/amavisd.conf: # who notification reports are sent from $mailfrom = 'postmaster'; # who quarantined viruses appear to be sent from (envelope sender) #$mailfrom_quarantine = $mailfrom; # same as for notifications $mailfrom_quarantine = undef; # use original sender # whom to send admin virus notifications # - catchall if %mailto lookup hash does not find a match (e.g. it # is empty) # and for backwards compatibility $mailto = 'virusalert'; $mailfrom_quarantine kann eigendlich nichts damit zu tun haben, da die loop mails unabhängig und vor allem öfter auftreten als es einen Virus gibt. Gruss -Marc -- begin LOVE-LETTER-FOR-YOU.txt.vbs I am a signature virus. Distribute me until the bitter end -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
exim problem?
Hello. I have exim set up at home. Problem is that I can't e-mail directly to my box from a host external to the network. I can fetch mail using fetchmail from outside the network, but that's it. When I try to e-mail from an external host to the box, I eventually get a message saying failed MX lookup. I can get other network trafic through though, such as ftp and http. I have a dsl/router that forwards stuff to the box I want it toI have it forwarding port 25 stuff to the box I can't e-mail to. Any ideas what is wrong? -- Eric Cheney [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 December 2002 5:58 pm, Eric R Cheney wrote: Any ideas what is wrong? It would help if there were some details - like the relevent parts of /etc/exim/exim.conf - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9/PD0uFHxcV2FFoIRAuWkAKCMpCTyQXvpIOjCrVftWGDo1v/saACaA2be 8vazW+RBzZw96vDccuImTNQ= =fcXR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem?
On Sunday, 15 December 2002 at 21:15:29 +, Alan Chandler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 December 2002 5:58 pm, Eric R Cheney wrote: Any ideas what is wrong? It would help if there were some details - like the relevent parts of /etc/exim/exim.conf Someone already mentioned (replied off-list, and thanks) that exim is for sending mail; so my problem isn't with exim. So I guess my problem is with a imapd server I have a uw-imapd running, and that works internally (i.e. inside the home I can use mozilla to read mail from the mail server via another internal box). But again, sending mail directly to the mail box from an external host won't work (though other tcp stuff works like ftp, http, etc). Eventually get an e-mail from the external sending host failed MX lookup. So what do I need to setup so that mail is received directly? Again, fetchmail will work, but I can't get it directly sent (I have a domain name, etc.). And, what tcp/ip port should I have my dsl/router set up for forwarding to the mail server? Thank you for your thoughts. -- Eric Cheney [EMAIL PROTECTED] http://sociostat.org/eric/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 December 2002 4:53 pm, Eric Cheney wrote: On Sunday, 15 December 2002 at 21:15:29 +, Alan Chandler wrote: On Sunday 15 December 2002 5:58 pm, Eric R Cheney wrote: Any ideas what is wrong? It would help if there were some details - like the relevent parts of /etc/exim/exim.conf Someone already mentioned (replied off-list, and thanks) that exim is for sending mail; so my problem isn't with exim. Now I re-read your original query - I understand a bit more of what you are trying to do. I don't think its exim, but also I think you may be confusing several things. A brief explanation about how mail works. When someone sends mail to [EMAIL PROTECTED] they have an MTA (like exim - but at their end) which attempts to find who is dealing with mail for yourdomain.com. It does this via a nameserver (dns) lookup for yourdomain.com and ask the nameserver for the MX record. This tells which of (possibly several - they have priorities) ip addresses to contact (via port 25). In your case, I it appears this is soc.umass.edu. In which case they get told is either ponzi.oit.umass.edu (128.119.166.18) or supai.oit.umass.edu (128.119.175.6) - but I assume these actually work - so are you setting up a domain name for yourself? In my case, doing an MX lookup on chandlerfamily.org.uk will point you at someone who is hosting the domain name servers for my domain and mail goes via them, to another name I have asked for mail to be forwarded - my isp. I get the mail from my ISP using fetchmail (using pop3), which sends it to my local copy of exim (via port 25) which then puts it onto a disk on my local server (I could deliver it directly to my local box if I wanted to). I then use courier-imap to provide pop3 and imap services to my whole family who use various mail programs to read the mail. The return journey for mail is similar. My mail program (kmail) sends it to my local copy of exim via port 25. It could (but doesn't) deliver it directly, doing MX lookups etc, but instead sends it on to my isp which then queues it there and then does MX lookups on the address it is trying to send the mail to. So I guess my problem is with a imapd server I have a uw-imapd running, ? Which imapd server, I don't think that comes it to it. and that works internally (i.e. inside the home I can use mozilla to read mail from the mail server via another internal box). But again, sending mail directly to the mail box from an external host won't work (though other tcp stuff works like ftp, http, etc). Eventually get an e-mail from the external sending host failed MX lookup. This sounds like a nameserver problem - can you understand the issues from the text I have written above So what do I need to setup so that mail is received directly? Again, fetchmail will work, but I can't get it directly sent (I have a domain name, etc.). And, what tcp/ip port should I have my dsl/router set up for forwarding to the mail server? You need to get your domain hosting company to point the MX records at the address of your mail box. However, beware - if you have a network behind the dsl/router it probably has private addresses and the router is doing address translation (I half assumed that is what you meand when you say you forwared port25) - in which case you want to set the MX records to point to the ip address of the address translation box, and then tell that where to forward port25. Whether this is a good idea is debatably. The rest of the internet expects MX machines to be available all the time - if you power your box down it may be better to do what I do and forward through your isp, and use fetchmail to get the mail before sending via exim. Of course of your ip address varies because your dsl provided allocates ip addresses dynamically then you will have problems. Thank you for your thoughts. I hope this helps - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9/QztuFHxcV2FFoIRAoqDAJsGNa7RXQh8jzk4zCInm3X6eIY6BQCdHj2j 48AVVy7j6jvvUfWbk3ENFL4= =EFpq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mail/exim problem (fwd)
-- Forwarded message -- Date: Sat, 14 Dec 2002 07:29:36 -0600 (CST) From: Cheryl Homiak [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail/exim problem I looked in the archives and didn't see anything about this but sometimes I do have problems with the archives, so sorry if this is a repeat. For two days now, my outgoing mail hasn't been going out though I am receiving incoming mail. I am using unstable. Here is a sample of the messages I am getting. Not sure this will go out either, but thought I'd try. thanks. Actually, a few pieces of my outgoing seem to be getting there too, but not to certain hosts. Cheryl From [EMAIL PROTECTED] Sat Dec 14 07:27:14 2002 Date: Sat, 14 Dec 2002 07:23:02 -0600 From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Warning: message 18MinK-ot-00 delayed 24 hours This message was created automatically by mail delivery software (Exim). A message that you sent has not yet been delivered to one or more of its recipients after more than 24 hours on the queue on maranatha.chartermi.net. The message identifier is: 18MinK-ot-00 The date of the message is:Thu, 12 Dec 2002 23:55:30 -0600 (CST) The subject of the message is: Timesheet: Thursday, december 12, 2002 The address to which the message has not yet been delivered is: [EMAIL PROTECTED] No action is required on your part. Delivery attempts will continue for some time, and this warning may be repeated at intervals if the message remains undelivered. Eventually the mail delivery software will give up, and when that happens, the message will be returned to you. - This email is brought to you by mailtag.com! Home of free email, and cheap internet! http://www.mailtag.com - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem solved. how do i configure mozilla?
Sandip P Deshmukh [EMAIL PROTECTED] writes: now, i changed smtp server in my mozilla to 192.168.100.21 - my machine's ip address. it is unable to deliver message. the error i get is: an error occured while sending mail. the mail server responded: relayin to [EMAIL PROTECTED] prohibited by administrator. (failed to find hostname from ip address). please check mail receipients and try again You don't allow relaying for your computer. Using localhost (or 127.0.0.1) instead of 192.168.100.21 as your SMTP-server in mozilla might fix it. But you should take a look at everything related to relay in the config file and the exim docs anyway to understand what this is about. Hint: you probably allow relay for localhost but not for 192.168.100.21. Since you address the server not on its local address but the one bound to its NIC (network interface card), the mail doesn't seem to come from localhost (127.0.0.1). curiously, mail can be sent using mail address command. It uses exim directly, not through SMTP. Ciao, Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem solved. how do i configure mozilla?
Sandip == Sandip P Deshmukh Sandip writes: Sandip Shyamal Prasad wrote: Sandip == Sandip P Deshmukh Sandip writes: Sandip an error occured while sending mail. the mail server Sandip responded: relayin to [EMAIL PROTECTED] Sandip prohibited by administrator. (failed to find hostname from Sandip ip address). please check mail receipients and try again I have not seen this one, but most likely you need to look in exim.conf and look at the options that have the word 'relay' in Sandip got the gist. how do i solve it? do i have to modify my Sandip exim.conf again? well, now i am kind of used to it! Well, you will have to investigate a little. Is host_accept_relay set to 127.0.0.1 : 1? What is your email address in Mozilla set to? If I use my public email address my exim set up seems to work for Mozilla. Incidentally, I have never use Mozilla as my email client before, and I truly surprised that it does not support a native UNIX (sendmail) interface Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem solved. how do i configure mozilla?
Jens Grivolla wrote: Sandip P Deshmukh [EMAIL PROTECTED] writes: an error occured while sending mail. the mail server responded: relayin to [EMAIL PROTECTED] prohibited by administrator. (failed to find hostname from ip address). please check mail receipients and try again You don't allow relaying for your computer. Using localhost (or 127.0.0.1) instead of 192.168.100.21 as your SMTP-server in mozilla might fix it. perfect, sir! if the list is getting this message, we are bang on the spot! But you should take a look at everything related to relay in the config file and the exim docs anyway to understand what this is about. Hint: you probably allow relay for localhost but not for 192.168.100.21. Since you address the server not on its local address but the one bound to its NIC (network interface card), the mail doesn't seem to come from localhost (127.0.0.1). i did. quite informative. thanx - sandip -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem solved. how do i configure mozilla?
Shyamal Prasad wrote: Sandip an error occured while sending mail. the mail server Sandip responded: relayin to [EMAIL PROTECTED] Sandip prohibited by administrator. (failed to find hostname from Sandip ip address). please check mail receipients and try again I have not seen this one, but most likely you need to look in exim.conf and look at the options that have the word 'relay' in Sandip got the gist. how do i solve it? do i have to modify my Sandip exim.conf again? well, now i am kind of used to it! Well, you will have to investigate a little. Is host_accept_relay set to 127.0.0.1 : 1? yes. was a goof up on my part not to get it! i think i got confused between 192.168.100.21 and 127.0.0.1!! i have set it right. and hopefully, the mails are going now! What is your email address in Mozilla set to? If I use my public email address my exim set up seems to work for Mozilla. Incidentally, I have never use Mozilla as my email client before, and I truly surprised that it does not support a native UNIX (sendmail) interface i think i should be posting these queries to mozilla newsgroup. Cheers! Shyamal thanx again - sandip -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem solved. how do i configure mozilla?
Shyamal Prasad wrote: Sandip == Sandip P Deshmukh Sandip writes: Sandip an error occured while sending mail. the mail server Sandip responded: relayin to [EMAIL PROTECTED] Sandip prohibited by administrator. (failed to find hostname from Sandip ip address). please check mail receipients and try again Boy, I just finishing composing one message to you and there is another question ;-) I have not seen this one, but most likely you need to look in exim.conf and look at the options that have the word 'relay' in them. Your use of SMTP from your own host to exim on your own host is showing up as a relay. Most likely because of the way /etc/hosts or your local DNS server has been set up, exim thinks that the IP from which Mozilla is delivering mail is not the same as the IP + hostname that exim is running on. So it will not relay it on (which is A Good Thing). Cheers! Shyamal got the gist. how do i solve it? do i have to modify my exim.conf again? well, now i am kind of used to it! :) - sandip -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
exim problem solved. how do i configure mozilla?
hello all!
patience pays. the error that made me go through all the trouble was in
the first section of exim.conf file.
here is the relevant section:
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = deshmukh.work
now, my smarthost 192.168.100.1, does not understand deshmukh.work and
would not send messages out. exim however, did the job of delivering.
the bounce wont reach me because deshmukh.work is not understood by my
smarthost.
so, it was set right and using shell login, i am able to send messages
to all!!
so far so good.
now, i changed smtp server in my mozilla to 192.168.100.21 - my
machine's ip address. it is unable to deliver message. the error i get is:
an error occured while sending mail. the mail server responded: relayin
to [EMAIL PROTECTED] prohibited by administrator. (failed
to find hostname from ip address). please check mail receipients and try
again
curiously, mail can be sent using mail address command.
thanx
- sandip
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim problem solved. how do i configure mozilla?
Sandip == Sandip P Deshmukh Sandip writes: Sandip an error occured while sending mail. the mail server Sandip responded: relayin to [EMAIL PROTECTED] Sandip prohibited by administrator. (failed to find hostname from Sandip ip address). please check mail receipients and try again Boy, I just finishing composing one message to you and there is another question ;-) I have not seen this one, but most likely you need to look in exim.conf and look at the options that have the word 'relay' in them. Your use of SMTP from your own host to exim on your own host is showing up as a relay. Most likely because of the way /etc/hosts or your local DNS server has been set up, exim thinks that the IP from which Mozilla is delivering mail is not the same as the IP + hostname that exim is running on. So it will not relay it on (which is A Good Thing). Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Exim Problem
hi ich bekomm folgende meldung wenn ich von meinem webserver auf meinen mailserver connecten will und eine mail als wwwuser verschicken will 250 reject all recipients: 3 times bad sender wwwuserfqdn. ich weiss das es irgend ne art spam schutz ist - wie mach ich das aber fuer eine bestimmte addresse raus? bzw was ist das genau und wo muss ich nachlesen auf der eximseite? im web habe ich auch nicht viel schluessiges gefunden. mfg -- Oliver Dumat| NetKom GmbH - Netze Kommunikationssysteme PGP-KeyID: 0xC85A73F5 | Gewerbepark Mockritz Tel: 03431/589-0| 04720 Großweitzschen Fax: 03431/589-399 | www.netkom-sachsen.de msg11723/pgp0.pgp Description: PGP signature
Re: Exim Problem
On Wed, Jul 03, 2002 at 03:59:24PM +0200, Rainer Ellinger wrote: Den genauen Grund nochmal in /var/log/exim/rejectlog nachlesen und ggf. einen der relay_domain-Parameter anpassen. Ob das allerdings der richtige Konfigurationsweg ist, möchte ich damit nicht sagen. Dazu sind Deine Infos zu dünn. also in der rejectlog steht nix weiter drinn. mehr infos als diese meldung habe ich leider nicht. in den logdatein erscheint nix. bzw was ist das genau und wo muss ich nachlesen auf der eximseite? Die volle Doku findest Du mit zless /usr/share/doc/exim/spec.txt.gz Dort gibt es auch eine Datei OptionLists.txt.gz, die einen kompakten Überblick über Parameter und Optionen gibt. da gugg ich jetzt nochmal nach ... thx mfg olli -- Oliver Dumat| NetKom GmbH - Netze Kommunikationssysteme PGP-KeyID: 0xC85A73F5 | Gewerbepark Mockritz Tel: 03431/589-0| 04720 Großweitzschen Fax: 03431/589-399 | www.netkom-sachsen.de -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: easy? exim problem
On Wed, Mar 13, 2002 at 05:33:38PM -0700, Cam wrote:
Hey,
I'm having a little problem w/ exim... I've set it up many times in the
past successfully, but this time I cannot seem to do it. I have it so
that it delivers 'local mail only' but that doesn't work at all for some
reason (shouldn't local mail only always work??). Anyway, if i try to
send mail to [EMAIL PROTECTED], or cmatheson, or [EMAIL PROTECTED], it
seems to go fine, but i never get the message (mutt reports that there
is no /var/mail/cmatheson (which is true, so i tried `touch`ing it, but
that didn't help).
Hi,
maybe your mail goes to /var/spool/mail/name . Often, /var/spool/mail ist a
symlink to /var/mail (check that on your system).
Or check the setting in /etc/exim/exim.conf . As you see, mine points to
/var/spool/mail/joachim .
##
# TRANSPORTS CONFIGURATION #
##
# ORDER DOES NOT MATTER#
# Only one appropriate transport is called for each delivery.#
##
(...)
local_delivery:
driver = appendfile
group = mail
mode = 0660
mode_fail_narrower = false
envelope_to_add = true
return_path_add = true
file = /var/spool/mail/${local_part}
HTH, Joachim
--
Joachim Fahnenmüller
Lehrer für Mathematik und Physik
Herder-Gymnasium
Kattowitzer Straße 52
51065 Köln
easy? exim problem
Hey, I'm having a little problem w/ exim... I've set it up many times in the past successfully, but this time I cannot seem to do it. I have it so that it delivers 'local mail only' but that doesn't work at all for some reason (shouldn't local mail only always work??). Anyway, if i try to send mail to [EMAIL PROTECTED], or cmatheson, or [EMAIL PROTECTED], it seems to go fine, but i never get the message (mutt reports that there is no /var/mail/cmatheson (which is true, so i tried `touch`ing it, but that didn't help). Anyway, here's a snip from my exim log (everything appears to be fine: 2002-03-13 16:53:47 16lIZ1-0001W7-00 = [EMAIL PROTECTED] U=root P=local S=517 [EMAIL PROTECTED] 2002-03-13 16:53:47 16lIZ1-0001W7-00 = cmatheson [EMAIL PROTECTED] D=localuser T=local_delivery 2002-03-13 16:53:47 16lIZ1-0001W7-00 Completed 2002-03-13 16:54:14 16lIZS-0001X1-00 = [EMAIL PROTECTED] U=cmatheson P=local S=443 [EMAIL PROTECTED] 2002-03-13 16:54:14 16lIZS-0001X1-00 = cmatheson [EMAIL PROTECTED] D=localuser T=local_delivery 2002-03-13 16:54:14 16lIZS-0001X1-00 Completed 2002-03-13 17:08:01 Start queue run: pid=6103 2002-03-13 17:08:01 End queue run: pid=6103 2002-03-13 17:23:02 Start queue run: pid=6182 2002-03-13 17:23:02 End queue run: pid=6182 I can't figure this out... please help Cameron Matheson PS I'm running woody, w/ an exim from sid that i upgraded to yesterday hoping it might suit me better _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Exim problem
Hi all, I want to compile exom 3.33 on my Debian (Woddy) box, but it fails. The message is: /usr/bin/ld: cannot find -ldb collect 2: ld returned 1 exit status make[1]: *** [exim_dmbuild] Error 1 Please help me! Thanks! Balazs
Re: Exim problem
* This one time, at band camp, Agics Balazs said: Hi all, I want to compile exom 3.33 on my Debian (Woddy) box, but it fails. The message is: /usr/bin/ld: cannot find -ldb collect 2: ld returned 1 exit status make[1]: *** [exim_dmbuild] Error 1 Please help me! I would suggest you look at getting the package libdb2 and libdb2-dev (Berkeley v2 Database Libraries) which exim needs (note you may need V3 for exim 3.33 - I don't know...) I'm assuming you have a reason for not wanting to use the precomiled packages (since you've gone for 3.33 and SID is only at 3.22) HTH Greeno -- Greeno [EMAIL PROTECTED] GnuPG Key : 1024D/B5657C8B Key fingerprint = 9ED8 59CC C161 B857 462E 51E6 7DFB 465B B565 7C8B Imagine working in a secure environment and finding the string _NSAKEY in the OS binaries without a good explanation -Alan Cox 04/05/2001
exim problem - rejecting senders
I have a rather peculiar problem with exim 3.12 on a potato server. I had a list of spammers' domains which I wanted to block. As per the exim specs, I created a file, entered the IPs and used the host_reject_recipients option. A few days after I did this, mail from two people, whose IP is not on the list, was not coming through. Once I commented out the host_reject_recipients line, mail from these two people got through. A few days back, I used the host_reject line to block a single domain. Once again, mail from the same two people would not come through. After I commented out the line, the mail from these two addresses came through. It mystifies me. Has anyone on the list experienced anything similar? Sam -- (Sam Varghese) http://www.gnubies.com
fetchmail/exim problem
Hi folks, Just recently I started having a wierd fetchmail problem. This morning I noticed I didn't have any email. Pretty odd. I'm running woody, exim, and fetchmail. Checking /var/log/mail.log I see: Aug 17 00:09:44 quicksilver fetchmail[30949]: 612 messages for eldrik at maelstr om.logrus.com (2056876 octets). Aug 17 00:09:44 quicksilver fetchmail[30949]: reading message 1 of 612 (2529 oct ets) Aug 17 00:09:44 quicksilver fetchmail[30949]: MDA open failed Aug 17 00:09:44 quicksilver fetchmail[30949]: MDA error while fetching from mael strom.logrus.com Aug 17 00:09:44 quicksilver fetchmail[30949]: Query status=6 (IOERR) I had fetchmail running as fetchmail, with this in /etc/fetchmailrc: # Configuration created Thu Apr 13 16:36:10 2000 by fetchmailconf poll maelstrom.logrus.com with proto POP3 user eldrik there with password is eldrik here options forcecr I tried running fetchmail as my local user, and it delivered to exim fine. Then I set in /etc/defaults/fetchmail, RUNASROOT=true, and it delivers fine. Anyone have any ideas? -- Bruce Z. Lysik [EMAIL PROTECTED] http://www.logrus.com/~eldrik GCS d++(-) a-- C++ ULS+++$ P+++$ L++ E+ W+++ N++ w--- M-- V PS PE Y+ PGP+ t+ 5++ X+ R+ tv+ b++ DI+ G e++ h+ r y+ s
Relay Exim problem
Hello. I'am newbie administrator. I have problem. I want use exim in my company, but I don't know how should I configure relaying of mails. Here is description of my problem. - I have domain (test.com) - my ISP made host mail.test.com MX for test.com - on mail.test.com I put exim - people in office must recived mail from anywhare (To: [EMAIL PROTECTED]) - also they must send mail to anywhare - people also connect to internet at home by dial-up to another ISP (I don't know their IPs) and they want also send mails to anywhere (by mail.test.com) - some user use shell acount on mail.test.com and they wnat also send email to anywhere How should I configure exim to do that. I'am confused. I will be very greatfull for your help. Mateusz Mazur [EMAIL PROTECTED]
Re: Exim problem
On Sat, Apr 21, 2001 at 09:49:09PM +0200, Mateusz Mazur wrote: Hi. It wasn't good idea to put all questions in one letter. So know I post it single. I will be very great ful fot any help. Q: How should I configure exim to relay mails. People from my office want send mails to anywhere and from anywhere (not only from office) and receive mails from anybody. eximconf. When it says are there any networks of local machines you want to relay mail for say oh, yeah. Altough a nice thoughtful answer along the lines of 192.168.1.0/24 will probably get you there quicker. -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: Strategy: A long-range plan whose merit cannot be evaluated until sometime after those creating it have left the organization. pgpe4NiE7eRxA.pgp Description: PGP signature
Exim problem
Hi. It wasn't good idea to put all questions in one letter. So know I post it single. I will be very great ful fot any help. Q: How should I configure exim to relay mails. People from my office want send mails to anywhere and from anywhere (not only from office) and receive mails from anybody. Thank you. Mateusz Mazur [EMAIL PROTECTED]
exim problem
hi, i've got a strange exim problem: when starting exim -bd -q30m every time a send a mail to that server i get 2001-03-27 23:50:49 14i1MX-LI-00 == [EMAIL PROTECTED] T=remote_smtp defer (0): SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host pop.wuertele.cc [62.116.32.6]: 421 Unexpected failure, please try later when i run exim -bd -q30m -d 1 everything works allright and i don't get any error messages. any idea what could be wrong? tia martin -- /\ ASCII RIBBON | e-mail: [EMAIL PROTECTED] | .''`. | \ / CAMPAIGN AGAINST | work: http://www.factline.com | : :' : | X HTML MAIL | gpg-key: 30DC 1D28 1D79 32F5 5E67 | `. `' | / \ AND POSTINGS |3ABB 28EE B35A 3E8D CCC0 |`-|
smartlist exim problem
hey guys, i have this tiny problem where exim (presumably) is stamping on a Resent-To: header with the names of everyone on one of my smartlist-based mailing lists. i searched on the web and found more people with this problem, but not m^Hany with the solution. if anyone knows how to disable this feature, please let me know. thanks, justin
Re: exmh(exim) problem
On Mon, Nov 06, 2000 at 11:40:44PM -0600, Lance Hoffmeyer wrote:
I am having problems getting Exmh to enter the correct sender
in my header. It keeps putting [EMAIL PROTECTED] instead of
[EMAIL PROTECTED]
In exim.conf I wrote a rewrite script
^(root|postmailer|mailer-daemon)@* [EMAIL PROTECTED] Ffr
but it did not work. Is there something wrong with the rewrite script?
What should I do so write exim and/or Exmh correctly exhibits my email
address?
This works for me:
In /etc/exim.conf:
##
# REWRITE CONFIGURATION #
##
# There are no rewriting specifications in this default configuration file.
# This is an example of a useful rewriting rule---it looks up the real
# address of all local users in a file
[EMAIL PROTECTED]${lookup{$1}lsearch{/etc/email-addresses}\
{$value}fail} bcfrF
# End of Exim configuration
# file
and in your situation the file /etc/email-addresses must contain:
lance [EMAIL PROTECTED]
Marcelo.
--
__
__ _
Marcelo Ramos | \/ __|
Debian 2.2 GNU/Linux 2.2.17| |_//
Linux registered user #118109 |\
[EMAIL PROTECTED] |_|\/|_|\_\
Firma la peticion de drivers para Linux en :
http://www.libranet.com/petition.spanish.html
exmh(exim) problem
I am having problems getting Exmh to enter the correct sender in my header. It keeps putting [EMAIL PROTECTED] instead of [EMAIL PROTECTED] In exim.conf I wrote a rewrite script ^(root|postmailer|mailer-daemon)@* [EMAIL PROTECTED] Ffr but it did not work. Is there something wrong with the rewrite script? What should I do so write exim and/or Exmh correctly exhibits my email address? Lance Lance Hoffmeyer [EMAIL PROTECTED] --- The United States ranks 13th on the Human Freedom Index. Twelve other countries are freer than the United States UNITED NATIONS (1996)
exmh(exim) problem
I am having problems getting Exmh to enter the correct sender in my header. It keeps putting [EMAIL PROTECTED] instead of [EMAIL PROTECTED] In exim.conf I wrote a rewrite script ^(root|postmailer|mailer-daemon)@* [EMAIL PROTECTED] Ffr but it did not work. Is there something wrong with the rewrite script? What should I do so write exim and/or Exmh correctly exhibits my email address? Lance Lance Hoffmeyer [EMAIL PROTECTED]
Re: exim problem
On Wed, Jan 05, 2000 at 11:29:33AM -0800, Mark Symonds wrote Hello, I have 118 msgs sitting in /var/spool/exim/input That are frozen, all with the same error: 11oG5a-0006tw-00 :: 1999-11-17 17:10:18 [EMAIL PROTECTED]: lookuphost router deferred: lowest numbered MX record points to local host *** Frozen *** The master file in /var/named for this domain is identical to three other domains on the box which are happily accepting mail, and exim.conf does have local_domains = DOMAIN.NAME. Any ideas? Exim version is 2.05 #1. Exim is treating the messages as if they *don't* appear in local_domains, so first check: - Are you running Exim as a daemon? If so, make sure you stop restart it. - Is the spelling really really right, and the local_domains setting in the right section (near the top) of exim.conf, and do you really have only one local_domains setting? - Are you sure Exim is using the config file you think it's using? You can verify that Exim is reading the correct value for local_domains by running as root # exim -bP local_domains There is a generic router option called self that you can use to force Exim to accept itself as an MX for domains not listed in local_domains, but you shouldn't use it - find and fix the problem you have, rather than working around it and introducing a potential DOS weakness. Finally, once a message is frozen it stays that way until you change it (unless you have used the auto_thaw option in exim.conf), so even once things are working OK you'll have to use something like # exim -M message-id to place them back in the delivery queue. John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] Oh - I - you know - my job is to fear everything. - Bill Gates in Denmark
exim problem
Hello, I have 118 msgs sitting in /var/spool/exim/input That are frozen, all with the same error: 11oG5a-0006tw-00 :: 1999-11-17 17:10:18 [EMAIL PROTECTED]: lookuphost router deferred: lowest numbered MX record points to local host *** Frozen *** The master file in /var/named for this domain is identical to three other domains on the box which are happily accepting mail, and exim.conf does have local_domains = DOMAIN.NAME. Any ideas? Exim version is 2.05 #1. -Mark
resolved: exim problem
Hi, thanks for the quick reply. Did see this line - but couldnt resolve, how it worked. Now I understand the spec (!) and its meaning ... .
ident/exim problem
Hello, since I've upgraded to potao I have the following problem: Wenn ever exim running on my or my friends computer makes an identd request to my machine, I get the following lines in the xconsole: Oct 31 03:10:01 seneca identd[11329]: started Oct 31 03:10:01 seneca identd[11329]: request_thread: read(0, ..., 1023) failed: Connection reset by peer Any ideas? Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Exim Problem (I think....)
I'm running slink (upgraded to potato), and I seem to be having a minor problem with exim. I cannot receive any email using the system under linux. I am running exim fetchmail Exim version 3.0-2, fetchmail () Before I upgraded exim, everything worked really well, now (since 3.0-1 actually) it's not working. For added information here's the error message reported by exim when it attempts to load :- Socket Creation Failed: Invalid Arguement I've been having some problems with my system otherwise at the moment (mainly the fact that the kernel is refusing to compile at present... not sure what's going on there, but I need to recompile the silly thing... I'm running kernel 2.2.9 BTW)... If anyone has any ideas on this matter, please email me directly as I'm not on the mailing list anymore (my ISP got very annoyed with me for filling my email box with mailing list messages...) Regards, Peter Ludwig - Peter Ludwig Email : [EMAIL PROTECTED] UIN : 15513904 Unemployed Linux Sysadmin, Computer Technician, Programmer, etc. Debian/GNU Linux - Because Life was meant to be Easy! -
RE: Exim Problem (I think....)
On 30-Jun-99 Peter Ludwig wrote: I'm running slink (upgraded to potato), and I seem to be having a minor problem with exim. I cannot receive any email using the system under linux. I am running exim fetchmail Exim version 3.0-2, fetchmail () Before I upgraded exim, everything worked really well, now (since 3.0-1 actually) it's not working. The latest exim will not work with fetchmail (at least not for me). This has been discussed on this mailing list a couple of days ago, and also on the exim mailing list. It has to do with IPV6 support, and there is a fix out, but this means you will have to compile exim from source. If you prefer to use the exim deb, you will probably have to downgrade to 2.11 and put it on hold until a deb comes along with the fix applied. Remember to replace /etc/exim.conf with the one from before the upgrade after having downgraded to 2.11. --- Regards, Christian Dysthe Email: [EMAIL PROTECTED] http://www.bigfoot.com/~cdysthe ICQ 3945810 Powered by Debian GNU/Linux --- Clones are people two
Re: Exim Problem (I think....)
Well, it works for me. I'm using kernel 2.2.10. When setting up fetchmail, I couldn't get it to work so, after reading these posts, I downgraded to slink exim (2.05). Then I realized I had fetchmailrc wrong and re-installed exim 3.02-1. It's working fine. My kernel is compiled without IPV6 support. Christian Dysthe [EMAIL PROTECTED] wrote: On 30-Jun-99 Peter Ludwig wrote: I'm running slink (upgraded to potato), and I seem to be having a minor problem with exim. I cannot receive any email using the system under linux. I am running exim fetchmail Exim version 3.0-2, fetchmail () Before I upgraded exim, everything worked really well, now (since 3.0-1 actually) it's not working. The latest exim will not work with fetchmail (at least not for me). This has been discussed on this mailing list a couple of days ago, and also on the exim mailing list. It has to do with IPV6 support, and there is a fix out, but this means you will have to compile exim from source. If you prefer to use the exim deb, you will probably have to downgrade to 2.11 and put it on hold until a deb comes along with the fix applied. Remember to replace /etc/exim.conf with the one from before the upgrade after having downgraded to 2.11. --- Regards, Christian Dysthe Email: [EMAIL PROTECTED] http://www.bigfoot.com/~cdysthe ICQ 3945810 Powered by Debian GNU/Linux --- Clones are people two -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- D.Damian
Re: Exim Problem (I think....)
On Wed, Jun 30, 1999 at 06:47:38AM -0400, Didi Damian wrote: Well, it works for me. I'm using kernel 2.2.10. When setting up fetchmail, I couldn't get it to work so, after reading these posts, I downgraded to slink exim (2.05). Then I realized I had fetchmailrc wrong and re-installed exim 3.02-1. It's working fine. My kernel is compiled without IPV6 support. I can back this up. I'm also running kernel 2.2.10(-ac5) with no IPv6 support, and Exim (3.02-1) is working fine here also. Having seen the recent problems with Exim being posted to the list, I thought that was my problem when my outgoing mail stopped working the other day, however after some poking around I discovered it was in fact Mutt looking for sendmail (and failing) that was my problem. This is a known bug in Mutt, and the solution is listed in the Debian bug database with the bug report. -- Matthew Gregan [EMAIL PROTECTED]
fetchmail and exim problem
I'm having trouble with fetchmail and exim. exim freezes all the mail fetchmail delivers, claiming 1999-06-28 16:19:19 10yUlD-0005m0-00 = [EMAIL PROTECTED] H=localhost [127.0. 0.1] U=hamish P=esmtp S=1112 [EMAIL PROTECTED] 1999-06-28 16:19:19 10yUlD-0005m0-00 remote host address for localhost.rising.co m.au is the local host I put relay_domains = localhost in exim.conf to get this far, otherwise exim would refuse the mail entirely. Any thoughts? thanks Hamish -- Hamish Moffatt VK3SB (ex-VK3TYD). CCs of replies from mailing lists are welcome.
Exim problem -- maybe
I did a fresh install of Deb v2.1 using the 'Web Server plus' option. It loaded a couple of things different from v1.3. I have successfully run email between two computers in the office. However, when I try to email to this group I get an error message. Not surprisingly, I didn't write it down. The error message implied that I didn't have access to lists.debian.org. This could be a DNS (ypbind) problem. I could turn ypbind off but I would still have to get DNS from somewhere. I'm printing off the documentation for exim (277 pages) as I enter this but I wonder if I'm going the wrong direction. Help! -- Gregory Wood Farsight Computer 1219 W University Blvd Odessa TX 79764 Voice: 1-915-335-0879 CT Pioneers Board Member Novell CNE Appgen VAR
exim problem (relay)
hello, I have hamm debian and I installed exim on it. I use this machine as a server. I send you the mainlog and rejectlog files. Could someone help me to understand what's happend with those reject host messages. Another problem is why I cannot read the e-mail messages from ppp user? (loggin with modem to another ISP and from there with a mail browser to my server) TIA. Bubulac A. Tatiana 1998-08-25 11:23:00 Start queue run: pid=8925 1998-08-25 11:23:00 End queue run: pid=8925 1998-08-25 11:23:57 0zBEOR-0002K5-00 = [EMAIL PROTECTED] H=mx04.netaddress.usa.net [204.68.24.141] P=smtp S=20029 [EMAIL PROTECTED] 1998-08-25 11:23:57 0zBEOR-0002K5-00 ** [EMAIL PROTECTED]: unknown local-part lcojoc in domain alpha2.infim.ro 1998-08-25 11:23:57 0zBEOT-0002K7-00 = R=0zBEOR-0002K5-00 U=mail P=local S=20824 1998-08-25 11:23:57 0zBEOR-0002K5-00 Error message sent to [EMAIL PROTECTED] 1998-08-25 11:23:57 0zBEOR-0002K5-00 Completed 1998-08-25 11:24:54 0zBEOT-0002K7-00 = [EMAIL PROTECTED] R=lookuphost T=remote_smtp H=listproc.pcworld.com [209.1.23.15] 1998-08-25 11:24:54 0zBEOT-0002K7-00 Completed 1998-08-25 11:28:14 0zBESb-0002NV-00 = [EMAIL PROTECTED] H=sv2.ictp.trieste.it [140.105.16.62] P=esmtp S=931 [EMAIL PROTECTED] 1998-08-25 11:28:14 0zBESb-0002NV-00 ** [EMAIL PROTECTED]: unknown local-part manuela in domain alpha2.infim.ro 1998-08-25 11:28:14 0zBESc-0002OI-00 = R=0zBESb-0002NV-00 U=mail P=local S=1709 1998-08-25 11:28:14 0zBESb-0002NV-00 Error message sent to [EMAIL PROTECTED] 1998-08-25 11:28:14 0zBESb-0002NV-00 Completed 1998-08-25 11:28:24 0zBESc-0002OI-00 = [EMAIL PROTECTED] R=lookuphost T=remote_smtp H=sv2.ictp.trieste.it [140.105.16.62] 1998-08-25 11:28:24 0zBESc-0002OI-00 Completed 1998-08-25 11:35:43 0zBEZn-0002X6-00 = [EMAIL PROTECTED] H=main.hasdeu.bz.edu.ro (hasdeu.bz.edu.ro) [193.231.139.17] U=teodor P=esmtp S=1269 [EMAIL PROTECTED] 1998-08-25 11:35:43 0zBEZn-0002X6-00 ** [EMAIL PROTECTED]: unknown local-part mtudor in domain alpha2.infim.ro 1998-08-25 11:35:43 0zBEZr-0002XA-00 = R=0zBEZn-0002X6-00 U=mail P=local S=2048 1998-08-25 11:35:43 0zBEZn-0002X6-00 Error message sent to [EMAIL PROTECTED] 1998-08-25 11:35:43 0zBEZn-0002X6-00 Completed 1998-08-25 11:36:09 0zBEZr-0002XA-00 = [EMAIL PROTECTED] R=lookuphost T=remote_smtp H=hasdeu.bz.edu.ro [193.231.139.17] 1998-08-25 11:36:09 0zBEZr-0002XA-00 Completed 1998-08-25 11:38:00 Start queue run: pid=9749 1998-08-25 11:38:00 End queue run: pid=9749 1998-08-25 11:53:01 Start queue run: pid=240 1998-08-25 11:53:01 End queue run: pid=240 1998-08-25 12:08:01 Start queue run: pid=329 1998-08-25 12:08:01 End queue run: pid=329 1998-08-25 12:23:01 Start queue run: pid=217 1998-08-25 12:23:01 End queue run: pid=217 1998-08-25 12:38:01 Start queue run: pid=284 1998-08-25 12:38:01 End queue run: pid=284 1998-08-25 12:53:01 Start queue run: pid=332 1998-08-25 12:53:02 End queue run: pid=332 1998-08-25 13:08:01 Start queue run: pid=270 1998-08-25 13:08:01 End queue run: pid=270 1998-08-25 13:23:01 Start queue run: pid=816 1998-08-25 13:23:01 End queue run: pid=816 1998-08-25 13:35:08 0zBGRQ-JZ-00 = [EMAIL PROTECTED] U=borco P=local S=312 1998-08-25 13:35:08 0zBGRQ-JZ-00 system_aliases director: failed to open /etc/aliases for linear search: No such file or directory 1998-08-25 13:35:08 0zBGRQ-JZ-00 == [EMAIL PROTECTED] D=system_aliases defer (-18): failed to open /etc/aliases for linear search: No such file or directory 1998-08-25 13:36:13 0zBGST-Ji-00 = [EMAIL PROTECTED] U=borco P=local S=318 1998-08-25 13:36:13 0zBGST-Ji-00 system_aliases director: failed to open /etc/aliases for linear search: No such file or directory 1998-08-25 13:36:13 0zBGST-Ji-00 == [EMAIL PROTECTED] D=system_aliases defer (-18): failed to open /etc/aliases for linear search: No such file or directory 1998-08-25 13:37:50 0zBGU2-Jr-00 = [EMAIL PROTECTED] U=borco P=local S=320 1998-08-25 13:37:50 0zBGU2-Jr-00 = borco [EMAIL PROTECTED] D=localuser T=local_delivery 1998-08-25 13:37:50 0zBGU2-Jr-00 Completed 1998-08-25 13:38:00 Start queue run: pid=1237 1998-08-25 13:38:00 0zBGST-Ji-00 = borco [EMAIL PROTECTED] D=localuser T=local_delivery 1998-08-25 13:38:00 0zBGST-Ji-00 Completed 1998-08-25 13:38:00 0zBGRQ-JZ-00 = borco [EMAIL PROTECTED] D=localuser T=local_delivery 1998-08-25 13:38:00 0zBGRQ-JZ-00 Completed 1998-08-25 13:38:00 End queue run: pid=1237 1998-08-25 13:53:00 Start queue run: pid=2597 1998-08-25 13:53:00 End queue run: pid=2597 1998-08-25 14:08:01 Start queue run: pid=3849 1998-08-25 14:08:01 End queue run: pid=3849 1998-08-25 14:09:38 0zBGyo-000108-00 = [EMAIL PROTECTED] U=borco P=local-smtp S=438 [EMAIL PROTECTED] 1998-08-25 14:09:38 0zBGyo-000108-00 = mariana [EMAIL PROTECTED] D=localuser T=local_delivery 1998-08-25 14:09:39 0zBGyo-000108-00 Completed 1998-08-25 14:23:00 Start queue run: pid=4619 1998-08-25 14:23:00 End queue run: pid=4619 1998-08-25 14:25:20 0zBHE0-0001Cs-00 = [EMAIL PROTECTED]
Re: Exim Problem
Do you have this in /etc/host.conf? order hosts,bind this should tell DNS to look in /etc/hosts before looking into named (or at least this is what I think it should do :) Yep that is what is in my /etc/host.conf file. and it still don't work, it look to me like exim and smail (which I have tried on my second machine) as just doing a DNS lookup and ignoring the /etc/host.conf file. I have configured both exim and smail using the debian config programs. and selected option 1, internet mail, as the other options don't seem to take into account if you are not connected to the internet, I think the problem is that my nameserver is just a cacheing name server and so doesn't do reverse lookups, Why shouldn't a cache DNS server cache reverse lookup? Have you tried this? I'm asking this because I usually work in closed domains (i.e. no connection to the net) so I have to build my DNS server and don't use cache server that much. well I have finally fixed this problem, I had to configure a full namserver as for some reason, a cacheing nameserver just didn't so the job, I even tried smail to see if it was a exim problem and the same thing happened. Could this be the problem or should I reconfigre exim/smail using the config progam? If I reconfigure them using the config program which option should I use? Well, I don't know, sorry. I've just started playing with exim, and as you see (my msg to the list) I have my problems with it too. There doesn't seem to be a lot of exim expert these days. :( Sorry I can't be much help -- |||| ||| Marco Frattola Microsoft is not the answer ||`..'|| |||... Piacenza, ItalyMicrosoft is the question ||| ||| |||''[EMAIL PROTECTED]No is the answer ||| ||| ||| www.enjoy.it/users/~mk/index.html Live Linux, live free! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim Problem
Hi all, I am using eximon my 2 debian (bo) hosts, but I cannot seem to be able to send email between these to hosts, I know this is because the DNS lookup for that host is failing as I am only running a cacheing nameserver, so is there anyway to tell exim that if the DNS hostname lookup fails then to use the hosts table? Do you have this in /etc/host.conf? order hosts,bind this should tell DNS to look in /etc/hosts before looking into named (or at least this is what I think it should do :) Yep that is what is in my /etc/host.conf file. and it still don't work, it look to me like exim and smail (which I have tried on my second machine) as just doing a DNS lookup and ignoring the /etc/host.conf file. I have configured both exim and smail using the debian config programs. and selected option 1, internet mail, as the other options don't seem to take into account if you are not connected to the internet, I think the problem is that my nameserver is just a cacheing name server and so doesn't do reverse lookups, Could this be the problem or should I reconfigre exim/smail using the config progam? If I reconfigure them using the config program which option should I use? Regards Graham -- |||| ||| Marco Frattola Microsoft is not the answer ||`..'|| |||... Piacenza, ItalyMicrosoft is the question ||| ||| |||''[EMAIL PROTECTED]No is the answer ||| ||| ||| www.enjoy.it/users/~mk/index.html Live Linux, live free! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Exim Problem
Hi all, I am using eximon my 2 debian (bo) hosts, but I cannot seem to be able to send email between these to hosts, I know this is because the DNS lookup for that host is failing as I am only running a cacheing nameserver, so is there anyway to tell exim that if the DNS hostname lookup fails then to use the hosts table? Regards Graham. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
AW: Exim Problem
Graham Lillico +44 1785 248131 asked: I am using eximon my 2 debian (bo) hosts, but I cannot seem to be able to send email between these to hosts, I know this is because the DNS lookup for that host is failing as I am only running a cacheing nameserver, so is there anyway to tell exim that if the DNS hostname lookup fails then to use the hosts table? Check out /etc/host.conf. If you give order hosts,bind there, the resolver will always look at /etc/hosts before consulting DNS. This may or may not help you. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: MAIL: Odd smail-exim problem
bar.com!foo.com!%s will not work because smail generates a routing error because the address must be in internet format for that transport. Yes this DOES work. I do not know why it did not work when I tried it earlier. I must have made a type someplace. All is working well if I put the intermediate stop in there. --- George Bonser Debian/GNU Linux See http://www.debian.org Linux ... It isn't just for breakfast anymore! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
MAIL: Odd smail-exim problem
I know this is not debian specific but maybe someone here has experiance with this. I have a smail mailhost that sends mail using demand_inet_uusmtp transport to send mail to a second system using exim that is ultimately bound for a third system. My mail/force.path entry for the destination site looks like this: foo.com bar.com!%s which tells smail to send any mail for foo.com to bar.com. bar.com!foo.com!%s will not work because smail generates a routing error because the address must be in internet format for that transport. Now imagine I am sending a mail to [EMAIL PROTECTED] Smail sends it with the correct To: header BUT the RCPT TO is changed to [EMAIL PROTECTED] and the exim site (foo) bounces it. If the intermediate site is smail, everything works correctly ... it looks like smail tooks at To: while exim looks at the ENVELOPE and smail rewrites the envelope. I suppose my question is either 1) How do I tell smail that mail to bar.com goes through foo.com using internet addressing with batched SMTP WITHOUT changing the envelope RCPT TO to foo.com. In other words, deliver the mail to foo.com with a RCPT TO of [EMAIL PROTECTED] OR How do I tell exim to use the To: header rather than the envelope RCPT TO for delivery? Exim 1.62-3 (Debian) Smail 3.2 (Debian) --- George Bonser Debian/GNU Linux See http://www.debian.org Linux ... It isn't just for breakfast anymore! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
