Re: reportbug - debian SMTP HELO forged

a SMTP... >>> SMTP send failure: {'m...@packages.debian.org': (550, b'HELO mismatch >>> Forged HELO for ([127.0.0.1])')}. That message was issued by the Debian SMTP server. [127.0.0.1] is a typical client HELO. In particular, it is what you get by: printf 'import

Re: reportbug - debian SMTP HELO forged

On 24/05/18 13:33, bw wrote: Thanks, I should have included the config, which was setup with $ reportbug --configure I chose novice and hit the enter key for defaults. I didn't find any documentation to show what has changed. Do you know if debian SMTP is now not supported on reportbug? Thank

Re: reportbug - debian SMTP HELO forged

at /tmp/reportbug-menu-backup-20180523-14318-dcelk7kd Connecting to packages.debian.org via SMTP... SMTP send failure: {'m...@packages.debian.org': (550, b'HELO mismatch Forged HELO for ([127.0.0.1])')}. Do you want to retry (or else save the report and exit)? [Y|n|q|?]? I send

reportbug - debian SMTP HELO forged

backup-20180523-14318-dcelk7kd Connecting to packages.debian.org via SMTP... SMTP send failure: {'m...@packages.debian.org': (550, b'HELO mismatch Forged HELO for ([127.0.0.1])')}. Do you want to retry (or else save the report and exit)? [Y|n|q|?]?

Re: Lenny/exim4: how to set helo for outgoing SMTP

for the firewall. > > correct, but note that that it has to identify with the hostname of your > "reverse" DNS, it took me a while before i understood this concept myself. Yes, that I am aware of and that is what I am trying to accomplish. >>> if both HELO and the PTR r

Re: Lenny/exim4: how to set helo for outgoing SMTP

fficult' one I send to > regularly is AOL. As the other poster already wrote, of course neither the A-record nor the PTR-record nor the HELO value must be in any way related to the MAIL FROM: value, but this is not the problem. > It is alleged that there are some mail admins who require H

Re: Lenny/exim4: how to set helo for outgoing SMTP

Kilian wrote: another option would be to ask your isp to change the PTR record on that IP to the HELO exim uses. I have a firewall with a public IP and a PTR record for that IP. There are several hosts behind the firewall with private IP addresses. i have the same, but i have setup

Re: Lenny/exim4: how to set helo for outgoing SMTP

Kilian wrote: [...] > RFC 822 states: Of course that's RFC 821, sorry for the typo. -- K. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Lenny/exim4: how to set helo for outgoing SMTP

randall wrote: >> Kilian wrote: >> >>> >>> Under etch, I just changed helo_data in /etc/exim4/exim4.conf.template >>> manually - not very nice, but it did what I needed. Now my mailconfig is >>> broken because some hosts won't accept my mails

Re: Lenny/exim4: how to set helo for outgoing SMTP

E_SMTP_HELO_DATA" is already defined (use "==" if you want to redefine it And when I change the second line to REMOTE_SMTP_HELO_DATA=='my.desired.helo.hostname' i get: can't redefine an undefined macro "REMOTE_SMTP_HELO_DATA" Now when I leave out the seco

Re: Lenny/exim4: how to set helo for outgoing SMTP

Joe wrote: Kilian wrote: Under etch, I just changed helo_data in /etc/exim4/exim4.conf.template manually - not very nice, but it did what I needed. Now my mailconfig is broken because some hosts won't accept my mails as the HELO does not match the IP of the firewall, of course. Is

Re: Lenny/exim4: how to set helo for outgoing SMTP

Kilian wrote: Under etch, I just changed helo_data in /etc/exim4/exim4.conf.template manually - not very nice, but it did what I needed. Now my mailconfig is broken because some hosts won't accept my mails as the HELO does not match the IP of the firewall, of course. Is there really no w

Re: Lenny/exim4: how to set helo for outgoing SMTP

Kilian wrote: > Hello, > > I am desperately trying to set the HELO value exim uses for outgoing > smtp connections because my host is behind a firewall which does NAT. > I've read /usr/share/doc/exim4-config/README.Debian.gz and created > /etc/exim4/exim4.conf.localmac

Lenny/exim4: how to set helo for outgoing SMTP

Hello, I am desperately trying to set the HELO value exim uses for outgoing smtp connections because my host is behind a firewall which does NAT. I've read /usr/share/doc/exim4-config/README.Debian.gz and created /etc/exim4/exim4.conf.localmacros witht the following co

Re: exim4 and HELO

On 2004-05-05, Brian Walker penned: Monique Y. Mudama wrote: On 2004-05-04, Brian Walker penned: Greetings, playing around with installing exim4 for mutt 1.5, I am unable to find out how to rectify this problem: exim4 -v [EMAIL PROTECTED] the output includes the error message: SMTP<< EHLO SMTP<< 50

Re: exim HELO=fully qualified host name?

ame aware of the issue and you fixed > it :-). A problem is never solved before the problem is recognized. But most servers won't reject messages due to an invalid HELO argument, so that the user may think that this is correct on his side. If all the servers did the same thing, there

Re: exim HELO=fully qualified host name?

On Tue, Mar 02, 2004 at 04:31:22PM +0100, Vincent Lefevre wrote: | On 2004-03-02 09:02:23 -0500, Derrick 'dman' Hudson wrote: | > RFC 2821, section 4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO) | > | >The argument field contains the fully-qualified domain name of the |

Re: exim HELO=fully qualified host name?

On 2004-03-02 09:02:23 -0500, Derrick 'dman' Hudson wrote: > RFC 2821, section 4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO) > >The argument field contains the fully-qualified domain name of the >SMTP client if one is available. In situations in which the SMTP &

Re: exim HELO=fully qualified host name?

ing only. | > | > You have a nice Catch-22 here. The receiver is not allowed to reject | > bad data, but the sender isn't allowed to send it either! | | This isn't necessarily bad data. RFC 2821, section 4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO) The argument field co

Re: exim HELO=fully qualified host name?

ays match. Same problems with machines on private networks, when NAT is used. > It boils down to what you, as a receiver, find acceptable. I find > requiring the HELO to be syntactically correct and fully-qualified to > be effective at limiting junk (spam and viruses) while not causing >

Re: exim HELO=fully qualified host name?

On Sun, Feb 29, 2004 at 10:16:23PM +0100, Vincent Lefevre wrote: | On 2004-02-23 22:24:28 -0500, Derrick 'dman' Hudson wrote: | > That depends on who's mail server you connect to. Some admins require | > the HELO parameter to be resolvable, and some even require it to | >

Re: exim HELO=fully qualified host name?

On 2004-02-23 22:24:28 -0500, Derrick 'dman' Hudson wrote: > That depends on who's mail server you connect to. Some admins require > the HELO parameter to be resolvable, and some even require it to > resolve to the IP of the machine making the connection. They should

Re: exim HELO=fully qualified host name?

which is resolvable via DNS rather than an /etc/hosts alias | > which is inaccessable to the remote host and can contain (and rightly | > so) a hostname resolving to 127.0.0.1. | | Not necessarily. It depends on the type of communication. For the | HELO command, the FQDN doesn't have to be reso

Re: exim HELO=fully qualified host name?

sable to the remote host and can contain (and rightly > so) a hostname resolving to 127.0.0.1. Not necessarily. It depends on the type of communication. For the HELO command, the FQDN doesn't have to be resolvable (and sometimes it can't, e.g. if you are on a network with private IP ad

Re: exim HELO=fully qualified host name?

On 2004-02-06 10:11:32 -0700, Monique Y. Herman wrote: > I believe that exim will, by default, report the first entry in your > /etc/hosts file. No, it doesn't. This would be a bug if it did that. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: - 100% validated (X)HTML - A

Re: exim HELO=fully qualified host name?

is wrote: > > | > >> I can not subscribe to the pcmcia-cs mailing list on source forge > | > >> because my helo only gives my host name and not my fully qualified > | > >> hostname. How do I resolve this problem? > | > > > | > > You need to se

Re: exim HELO=fully qualified host name?

On 2004-02-06, David Clymer penned: > On Fri, 2004-02-06 at 12:11, Monique Y. Herman wrote: >> On 2004-02-06, David Clymer penned: >> > On Fri, 2004-02-06 at 09:07, davis wrote: >> >> Hello >> >> >> >> I can not subscribe to the pcmcia-cs m

Re: exim HELO=fully qualified host name?

| > >> because my helo only gives my host name and not my fully qualified | > >> hostname. How do I resolve this problem? | > > | > > You need to set exim's primary_hostname to your FQDN (or the | > > equivilant configuration variable for your choice of MTA)

Re: exim HELO=fully qualified host name?

On Fri, 2004-02-06 at 12:11, Monique Y. Herman wrote: > On 2004-02-06, David Clymer penned: > > On Fri, 2004-02-06 at 09:07, davis wrote: > >> Hello > >> > >> I can not subscribe to the pcmcia-cs mailing list on source forge > >> because my helo only

Re: exim HELO=fully qualified host name?

On 2004-02-06, David Clymer penned: > On Fri, 2004-02-06 at 09:07, davis wrote: >> Hello >> >> I can not subscribe to the pcmcia-cs mailing list on source forge >> because my helo only gives my host name and not my fully qualified >> hostname. How do I resolve th

Re: exim HELO=fully qualified host name?

On Fri, 2004-02-06 at 09:07, davis wrote: > Hello > > I can not subscribe to the pcmcia-cs mailing list on source forge because my helo > only gives my host name and not my fully qualified hostname. How do I resolve this > problem? > > JD > You need to set exim&#x

Re: exim HELO=fully qualified host name?

I think I solved this problem on my server (not 100% sure) by updating /etc/hosts like that : 127.0.0.0localhost myserver myserver.mydomain.org Perhaps it helps.. Regards, Frédéric davis wrote: Hello I can not subscribe to the pcmcia-cs mailing list on source forge because my helo

exim HELO=fully qualified host name?

Hello I can not subscribe to the pcmcia-cs mailing list on source forge because my helo only gives my host name and not my fully qualified hostname. How do I resolve this problem? JD http://www.skink.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubs

exim troubles - HELO

recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after HELO toadstool: host mail.sourceforge.net [66.35.250.206]: 550 Don't like your HELO/EHLO. Hostname must contain a dot. So I telnet to port 25 of my machine and

exim troubles - HELO

recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after HELO toadstool: host mail.sourceforge.net [66.35.250.206]: 550 Don't like your HELO/EHLO. Hostname must contain a dot. So I telnet to port 25 of my machin

Re: helo

On Tue, Sep 10, 2002 at 09:15:06AM -0700, nate wrote: | Stefan said: | > I have a problem with my lq100 | > I`m using windows 2000 and i have problems printing [...] | if it does not related to linux you should contact the support group | or company responsible for the device you are using. in thi

Re: helo

On 0, Stefan <[EMAIL PROTECTED]> wrote: > I have a problem with my lq100 I`m using windows 2000 and i have > problems printing the self test printes ok but when I try to print > enything in windows it apears with a space the letters are broken > with a white space between A troll, surely? Tom -

Re: helo

Stefan said: > I have a problem with my lq100 > I`m using windows 2000 and i have problems printing > the self test printes ok but when I try to print enything in windows it > apears with a space the letters are broken with a white space between > please help > Stefan > your post doesn't appear t

helo

I have a problem with my lq100 I`m using windows 2000 and i have problems printing the self test printes ok but when I try to print enything in windows it apears with a space the letters are broken with a white space between please help Stefan  

Re: HELO command in exim

Hi Tony, That solved the problem. Thanks Pedro On Wed, Jul 04, 2001 at 05:54:50PM +0200, Tony Crawford wrote: > Pedro Zorzenon Neto wrote (on 4 Jul 2001, at 9:45): > > > How can I tell exim to send my full domain in the HELO > > instead of my hostname? > > &g

Re: HELO command in exim

Pedro Zorzenon Neto wrote (on 4 Jul 2001, at 9:45): > How can I tell exim to send my full domain in the HELO > instead of my hostname? >From the exim info, under Main Configuration: primary_hostname *option* - Option: primary_hostname Type: string Default: &

HELO command in exim

Please CC copies of replies to me as I'm not a subscriber of this list Hi all, I have some problem with exim. When it contacts foreign hosts to send my mail, it starts with: HELO milho (milho is my hostname) But some servers reject the messages because they check the

Re: smail, HELO hostname without dot

joost witteveen wrote: > > The current debian smail (3.2.0.100-4) daemon does not accept HELO comands > with non-fully qualified hostnames. See the following, "rulvsa" is not OK, > whereas "rulvsa.leidenuniv.nl" is: > > $ telnet rulcmc.leidenuniv.nl 25 &

smail, HELO hostname without dot

The current debian smail (3.2.0.100-4) daemon does not accept HELO comands with non-fully qualified hostnames. See the following, "rulvsa" is not OK, whereas "rulvsa.leidenuniv.nl" is: $ telnet rulcmc.leidenuniv.nl 25 Trying 132.229.1.33... Connected to rulcmc.leidenuniv.nl.